public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
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 14:22:08 -0700	[thread overview]
Message-ID: <4C72E680.9030903@gmail.com> (raw)
In-Reply-To: <i4uo4t$ssq$1@dough.gmane.org>

  Hi Grant,

On 8/23/2010 2:10 PM, Grant Edwards wrote:
> On 2010-08-23, Detlev Zundel<dzu@denx.de>  wrote:
>
>>>>> I didn't say that. I was trying to say that our bareboard system
>>>>> doesn't support Ethernet and does not have TCP/IP stack (like Linux).
>>>>> If our system was a Linux system, we wouldn't be having this
>>>>> conversation.
>>>> We use tftp in U-Boot exactly because we also do not have a TCP/IP
>>>> stack :)
>>>>
>>>> tftp needs only udp is thus "not too complex" to implement on bare
>>>> ethernet.
>>> Doesn't "our bareboard system doesn't support Ethernet" preclude the
>>> use of Ethernet (UDP or otherwise)?
>> Yes, sorry.  I was mislead by the "and not the more efficient FTP
>> used in Linux".  The pure mentioning of FTP which does not make any
>> sense without a network port made me read the following statement not
>> close enough.
> I thought maybe I had lost track of who posted what. :)
>
>>>> 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.
>
> 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.  [It also
> U-Boot commands to be sent via the tftp protocol.]
>
> 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.
>
I can see how this could be useful.  Please reconsider and we'll try to 
keep the scolding to a minimum :)

regards,
Ben

  reply	other threads:[~2010-08-23 21:22 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 [this message]
2010-08-23 21:42                 ` Grant Edwards
2010-08-23 21:24               ` Detlev Zundel
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=4C72E680.9030903@gmail.com \
    --to=biggerbadderben@gmail.com \
    --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