From: Krzysztof Halasa <khc@pm.waw.pl>
To: Thomas Hellstr?m <thomas@shipmail.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 21:03:58 +0200 [thread overview]
Message-ID: <m33a8ruqg1.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20090720140956.GB11781@centrinvest.ru> (Andrey Panin's message of "Mon\, 20 Jul 2009 18\:09\:56 +0400")
"Andrey Panin" <pazke@centrinvest.ru> writes:
> * Users are still on mercy of binary blob supplier. Will this blob run on arm ?
> Or powerpc ? Or even x86_64 ? Will it be compatible with XOrg X.Y ?
> Nobody knows that and there is no gain for users too.
Actually there is a loss - users see the kernel (or partial) driver and
think it's open source solution. Been there, it wasn't nice at start
and even less nice when the thing chose not to work as advertised.
This was (is?) also the case with NVidia graphics drivers, I know many
people who purchased their cards thinking they are fully open-source
(because their drivers had to be "compiled").
--
Krzysztof Halasa
prev parent reply other threads:[~2009-07-20 19:04 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
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 [this message]
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=m33a8ruqg1.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=dri-devel@lists.sourceforge.net \
--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