On Thu, 2008-02-14 at 08:20 +0000, Dave Airlie wrote: > If you can clarify exactly what you mean by DRI clients (i.e. mesa itself > or GL apps on top of Mesa), old X server (i.e. what we have now.. or > modesetting or TTM etc..), we might be able to find a point of usefulness, > like we can run old X servers on cards that don't support this stuff hence > the legacy node will always be there..
Sure, the legacy node seems necessary to avoid flag day for the system. Just wanting to make sure we noted that you wouldn't be able to cleanly switch between a legacy X server and a new X server, without shutting one down before starting the other. Given the user-mode modesetting in the legacy X server, it does seem like a lot of work to get back to text mode and clear the card memory before switching. > fbdev will probably look like it does now in the modesetting tree mainly, > hopefully someone does a userspace console at some point... but fbdev > would have a BO for its front buffer and one per set of outputs would > exist, so the control node splitting out crtcs and outputs would give you > an fbdev per crtc.. otherwise cloned fbdev.. So it's all controlled from user mode. Are we going to deprecate fbdev, or do we expect system startup and the kernel graphics-mode console to sit atop it still? -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
