On Llu, 2004-04-19 at 21:21, Jon Smirl wrote: > Do you really want to teach FB about setting modes on multiple heads?
Yes and I know it needs to know about memory management too. Lots of cards need memory management anyway either for textures or even AGP drawn frame buffers. A lot of the computation of modes can be user space as BenH suggested. > The DRM version I posted I used a different scheme. It provided a minimal I2C > driver for making the DDC data visible to user space via the standard I2C sysfs DDC is required for 2D mode handling > memory manager is used to allocate the buffer space. Thats frame buffer + user space stuff not frame buffer + DRM stuff though. > This is over 100K of code I have in user space that would be transfered into > kernel space in the FB model. The code is rarely used and it would be in > non-swapable memory. It would be running in ring 0. My user space library code > can run at user level priv and it's swappable. I agree entirely it wants to be in user space save for some kind of initial mode, and for the mode data needed to implement SACK recovery (which may be doable via hotplug entirely). ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
