Re: firmware hotpluging

[Dave Sampson <samper.d@gmail.com>]

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