From: Dave Sampson <samper.d@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: firmware hotpluging
Date: Fri, 13 Apr 2007 16:07:01 +0000 [thread overview]
Message-ID: <461FAAA5.7090905@gmail.com> (raw)
In-Reply-To: <461F31E8.5090802@gmail.com>
Kay,
thanks for the prompt reply.
The bellow output is what udev monitor --env spits back when I plug in
my PCMCIA card (which essentialy loads the module at the same time). I
really need to learn more about udev, cause it is a big black box.
Furthermore I don't wish to complicate matters but I notice that it
creates device wlan0.. is there a way to make it create a ethX device. I
know its a wireless device so that is convention, but the application i
am trying to get going (kismet) thinks that acx will mount as a
/dev/ethx. If its an easy answer great, if not then lets focus on the
firmware first.
Cheers
========
UEVENT[1176480087.807608] add@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
ACTIONd
DEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
SUBSYSTEM=pci
SEQNUM\x1036
PHYSDEVBUS=pci
PCI_CLASS(000
PCI_ID\x104C:8400
PCI_SUBSYS_ID\x1186:3B00
PCI_SLOT_NAME\000:02:00.0
MODALIAS=pci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00
UEVENT[1176480087.807781] add@/class/firmware/0000:02:00.0
ACTIONd
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1037
FIRMWARE=tiacx100c0D
TIMEOUT\x10
UEVENT[1176480087.827201] remove@/class/firmware/0000:02:00.0
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1038
FIRMWARE=tiacx100c0D
TIMEOUT\x10
UEVENT[1176480087.827314] add@/class/firmware/0000:02:00.0
ACTIONd
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1039
FIRMWARE=tiacx100
TIMEOUT\x10
UDEV [1176480087.834629] remove@/class/firmware/0000:02:00.0
UDEV_LOG=3
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1038
FIRMWARE=tiacx100c0D
TIMEOUT\x10
UDEVD_EVENT=1
UEVENT[1176480087.879648] remove@/class/firmware/0000:02:00.0
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1040
FIRMWARE=tiacx100
TIMEOUT\x10
UDEV [1176480087.889647] remove@/class/firmware/0000:02:00.0
UDEV_LOG=3
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1040
FIRMWARE=tiacx100
TIMEOUT\x10
UDEVD_EVENT=1
UDEV [1176480088.031793] add@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
UDEV_LOG=3
ACTIONd
DEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
SUBSYSTEM=pci
SEQNUM\x1036
PHYSDEVBUS=pci
PCI_CLASS(000
PCI_ID\x104C:8400
PCI_SUBSYS_ID\x1186:3B00
PCI_SLOT_NAME\000:02:00.0
MODALIAS=pci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00
UDEVD_EVENT=1
UEVENT[1176480088.110214] add@/class/firmware/0000:02:00.0
ACTIONd
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1041
FIRMWARE=tiacx100r0D
TIMEOUT\x10
UEVENT[1176480088.113670] remove@/class/firmware/0000:02:00.0
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1042
FIRMWARE=tiacx100r0D
TIMEOUT\x10
UDEV [1176480088.116731] remove@/class/firmware/0000:02:00.0
UDEV_LOG=3
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUM\x1042
FIRMWARE=tiacx100r0D
TIMEOUT\x10
UDEVD_EVENT=1
UEVENT[1176480088.356545] add@/class/net/wlan0
ACTIONd
DEVPATH=/class/net/wlan0
SUBSYSTEM=net
SEQNUM\x1043
PHYSDEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
PHYSDEVBUS=pci
PHYSDEVDRIVER¬x_pci
INTERFACE=wlan0
UDEV [1176480088.365575] add@/class/net/wlan0
UDEV_LOG=3
ACTIONd
DEVPATH=/class/net/wlan0
SUBSYSTEM=net
SEQNUM\x1043
PHYSDEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
PHYSDEVBUS=pci
PHYSDEVDRIVER¬x_pci
INTERFACE=wlan0
UDEVD_EVENT=1
========
Kay Sievers wrote:
> On 4/13/07, Dave Sampson <samper.d@gmail.com> wrote:
>> Hey folks.
>>
>> I am using the ACX100 driver from http://acx100.sourceforge.net
>>
>> there is a requirement for hotplug to load firmware.
>>
>> I have the firmware in /lib/firmware
>>
>> but dmesg claims the firmware is never laoded and that I have it in the
>> wrong place.
>>
>> I am using fedora core 6.
>>
>> How do I get the firmware pluged in with hotplug?
>
> What's the output of:
> udevmonitor --env
> when you load the kernel module?
>
> Kay
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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:[~2007-04-13 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 7:31 firmware hotpluging Dave Sampson
2007-04-13 9:44 ` Kay Sievers
2007-04-13 16:07 ` Dave Sampson [this message]
2007-04-13 16:31 ` Kay Sievers
2007-04-13 17:14 ` Dave Sampson
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=461FAAA5.7090905@gmail.com \
--to=samper.d@gmail.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).