linux-kernel - Re: [GIT PATCH] more Driver core patches for 2.6.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0612131306460.5718@woody.osdl.org>
Date:	Wed, 13 Dec 2006 13:08:03 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	Greg KH <gregkh@...e.de>
cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de
Subject: Re: [GIT PATCH] more Driver core patches for 2.6.19



On Wed, 13 Dec 2006, Linus Torvalds wrote:
> 
> Btw: there's one driver we _know_ we want to support in user space, and 
> that's the X kind of direct-rendering thing. So if you can show that this 
> driver infrastructure actually makes sense as a replacement for the DRI 
> layer, then _that_ would be a hell of a convincing argument.

Btw, the other side of this argument is that if a user-space driver 
infrastructure can _not_ help the DRI kind of situation, then it's largely 
by definition not interesting. Merging something like that would just mean 
that we end up with multiple _different_ user-space helper infrastructure 
shells, which sounds distinctly unpalatable.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/