Hey, > Excellent news. Two comments about your patch, though: > As you don't seem to need a wakeup quirk, you can leave out this check here.
Well, it seems that my success report was a little thoughtless. The results I get with the card are totally inconclusive. Sometimes the HCI device is registered successfully, and sometimes it's not. The funny thing that I can't find any obvious reason why it works one time, and why not the other time. If it works I get the following log messages: r...@orion:~# tail /var/log/messages Jan 5 10:39:09 orion kernel: pcmcia 1.0: firmware: requesting cis/IBMBT.cis Jan 5 10:39:09 orion kernel: 1.0: ttyS1 at I/O 0x1e0 (irq = 3) is a 16C950/954 Jan 5 10:39:10 orion kernel: Bluetooth: HCI UART driver ver 2.2 Jan 5 10:39:10 orion kernel: Bluetooth: HCI H4 protocol initialized Jan 5 10:39:10 orion kernel: Bluetooth: HCI BCSP protocol initialized Jan 5 10:39:10 orion kernel: Bluetooth: HCILL protocol initialized Jan 5 10:39:10 orion hcid[2462]: HCI dev 0 registered Jan 5 10:39:10 orion hcid[2462]: HCI dev 0 up Jan 5 10:39:10 orion hcid[2462]: Device hci0 has been added Jan 5 10:39:10 orion hcid[2462]: Starting security manager 0 r...@orion:~# tail /var/log/syslog Jan 5 10:39:09 orion kernel: ttyS1: detected caps 00000700 should be 00000100 Jan 5 10:39:11 orion hcid[2462]: Can't read version info for hci0: Connection timed out (110) Jan 5 10:39:20 orion hcid[2605]: Can't set link policy on hci0: Connection timed out (110) Jan 5 10:39:20 orion kernel: hci_cmd_task: hci0 command tx timeout However if the registration of the HCI device fails, I only get this: r...@orion:~# dmesg | tail Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1 pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia 1.0: pcmcia: registering new device pcmcia1.0 pcmcia 1.0: firmware: requesting cis/IBMBT.cis ttyS1: detected caps 00000700 should be 00000100 1.0: ttyS1 at I/O 0x1e0 (irq = 3) is a 16C950/954 r...@orion:~# tail /var/log/syslog Oct 25 00:40:07 orion hcid[2465]: Can't create GN bridge Jan 4 23:29:07 orion kernel: ttyS1: detected caps 00000700 should be 00000100 r...@orion:~# tail /var/log/messages Jan 4 23:29:07 orion kernel: pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1 Jan 4 23:29:07 orion kernel: pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: clean. Jan 4 23:29:07 orion kernel: pcmcia 1.0: pcmcia: registering new device pcmcia1.0 Jan 4 23:29:07 orion kernel: pcmcia 1.0: firmware: requesting cis/IBMBT.cis Jan 4 23:29:07 orion kernel: 1.0: ttyS1 at I/O 0x1e0 (irq = 3) is a 16C950/954 Jan 4 23:29:17 orion hciattach: BCSP initialization timed out Another thing is that if I go through a suspend/resume cycle, then the HCI doesn't work afterwards, even though the HCI was successfully registered before the suspension of the system. Of course this may also be a bug/deficiency of the pm-utils package, that Slackware makes use of. Anyway, the symptom of this is that any commands I pass to the HCI reach a time out. (hciconfig hci0 reset for example.) I assigned the oxsemi16c950 wakeup quirk to this card also, as it is supposed to be oxsemi16c950 based. This doesn't seem to have much of an impact on whether the card is works or not. > Could you send me an updated patch, please, along with a proper > Signed-off-by: line so that either I or the maintainer at I have attaches a modified version of the patch. Please give me some ideas on how I could determine what causes this inconclusive behaviour. Thanks! Best regards, Janos
ibmbt.diff
Description: Binary data
_______________________________________________ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
