All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas@shipmail.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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:48 +0200	[thread overview]
Message-ID: <4A648718.9000709@shipmail.org> (raw)
In-Reply-To: <20090720135844.GA16844@infradead.org>

Christoph Hellwig wrote:
>
>
> I think you're just trying to push your agenda.  
>
> I think you're just trying to defend your business writing closed source
> drivers.  Drivers that aren't usable without binary blobs don't have
> a business in the kernel tree, and your whining doesn't help it.  You'd
> be better off spending your time getting proper open drivers done than
> defending doing the work to support closed binaries.
>   

You obviously got all this completely wrong.

I avoid writing closed source drivers whenever I can, I'm not whining 
and I'm not trying to push any of them. The code VIA is trying to submit 
has not been written by me nor anybody I know. All VIA code I and the 
companies I've worked for has written is open-sourced and contributed to 
the Openchrome / mesa / drm project.

The point I'm trying to make is the following:

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!

/Thomas








  reply	other threads:[~2009-07-20 15:03 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 [this message]
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
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=4A648718.9000709@shipmail.org \
    --to=thomas@shipmail.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.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.