From: Tilman Schmidt <tilman@imap.cc>
To: LKML <linux-kernel@vger.kernel.org>, linux-serial@vger.kernel.org
Subject: struct termios/termios2 rationale and usage
Date: Thu, 27 Mar 2008 12:23:08 +0100 [thread overview]
Message-ID: <47EB839C.8070605@imap.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
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@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
reply other threads:[~2008-03-27 11:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47EB839C.8070605@imap.cc \
--to=tilman@imap.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox