From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Thomas Hellström" <thomas@shipmail.org>,
"Christoph Hellwig" <hch@infradead.org>,
DRI <dri-devel@lists.sourceforge.net>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: DRM drivers with closed source user-space: WAS [Patch 0/3] Resubmit VIA Chrome9 DRM via_chrome9 for upstream
Date: Mon, 20 Jul 2009 16:52:26 +0100 [thread overview]
Message-ID: <20090720155226.GA27885@srcf.ucam.org> (raw)
In-Reply-To: <20090720161620.7b027f8d@lxorguk.ukuu.org.uk>
On Mon, Jul 20, 2009 at 04:16:20PM +0100, Alan Cox wrote:
> > If the common agreement of the linux community is to *NOT* allow these
> > drivers in, so be it, then be honest and go ahead and tell the driver
> > writers. Don't make them respin their development trying to fix minor
> > flaws when their driver won't get in anyway!
>
> The existing policy based on what has been rejected is:
>
> - If you have something which only works with some non-free tightly
> integrated software then we don't accept it
>
> Examples - GMX500, Intel wireless regulatory daemon.
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?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-07-20 15:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 13:38 DRM drivers with closed source user-space: WAS [Patch 0/3] Resubmit VIA Chrome9 DRM via_chrome9 for upstream Thomas Hellström
2009-07-20 13:58 ` Christoph Hellwig
2009-07-20 15:02 ` Thomas Hellström
2009-07-20 15:16 ` Alan Cox
2009-07-20 15:52 ` Matthew Garrett [this message]
2009-07-20 15:57 ` Christoph Hellwig
2009-07-20 16:02 ` Matthew Garrett
2009-07-20 16:37 ` Alan Cox
2009-07-20 23:28 ` Alan Cox
2009-07-20 23:33 ` Matthew Garrett
2009-07-20 19:13 ` Stephane Marchesin
2009-07-20 20:19 ` Thomas Hellström
2009-07-20 20:43 ` Dave Airlie
2009-07-20 21:40 ` Stephane Marchesin
2009-07-20 22:31 ` Dave Airlie
2009-07-20 14:06 ` Peter Zijlstra
2009-07-20 14:52 ` Alan Cox
2009-07-20 15:07 ` Thomas Hellström
2009-07-20 19:51 ` Dave Airlie
2009-07-20 14:09 ` Andrey Panin
2009-07-20 19:03 ` Krzysztof Halasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090720155226.GA27885@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@shipmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.