From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: eCos Developers <ecos-devel@ecos.sourceware.org>
Cc: Gary Thomas <gary@mlbassoc.com>
Subject: Re: RedBoot's TFTP client and dumb TFTP servers
Date: Thu, 13 Jan 2011 20:57:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1101132222570.2311@sg-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1101101644550.16818@sg-desktop.belvok.com>
Hi,
On Mon, 10 Jan 2011, Sergei Gavrikov wrote:
> On Mon, 10 Jan 2011, Gary Thomas wrote:
> > On 01/10/2011 07:13 AM, Sergei Gavrikov wrote:
<...>
> > > I tried to get working the QEMU's embedded TFTP server with
> > > RedBoot's FTP client and the RedBoot's 'load' command always wept,
> > > -- "illegal TFTP operation".
<...>
> > I've never run across another TFTP server that can't handle OCTET in
> > upper case.
Indeed, I've checked out 'netkit-tftp', 'atftp', and 'tftp-hpa' sources.
All TFTP servers use either strcasecmp() or tolower() then strcmp() on
checking the mode field. But all companion (TFP clients) send the mode
field in *lower* case.
> > By your reference, the QEMU server is what's broken - why not fix it
> > instead?
>
> Gary, thanks for your expertise, then I will disturb qemu-devel list.
FYI: they applied my patch, but it is unlikely that everyone loves build
QEMU from sources :-) IMO, we could get the RedBoot's TFTP client be more
compliant/tolerant, but can be the RedBoot on QEMU is rarely the case.
Sergei
prev parent reply other threads:[~2011-01-13 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 14:14 Sergei Gavrikov
2011-01-10 14:31 ` Gary Thomas
2011-01-10 14:48 ` Sergei Gavrikov
2011-01-13 20:57 ` Sergei Gavrikov [this message]
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=alpine.DEB.2.00.1101132222570.2311@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).