rt2500usb strangeness

[Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>]

On x86_64 2.6.32-rc5-git4, dmesg says
phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt2500usb
 # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501USB
Wireless Adapter

# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:0E:2E:F1:36:99
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17041 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18304 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2873301 (2.7 Mb)  TX bytes:4280417 (4.0 Mb)
So it gets enumerated and configured via dhcp.
====================================================================
On linux-omap 2.6.32-rc6
[12729.717712] usbcore: registered new interface driver rt2500usb
[12751.037414] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset
detected.
[12751.051361] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate
device.
root@beagleboard:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04cc:1521 Philips Semiconductors USB 2.0 Hub
Bus 002 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501USB
Wireless Adapter
root@beagleboard:~# ifconfig wlan0
wlan0: error fetching interface information: Device not found

In either case it looks wrong, though it works on all x86_64 boxes.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html