On Llu, 2004-04-19 at 17:00, Jon Smirl wrote: > These PCI changes duplicate things that are in framebuffer. Shouldn't we be > having a giant argument about them? I would think that is worse that DRM is is > duplicating something in FB. The two IOCTLs I needed for reset don't exist in > either FB or DRM. Anyway I think these changes need to go in. The existing code > is broken in respect to PCI hotplug.
If they are needed then probably the basic video restore for fb modes belongs in the FB driver, and the 3D engine restore in the dri driver. That way users get the pieces they need. In time once we have a consistent video layer it will tidy up. For the 2D side I don't think its an ioctl problem as it is driven by the power management hooks. For 3D I can see it being relevant since you may want to reset the 3D engine from user space when the X server decides we have a failure, either by doing the work in the ioctl or by faking a hot unplug, dropping the card to D3 (off), waiting, turning it back to D0, and faking a hot insert which would run the normal setup and go code [disclaimer: there is a patent pending on the use of D0/D3 and faking hot unplug/replug but we have rights for GPL use of it in Linux or any other GPL code] Alan ------------------------------------------------------- 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
