On 2011-04-06, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, 6 Apr 2011 16:48:49 +0000 (UTC)
> Grant Edwards <grant.b.edwards@xxxxxxxxx> wrote:
>
>> I'm working on a driver for a serial board that supports 921600 bps,
>> and it would be awfully nice if there was a way to specify that using
>> the ASYNC_SPD_xxxxx mechanism. Is there any reason why this wouldn't
>> work?
>
> The ASYNC_SPD_xxxx mechanism is obsolete.
I know -- unfortunately, so are many customer applications.
> Just set the baud rate to 921600, the kernel has supported arbitary
> baud rates for some time.
Yep, but there are customers with existing, fielded, applications that
depend on the ASYNC_SPD_xxxx mechanism to map 38400 to <whatever>
[where <whatever> is determined by the SPD_xxxx flags controlled by
setserial].
In the past, we've provided a customized version of setserial that
supported a SPD_WARP13 flag setting for 921600, but it only worked
with a particular driver. I'd like to ditch that and in future use
the standard setserial and standard SPD_xxxx flags. But, there is no
standard way to set flags for 921600.
I could tell them to go the SPD_CUST route to get 921600, but I was
hoping to provide an option that would support 921600 the same way
that 57600, 230400, and 460800 are supported.
--
Grant Edwards grant.b.edwards Yow! I'm dressing up in
at an ill-fitting IVY-LEAGUE
gmail.com SUIT!! Too late...
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
