linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-api@vger.kernel.org, libc-alpha@sourceware.org,
	linuxppc-dev@lists.ozlabs.org, hpa@zytor.com
Subject: Re: [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339]
Date: Thu, 11 Apr 2019 09:53:30 -0300	[thread overview]
Message-ID: <db468a0f-4a7b-d251-601f-428885275d08@linaro.org> (raw)
In-Reply-To: <87imvker6t.fsf@oldenburg2.str.redhat.com>



On 11/04/2019 08:07, Florian Weimer wrote:
> * Adhemerval Zanella:
> 
>> This allows us to adjust the baud rates to non-standard values using termios
>> interfaces without to resorting to add new headers and use a different API
>> (ioctl).
> 
> How much symbol versioning will be required for this change?

I think all interfaces that have termios as input for sparc and mips 
(tcgetattr, tcsetattr, cfmakeraw, cfgetispeed, cfgetospeed, cfsetispeed,
cfsetospeed, cfsetspeed).

Alpha will also need to use termios1 for pre-4.20 kernels.

> 
>> As Peter Anvin has indicated, he create a POC [1] with the aforementioned
>> new interfaces.  It has not been rebased against master, more specially against
>> my termios refactor to simplify the multiple architecture header definitions,
>> but I intend to use as a base.
> 
> Reference [1] is still missing. 8-(

Oops... it is https://git.zytor.com/users/hpa/glibc/termbaud.git/log/?h=wip.termbaud

> 
> Thanks,
> Florian
> 

  reply	other threads:[~2019-04-11 13:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 10:47 [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339] Florian Weimer
2019-04-09 15:02 ` hpa
2019-04-10  6:50   ` Florian Weimer
2019-04-15 15:54     ` hpa
2019-04-09 15:07 ` hpa
2019-04-09 16:04   ` Florian Weimer
2019-04-10 20:24 ` Adhemerval Zanella
2019-04-11 11:07   ` Florian Weimer
2019-04-11 12:53     ` Adhemerval Zanella [this message]
2019-04-12  7:50       ` Florian Weimer
2019-04-15 12:28         ` Florian Weimer
2019-04-15 15:53         ` hpa
2019-04-15 17:22           ` Adhemerval Zanella
2019-04-17 22:04             ` H. Peter Anvin
2019-04-18 11:09               ` Adhemerval Zanella
2019-04-18 14:46                 ` hpa
2019-04-16  9:59           ` Florian Weimer
2019-04-16 12:11             ` Adhemerval Zanella
2019-04-17 22:06             ` H. Peter Anvin
2019-04-17 21:22 ` Joseph Myers

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=db468a0f-4a7b-d251-601f-428885275d08@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=hpa@zytor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).