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: <4A648718.9000709@shipmail.org>
Date:	Mon, 20 Jul 2009 17:02:48 +0200
From:	Thomas Hellström <thomas@...pmail.org>
To:	Christoph Hellwig <hch@...radead.org>
CC:	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

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

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