From: Arne Caspari <arne@datafloater.de>
To: linux-kernel@vger.kernel.org
Subject: hpsb protocol driver: probe callback not called
Date: Mon, 06 Dec 2004 12:07:36 +0100 [thread overview]
Message-ID: <41B43D78.4000509@datafloater.de> (raw)
Hi List!
I am working on a video-4-linux driver for IEEE-1394 cameras. The driver
exposes a struct ieee1394_device_id table to match devices on a certain
specifier.
If I specify a match for a specifier_id of 0xa02d and a version of
0x100, the "probe" callback supplied via "hpsb_register_protocol" is
never called, even if such a device is connected.
The driver is loaded by "hotplug" though so obviously the match is correct.
Now if I change the supplied specifier_id to match some other device and
leave the rest of the code just alike, the "probe" callback _is_ called.
The only difference between the two situations I can spot is that for
the specifier_id of "0xa02d", there are already two modules registered:
raw1394 and video1394. For the specifier_id of the other device, there
is no other registered driver.
Am I missing something obvious? Or is it really not possible to register
a driver for a device that has a match on some other driver? Or is it
just a bug in the ieee1394 node manager?
Thanks,
/Arne
reply other threads:[~2004-12-06 11:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41B43D78.4000509@datafloater.de \
--to=arne@datafloater.de \
--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