From: Johannes Stezenbach <js@linuxtv.org>
To: Michael Krufky <mkrufky@kernellabs.com>
Cc: linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] au0828: experimental support for Syntek Teledongle [05e1:0400]
Date: Tue, 18 Aug 2009 13:00:41 +0200 [thread overview]
Message-ID: <20090818110041.GA14710@linuxtv.org> (raw)
In-Reply-To: <37219a840908171359m152363a2ub377abe6e27ff237@mail.gmail.com>
On Mon, Aug 17, 2009 at 04:59:42PM -0400, Michael Krufky wrote:
>
> variations, nobody has ever verified that the GPIO programming is safe
> to use, and there is no way to prevent the potentially harmful code
> from running on the wrong device.
>
> I, personally, do not want the responsibility of explaining to users
> that their usb sticks may be damaged because of code that got merged
I would be interested to know if someone _actually_ managed
to break their hardware by using buggy drivers. IANAL but
I think that consumer electronics hardware which can be damaged by
software is broken by design. A vendor selling such hardware is
stupid because people would return the broken hardware and get
a replacement. I don't see how a vendor could proof that the device
was not damaged by an obscure bug in the Windows driver to get
around their responsibility to replace broken hardware within
the warranty period.
Johannes
next prev parent reply other threads:[~2009-08-18 11:00 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 [this message]
2009-08-18 14:07 ` Devin Heitmueller
2009-08-20 2:38 ` hermann pitton
2009-08-20 14:32 ` Johannes Stezenbach
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=20090818110041.GA14710@linuxtv.org \
--to=js@linuxtv.org \
--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