From: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] usb.agent should processes usermap before other maps.
Date: Thu, 18 Jul 2002 03:59:12 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102696506820116@msgid-missing> (raw)
Hi Folks,
Currently usb.agent processes usermap after the kernelmap. Unfortunately it
doesn't work for
Broadcom USB (BCM) firmware loader. The problem is that Bluetooth HCI USB
driver (hci_usb)
has to claim any device with proper Bluetooth class, subclass and protocol
regardless
of the vendorid/productid. But at the same time fw loader has to be able to
claim devices
with specific vendorid/productid even if they have proper Bluetooth class,
subclass, proto.
Here is an example of BCM config descriptors
before fw load
bDeviceClass 224
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x2033
after
bDeviceClass 224
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x2000
I added a5c/2033 to usb.handmap but since kernel map is processed first
usb.agent doesn't call the loader.
So, the solution is to process usermap first. It kinda makes sense anyway,
usermap should have priority over kernelmap.
Patch against hotplug 2002.04.01 is here
http://bluez.sourceforge.net/patches/patch.hotplug-2002.04.01.gz
Comments ?
Max
http://bluez.sf.net
http://vtun.sf.net
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2002-07-18 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 3:59 Maksim (Max) Krasnyanskiy [this message]
2002-07-18 5:35 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 16:49 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 17:19 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 17:47 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 17:51 ` [PATCH] usb.agent should processes usermap before other maps Johannes Erdfelt
2002-07-18 20:17 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 20:55 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 21:40 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 21:49 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 22:03 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-07-18 23:03 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
2002-07-18 23:47 ` [PATCH] usb.agent should processes usermap before other Maksim (Max) Krasnyanskiy
2002-08-09 18:22 ` [PATCH] usb.agent should processes usermap before other maps David Brownell
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=marc-linux-hotplug-102696506820116@msgid-missing \
--to=maxk@qualcomm.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).