> > Three tiers is fine with me and I've never been against it. But we've > only been talking about this for two years now and no one has stepped > up to fix 67 fbdev drivers - I'm sure not going to it. I don't want to > wait another two years to build Xegl so I'm trying to come up with > some way around the problems.
You don't need to fix the 67 drivers, I dropped Alan Cox's idea of vga_class on its arse after I did a full investigation on it (I did a fair bit of work on it before I dismissed it...) I have on my PC somewhere attempt 2 (but I think I lost if in all my bitkeeper vs git trees), that uses a video_lowlayer.c module that doesn't bind to anything, but a lowlevel radeon driver links against it, and registers its handlers for everything (kinda like the DRM does now), then fbdev and DRM sit on top of it/lowlevel radeon, it looked like a good idea, but it still needs a bit more investigation.. we haven't been sitting on our hands on this, I just happen to have 0 time and benh is working on things which although aren't as "cool" are needed just as much (the VGA arbiter).. I'm also trying to prove architecture with respect to Intel chipsets if I can so at least it might have a hope of moving beyond radeon... (but a memory manager becomes more of an issue with Intel chipsets which share RAM via AGP...) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
