I have experimented with creating the driver list dynamically from the installed drivers, and it works so far. But I think this approach also has some problems: - there are drivers that are not documented in the information.py (amd, atimisc, dummy, psb, v4l, and ztv). Of these, maybe the dummy driver shouldn't be listed here at all, and the others should probably be added to information.py. All in all this means that this external information file still has to be kept synced to the list of installable drivers. - the vendor/model list still contains some "bugs" (independent of the driver list). For example, selecting "Other -> Openchrome" doesn't change the selected driver, probably because the associated driver name (openchrome?) is not contained in the list. It wasn't contained in Guidance's hardcoded list either. And to make it available I probably would have to install the xserver-xorg-video-openchrome package... So why list this card model if the driver is not installed anyway?
I start to like the approach of shipping information files with the xserver-xorg-video-* packages... That could solve at least the two problems I've listed above, and might also make some other features possible. For example, the -via and the -openchrome and the -unichrome packages all seem to support the same devices, so they could all announce that, and displayconfig could list the three drivers in the "Available drivers" list (where it currently only offers open and proprietary drivers). Such a change would require some discussion with the Guidance devs, I guess. -- driver list doesn't contain "via" driver https://bugs.launchpad.net/bugs/149793 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
