<br><br><div class="gmail_quote">On Wed, Feb 4, 2009 at 2:14 PM, Alan Nishioka <span dir="ltr"><<a href="mailto:alan@nishioka.com">alan@nishioka.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
request_firmware uses the hotplug code so the kernel doesn't have any sourceless binaries compiled into it. on init, the driver requests the firmware, user mode hotplug daemon loads the firmware from disk and gives the driver a pointer to it.<br>
<br>
since this is a short term problem, i would suggest converting rt73.bin to a header file and compiling it into the kernel. you have to make a few minor changes to where request_firmware is called, but in the end firmware is just an array of bytes with a pointer to it. this is what i did when i was testing usb wifi a little while ago.<br>
<br>
i am probably going to open source hell for suggesting this, but i'm a hardware engineer, so i am in hell already.<br><font color="#888888">
<br>
alan nishioka</font></blockquote><div><br>Yes, you will certainly burn for this. :-)<br><br>Mike Timmons:<br><br>I'll show you how MINE works (and if someone out there can point out errors, fire away -- I'm not making the claim that this is completely correct). I hope that this will be new and helpful information for you. If it's not, my apologies; feel free to dump this in the bit bucket.<br>
<br>In my /sbin/hotplug I have a bunch of stuff for doing field updates, but at the very bottom, I have this:<br><br>if [ "$1" == "firmware" ] && [ "$ACTION" == "add" ]; then<br>
echo 1 > /sys/$DEVPATH/loading<br> cat /lib/firmware/$FIRMWARE > /sys/$DEVPATH/data<br> echo 0 > /sys/$DEVPATH/loading<br> echo "RT73 firmware loaded." > /dev/console<br>fi<br><br>That's how the firmware is loaded.<br>
<br>caveat: I am using 2.6.25 in my system. I have no idea what's changed from .24 to .25 that might be getting in your way. You could consider moving just the section in .25 that deals with the chipsets in question (ralink, I think??).<br>
<br>I put all this together in about an hour after doing a little reading. It all works very well.<br><br>Now if I could just get that pesky AP mode working...<br><br>Also in my hotplug script is<br><br>if [ "$1" == "net" ] && [ "$ACTION" == "add" ] && [ "$INTERFACE" == "wlan0" ]; then<br>
iwconfig wlan0 mode managed<br> iwconfig wlan0 channel auto<br> iwconfig wlan0 key DADADADADADADADADADADADADA<br> iwconfig wlan0 essid mlxwap<br>fi<br><br>You will want to get the sources for the wifi utilities compiled for your target, too. Not hard to do. I don't think I had to make any changes to it.<br>
<br>Those who wish, feel free to post suggestions, etc. I'm doing all of my work on an ARM target, so I don't know if there are any gotchas in the rt drivers for the rt73 usb stuff.<br><br>Also, you could check out <a href="http://rt2x00.serialmonkey.com">rt2x00.serialmonkey.com</a> if you haven't found it. They are live (well, mostly dead) on #rt2x00 on freenode.<br>
<br>Good luck; if you have questions, feel free to email me directly.<br></div></div><br>