Hi guys, Keith Packard escreveu: > On Wed, 2008-02-13 at 19:22 -0500, Alex Deucher wrote: > >> How about a "compat" node for old clients and a "new" render node that >> handles both new clients and GPGPU? Then the backwards compat stuff >> could just be a shim layer and everything else could use the same code >> instead of dealing with separate render and gpgpu nodes. > > Recall that one of the goals is to support multiple user sessions > running at the same time, so we really do want to have per-session > 'devices' which relate the collection of applications running within > that session and reflect the access permissions of the various objects > and methods within that session. >
I'm not sure what the scope of the work you're proposing here, but in a not so long future I'll need to glue this with the VGA arbitration code [0]. We need to design something about the case where the cards generate an interrupt when the arbiter has disable MEM decoding, for instance. Someone already mentioned about implement a driver callback for disabling IRQ emission on a given card when it's being disabled by the arbiter. But I don't know for sure yet. Do you have an idea where I'll need to hook this all? Thanks, [0] http://www.x.org/wiki/VgaArbiter Anyway, this things aren't *so* updated. I have more code here synced with the master branch of X server but currently I'm fighting with some pciaccess drivers which refuse to initialize a secondary card. Sigh. -- Tiago Vignatti C3SL - Centro de Computação Científica e Software Livre www.c3sl.ufpr.br ------------------------------------------------------------------------- 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
