Via chrome9 driver#
The above hardware list is all the device this driver should support theoretically, but sadly only 3 devices really are supported today. Sure, this driver currently doesn't have a few glittery bits, but ask yourself: what use are they if you are unable to display them in the first place? Will you still care about those a year or two from now? If an X developer, 10 years from now, passes over this driver to adjust it to X-side changes, what will he think about those glittery bits and will they survive? It's easier to fix, easier to expand and it less likely to fail upon future changes. It is also the biggest source of user frustration, this while people never are prepared to spend time on it. Modesetting is the most fundamental functionality and tough to get right. No more register table for this device!Īs a driver developer, my focus is on clean and well-structured code and modesetting.
Via chrome9 full#
It offers full algorithmic modesetting (for supported devices and the CRT), feel free to throw any modeline at it you want.The current unichrome driver already is quite advanced and well underway to become what i need it to be:
![via chrome9 via chrome9](https://i.ytimg.com/vi/3t6bHPbfBw4/maxresdefault.jpg)
This makes the unichrome tough on any self-respecting driver developer. Most unichromes are also capable of sharing two heads amongst 4 different outputs (3 for VT3122). The most recent (still unreleased) unichrome even has some built in devices. It largely depends on external encoders to offer things like TV, TMDS (DVI) and LVDS (panel). This is one advantage the unichrome has over many other devices (intel is now taking the lead though). Thanks to VIA's code releases, however irregular, entangled and buggy, a lot is known about the unichromes, and it is possible to do just about anything you want with them. Despite VIA's failure to properly understand and cooperate with Free and Open Source Software communities, this driver is very important.