From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Sampson Date: Fri, 13 Apr 2007 16:07:01 +0000 Subject: Re: firmware hotpluging Message-Id: <461FAAA5.7090905@gmail.com> List-Id: References: <461F31E8.5090802@gmail.com> In-Reply-To: <461F31E8.5090802@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Kay, thanks for the prompt reply. The bellow output is what udev monitor --env spits back when I plug in=20 my PCMCIA card (which essentialy loads the module at the same time). I=20 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=20 creates device wlan0.. is there a way to make it create a ethX device. I=20 know its a wireless device so that is convention, but the application i=20 am trying to get going (kismet) thinks that acx will mount as a=20 /dev/ethx. If its an easy answer great, if not then lets focus on the=20 firmware first. Cheers =3D=3D=3D=3D=3D=3D=3D=3D UEVENT[1176480087.807608] add@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0 ACTION=ADd DEVPATH=3D/devices/pci0000:00/0000:00:0c.0/0000:02:00.0 SUBSYSTEM=3Dpci SEQNUM=1036 PHYSDEVBUS=3Dpci PCI_CLASS(000 PCI_ID=104C:8400 PCI_SUBSYS_ID=1186:3B00 PCI_SLOT_NAME=0000:02:00.0 MODALIAS=3Dpci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00 UEVENT[1176480087.807781] add@/class/firmware/0000:02:00.0 ACTION=ADd DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1037 FIRMWARE=3Dtiacx100c0D TIMEOUT=10 UEVENT[1176480087.827201] remove@/class/firmware/0000:02:00.0 ACTION=3Dremove DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1038 FIRMWARE=3Dtiacx100c0D TIMEOUT=10 UEVENT[1176480087.827314] add@/class/firmware/0000:02:00.0 ACTION=ADd DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1039 FIRMWARE=3Dtiacx100 TIMEOUT=10 UDEV [1176480087.834629] remove@/class/firmware/0000:02:00.0 UDEV_LOG=3D3 ACTION=3Dremove DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1038 FIRMWARE=3Dtiacx100c0D TIMEOUT=10 UDEVD_EVENT=3D1 UEVENT[1176480087.879648] remove@/class/firmware/0000:02:00.0 ACTION=3Dremove DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1040 FIRMWARE=3Dtiacx100 TIMEOUT=10 UDEV [1176480087.889647] remove@/class/firmware/0000:02:00.0 UDEV_LOG=3D3 ACTION=3Dremove DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1040 FIRMWARE=3Dtiacx100 TIMEOUT=10 UDEVD_EVENT=3D1 UDEV [1176480088.031793] add@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0 UDEV_LOG=3D3 ACTION=ADd DEVPATH=3D/devices/pci0000:00/0000:00:0c.0/0000:02:00.0 SUBSYSTEM=3Dpci SEQNUM=1036 PHYSDEVBUS=3Dpci PCI_CLASS(000 PCI_ID=104C:8400 PCI_SUBSYS_ID=1186:3B00 PCI_SLOT_NAME=0000:02:00.0 MODALIAS=3Dpci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00 UDEVD_EVENT=3D1 UEVENT[1176480088.110214] add@/class/firmware/0000:02:00.0 ACTION=ADd DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1041 FIRMWARE=3Dtiacx100r0D TIMEOUT=10 UEVENT[1176480088.113670] remove@/class/firmware/0000:02:00.0 ACTION=3Dremove DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1042 FIRMWARE=3Dtiacx100r0D TIMEOUT=10 UDEV [1176480088.116731] remove@/class/firmware/0000:02:00.0 UDEV_LOG=3D3 ACTION=3Dremove DEVPATH=3D/class/firmware/0000:02:00.0 SUBSYSTEM=3Dfirmware SEQNUM=1042 FIRMWARE=3Dtiacx100r0D TIMEOUT=10 UDEVD_EVENT=3D1 UEVENT[1176480088.356545] add@/class/net/wlan0 ACTION=ADd DEVPATH=3D/class/net/wlan0 SUBSYSTEM=3Dnet SEQNUM=1043 PHYSDEVPATH=3D/devices/pci0000:00/0000:00:0c.0/0000:02:00.0 PHYSDEVBUS=3Dpci PHYSDEVDRIVER=ACx_pci INTERFACE=3Dwlan0 UDEV [1176480088.365575] add@/class/net/wlan0 UDEV_LOG=3D3 ACTION=ADd DEVPATH=3D/class/net/wlan0 SUBSYSTEM=3Dnet SEQNUM=1043 PHYSDEVPATH=3D/devices/pci0000:00/0000:00:0c.0/0000:02:00.0 PHYSDEVBUS=3Dpci PHYSDEVDRIVER=ACx_pci INTERFACE=3Dwlan0 UDEVD_EVENT=3D1 =3D=3D=3D=3D=3D=3D=3D=3D Kay Sievers wrote: > On 4/13/07, Dave Sampson 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=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ 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