|
From: Michel <mi...@da...> - 2003-01-16 20:14:19
|
On Don, 2003-01-16 at 04:52, Jon Smirl wrote: > > 1) We have two drivers for the same hardware. They > should be sharing the same include files describing > the hardware. Might be a good idea. > 2) Bug fixing, in some cases the same hardware bug > would need to be fixed in two places. Not sure about this, as I don't see much overlap, but it's plausible I guess. > 3) State saving. When the virtual terminal is changed > is the complete state of the DRM driver saved? What if > one of the other virtual terminals plays with 3D mode? A 3D driver (at least an OpenGL driver) needs to always keep track of hardware state anyway, so after a VT switch it can just upload everything it needs again. > 4) DDC and secondary reset support. I was looking at > adding this to some of the framebuffer drivers. The X > driver can't share this code. The framebuffer device could offer interfaces for these though? > 5) General kernel config. The same peice of hardware > appears in two different places. For very different purposes. Anyway, couldn't the config hierarchy be changed without moving code around, at least with Kconfig? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |