From: andy.shevchenko@gmail.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems
Date: Tue, 4 Apr 2017 21:04:24 +0300 [thread overview]
Message-ID: <CAHp75VfQVdMRZnbDFyH9m=HfSuoiUxqhf2y+H07u4u6xPd7DUA@mail.gmail.com> (raw)
In-Reply-To: <1491328749.7125.66.camel@tzanussi-mobl.amr.corp.intel.com>
On Tue, Apr 4, 2017 at 8:59 PM, Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> On Tue, 2017-04-04 at 20:08 +0300, Andy Shevchenko wrote:
>> On Tue, Apr 4, 2017 at 7:59 PM, Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
>> > On Tue, 2017-04-04 at 00:05 +0300, Andy Shevchenko wrote:
>> > I was focused at that point mainly on the kernel static size, and using
>> > a combination of Josh Triplett's tinification tree, Andi Kleen's LTO and
>> > net-diet patches, and my own miscellaneous patches that I was planning
>> > on eventually upstreaming, I ended up with a system that I could boot to
>> > shell with a 455k text size:
>> >
>> > Memory: 235636K/245176K available (455K kernel code, 61K rwdata,
>> > 64K rodata, 132K init, 56K bss, 3056K reserved, 0K cma-reserved)
>> Thanks for sharing your experience. The question closer to this
>> discussion what did you do against TTY/UART/(related) layer(s)?
>>
>
> I'd have to go back and take a look, but nothing special AFIAR.
>
> No patches or hacks along those lines, and the only related thing I see
> as far as config is:
>
> cfg/pty-disable.scc \
>
> which maps to:
>
> # CONFIG_UNIX98_PTYS is not set
But on your guestimation how much can we squeeze TTY/UART layer if we
do some compile-time configuration?
Does it even make sense or better to introduce something like minitty
special layer instead?
I believe you did some research during time of that project?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2017-04-04 18:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 22:21 [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems Nicolas Pitre
2017-04-01 22:21 ` [PATCH v2 1/5] console: move console_init() out of tty_io.c Nicolas Pitre
2017-04-01 22:21 ` [PATCH v2 2/5] tty: move baudrate handling code to a file of its own Nicolas Pitre
2017-04-01 22:21 ` [PATCH v2 3/5] serial: small Makefile reordering Nicolas Pitre
2017-04-02 12:55 ` Andy Shevchenko
2017-04-02 15:49 ` Nicolas Pitre
2017-04-01 22:21 ` [PATCH v2 4/5] serial: split generic UART driver helper functions into a separate file Nicolas Pitre
2017-04-02 13:16 ` Andy Shevchenko
2017-04-02 15:44 ` Nicolas Pitre
2017-04-03 7:35 ` kbuild test robot
2017-04-01 22:21 ` [PATCH v2 5/5] minitty: minimal TTY support alternative for serial ports Nicolas Pitre
2017-04-02 13:22 ` [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems Andy Shevchenko
2017-04-02 15:55 ` Nicolas Pitre
2017-04-03 12:56 ` Alan Cox
2017-04-03 16:06 ` Nicolas Pitre
2017-04-03 18:05 ` Alan Cox
2017-04-03 19:50 ` Nicolas Pitre
2017-04-04 13:40 ` Alan Cox
2017-04-04 19:26 ` Nicolas Pitre
2017-04-02 20:47 ` Andi Kleen
2017-04-02 21:41 ` Nicolas Pitre
2017-04-02 22:44 ` Stuart Longland
2017-04-03 1:01 ` Nicolas Pitre
2017-04-04 0:39 ` Stuart Longland
2017-04-03 18:14 ` Geert Uytterhoeven
2017-04-03 18:57 ` Rob Herring
2017-04-03 19:46 ` Geert Uytterhoeven
2017-04-03 21:05 ` Andy Shevchenko
2017-04-04 16:59 ` Tom Zanussi
2017-04-04 17:08 ` Andy Shevchenko
2017-04-04 17:59 ` Tom Zanussi
2017-04-04 18:04 ` Andy Shevchenko [this message]
2017-04-04 18:31 ` Nicolas Pitre
2017-04-04 19:58 ` Tom Zanussi
2017-04-04 20:27 ` Nicolas Pitre
2017-04-04 18:53 ` Nicolas Pitre
2017-04-03 7:54 ` Andy Shevchenko
2017-04-03 15:31 ` Andi Kleen
2017-04-03 17:27 ` Nicolas Pitre
2017-04-03 19:57 ` Adam Borowski
2017-04-03 20:09 ` Nicolas Pitre
2017-04-03 20:32 ` Adam Borowski
2017-04-03 16:40 ` Nicolas Pitre
2017-04-03 7:44 ` Greg Kroah-Hartman
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='CAHp75VfQVdMRZnbDFyH9m=HfSuoiUxqhf2y+H07u4u6xPd7DUA@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).