firmware hotpluging

firmware hotpluging

[Dave Sampson]

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?

Cheers

-------------------------------------------------------------------------
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

Re: firmware hotpluging

[Kay Sievers]

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

Re: firmware hotpluging

[Dave Sampson]

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
ACTION­d
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
ACTION­d
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
ACTION­d
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
ACTION­d
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
ACTION­d
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
ACTION­d
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
ACTION­d
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

Re: firmware hotpluging

[Kay Sievers]

On Fri, 2007-04-13 at 12:07 -0400, Dave Sampson wrote:
> 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.

You get this event:
  UEVENT[1176480087.807781] add@/class/firmware/0000:02:00.0
  ACTION­d
  DEVPATH=/class/firmware/0000:02:00.0
  SUBSYSTEM=firmware
  SEQNUM\x1037
  FIRMWARE=tiacx100c0D

Do you have that file on your box?:
  /lib/firmware/tiacx100c0D

> 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.

Most distros create persistent network names, by writing rules for every
discovered device and assing the same name after reboot. You would just
need to edit the rules file and set a different name.

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

Re: firmware hotpluging

[Dave Sampson]

Alright,

So I am looking at this as a hotplug config issue, so I apologise if I 
cross the bounds. Maybe I just need to change some rules.

from the ACX site these are the available firmwares

======
What that means is, it will be something along the lines of:

tiacx111c16 (1)
tiacx100r11 (2)
tiacx100 (3)
tiacx100usb (4)
tiacx100r0D (5)

(1) is a combined firmware for a ti acx111 card that uses radio 16 
(originally named FwRad16.bin)
(2) is a radio only firmware for a ti acx100 that uses radio 11 
(originally named RADIO11.BIN)
(3) is a master firmware for a ti acx100 (originally named WLANGEN.BIN)
(4) is the firmware image for all ACX100 USB devices
(5) is a radio complement firmware required by ACX100 PCMCIA device 
(originally named RADIO0d.BIN)
=======
So I need 2,3 and 5

this is the lib/firmware directory
======
[sampson@mobile ~]$ ls /lib/firmware/
BCM2033-FW.bin  STLC2500_R4_00_03.ptc       STLC2500_R4_02_04.ptc  
tiacx100r11
BCM2033-MD.hex  STLC2500_R4_00_06.ssf       tiacx100               
tiacx100usb
BCM-LEGAL.txt   STLC2500_R4_02_02_WLAN.ssf  tiacx100r0d            
tiacx111c16
[sampson@mobile ~]$
=======
 
So I don't know what UDEV wants to load the firmware for...  I shall 
google that firmware though for kicks...

For the other firmwares it appears that UDEV attempts to load it, then 
removes them after timeout for 10 seconds?
Any explinantions?

Cheers


Kay Sievers wrote:
> On Fri, 2007-04-13 at 12:07 -0400, Dave Sampson wrote:
>   
>> 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.
>>     
>
> You get this event:
>   UEVENT[1176480087.807781] add@/class/firmware/0000:02:00.0
>   ACTION­d
>   DEVPATH=/class/firmware/0000:02:00.0
>   SUBSYSTEM=firmware
>   SEQNUM\x1037
>   FIRMWARE=tiacx100c0D
>
> Do you have that file on your box?:
>   /lib/firmware/tiacx100c0D
>
>   
>> 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.
>>     
>
> Most distros create persistent network names, by writing rules for every
> discovered device and assing the same name after reboot. You would just
> need to edit the rules file and set a different name.
>
> 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