Messages in this thread | | | Subject | Re: [SERIAL] Don't optimise away baud rate changes when BOTHER is used | From | David Woodhouse <> | Date | Fri, 08 Jun 2007 12:01:07 +0100 |
| |
On Thu, 2007-06-07 at 23:54 +0100, Alan Cox wrote: > If it doesn't only involve editing the header files for this case (and > maybe needing a define to indicate old==new) then the tty layer wants > fixing to sort that out. Its on my todo list.
It works fine. The only problem is that if I set a _standard_ baud rate with BOTHER and then read it back with something that doesn't grok BOTHER, I get it back just as I set it.
[root@pegasos ~]# ./testit1 Get: c_flag 0x1f0b1f(31,31), ispeed 38400, ospeed 38400 [root@pegasos ~]# stty speed 0 baud; line = 0;
It might be better if it was returning B38400, rather than BOTHER. Should we be using tty_termios_encode_baud_rate() for TCGETS()?
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |