Hello David, On Mon, 2011-03-14 at 14:46 +0000, David Vrabel wrote: > I hope you like writing kernel code and reverse engineering USB devices > as HWAs are unlikely to work well (or at all) with the current code. Hm - time's pretty limited right now, but can you point me to any additional information (specs etc.)? > Try manually loading the hwa-rc and hwa-hc modules in that order. > > modprobe -r hwa-hc > modprobe -r hwa-rc > modprobe hwa-rc > modprobe hwa-rc > > The problem here is the WUSB host controller module was started before > the radio controller and it must be done the other way around. That helped, at least partially: uwb_rc uwb0: event 0x00/0013/05 (5 bytes): nobody cared uwb_rc uwb0: new uwb radio controller (mac 0a:00:00:09:63:ce dev c0:1e) on usb 2-1.2:1.1 usbcore: registered new interface driver hwa-rc usb 2-1.2: supported encryption types: CCM-1 (0x01) hwa-hc 2-1.2:1.0: Wireless USB HWA host controller hwa-hc 2-1.2:1.0: new USB bus registered, assigned bus number 3 hwa-hc 2-1.2:1.0: Wireless USB Cluster ID set to 0xfe hub 3-0:1.0: USB hub found hub 3-0:1.0: 5 ports detected usbcore: registered new interface driver hwa-hc > > uwb_rc uwb0: SCAN: command execution failed: invalid state (10) > > The documentation both in the kernel source and on linuxuwb.org seems > > pretty outdated; can somebody give me some pointers/tips here? > You're unlikely to be able to see a Wireless USB device's beacons until > it has seen a wireless USB host to connect to. Is this documented anywhere? What's the meaning of the values in the beacon and scan files? Thanks, Florian -- SENT FROM MY DEC VT50 TERMINAL -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
