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 ... > > > On Wed, Oct 20, 2010 at 12:46 PM, David McCullough > wrote: > > > > - 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. > > > > Hooray I guess ;) > > > > - 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'm not sure what you mean with "the USB port is under SW control (is powered > on)" - could you clarify? It may be that the HW designers wanted to make sure the USB port could be turned off, maybe during boot or always, who knows. You may need to toggle a GPIO pin or something similar to power it up. > > > I take it the camera is soldered on the board but the rt73 is plugged > into > a USB port. > > > > Yes that's correct. How did you know?! ;) Because it's working :-) > > 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. > > > The needle in the haystack... > > > > - 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 ? > > > > Haha! "Hello this is IT support! Your computer isn't working? Have you > checked that the power cable is plugged in?" > I'll look into that, thanks for the reminder =) It's a start at least :-) 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 > >
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 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 > 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
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 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
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 ap
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
On Wed, Oct 20, 2010 at 12:33 PM, Philippe De Muyter 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
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
