> > I can also predict the probable outcome on kernel submission if we use > the stub to start building suspend/resume in two different places - > DRM and fbdev.
My stub isn't your totally fb in the stub, we are only going to put initially interrupt handling, suspend/resume, PCI driver handling and some arbitration into the stub... this is similiar to what was going into the vga class stuff before, myself and benh have been talking this over and believe there is no point having mode setting or monitor detection in a lowlevel stub, You cannot do intelfb modesetting in the kernel, it needs VBE calls no-one is going to put those near the kernel hopefully... I'm trying to decide if the stub framework is worth the hassle of making generic or whether doing it for each driver is probably less trouble... 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
