On 6/17/05, Alan Hourihane <[EMAIL PROTECTED]> wrote:
> > > The current situation is that when fbdev is loaded the DRM falls back
> > > to using the sysdev approach. If fbdev isn't loaded it takes direct
> > > control as the DRM becomes a real PCI driver and accesses the PCI 
> > > functions
> > > for suspend/resume directly.
> >
> > The code for DRM conditionally taking direct control of the device is
> > only in DRM CVS. It was rejected as a kernel submission.
> 
> I realize that Jon, I'm trying to understand the issues with sysdev regardless
> of the current situation with the kernel.

I was going to delete the code that looks for fbdev and conditionally
takes control since it had been rejected. Should I leave it in?

-- 
Jon Smirl
[EMAIL PROTECTED]


-------------------------------------------------------
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_idt77&alloc_id492&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to