From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] FW: which protocol do I use to send S-record files when using the loads command ?
Date: Mon, 23 Aug 2010 23:24:52 +0200 [thread overview]
Message-ID: <m2zkwd58ez.fsf@ohwell.denx.de> (raw)
In-Reply-To: <i4uo4t$ssq$1@dough.gmane.org> (Grant Edwards's message of "Mon, 23 Aug 2010 21:10:53 +0000 (UTC)")
Hi Grant,
>>>> Maybe you can implement a server on your hardware?
>>>
>>> What sort of server?
>>
>> It would be a tftp server of course but that is out of the question
>> without a network hardware.
>
> Now that you mention it, I have implemented a tftp server for U-Boot.
Nice job!
> We needed a way to recover "bricked" units in the field, and there's
> simply no way we could require out customers to install a tftp server
> on their machines. Making U-Boot the tftp server and our "restore"
> program the client solved several problems. I also find have U-Boot
> be the server is a lot more convenient for development use.
Yes, I can see that this is very nice in some scenarios.
> [It also U-Boot commands to be sent via the tftp protocol.]
Now this is actually very intersting. I never considered something like
this. Of course it has the possibility to do "bad things" from the
outside, but the netconsole code has the same problem. But unlike
netconsole the "client side" is fully standard. Indeed very
interesting. Can you pass back results, i.e. the output of an md
command?
> I thought about submitting patches (it's pretty much a stand-alone
> addition except for 3-4 lines in net.[ch]). But it was made
> abundantly clear that tftp server code for U-Boot would never be
> considered -- I was scolded for even asking about it.
Maybe I can talk you into posting the patches? It would be an awful
waste of effort not to at least post your (working!) implementation here
and thus (at least) get it archieved. In Free Software written code
always has the potential to change minds ;)
Cheers
Detlev
--
... what [Microsoft] Exchange provides is *like* email, but it is *not* email.
Once you start trying to use it for real email, you find it's broken by design
in a large number of ways. It makes no sense for [a company] to require that
you use Exchange for Internet email, because that's not what Exchange does.
-- David Woodhouse <1281348164.12908.47.camel@localhost>
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2010-08-23 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <226BC4AFA29FC24789DFD00DFF3084C2524247EECE@SAFEMAIL.safetran.railad.com>
2010-08-19 17:28 ` [U-Boot] FW: which protocol do I use to send S-record files when using the loads command ? Jef Mangelschots
2010-08-19 17:33 ` [U-Boot] " Jef Mangelschots
2010-08-19 19:46 ` [U-Boot] FW: " Rogan Dawes
2010-08-19 20:06 ` Wolfgang Denk
2010-08-19 20:56 ` Jef Mangelschots
2010-08-19 21:13 ` Wolfgang Denk
2010-08-19 21:15 ` Wolfgang Denk
2010-08-23 15:07 ` Detlev Zundel
2010-08-23 16:34 ` Grant Edwards
2010-08-23 21:00 ` Detlev Zundel
2010-08-23 21:10 ` Grant Edwards
2010-08-23 21:22 ` Ben Warren
2010-08-23 21:42 ` Grant Edwards
2010-08-23 21:24 ` Detlev Zundel [this message]
2010-08-23 21:50 ` Grant Edwards
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=m2zkwd58ez.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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