All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Nisota <alannisota@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Patrick Boettcher <patrick.boettcher@desy.de>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] Remove support for Genpix-CW3K (damages hardware)
Date: Sun, 05 Apr 2009 08:19:55 -0700	[thread overview]
Message-ID: <49D8CC1B.5070104@gmail.com> (raw)
In-Reply-To: <20090405115539.61d7b600@pedra.chehab.org>

Mauro Carvalho Chehab wrote:
> We shouldn't drop support for a device just because the manufacturer doesn't
> want it to be supported. If it really damages the hardware or violates the
> warranty, then we can print a warning message clearly stating that the vendor
> refuses to collaborate, briefly explaining the issues and recommending the user
> to replace the device to some other from a vendor-friendly at dmesg, but keep
> allowing they to use it, with some force option for people that wants to take
> the risk.
>   
I'm not going to go through the entire soap-opera as I know it, but 
basically the manufacturer has 2 tiers of devices, those that were 
designed to work only with a specific piece of hardware, and those that 
are supported in Windows and Linux, but come with a significant price 
premium.  The latter devices are supported by the kernel and should be 
continued to be.  The former is what we're talking about and what my 
patch removes support for.  The patch was in response to real users with 
real problems.

I am in no way associated with the manufacturer other than that he 
provided me with initial help writing the Linux drivers several years 
ago.  I no longer have a use for the drivers myself, and any support I 
do is just to help the community out.  I have provided a patch which 
makes the driver safe to use.  If you prefer an alternate method of 
achieving the same goal, or wish to just ignore it altogether, that is 
ok, but I don't have the time to develop and test a patch that is more 
complicated then what I've already posted.  If you are going to take any 
action, I would prefer it get pushed into the current kernel development 
tree to minimize the potential harm to users.



  reply	other threads:[~2009-04-05 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 15:15 [PATCH] Remove support for Genpix-CW3K (damages hardware) Alan Nisota
2009-04-01  7:35 ` Patrick Boettcher
2009-04-01 20:01   ` Alan Nisota
2009-04-05 14:55     ` Mauro Carvalho Chehab
2009-04-05 15:19       ` Alan Nisota [this message]
2009-05-20  8:52 ` Patrick Boettcher

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=49D8CC1B.5070104@gmail.com \
    --to=alannisota@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=patrick.boettcher@desy.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.