From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Luc Verhaegen <libv@skynet.be>
Cc: Dave Airlie <airlied@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Closed source userspace graphics drivers with an open source kernel component
Date: Fri, 2 Jul 2010 18:01:44 +0400 [thread overview]
Message-ID: <20100702140144.GA27618@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20100702111029.GB6802@skynet.be>
On Fri, Jul 02, 2010 at 01:10:29PM +0200, Luc Verhaegen wrote:
[...]
> > They'll keep shipping closed stuff, just like they are now. Are you
> > going to reverse engineer the userspace drivers, so people who care
> > about open and free software platforms can use these drivers? (or have
> > you already signed NDAs saying you can't). Why should we maintain a
> > bunch of kernel code, when they are hiding away all the really useful
> > stuff that people could improve.
>
> Maintaining this exact code is not _your_ job, [...]
Correct, it's not solely his job, but it's also every kernel
developers' job.
When I change kernel API I have to grep through all the kernel
drivers, sometimes understand how they work, and then make the
change to the whole kernel source tree.
And I would not want to maintain this code, as these drivers
are wasting my time without returning anything back.
It was said many times. Actually, so many times that it started
to become boring to repeat, and the Kernel Driver Statement was
written:
"We, the undersigned Linux kernel developers, consider any
closed-source Linux kernel module or driver to be harmful and
undesirable."
http://www.linuxfoundation.org/collaborate/publications/kernel-driver-statement
While the doc mostly says "kernel code", I truly believe that
there's actually no huge difference between "closed-source
kernel module" and "open source dummy kernel module + userspace
blob".
Both are closed source solutions, and generally useless for the
open source. And, what is worse, the last one is harmful for me
personally.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2010-07-02 14:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 22:10 Closed source userspace graphics drivers with an open source kernel component Dave Airlie
2010-07-01 22:36 ` Dave Airlie
2010-07-01 22:51 ` Daniel Walker
2010-07-01 22:57 ` Dave Airlie
2010-07-01 23:29 ` Daniel Walker
2010-07-01 23:37 ` Dave Airlie
2010-07-02 0:08 ` Daniel Walker
2010-07-02 0:13 ` Dave Airlie
2010-07-02 0:18 ` Saravana Kannan
[not found] ` <AANLkTilsqmCZwLUNJhvDKkralHQZzlRV3ZxaIGbt9-xB@mail.gmail.com>
[not found] ` <AANLkTinvzJrx4AqgWYuMg66Djf-snouLQZE7wI9Bu0Kv@mail.gmail.com>
2010-07-02 0:42 ` Timothy Meade
2010-07-02 2:46 ` Dave Airlie
2010-07-02 3:01 ` Piotr Gluszenia Slawinski
2010-07-02 4:54 ` Howard Chu
2010-07-02 6:52 ` Piotr Gluszenia Slawinski
2010-07-14 13:24 ` Pavel Machek
2010-07-16 0:42 ` Tim HRM
2010-07-01 23:51 ` Piotr Gluszenia Slawinski
2010-07-02 1:27 ` Corbin Simpson
2010-07-02 7:48 ` Christoph Hellwig
2010-07-02 9:58 ` Luc Verhaegen
2010-07-02 10:15 ` Christoph Hellwig
2010-07-02 11:12 ` Luc Verhaegen
2010-07-02 11:26 ` Dave Airlie
2010-07-02 10:23 ` Dave Airlie
2010-07-02 11:10 ` Luc Verhaegen
2010-07-02 11:53 ` Dave Airlie
2010-07-02 12:07 ` "C. Bergström"
2010-07-02 14:45 ` Xavier Bestel
2010-07-02 15:03 ` "C. Bergström"
[not found] ` <AANLkTinZXHi_mbmsX1HTzbMNjQx7j0rbEfTKSoz-02CF@mail.gmail.com>
2010-07-04 7:27 ` Dave Airlie
2010-07-04 11:03 ` Theodore Tso
2010-07-04 15:37 ` Matthew Garrett
2010-07-04 20:05 ` Dave Airlie
2010-07-02 14:01 ` Anton Vorontsov [this message]
2010-07-03 0:41 ` Ian Romanick
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=20100702140144.GA27618@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=libv@skynet.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox