Re: USB driver selection algorithm?
From: Bernd Walter (ticso_at_cicely12.cicely.de)
Date: 07/01/04
- Previous message: Q: "Re: FreeBSD and MacOS"
- In reply to: Alex K: "USB driver selection algorithm?"
- Next in thread: Alex K: "uplcom.c changes (was: USB driver selection algorithm?)"
- Reply: Alex K: "uplcom.c changes (was: USB driver selection algorithm?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 1 Jul 2004 14:36:17 +0200 To: Alex K <lesha@intercaf.ru>
On Wed, Jun 30, 2004 at 07:04:44PM +0400, Alex K wrote:
>
> Hello, everyone!
>
> As far as I understand drivers for USB devices are selected and attached
> based on USB VendorID and ProductID match. Here I have situation where
> I have 2 diffrent USB devices (cables) which got same Vendor and Device
> IDs, only revision differes.
USB drivers are selected based on the drivers need.
That is usually deviceclass, interfaceclass or vendor/product.
First all drivers are asked if they want the whole device.
If none takes it than all drivers are asked for each interface of the
device - an interface is a functional part of an USB device.
If that also fails the driver is given to ugen as a whole.
> It is mobile phone cables based on PL2303 and PL2303X chipsets.
uplcom takes devices (or maybe interfaces) based on vendor/product ID.
> What approach will you recommend?
What is your problem?
-- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: Q: "Re: FreeBSD and MacOS"
- In reply to: Alex K: "USB driver selection algorithm?"
- Next in thread: Alex K: "uplcom.c changes (was: USB driver selection algorithm?)"
- Reply: Alex K: "uplcom.c changes (was: USB driver selection algorithm?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
