mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: christian.buettner@rafi.de
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Antwort: Re: Antwort: Re: barebox JSON
Date: Mon, 16 Apr 2012 14:26:20 +0200	[thread overview]
Message-ID: <OFE1B60695.7A4CF434-ONC12579E2.0043DD1E-C12579E2.004453E0@o0802.rafi.inhouse> (raw)
In-Reply-To: <20120416121937.GR3852@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 1429 bytes --]

Ok, thank you anyway..
We have a plan to 'remote control' barebox.. Would have been good, if i 
wasn't the first doing this ;)

- christian



Von:    Sascha Hauer <s.hauer@pengutronix.de>
An:     christian.buettner@rafi.de
Kopie:  Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>, 
barebox@lists.infradead.org
Datum:  16.04.2012 14:19
Betreff:        Re: Antwort: Re: barebox JSON



On Mon, Apr 16, 2012 at 01:52:33PM +0200, christian.buettner@rafi.de 
wrote:
> The advantage is a generic interface used in mass production.
> 
> I formulate my question in another way.
> Is there an approach launching a little tool, that listens to UART or 
> Ethernet when the bootloader starts.
> The tool is kind of an dispatcher, using an incoming message to start 
e.g. 
> an update of the kernel.

Well we have UART console and network console, you can use something
like kermit or expect to remote control barebox.

I know this sucks and is not what you wanted to hear, but currently this
is all we have.

I more than once thought about a real machine interface to barebox, but
I have no good idea how to do this.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


[-- Attachment #1.2: Type: text/html, Size: 2664 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

  reply	other threads:[~2012-04-16 12:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 10:01 christian.buettner
2012-04-16 11:11 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-16 11:52   ` Antwort: " christian.buettner
2012-04-16 12:19     ` Sascha Hauer
2012-04-16 12:26       ` christian.buettner [this message]
2012-04-16 12:22         ` Antwort: " Jean-Christophe PLAGNIOL-VILLARD
2012-04-16 12:52           ` Antwort: " christian.buettner
2012-04-16 12:46             ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-16 12:53         ` Eric Bénard
2012-04-16 13:10           ` Antwort: " christian.buettner
2012-04-16 15:03           ` tftpserver christian.buettner
2012-04-23  7:06             ` tftpserver Jean-Christophe PLAGNIOL-VILLARD
2012-04-23  7:24             ` tftpserver Franck Jullien
2012-04-19 10:59       ` Antwort: Re: Antwort: Re: barebox JSON christian.buettner
2012-04-19 11:32         ` Jean-Christophe PLAGNIOL-VILLARD

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=OFE1B60695.7A4CF434-ONC12579E2.0043DD1E-C12579E2.004453E0@o0802.rafi.inhouse \
    --to=christian.buettner@rafi.de \
    --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