On Wed, 27 Jul 2005 [email protected] write:
> To: [email protected]
> Subject: Re: [Bluez-users] Kernel module for PCMCIA/CF Bluetooth cards with CSR chipset
> Date: Wed, 27 Jul 2005 20:54:48 +0200
> Reply-To: [email protected]
>
> On Wednesday 27 July 2005 19:11, andy thomas wrote:
>> One thing puzzles me - back in March this year, Erwin Authried wrote
>> in this mailing list that PCMCIA/CF UARTs are register-compatible
>> emulations of a standard UART (see original mail below). Does this
>> mean that I could be using just the serial_cs.o kernel module for the
>> Socket CF+ card?
>
> Yes. I do it on my Zaurus.
Success! This seems to work - serial_cs is loaded as soon as I insert the
Socket Bluetooth card and setserial reports that it is now on ttyS1
# setserial /dev/ttyS1
/dev/ttyS1, UART: 16950/954, Port: 0x02f8, IRQ: 3
I now load the bluez, l2cap, hci_uart kernel modules and start the HCI
daemon, hcid - no errors are reported in either the messages or syslog
logs. Then I try to attach the UART at /dev/ttyS1 with hciattach
using the bcsp protocol that is supported by the CSR chipset but it times
out:
# hciattach ttyS1 bcsp 19200 flow
BCSP initialization timed out
hciattach seems to ignore the -t <timeout> parameter - if I set it to 240
second, it still times out after 10 seconds. Now, if I instead attach the
UART using 'any' instead of 'bcsp', then it does indeed attach:
# hciattach -t240 ttyS1 any 19200 flow
# hciconfig -a
hci0: Type: UART
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:236 acl:0 sco:0 events:0 errors:236
TX bytes:4 acl:0 sco:0 commands:1 errors:0
but the interface won't come up:
# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
and there are a lot of error messages in the syslog about the h4
protocol:
Jul 28 12:06:54 latitude kernel: h4_recv: Unknown HCI packet type 60
Jul 28 12:06:54 latitude kernel: h4_recv: Unknown HCI packet type 28
What am I doing wrong? Also, is there any way to detach the UART if it has
been attached, without rebooting the laptop?
Andy
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On Thu, 28 Jul 2005, Wolfgang M?es wrote:
> On Thursday 28 July 2005 13:10, andy thomas wrote:
>> # hciattach ttyS1 bcsp 19200 flow
>
> ommit the baud rate and the "flow" parameter. It is done automaticly.
> Baud rate is set to 230K. Other won't work.
Ah, I thought I'd try a low baud rate to begin with. But it still times
out if I use the 'bcsp' parameter although if I use 'any' then the hci0
device is registered:
# hciattach ttyS1 any
# hciconfig -a
hci0: Type: UART
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:2086 acl:0 sco:0 events:6 errors:168
TX bytes:4 acl:0 sco:0 commands:1 errors:0
but it still won't come up.
# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
Maybe there is something wrong with my hcid.conf? I note that there is no
BD address defined in the 'hciconfig -a' report above. Or perhaps I need
to enable support in the kernel for the 'h4' protocol although I thought
this protocol was no longer recommended for CSR-chipset cards.
Many thanks,
Andy
On Thursday 28 July 2005 13:10, andy thomas wrote:
> # hciattach ttyS1 bcsp 19200 flow
ommit the baud rate and the "flow" parameter. It is done automaticly.
Baud rate is set to 230K. Other won't work.
best regards
Wolfgang
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On 28.07.05 13:08:13, andy thomas wrote:
> Ah, I thought I'd try a low baud rate to begin with. But it still times
> out if I use the 'bcsp' parameter although if I use 'any' then the hci0
> device is registered:
>
> # hciattach ttyS1 any
> # hciconfig -a
> hci0: Type: UART
> BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
> DOWN
> RX bytes:2086 acl:0 sco:0 events:6 errors:168
> TX bytes:4 acl:0 sco:0 commands:1 errors:0
>
> but it still won't come up.
>
> # hciconfig hci0 up
> Can't init device hci0: Connection timed out (110)
if you're using a 2.6 kernel: did you apply the patch for the serial
driver I posted here some time ago? had the same problems before.
Regards,
Mathias
--
Perfection is achieved not when you have nothing more to add,
but when you have nothing left to take away.
- Antoine de Saint-Exupery
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users