Hi Brad,
> thanks for the reply.
>
> > I discovered that I have the infamous "G" aka 2.5 model of this socket
> > cf bluetooth card, so dtl1_cs doesn't help me.
> >
> > # hciattach /dev/ttyS1 socket
> > Can't set device: Protocol not supported
> > Can't initialize device: Illegal seek
> >
> > Cardmgr seems to have the serial port wrong. Could that be part of it?
> >
> > Oct 17 07:14:35 jab cardmgr[12540]: socket 1: Serial or Modem
> > Oct 17 07:14:35 jab cardmgr[12540]: executing: './serial start ttyS3'
>
>
> if cardmgr says it is ttyS3, why don't you try it?
>
> the output from cardmgr now agrees with the kernel. ttyS1. Not sure when
> it started agreeing. The error when I run hciattach is the same. I did
> patch the stock 2.4.22 kernel with the bluez drivers patch (the new kernel
> reports itself as 2.4.22-mh1) but it didn't help with the hciattach. (and
> anyway the changelog wasn't suggesting it would help)
>
> FWIW, I called socket presales and simply asked them how I could buy a
> model 'F' card. They didn't seem to know that no one (who's talking) has
> gotten it working in Linux. I pointed out the thread in their discussion
> boards in which several people report it doesn't work. Socket was supposed
> to get back with me and tell me if they had any left.
the card should work with the hci_uart.o driver. Is this driver loaded?
You need at least these options activated in your kernel
CONFIG_BLUEZ_HCIUART=m
CONFIG_BLUEZ_HCIUART_H4=y
CONFIG_BLUEZ_HCIUART_BCSP=y
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
|
