On Wednesday 22 Oct 2003 09:18, Marcel Holtmann wrote:
> Hi Brad,
>
> > if the hciattach command is "hciattach /dev/ttyS1 socket" then what
> > should I put in the uart {} section in hcid.conf to make it automatic?
>
> the hcid.conf has no uart section. You must use one of the PCMCIA
> scripts. The /etc/pcmcia/bluetooth can do this if your cardmgr is new
> enough. If not, then you have to hack it into the serial script.
We have found on the Sharp Zaurus (linux PDA) that the Socket G card must
first be recognised as a serial card, which means leaving the ident
information out of /etc/pcmcia/bluetooth.conf and then manually run
hciattach /dev/ttyS3 bcsp 230400
followed by
modprobe hci_uart
If it has the appropriate entry in /etc/pcmcia/bluetooth.conf and is bound
with hci_uart this way, then the serial part does not get initialised and the
hciattach call fails.
I am currently trying to work on a way that automates this, but without
hacking /etc/pcmcia/serial I can't see how to do this. Perhaps the whole of /
etc/pcmcia/serial must be included in /etc/pcmcia/bluetooth for serial cards?
(Just running '/etc/pcmcia/serial start ttyS3' in the bluetooth script gives
the serial script usage output on the Zaurus)
--
Colin Pinkney
http://www.cpinkney.org.uk
-------------------------------------------------------
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
|
