linux-kernel - struct termios/termios2 rationale and usage

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <47EB839C.8070605@imap.cc>
Date:	Thu, 27 Mar 2008 12:23:08 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	LKML <linux-kernel@...r.kernel.org>, linux-serial@...r.kernel.org
Subject: struct termios/termios2 rationale and usage

I'm currently trying to conceive of a way to portably use the "new"
(relatively) way of setting serial line bit rates via BOTHER and
c_ispeed/c_ospeed from a userspace utility. (ldattach(1), to be
included in the next release of util_linux_ng, in case you're
interested.) I notice that most architectures have introduced
new ioctls (TCGETS2 etc.) and struct termios2 for that, while some
(eg. powerpc) have integrated the c_ispeed/c_ospeed fields in
struct termios and supposedly get/set them via the old "non-2"
ioctls.

What's the rationale behind this? What is the recommended usage
for a Linux userspace program wanting to use the BOTHER speed
setting mechanism on a variety of architectures?

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)