From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems
Date: Sun, 2 Apr 2017 17:41:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1704021729470.1847@knanqh.ubzr> (raw)
In-Reply-To: <87pogur0y9.fsf@firstfloor.org>
On Sun, 2 Apr 2017, Andi Kleen wrote:
> Nicolas Pitre <nicolas.pitre@linaro.org> writes:
> >
> > Of course, making it "mini" means there are limitations to what it does:
> >
> > - This supports serial ports only. No VT's, no PTY's.
>
> No PTYs seems like a big limitation. This means no sshd?
Again, my ultimate system target is in the sub-megabyte of RAM. I
really doubt you'll be able to fit an SSH server in there even if PTYs
were supported, unless sshd (or dropbear) can be made really tiny.
Otherwise you most probably have sufficient resources to run the regular
TTY code.
That being said, maybe there could be a way to cheaply support PTYs. I
just didn't investigate it.
> > But again, most small embedded systems simply don't need those things.
>
> They don't need a (debug) way to login over the network? Hard to
> believe.
This most likely won't be via a standard shell.
Nicolas
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems
Date: Sun, 2 Apr 2017 17:41:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1704021729470.1847@knanqh.ubzr> (raw)
In-Reply-To: <87pogur0y9.fsf@firstfloor.org>
On Sun, 2 Apr 2017, Andi Kleen wrote:
> Nicolas Pitre <nicolas.pitre@linaro.org> writes:
> >
> > Of course, making it "mini" means there are limitations to what it does:
> >
> > - This supports serial ports only. No VT's, no PTY's.
>
> No PTYs seems like a big limitation. This means no sshd?
Again, my ultimate system target is in the sub-megabyte of RAM. I
really doubt you'll be able to fit an SSH server in there even if PTYs
were supported, unless sshd (or dropbear) can be made really tiny.
Otherwise you most probably have sufficient resources to run the regular
TTY code.
That being said, maybe there could be a way to cheaply support PTYs. I
just didn't investigate it.
> > But again, most small embedded systems simply don't need those things.
>
> They don't need a (debug) way to login over the network? Hard to
> believe.
This most likely won't be via a standard shell.
Nicolas
next prev parent reply other threads:[~2017-04-02 21:41 UTC|newest]
Thread overview: 103+ 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 ` 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 ` 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 ` Nicolas Pitre
2017-04-01 22:21 ` [PATCH v2 3/5] serial: small Makefile reordering Nicolas Pitre
2017-04-01 22:21 ` Nicolas Pitre
2017-04-02 12:55 ` Andy Shevchenko
2017-04-02 12:55 ` Andy Shevchenko
2017-04-02 15:49 ` Nicolas Pitre
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-01 22:21 ` Nicolas Pitre
2017-04-02 13:16 ` Andy Shevchenko
2017-04-02 13:16 ` Andy Shevchenko
2017-04-02 15:44 ` Nicolas Pitre
2017-04-02 15:44 ` Nicolas Pitre
2017-04-03 7:35 ` kbuild test robot
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-01 22:21 ` 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 13:22 ` Andy Shevchenko
2017-04-02 15:55 ` Nicolas Pitre
2017-04-02 15:55 ` Nicolas Pitre
2017-04-03 12:56 ` Alan Cox
2017-04-03 12:56 ` Alan Cox
2017-04-03 16:06 ` Nicolas Pitre
2017-04-03 16:06 ` Nicolas Pitre
2017-04-03 16:06 ` Nicolas Pitre
2017-04-03 18:05 ` Alan Cox
2017-04-03 18:05 ` Alan Cox
2017-04-03 19:50 ` Nicolas Pitre
2017-04-03 19:50 ` Nicolas Pitre
2017-04-04 13:40 ` Alan Cox
2017-04-04 13:40 ` Alan Cox
2017-04-04 19:26 ` Nicolas Pitre
2017-04-04 19:26 ` Nicolas Pitre
2017-04-02 20:47 ` Andi Kleen
2017-04-02 20:47 ` Andi Kleen
2017-04-02 21:41 ` Nicolas Pitre [this message]
2017-04-02 21:41 ` Nicolas Pitre
2017-04-02 22:44 ` Stuart Longland
2017-04-02 22:44 ` Stuart Longland
2017-04-02 22:44 ` Stuart Longland
2017-04-03 1:01 ` Nicolas Pitre
2017-04-03 1:01 ` Nicolas Pitre
2017-04-04 0:39 ` Stuart Longland
2017-04-04 0:39 ` Stuart Longland
2017-04-04 0:39 ` Stuart Longland
2017-04-03 18:14 ` Geert Uytterhoeven
2017-04-03 18:14 ` Geert Uytterhoeven
2017-04-03 18:14 ` Geert Uytterhoeven
2017-04-03 18:57 ` Rob Herring
2017-04-03 18:57 ` Rob Herring
2017-04-03 18:57 ` Rob Herring
2017-04-03 19:46 ` Geert Uytterhoeven
2017-04-03 19:46 ` Geert Uytterhoeven
2017-04-03 19:46 ` Geert Uytterhoeven
2017-04-03 21:05 ` Andy Shevchenko
2017-04-03 21:05 ` Andy Shevchenko
2017-04-03 21:05 ` Andy Shevchenko
2017-04-04 16:59 ` Tom Zanussi
2017-04-04 16:59 ` Tom Zanussi
2017-04-04 16:59 ` Tom Zanussi
2017-04-04 17:08 ` Andy Shevchenko
2017-04-04 17:08 ` Andy Shevchenko
2017-04-04 17:08 ` Andy Shevchenko
2017-04-04 17:59 ` Tom Zanussi
2017-04-04 17:59 ` Tom Zanussi
2017-04-04 17:59 ` Tom Zanussi
2017-04-04 18:04 ` Andy Shevchenko
2017-04-04 18:04 ` Andy Shevchenko
2017-04-04 18:04 ` Andy Shevchenko
2017-04-04 18:31 ` Nicolas Pitre
2017-04-04 18:31 ` Nicolas Pitre
2017-04-04 18:31 ` Nicolas Pitre
2017-04-04 19:58 ` Tom Zanussi
2017-04-04 19:58 ` Tom Zanussi
2017-04-04 19:58 ` Tom Zanussi
2017-04-04 20:27 ` Nicolas Pitre
2017-04-04 20:27 ` Nicolas Pitre
2017-04-04 20:27 ` Nicolas Pitre
2017-04-04 18:53 ` Nicolas Pitre
2017-04-04 18:53 ` Nicolas Pitre
2017-04-04 18:53 ` Nicolas Pitre
2017-04-03 7:54 ` Andy Shevchenko
2017-04-03 7:54 ` Andy Shevchenko
2017-04-03 15:31 ` Andi Kleen
2017-04-03 15:31 ` Andi Kleen
2017-04-03 17:27 ` Nicolas Pitre
2017-04-03 17:27 ` Nicolas Pitre
2017-04-03 19:57 ` Adam Borowski
2017-04-03 19:57 ` Adam Borowski
2017-04-03 20:09 ` Nicolas Pitre
2017-04-03 20:09 ` Nicolas Pitre
2017-04-03 20:32 ` Adam Borowski
2017-04-03 20:32 ` Adam Borowski
2017-04-03 16:40 ` Nicolas Pitre
2017-04-03 16:40 ` Nicolas Pitre
2017-04-03 7:44 ` Greg Kroah-Hartman
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=alpine.LFD.2.20.1704021729470.1847@knanqh.ubzr \
--to=nicolas.pitre@linaro.org \
--cc=andi@firstfloor.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.