lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 2 Nov 2017 18:44:11 +0000
From:   Alan Cox <gnomes@...rguk.ukuu.org.uk>
To:     "Theodore Ts'o" <tytso@....edu>
Cc:     Paul Menzel <pmenzel+linux-serial@...gen.mpg.de>,
        linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Is 115200 still the maximum baudrate?

On Thu, 2 Nov 2017 13:13:55 -0400
"Theodore Ts'o" <tytso@....edu> wrote:

> On Thu, Nov 02, 2017 at 04:42:56PM +0100, Paul Menzel wrote:
> > 
> > The Linux serial console documentation [1] says that 115200 is the maximum
> > supported baudrate.
> >   
> > > The maximum baudrate is 115200.  
> > 
> > Is that still accurate? If yes, where should I look to support higher
> > values?  
> 
> See the setserial man page and the spd_* options:

Those have been obsolete for over a decade and doesn't work on all
devices.

The core Linux code supports arbitrary baud rate setting. Although it was
designed with the glibc maintainers at the time it seems they never
adopted it so you have do the following Linux specific:


	struct termios t;

	iotl(tty, TCGETS2, &t);
	t.c_flag &= ~CBAUD;
	t.c_flag |= BOTHER;
	t.c_ispeed = input baud;
	t.c_ospeed = output baud;
	ioctl(tty, TCSETS2, &t);


and it'll let you ask for any speed you want including things like midi
baud rates. 76Kbit for ESP8266 devices and so on.

After the calls check the c_ispeed/c_ospeed to see what you got.

Alan

Powered by blists - more mailing lists