Dne pá 27. května 2005 3:58 jste napsal(a): > On Thursday 26 May 2005 11:18 am, Michal Semler wrote: > > Dne čt 26. května 2005 19:34 jste napsal(a): > > > That is, you unplug the dongle -- breaking the USB power session -- and > > > then plug in a mouse? And the kernel does something other than > > > > USB BT Dongle is in USB port switched into HCI mode. Then I hibernate > > (suspend to disk). Get my laptop and take it with me to other office, > > where I plug BT dongle again into USB port, but when power on, dongle is > > in it's default state - HID proxy mode acting like: > > > > input: USB HID v1.11 Keyboard [0a12:1000] on usb-0000:00:1d.2-1 > > input: USB HID v1.11 Mouse [0a12:1000] on usb-0000:00:1d.2-1 > > > > > disconnecting the dongle, and then enumerate a new mouse? That'd be a > > > bug. > > > > It is still the same BT dongle, but when power on, it starts acts like > > USB mouse and keyboard. Then it needs to be switched into HCI mode using > > hid2hci util from bluez-utils - see it on www.bluez.org > > From what you've said, everything at the USB level is doing the right > thing. > > And it's not clear there's anything going wrong with bluetooth either ... > you had to put it into "hci mode" by hand in the first place after first > enumeration, so having to do it in the second place after the second > enumeration is normal. > > > > can normally maintain USB > > > power sessions. And even then, the device drivers need to be prepared > > > to maintain them ... and do things like stop active I/O requests, and > > > resume them later. > > > > > > You said this was an all-Intel system. So which host controller driver > > > is in use here ... UHCI? EHCI? > > > > both of them: > > I suspect the bluetooth dongle is going through UHCI; it's not like it > needs much bandwidth. But whatever it's doing, nothing at the USB > level seems to be making trouble. > > > I'll try, but as I mentioned, laptop boots, finds suspended image, reads > > it till 100% and then freezes imeditially...no debug is possible.... > > Your explanations are internally inconsistent. Either it freezes > immediately and no debug is possible ... OR it came back but not in HCI > mode. You've said both. That doesn't make sense. Uff again:
This dongle acts as two devices: 1] usb keyboard and usb mouse - reason is, that BIOS can't handle BT at all, so this is done for compatibility - it can handle usb keyboard and mouse. So when BT keyboard and mouse connects to BT dongle in HID proxy mode, system sees keyboard and mouse, but BT doesn't work 2] BT usb dongle - after switching via hid2hci util where you need some additional daemons runs to take keyboard working (hidd --server) and system doesn't sees keyboard and mouse - see only BT dongle in HCI mode and handling of keyboard and mouse is done via daemon hidd and kernel module hidp. When dongle is plugged into USB port (has no voltage before), it can be seen as: lsusb Bus 003 Device 005: ID 0a12:1000 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HID proxy mode) and dmesg reports: usb 3-1: new full speed USB device using uhci_hcd and address 3 input: USB HID v1.11 Keyboard [0a12:1000] on usb-0000:00:1d.2-1 input: USB HID v1.11 Mouse [0a12:1000] on usb-0000:00:1d.2-1 then I needs to use hid2hci utility to get it work as BT device hid2hci lsusb Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) and dmesg: Bluetooth: Core ver 2.7 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.7 Bluetooth: L2CAP socket layer initialized usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -84 Bluetooth: RFCOMM ver 1.5 Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized usb 3-1: USB disconnect, address 3 usb 3-1: new full speed USB device using uhci_hcd and address 4 Bluetooth: HCI USB driver ver 2.8 usbcore: registered new driver hci_usb See different minor USB dongle's ID... So when I suspend to disk system sees BT dongle 0a12:0001 then system power offs -> BT dongle is back in HID proxy mode (has no voltage again) and after after power on system sees 0a12:1000 Then when system boots, it freezes imeditially after reads suspended memory from swap. When I boots normally without hibernate everything works. Do you understand what I means and where is problem now? For system this Bluetooth dongle si totally different HW when it is switched to HCI mode and when it is in initial HIDproxy mode For debuging buy Dlink DBT-120 rev B3 BT dongle and flash it with Apple firmware Michal > > - Dave -- S pozdravem Michal Semler ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
