From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>,
Rogier Wolff <R.E.Wolff@BitWizard.nl>,
kuba@mareimbrium.org, bryder@sgi.com,
linux-kernel@vger.kernel.org, edwin@harddisk-recovery.nl
Subject: Re: FTDI SIO patch to allow custom vendor/product IDs.
Date: Thu, 2 Dec 2004 10:00:12 -0800 [thread overview]
Message-ID: <20041202180012.GD7655@kroah.com> (raw)
In-Reply-To: <20041202133437.GA27994@infradead.org>
On Thu, Dec 02, 2004 at 01:34:37PM +0000, Christoph Hellwig wrote:
> On Thu, Dec 02, 2004 at 01:48:31PM +0100, Rogier Wolff wrote:
> >
> > To prevent XP from hijacking devices that require a different driver,
> > some people flash a different Vendor/Product ID into their FTDI based
> > device.
> >
> > Also some "new" devices may come out which are perfectly valid to be
> > driven by the ftdi_sio driver, but happen to have a vendor/product
> > id which is not (yet) included in the driver. I've built a patch
> > that allows you to tell the driver "vendor=... product=...." to
> > make it accept such devices.
> >
> > Does this patch make sense?
>
> I think it would be much better to have something like the dynamic PCI IDs
> support to USB aswell.
I agree, and this is what I have stated a number of times already. But
it's going to take some driver core rework to get correct, and I'm
finding less time than I expected in order to do that work...
Hopefully soon...
thanks,
greg k-h
next prev parent reply other threads:[~2004-12-02 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 12:48 FTDI SIO patch to allow custom vendor/product IDs Rogier Wolff
2004-12-02 13:34 ` Christoph Hellwig
2004-12-02 18:00 ` Greg KH [this message]
2004-12-02 13:57 ` Jan Dittmer
2004-12-02 14:02 ` Jan Dittmer
2004-12-02 18:00 ` Greg KH
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=20041202180012.GD7655@kroah.com \
--to=greg@kroah.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=bryder@sgi.com \
--cc=edwin@harddisk-recovery.nl \
--cc=hch@infradead.org \
--cc=kuba@mareimbrium.org \
--cc=linux-kernel@vger.kernel.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