mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Thomas Hellstr?m <thomas@shipmail.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 17:02:15 +0100	[thread overview]
Message-ID: <20090720160215.GB27885@srcf.ucam.org> (raw)
In-Reply-To: <20090720155745.GB12536@infradead.org>

On Mon, Jul 20, 2009 at 11:57:45AM -0400, Christoph Hellwig wrote:

> Greg still claims that qcserial could be used by rebooting from Windows,
> right?

I think any argument that involves us requiring open userspace but 
allows us to get away with using Windows as a firmware loader is a 
dubious one :) But yes, it's certainly borderline. I'm not going to 
argue that it's clearly wrong, and I'm also aware that putting explicit 
limits on any of this is potentially an invitation for people to try to 
get as close to the line as they can.

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

I'd lean in the same direction.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-07-20 16:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 13:38 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
2009-07-20 15:57         ` Christoph Hellwig
2009-07-20 16:02           ` Matthew Garrett [this message]
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=20090720160215.GB27885@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome