From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/7] scripts: kwboot: various improvements
Date: Wed, 28 Sep 2016 20:50:10 +0200 [thread overview]
Message-ID: <20160928185017.25002-1-u.kleine-koenig@pengutronix.de> (raw)
Hello,
this series is the result of my efforts to make UART booting on an
Netgear ReadyNAS 2120 work.
Best regards
Uwe
Uwe Kleine-König (7):
scripts: kwboot: try to resync on packet boundary after receiving a
NAK
scripts: kwboot: flush input and output only once
scripts: kwboot: improve diagnostic output
scripts: kwboot: shorten delay between two boot messages
scripts: kwboot: simplify kwboot_mmap_image
scripts: kwboot: set boot source to UART before sending
images: mvebu: don't generate uart images
images/Makefile.mvebu | 29 ---------------
scripts/kwboot.c | 101 +++++++++++++++++++++++++++++++++++++++-----------
2 files changed, 80 insertions(+), 50 deletions(-)
--
2.9.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2016-09-28 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 18:50 Uwe Kleine-König [this message]
2016-09-28 18:50 ` [PATCH 1/7] scripts: kwboot: try to resync on packet boundary after receiving a NAK Uwe Kleine-König
2016-09-28 18:50 ` [PATCH 2/7] scripts: kwboot: flush input and output only once Uwe Kleine-König
2016-09-28 18:50 ` [PATCH 3/7] scripts: kwboot: improve diagnostic output Uwe Kleine-König
2016-09-28 18:50 ` [PATCH 4/7] scripts: kwboot: shorten delay between two boot messages Uwe Kleine-König
2016-09-28 18:50 ` [PATCH 5/7] scripts: kwboot: simplify kwboot_mmap_image Uwe Kleine-König
2016-09-28 18:50 ` [PATCH 6/7] scripts: kwboot: set boot source to UART before sending Uwe Kleine-König
2016-09-28 18:50 ` [PATCH 7/7] images: mvebu: don't generate uart images Uwe Kleine-König
2016-10-04 6:05 ` [PATCH 0/7] scripts: kwboot: various improvements Sascha Hauer
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=20160928185017.25002-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox