mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Aleksander Morgado <aleksander@aleksander.es>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] sandbox: new --stdinout option to enable a bidirectional console
Date: Tue, 6 Jun 2017 09:00:19 +0200	[thread overview]
Message-ID: <CAAP7ucL3sUqHfDxgTN86KgjbB_pBR1kktVOpNKRz=0f4=gN41w@mail.gmail.com> (raw)
In-Reply-To: <20170606065321.rlogztxfb4l4ap5e@pengutronix.de>

On Tue, Jun 6, 2017 at 8:53 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>> In addition to allowing read-only and write-only consoles with --stdin
>> and --stdout, we now allow bidirectional read/write consoles with FIFO
>> files. This is e.g. to allow doing RATP over the FIFO based consoles.
>>
>> Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
>> ---
>>  arch/sandbox/os/common.c | 53 ++++++++++++++++++++++++++++++++++++++----------
>>  1 file changed, 42 insertions(+), 11 deletions(-)
>
> Applied, thanks.
>
> Have you tried RATP over the FIFO consoles? Does it work as expected?

Not completely, because the pyserial backend in bbremote didn't want
FIFOs, but I did try with my own minimal RATP implementation and it
did work ok up to where I tested.

-- 
Aleksander
https://aleksander.es

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-06-06  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 12:01 Aleksander Morgado
2017-06-06  6:53 ` Sascha Hauer
2017-06-06  7:00   ` Aleksander Morgado [this message]

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='CAAP7ucL3sUqHfDxgTN86KgjbB_pBR1kktVOpNKRz=0f4=gN41w@mail.gmail.com' \
    --to=aleksander@aleksander.es \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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