1
0
mirror of https://sourceware.org/git/glibc.git synced 2026-10-24 01:33:52 +03:00
Files
glibc/include
H. Peter Anvin (Intel) 5f138519eb termios: add new baud_t interface, defined to be explicitly numeric
Add an explicitly numeric interface for baudrate setting. For glibc,
this only announces what is a fair accompli, but this is a plausible
way forward for standardization, and may be possible to infill on
non-compliant systems. The POSIX committee has stated:

[https://www.austingroupbugs.net/view.php?id=1916#c7135]

	A future version of this standard is expected to add at least
	the following symbolic constants for use as values of objects
	of type speed_t: B57600, B115200, B230400, B460800, and
	B921600.

	Implementations are encouraged to propose additional
	interfaces which will make it possible to set and query a
	wider range of speeds than just those enumerated by the
	constants beginning with B. If a set of common interfaces
	emerges between several implementations, a future version of
	this standard will likely add those interfaces.

This is exactly that interface.

The use of the term "baud" is due to the need to have a term
contrasting "speed", and it is already well established as a legacy
term -- including in the names of the legacy Bxxx
constants. Futhermore, it *is* valid from the point of view that the
termios interface fundamentally emulates an RS-232 serial port as far
as the application software is concerned.

The documentation states that for the current version of glibc,
speed_t == baud_t, but explicitly declares that this may not be the
case in the future.

Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2025-06-17 09:11:38 -03:00
..
…
…
…
…
2021-06-22 12:09:52 -03:00
…
…
2023-05-01 19:33:21 +02:00
2025-01-28 18:25:13 +01:00
…
…
2021-06-15 10:42:11 -03:00
2021-06-15 10:42:11 -03:00
…
…
…
…
…
…
2021-07-22 18:38:04 +05:30
…
…
…
…
2021-06-30 08:43:37 +02:00
2023-10-24 12:30:59 +02:00
2023-05-01 09:08:59 -04:00
2019-05-02 11:42:51 +02:00
…
2023-10-24 12:30:59 +02:00
2019-10-09 17:48:41 -03:00
…
2024-01-03 12:07:14 +00:00
2024-04-10 14:53:39 -03:00
…
…
…
…
…
…
…
…
2021-06-30 08:43:37 +02:00
2019-11-06 09:20:52 -03:00
2024-02-01 11:02:01 +00:00
…
…