From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] usb.agent should processes usermap before other maps.
Date: Thu, 18 Jul 2002 05:35:59 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102698502032673@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102696506820116@msgid-missing>
Maksim (Max) Krasnyanskiy wrote:
> 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.
If hci_usb shouldn't be claiming specific devices, it's simple
to teach it not to do so. I notice it's not using driver_info
for anything, so it'd be easy to store flags there telling it
not to bind to the pre-firmware IDs (idProduct = 0x2033); then
the with-firmware path would work normally (idProduct = 0x2000).
That'd total about half a dozen lines: define the flag, add a
MODULE_DEVICE_TABLE entry to blacklist that one device, add code
in the probe() routine to test that flag and return if it's set.
> So, the solution is to process usermap first. It kinda makes sense anyway,
> usermap should have priority over kernelmap.
No can do ... remember that when drivers are statically linked,
the kernel is going to get first whack regardless of what you
try to make userland do. Changing that isn't an option today,
and wouldn't IMO be a good idea in any case.
That means you must make the kernel driver bind correctly,
or in the case of this no-firmware device, not bind.
- Dave
-------------------------------------------------------
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 prev parent reply other threads:[~2002-07-18 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 3:59 [PATCH] usb.agent should processes usermap before other maps Maksim (Max) Krasnyanskiy
2002-07-18 5:35 ` David Brownell [this message]
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-102698502032673@msgid-missing \
--to=david-b@pacbell.net \
--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).