On Tue, Jan 6, 2009 at 7:10 AM, Kristian Høgsberg k...@redhat.com wrote:
The kernel shouldn't be in the business of telling user space which
driver to load. The kernel defers mapping PCI IDs to module names
to user space and we should do the same for DRI drivers.
And in fact, that's how it
On Thu, 2009-01-29 at 23:58 +0100, Thomas Hellström wrote:
Hmm,
Wasn't this at some point intended for server-free operation?
I think that was John Smirls intention when he added it but it's the
wrong approach.
Anyway, dri_library_name is misleading since there are other dri clients
than
Hey; comments on this? Can we put it in one of the git tree so it
doesn't fall through the cracks? It's pretty harmless and could be
merged for the 2.6.29 kernel, or we could push it the the next merge
window if it's not suitable for the rc phase. Either way, we need to
squash this.
cheers,
Hmm,
Wasn't this at some point intended for server-free operation?
Anyway, dri_library_name is misleading since there are other dri clients
than OpenGL...
/Thomas
Kristian Høgsberg wrote:
Hey; comments on this? Can we put it in one of the git tree so it
doesn't fall through the cracks?
On Thu, 2009-01-29 at 16:32 -0500, Kristian Høgsberg wrote:
Hey; comments on this? Can we put it in one of the git tree so it
doesn't fall through the cracks? It's pretty harmless and could be
merged for the 2.6.29 kernel, or we could push it the the next merge
window if it's not suitable
On Mon, 2009-01-05 at 16:10 -0500, Kristian Høgsberg wrote:
The kernel shouldn't be in the business of telling user space which
driver to load. The kernel defers mapping PCI IDs to module names
to user space and we should do the same for DRI drivers.
And in fact, that's how it does work
The kernel shouldn't be in the business of telling user space which
driver to load. The kernel defers mapping PCI IDs to module names
to user space and we should do the same for DRI drivers.
And in fact, that's how it does work today. Nothing uses the
dri_library_name attribute, and the
