From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.rafi.de ([178.15.151.13]) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1SJikT-0004Yf-2e for barebox@lists.infradead.org; Mon, 16 Apr 2012 10:01:30 +0000 MIME-Version: 1.0 Message-ID: From: christian.buettner@rafi.de Date: Mon, 16 Apr 2012 12:01:22 +0200 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1361740564381052891==" Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: barebox JSON To: barebox@lists.infradead.org Dies ist eine mehrteilige Nachricht im MIME-Format. --===============1361740564381052891== Content-Type: multipart/alternative; boundary="=_alternative 00370E2BC12579E2_=" Dies ist eine mehrteilige Nachricht im MIME-Format. --=_alternative 00370E2BC12579E2_= Content-Type: text/plain; charset="US-ASCII" 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.. - christian --=_alternative 00370E2BC12579E2_= Content-Type: text/html; charset="US-ASCII" 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..

- christian --=_alternative 00370E2BC12579E2_=-- --===============1361740564381052891== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox --===============1361740564381052891==--