From: "René Nielsen" <rbn@vitesse.com>
To: ecos-devel@ecos.sourceware.org
Subject: Re: RedBoot: Auto-detection of gzipped/non-gzipped images
Date: Fri, 30 Nov 2007 09:05:00 -0000 [thread overview]
Message-ID: <14042399.post@talk.nabble.com> (raw)
In-Reply-To: <13967870.post@talk.nabble.com>
Hello again,
I posted a bug regarding "fis load -d" on ecos-discuss the day before
yesterday (see e.g.
http://www.nabble.com/forum/ViewPost.jtp?post=13993780&framed=y).
Gary Thomas asked me to send a patch for that, so I have merged the "fis
load -d" bug patch with the zip-image auto-detect patch, and attached it to
this post.
Also, I've snail-mailed an eCos Copyright Assignment as suggested by Gary in
the aforementioned mail.
/René
http://www.nabble.com/file/p14042399/diff2.patch diff2.patch
--
View this message in context: http://www.nabble.com/RedBoot%3A-Auto-detection-of-gzipped-non-gzipped-images-tf4880764.html#a14042399
Sent from the Sourceware - ecos-devel mailing list archive at Nabble.com.
prev parent reply other threads:[~2007-11-30 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 9:57 René Nielsen
2007-11-30 9:05 ` René Nielsen [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=14042399.post@talk.nabble.com \
--to=rbn@vitesse.com \
--cc=ecos-devel@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).