linux-kernel - Re: DRM drivers with closed source user-space: WAS [Patch 0/3] Resubmit VIA Chrome9 DRM via

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: <20090720155745.GB12536@infradead.org>
Date:	Mon, 20 Jul 2009 11:57:45 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Thomas Hellstr?m <thomas@...pmail.org>,
	Christoph Hellwig <hch@...radead.org>,
	DRI <dri-devel@...ts.sourceforge.net>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: DRM drivers with closed source user-space: WAS  [Patch 0/3]
	Resubmit VIA Chrome9 DRM via_chrome9 for upstream

On Mon, Jul 20, 2009 at 04:52:26PM +0100, Matthew Garrett wrote:
> I think "tightly integrated" could do with some clarification here. 
> qcserial was accepted despite not being functional without a closed 
> userspace component - an open one's since been rewritten to allow it to 
> work. Do we define "tightly integrated" as "likely to cross the GPL 
> line" (potentially the case with Poulsbo, not the case with qcserial), 
> or is it a pragmatic issue? What about specialised hardware drivers that 
> only have closed applications?

Greg still claims that qcserial could be used by rebooting from Windows,
right?  In that it would still be extremly borderline to me, but it's
settled now.  We also have various SCSI HBA drivers that can be used
just fine, but contain tons ot ioctls for management tools that aren't
available as open source (or even easily obtainable at all).  Personally
I don't think we should merge those unless we have userspace code
available freely, but it's a less urgent issue than merging drivers that
can't be used at all.  The DRM modules fall to me exactly into that
category for "specialised hardware drivers that only have closed
applications", and the answer to those should be a clear no.

--
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/