From: JPT <j-p-t@gmx.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] offer: program to deal with kirkwood "boot from UART"
Date: Fri, 12 Apr 2013 14:27:37 +0200 [thread overview]
Message-ID: <5167FDB9.9090003@gmx.net> (raw)
In-Reply-To: <20130408191741.GD13280@titan.lakedaemon.net>
Am 08.04.2013 21:17, schrieb Jason Cooper:
> Jan,
>
> On Mon, Apr 08, 2013 at 11:14:25AM +0200, JPT wrote:
>> during my dealing with the bricked kirkwood board I wrote an app
>> which automates the process of booting from UART.
>> It's rather stable now, except right now it doesn't work any more.
>
> Never was a more contradictory sentence uttered ;-)
LOL
> Very nice! Please take a look at tools/kwboot.c. It is the current
> in-tree tool doing the job you have set out. However, it doesn't have
> as many features as your code appears to have.
as soon as I realized Kirkwood boot is integrated into u-boot, I should
have searched for a kw client... o.O
Well, didn't...
> Could you lay out your patches to add missing features to kwboot? It
> would facilitate review, and would avoid duplicate tools in the source
> tree.
Well. I am sorry, I wasn't planning integration into u-boot source tree.
- it's pascal (I don't know c/cpp very well)
- it uses a rather fat opensource communication library (synapse, 1.5 MB
of pascal source)
Since I am done with recovering my NAS, I won't continue work on this.
Any idea where to anyway provide the source?
I could upload it where I wrote the guide on upgrading my Netgear NAS.
http://netgear.nas-central.org/wiki/ReadyNasDUO-200_customisation_guide
But... xmodem boot solves only far less problems than the custom
emergency boot holding the backup button. So for the Netgear NAS it's
useless. But maybe it's of use if I put it into a more general section
on http://www.nas-central.org/
Jan
next prev parent reply other threads:[~2013-04-12 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:14 [U-Boot] offer: program to deal with kirkwood "boot from UART" JPT
2013-04-08 19:17 ` Jason Cooper
2013-04-12 12:27 ` JPT [this message]
2013-04-08 20:30 ` Tom Rini
2013-04-09 7:32 ` Prafulla Wadaskar
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=5167FDB9.9090003@gmx.net \
--to=j-p-t@gmx.net \
--cc=u-boot@lists.denx.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