From: Johannes Stezenbach <js@linuxtv.org>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org, linux-dvb@linuxtv.org,
Michael Krufky <mkrufky@kernellabs.com>
Subject: Re: [linux-dvb] au0828: experimental support for Syntek Teledongle [05e1:0400]
Date: Thu, 20 Aug 2009 16:32:00 +0200 [thread overview]
Message-ID: <20090820143200.GA29984@linuxtv.org> (raw)
In-Reply-To: <829197380908180707r3aba262fie192090c653c42be@mail.gmail.com>
On Tue, Aug 18, 2009 at 10:07:04AM -0400, Devin Heitmueller wrote:
> The risk of
> trusting some random Linux developer's driver work is a reason why
> some vendors don't want to support Linux. If I were a vendor, and I
> endorsed a Linux driver written by someone without the appropriate
> knowledge of the hardware, I could end up with large number of product
> returns, and I would incur the cost of those losses.
This is an interesting statement. Let me rephrase it:
If I were a vendor selling ill-designed hardware which can
be permanently damaged by buggy software, I'd make sure
as hell that I get the information about how to avoid the
damage out to every Open Source developer. Otherwise
I would have to live with the risk of seeing an increased
rate of product returns.
BTW, there is a big difference of "after I plugged the device
in under Linux it was dead" and "it runs hot under Linux, that might
shorten the life span". I hope there is no hardware of the first
kind. For the second kind you can fairly safely experiment until
you solved the problem.
Thanks,
Johannes
prev parent reply other threads:[~2009-08-20 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 20:25 [linux-dvb] au0828: experimental support for Syntek Teledongle [05e1:0400] Malcolm Lewis
2009-08-17 20:59 ` Michael Krufky
2009-08-17 21:20 ` Malcolm Lewis
2009-08-18 11:00 ` Johannes Stezenbach
2009-08-18 14:07 ` Devin Heitmueller
2009-08-20 2:38 ` hermann pitton
2009-08-20 14:32 ` Johannes Stezenbach [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=20090820143200.GA29984@linuxtv.org \
--to=js@linuxtv.org \
--cc=dheitmueller@kernellabs.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@kernellabs.com \
/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