[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bluetooth-dev] [PATCH] Brainbox 620 Pcmcia card at 921600 baud
- To: Johan Adolfsson <firstname.lastname@example.org>
- Subject: Re: [bluetooth-dev] [PATCH] Brainbox 620 Pcmcia card at 921600 baud
- From: Jean Tourrilhes <email@example.com>
- Date: Wed, 31 Oct 2001 09:58:14 -0800
- Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
- Cc: firstname.lastname@example.org, "'Ulrich M?ller'" <email@example.com>, Peter Kjellerstedt <firstname.lastname@example.org>, email@example.com
- E-mail: firstname.lastname@example.org
- In-Reply-To: <email@example.com>; from firstname.lastname@example.org on Wed, Oct 31, 2001 at 11:19:24AM +0100
- Organisation: HP Labs Palo Alto
- References: <20011030135731.A30752@xxxxxxx.com> <email@example.com>
- Reply-To: firstname.lastname@example.org
- Sender: email@example.com
- User-Agent: Mutt/1.2.5i
On Wed, Oct 31, 2001 at 11:19:24AM +0100, Johan Adolfsson wrote:
> I don't know if it will work for you, but I added support to OpenBT
> to specifiy the baudrate as "baudbase/divisor" that will use the
> SETSERIAL ioctl() to specify baudbase and custom _divisor.
> In theory you shouldn't need setserial but I guess it only works if
> the driver knows how to change to the correct baudbase...
You have to be careful there. The baudbase and custom divisor
is a property of the UART, not of the BlueTooth chip, and the two
things are orthogonal. You may have a CSR chip mated with a wide
variety of UARTs (example : the Brainboxes Pcmcia and CF cards use two
totally different UARTs, and the Casira board will use the regular
In the case of the Brainboxes Pcmcia card, it make sense to
change the baud_base *only* if you set the WMSR to the corresponding
value. In other words, if you add support for baud_base but not WMSR,
the result will be undefined. But this is specific to this precise
implementation of the UART.
I don't know what's the proper approach here. My approach was
that before to start the BlueTooth stack, it was the responsability of
the user (or whatever init script) to put the UART in a sensible
configuration through setserial.
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org