Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
On Wed, Oct 20, 2010 at 11:53:58AM +0200, Sima Baymani wrote: Hi David (and everyone else)! Just to make sure I understand, I have some questions to clarify to myself how it works and what my options are. - the RT73 is a Ralink wifi-unit. According to Ralink, it should work on Linux 2.4 and 2.6. Does that (generally) mean that Linux 2.4 and 2.6 have those vendor patches/fixes but uClinux does not? That could also mean that ralink provides drivers on a CD or on its website that you must compile for your kernel. Philippe ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
On Wed, Oct 20, 2010 at 12:33 PM, Philippe De Muyter p...@macqel.be wrote: On Wed, Oct 20, 2010 at 11:53:58AM +0200, Sima Baymani wrote: Hi David (and everyone else)! Just to make sure I understand, I have some questions to clarify to myself how it works and what my options are. - the RT73 is a Ralink wifi-unit. According to Ralink, it should work on Linux 2.4 and 2.6. Does that (generally) mean that Linux 2.4 and 2.6 have those vendor patches/fixes but uClinux does not? That could also mean that ralink provides drivers on a CD or on its website that you must compile for your kernel. The driver I try to get working is actually the one from Ralink. =/ So the driver compiles and apparently gets registered but the device does not pop up. Has the driver usually anything to do with the device popping up or is it only to make the device work? I am honestly a bit confused here between what is the responsibility of the driver and of the kernel. -Sima Philippe ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
Jivin Philippe De Muyter lays it down ... On Wed, Oct 20, 2010 at 11:53:58AM +0200, Sima Baymani wrote: Hi David (and everyone else)! Just to make sure I understand, I have some questions to clarify to myself how it works and what my options are. - the RT73 is a Ralink wifi-unit. According to Ralink, it should work on Linux 2.4 and 2.6. Does that (generally) mean that Linux 2.4 and 2.6 have those vendor patches/fixes but uClinux does not? That could also mean that ralink provides drivers on a CD or on its website that you must compile for your kernel. Which is almost certainly the case here, at least in my experience with the rt73 driver :-) Cheers, Davidm -- David McCullough, david_mccullo...@mcafee.com, Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
Jivin Sima Baymani lays it down ... Hi David (and everyone else)! Just to make sure I understand, I have some questions to clarify to myself how it works and what my options are. - the RT73 is a Ralink wifi-unit. According to Ralink, it should work on Linux 2.4 and 2.6. Does that (generally) mean that Linux 2.4 and 2.6 have those vendor patches/fixes but uClinux does not? No, it means you can build the ralink source against either kernel and get it to work. - Is it generally so that a unit like this needs to have support in the kernel? In my naivety I was thinking that it was a USB unit, therefore it should communicate in a well known way - at least the device ID would pop up even if the device wouldn't work - I could continue from that. It should, but perhaps the USB port is under SW control (is powered on). There may be board level IO pins or other things that need to be enabled to get a USB device to function in that port. I take it the camera is soldered on the board but the rt73 is plugged into a USB port. Do you (in general) have to have support in the kernel for your device (other than the driver) in order for your device to work? You need a working USB host and a driver that will claim the USB ID your device has. It sounds like you have both of those, just some small bit is missing. - What would be the first steps for me to try to figure out how to make this little bastard pop up? E.g. 1. Look in files usb_x, usb_y and usb_z. They are the ones probing for new devices. 2. Read the RT73 datasheet to find out about operation A 3. Patch your kernel with a call of type do_this_and_that() I have vague notions on how to move forward, but need some directions in the labyrinth that this is for me... See if the USB port has power ? Cheers, Davidm Jivin Sima Baymani lays it down ... Time for a status report! Now I have support for usbfs in my kernel and I mounted /proc/bus/usb. Thanks for that - I learned something new =) Since before I had activated USB verbose debug messages in the kernel config - not sure if there are more places to activate USB debugging? I found USB_SERIAL_DEBUG and USB_STORAGE_DEBUG but those don't really apply I guess. This is what appeared in the directory after I mounted it: /proc/bus/usb ls -l dr-xr-xr-x 1 00 0 Jan 01 00:05 001 -r--r--r-- 1 00 0 Jan 01 00:05 devices -r--r--r-- 1 00 0 Jan 01 00:05 drivers /proc/bus/usb ls -l 001 -rw-r--r-- 1 00 18 Jan 01 00:05 001 -rw-r--r-- 1 00 18 Jan 01 00:05 002 /proc/bus/usb cat drivers usbdevfs hub rt73 usb-storage /proc/bus/usb cat devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB OHCI Root Hub S: SerialNumber=fff05000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ef(unk. ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0c45 ProdID=62f1 Rev= 1.00 S: Manufacturer=Sonix Technology Co., Ltd. S: Product=USB 2.0 Camera C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=0e(unk. ) Sub=01 Prot=00 Driver=(none) E: Ad=83(I) Atr=03(Int.) MxPS= 16 Ivl=6ms I: If#= 1 Alt= 0 #EPs= 0 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) I: If#= 1 Alt= 1 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 128 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 256 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 600 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 800 Ivl=1ms I: If#= 1 Alt= 6 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 956 Ivl=1ms from what I can see, the wifi-device is not there (but the camera is...). The wifi does not appear after some time either. Any thoughts on how to proceed? Until the device ID shows up not much more will happen.
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
On Wed, Oct 20, 2010 at 12:40:47PM +0200, Sima Baymani wrote: On Wed, Oct 20, 2010 at 12:33 PM, Philippe De Muyter p...@macqel.be wrote: On Wed, Oct 20, 2010 at 11:53:58AM +0200, Sima Baymani wrote: Hi David (and everyone else)! Just to make sure I understand, I have some questions to clarify to myself how it works and what my options are. - the RT73 is a Ralink wifi-unit. According to Ralink, it should work on Linux 2.4 and 2.6. Does that (generally) mean that Linux 2.4 and 2.6 have those vendor patches/fixes but uClinux does not? That could also mean that ralink provides drivers on a CD or on its website that you must compile for your kernel. The driver I try to get working is actually the one from Ralink. =/ So the driver compiles and apparently gets registered but the device does not pop up. Has the driver usually anything to do with the device popping up or is it only to make the device work? I am honestly a bit confused here between what is the responsibility of the driver and of the kernel. Without the driver, you won't get a device popping up (if I understand what you mean by popping up), e.g. you won't get a ethX or wlanX for your device. Philippe -- Philippe De Muyter phdm at macqel dot be Tel +32 27029044 Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077 ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
On Wed, Oct 20, 2010 at 12:50 PM, Philippe De Muyter p...@macqel.be wrote: On Wed, Oct 20, 2010 at 12:40:47PM +0200, Sima Baymani wrote: On Wed, Oct 20, 2010 at 12:33 PM, Philippe De Muyter p...@macqel.be wrote: On Wed, Oct 20, 2010 at 11:53:58AM +0200, Sima Baymani wrote: Hi David (and everyone else)! Just to make sure I understand, I have some questions to clarify to myself how it works and what my options are. - the RT73 is a Ralink wifi-unit. According to Ralink, it should work on Linux 2.4 and 2.6. Does that (generally) mean that Linux 2.4 and 2.6 have those vendor patches/fixes but uClinux does not? That could also mean that ralink provides drivers on a CD or on its website that you must compile for your kernel. The driver I try to get working is actually the one from Ralink. =/ So the driver compiles and apparently gets registered but the device does not pop up. Has the driver usually anything to do with the device popping up or is it only to make the device work? I am honestly a bit confused here between what is the responsibility of the driver and of the kernel. Without the driver, you won't get a device popping up (if I understand what you mean by popping up), e.g. you won't get a ethX or wlanX for your device. Ah, I was maybe a bit unclear. I meant pop up = device ID showing up. Does that change your answer? I do understand that without the driver - no network interface. Philippe -- Philippe De Muyter phdm at macqel dot be Tel +32 27029044 Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077 ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
Jivin Sima Baymani lays it down ... Time for a status report! Now I have support for usbfs in my kernel and I mounted /proc/bus/usb. Thanks for that - I learned something new =) Since before I had activated USB verbose debug messages in the kernel config - not sure if there are more places to activate USB debugging? I found USB_SERIAL_DEBUG and USB_STORAGE_DEBUG but those don't really apply I guess. This is what appeared in the directory after I mounted it: /proc/bus/usb ls -l dr-xr-xr-x 1 00 0 Jan 01 00:05 001 -r--r--r-- 1 00 0 Jan 01 00:05 devices -r--r--r-- 1 00 0 Jan 01 00:05 drivers /proc/bus/usb ls -l 001 -rw-r--r-- 1 00 18 Jan 01 00:05 001 -rw-r--r-- 1 00 18 Jan 01 00:05 002 /proc/bus/usb cat drivers usbdevfs hub rt73 usb-storage /proc/bus/usb cat devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB OHCI Root Hub S: SerialNumber=fff05000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ef(unk. ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0c45 ProdID=62f1 Rev= 1.00 S: Manufacturer=Sonix Technology Co., Ltd. S: Product=USB 2.0 Camera C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=0e(unk. ) Sub=01 Prot=00 Driver=(none) E: Ad=83(I) Atr=03(Int.) MxPS= 16 Ivl=6ms I: If#= 1 Alt= 0 #EPs= 0 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) I: If#= 1 Alt= 1 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 128 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 256 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 1 Cls=0e(unk. ) Sub=02 Prot=00 Driver=(none) E: Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=1ms
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
David, thanks a lot for your input. On Thu, Oct 14, 2010 at 6:28 AM, David McCullough david_mccullo...@mcafee.com wrote: Jivin Sima Baymani lays it down ... Hi all, I've been lurking a bit on this list since I got a uClinux project in my lap this summer. I've fiddled a bit with Linux, but this is my first uClinux project and I've not worked this deep with linux drivers before even though I'm familiar with working low level. And now to the question! I know this is ancient 2.4, but this is what I have to work with. I don't expect answers but am grateful for any advice or thoughts you might have. Platform: ARM7 from Nuvoton, more precisely called NUC745. uClinux version: 2.4.20 The product is a webcam with ethernet and wifi, a clone of one of the FOSCAM cameras, produced by Apexis. I need to do a lot of changes in the software and the programs on it. They will not share their source code even though I _know_ they have used uClinux and other open source software under GPL. I got the uClinux-source from a BSP somewhere else. The BSP source runs fine with ethernet working. My problem is that I need wifi to work as well. The driver I have is the RT73 driver from Ralink. Apexis use the same driver but I don't know how much they had to change it to work. I have managed to add the driver to the kernel build and it seems to be loaded (full logs at end of email): usb.c: registered new driver hub add a static ohci host controller device : USB OHCI at membase 0xfff05000, IRQ 15 hc_alloc_ohci usb-ohci.c: AMD756 erratum 4 workaround hc_reset usb.c: new USB bus registered, assigned bus number 1 Product: USB OHCI Root Hub SerialNumber: fff05000 hub.c: USB hub found hub.c: 2 ports detected -RT73-7usb_rtusb_init-- //usb_rtusb_init is the module_init function though this is a compiled in driver SIMA in da house! usb.c: registered new driver rt73 This only tells you the driver was registered. There doesn't seem to be any device detected that matches the rt73 driver. I've had the same thoughts but had no idea how to debug, good to know I was on the right track. The BSP does not have any lsusb program to compile in, neither standalone nor in busybox. I will look into if I can get lsusb in the build some other way. I'm not sure how to talk to the device otherwise, is it with some kind of ioctl-call? I don't know anything about this, but it's what I have stumbled over that makes some sense. What I'm thinking is that the manufacturer kick-starts the device somehow by making some kind of HW-configuration - but I have no idea where to start there. Would it be something like ioctl(DEV_ADDR, DEV_OPERATION)? What should I be looking for? SIMA - Registered RT73 driver! Usb device driver by ns24 zswan designed successfully! Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. But when I get to the prompt neither ifconfig nor iwconfig list any wireless interfaces. If I compare to the original boot log, it looks like hub.c does a bit of probing that my log doesn't have: hub.c: connect-debounce failed, port 1 disabled new USB device :80fc8004-fed640 hub.c: new USB device 1, assigned address 2 probing sonix288 usb camera ... dvm camera registered as video0 new USB device :80fc8604-fed640 hub.c: new USB device 2, assigned address 3 idVendor = 0x148f, idProduct = 0x2573 trying to set up the wireless interfaces gives me this: / ifconfig rausb0 inet 192.168.5.135 up How long after boot ? Sometimes it takes a while for the usb devices to appear, but if you waited at least 15-20 seconds, it isn't going to show :-) I've waited that long and more, and it doesn't pop up =/ It seems like I'm missing something, some code I might lack or daemon I don't have perhaps? You need to get lsusb or look at the appropriate /proc files and see if the wireless USB is actually appearing. Unfortunately no lsusb, unless I find out how to get it into my build myself. I've had a look in the /proc files but not found anything relevant, any ideas on what kind of files I shall look for? would it be usb-files or net files or wireless files? I understand all of this is very dependent on the implementation of the driver, but any directions for me are welcome as it makes it easier for me to start untangling the mess =) At least I will know where it's not, and can proceed with new ideas. Thanks for reading and for any thoughts you might have! -Sima Cheers, Davidm SIOCSIFADDR: No such device SIOCGIFFLAGS: No such device So, it seems the driver is loaded but not started. I have double checked the vend/prod id (0x148f/0x2573), and they seem to be right and in the source code devices list. My first questions: - How can I start the driver? Is there a common practice/standard/usual way of doing that? I'm totally in the dark about this =/ The second question:
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
Jivin Sima Baymani lays it down ... David, thanks a lot for your input. On Thu, Oct 14, 2010 at 6:28 AM, David McCullough david_mccullo...@mcafee.com wrote: Jivin Sima Baymani lays it down ... Hi all, I've been lurking a bit on this list since I got a uClinux project in my lap this summer. I've fiddled a bit with Linux, but this is my first uClinux project and I've not worked this deep with linux drivers before even though I'm familiar with working low level. And now to the question! I know this is ancient 2.4, but this is what I have to work with. I don't expect answers but am grateful for any advice or thoughts you might have. Platform: ARM7 from Nuvoton, more precisely called NUC745. uClinux version: 2.4.20 The product is a webcam with ethernet and wifi, a clone of one of the FOSCAM cameras, produced by Apexis. I need to do a lot of changes in the software and the programs on it. They will not share their source code even though I _know_ they have used uClinux and other open source software under GPL. I got the uClinux-source from a BSP somewhere else. The BSP source runs fine with ethernet working. My problem is that I need wifi to work as well. The driver I have is the RT73 driver from Ralink. Apexis use the same driver but I don't know how much they had to change it to work. I have managed to add the driver to the kernel build and it seems to be loaded (full logs at end of email): usb.c: registered new driver hub add a static ohci host controller device : USB OHCI at membase 0xfff05000, IRQ 15 hc_alloc_ohci usb-ohci.c: AMD756 erratum 4 workaround hc_reset usb.c: new USB bus registered, assigned bus number 1 Product: USB OHCI Root Hub SerialNumber: fff05000 hub.c: USB hub found hub.c: 2 ports detected -RT73-7usb_rtusb_init-- //usb_rtusb_init is the module_init function though this is a compiled in driver SIMA in da house! usb.c: registered new driver rt73 This only tells you the driver was registered. There doesn't seem to be any device detected that matches the rt73 driver. I've had the same thoughts but had no idea how to debug, good to know I was on the right track. The BSP does not have any lsusb program to compile in, neither standalone nor in busybox. I will look into if I can get lsusb in the build some other way. I'm not sure how to talk to the device otherwise, is it with some kind of ioctl-call? I don't know anything about this, but it's what I have stumbled over that makes some sense. What I'm thinking is that the manufacturer kick-starts the device somehow by making some kind of HW-configuration - but I have no idea where to start there. Would it be something like ioctl(DEV_ADDR, DEV_OPERATION)? What should I be looking for? Go looking under /proc/bus/usb SIMA - Registered RT73 driver! Usb device driver by ns24 zswan designed successfully! Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. But when I get to the prompt neither ifconfig nor iwconfig list any wireless interfaces. If I compare to the original boot log, it looks like hub.c does a bit of probing that my log doesn't have: hub.c: connect-debounce failed, port 1 disabled new USB device :80fc8004-fed640 hub.c: new USB device 1, assigned address 2 probing sonix288 usb camera ... dvm camera registered as video0 new USB device :80fc8604-fed640 hub.c: new USB device 2, assigned address 3 idVendor = 0x148f, idProduct = 0x2573 trying to set up the wireless interfaces gives me this: / ifconfig rausb0 inet 192.168.5.135 up How long after boot ? Sometimes it takes a while for the usb devices to appear, but if you waited at least 15-20 seconds, it isn't going to show :-) I've waited that long and more, and it doesn't pop up =/ It seems like I'm missing something, some code I might lack or daemon I don't have perhaps? You need to get lsusb or look at the appropriate /proc files and see if the wireless USB is actually appearing. Unfortunately no lsusb, unless I find out how to get it into my build myself. I've had a look in the /proc files but not found anything relevant, any ideas on what kind of files I shall look for? would it be usb-files or net files or wireless files? I understand all of this is very dependent on the implementation of the driver, but any directions for me are welcome as it makes it easier for me to start untangling the mess =) At least I will know where it's not, and can proceed with new ideas.
Re: [uClinux-dev] Get RT73 driver to work on 2.4 or try to move to 2.6? ARM7 from Nuvoton
Jivin Sima Baymani lays it down ... Hi all, I've been lurking a bit on this list since I got a uClinux project in my lap this summer. I've fiddled a bit with Linux, but this is my first uClinux project and I've not worked this deep with linux drivers before even though I'm familiar with working low level. And now to the question! I know this is ancient 2.4, but this is what I have to work with. I don't expect answers but am grateful for any advice or thoughts you might have. Platform: ARM7 from Nuvoton, more precisely called NUC745. uClinux version: 2.4.20 The product is a webcam with ethernet and wifi, a clone of one of the FOSCAM cameras, produced by Apexis. I need to do a lot of changes in the software and the programs on it. They will not share their source code even though I _know_ they have used uClinux and other open source software under GPL. I got the uClinux-source from a BSP somewhere else. The BSP source runs fine with ethernet working. My problem is that I need wifi to work as well. The driver I have is the RT73 driver from Ralink. Apexis use the same driver but I don't know how much they had to change it to work. I have managed to add the driver to the kernel build and it seems to be loaded (full logs at end of email): usb.c: registered new driver hub add a static ohci host controller device : USB OHCI at membase 0xfff05000, IRQ 15 hc_alloc_ohci usb-ohci.c: AMD756 erratum 4 workaround hc_reset usb.c: new USB bus registered, assigned bus number 1 Product: USB OHCI Root Hub SerialNumber: fff05000 hub.c: USB hub found hub.c: 2 ports detected -RT73-7usb_rtusb_init-- //usb_rtusb_init is the module_init function though this is a compiled in driver SIMA in da house! usb.c: registered new driver rt73 This only tells you the driver was registered. There doesn't seem to be any device detected that matches the rt73 driver. SIMA - Registered RT73 driver! Usb device driver by ns24 zswan designed successfully! Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. But when I get to the prompt neither ifconfig nor iwconfig list any wireless interfaces. If I compare to the original boot log, it looks like hub.c does a bit of probing that my log doesn't have: hub.c: connect-debounce failed, port 1 disabled new USB device :80fc8004-fed640 hub.c: new USB device 1, assigned address 2 probing sonix288 usb camera ... dvm camera registered as video0 new USB device :80fc8604-fed640 hub.c: new USB device 2, assigned address 3 idVendor = 0x148f, idProduct = 0x2573 trying to set up the wireless interfaces gives me this: / ifconfig rausb0 inet 192.168.5.135 up How long after boot ? Sometimes it takes a while for the usb devices to appear, but if you waited at least 15-20 seconds, it isn't going to show :-) You need to get lsusb or look at the appropriate /proc files and see if the wireless USB is actually appearing. Cheers, Davidm SIOCSIFADDR: No such device
