All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Nisota <alannisota@gmail.com>
To: Patrick Boettcher <patrick.boettcher@desy.de>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] Remove support for Genpix-CW3K (damages hardware)
Date: Wed, 01 Apr 2009 13:01:25 -0700	[thread overview]
Message-ID: <49D3C815.6000004@gmail.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0904010934590.21921@pub4.ifh.de>

Patrick Boettcher wrote:
> Hi Alan,
>
> Don't you think it is enough to put a Kconfig option to activate the 
> USB-IDs (by default: off) rather than throwing everything away?
>
We could, but honestly, there are likely few people using this device 
who don't have to patch their kernel anyway, and it is a trivial patch 
to apply.  There have been 4 incarnations of the CW3K as the 
manufacturer has tried to actively make it not work in Linux (and users 
have found ways around that for each subsequent revision).  When I 
created the patch, I was not aware that the developer would take this 
stance.  Only the 1st batch of devices works with the existing code, and 
I'm not aware of any way to detect the device version. 

Given the manufacturer's stance and the potential to unknowingly damage 
the device (I've been informed that the manufacturer has stated that use 
of the Linux drivers with the CW3K will void any manufacturer's 
warranty), I would rather remove support for this piece of hardware 
outright.  I believe the manufacturer still supports the 8PSK->USB and 
Skywalker1 versions of the hardware on Linux (plus a new Skywalker2 
which requires a kernel patch to enable).



  reply	other threads:[~2009-04-01 20:04 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 [this message]
2009-04-05 14:55     ` Mauro Carvalho Chehab
2009-04-05 15:19       ` Alan Nisota
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=49D3C815.6000004@gmail.com \
    --to=alannisota@gmail.com \
    --cc=linux-media@vger.kernel.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.