Antwort: Re: barebox JSON

From: christian.buettner@rafi.de
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Antwort: Re: barebox JSON
Date: Mon, 16 Apr 2012 13:52:33 +0200	[thread overview]
Message-ID: <OF8CCAF0FB.FEC72171-ONC12579E2.004009D2-C12579E2.00413C07@o0802.rafi.inhouse> (raw)
In-Reply-To: <20120416111108.GV30672@game.jcrosoft.org>

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

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.

- christian

Von:    Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
An:     christian.buettner@rafi.de
Kopie:  barebox@lists.infradead.org
Datum:  16.04.2012 13:29
Betreff:        Re: barebox JSON

On 12:01 Mon 16 Apr     , christian.buettner@rafi.de wrote:
>    hi all,
> 
>    is there allready an approach to accept JSON messages through a UART 
or
>    Ethernet interface?
>    I am thinking of an update mechanism in the bootloader, beeing able 
to
>    exchange the kernel, rootfs or change env settings..
JSON no

but you can use script to do it other container

and protocol like xyzmodem /nfs and co so what is the advantage of JSON?

Best Regards,
J.
> 
>    - christian

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

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

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

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