> Also, these is no rule saying a device driver can't have several tables of _init > register values that can be used to set the mode on a primary monitor at boot. I > would just like to see all of the code that does DDC decoding and modeline > computations moved to user space. When you add up that code there is about 40K > of it in the fbdriver and about 50K in the radeon driver. When the fbdev drivers > start probing for multiple heads, TV support, etc that code is going to get even > larger. Since the code is used only rarely (in kernel terms) this code should be > in user space instead of the driver. > > I've also proposed that if you really, really want to you could do the DDC > probing the in driver at boot and mark all of the code _init. Then the user > space code would take over after that. Note that I'm talking about early > userspace (initrd) timeframe, not normal user space.
DDC probing is still new. I doubt it will be that large in the long run. I bet we will see redudency in the drivers that we seperate out. Give me time and I can show that it will be minimum code. ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
