From: Gary Thomas <gary@mlbassoc.com>
To: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: AW: [ECOS] [Proposal & Patch] enhancing redboot/fis for failsafeflash updates
Date: Mon, 01 Nov 2004 12:26:00 -0000 [thread overview]
Message-ID: <1099311987.31163.1.camel@hermes> (raw)
In-Reply-To: <5A8A17126B73AC4C83968F6C4505E3C5013EFA04@JO-EX01.JENOPTIK.NET>
On Mon, 2004-11-01 at 04:33, Neundorf, Alexander wrote:
> > -----Ursprüngliche Nachricht-----
> > Von: Gary Thomas [mailto:gary@mlbassoc.com]
> > Gesendet: Freitag, 8. Oktober 2004 16:50
> > An: Neundorf, Alexander
> > Cc: eCos Discussion
> > Betreff: Re: [ECOS] [Proposal & Patch] enhancing redboot/fis for
> > failsafeflash updates
> >
> >
> > On Fri, 2004-10-08 at 08:29, Neundorf, Alexander wrote:
> > > Hi,
> > >
> > > we need to be able to perform safe updates of the firmware,
> > safe regarding power loss at any point in time. Since redboot
> > comes with FIS, we'd like to use fis.
> > > In order to update the firmware a new firmware image has to
> > be placed on the flash and the fis directory has to be
> > updated. When updating the fis directory, the directory is
> > erased and afterwards written with the new contents.
> > > Now if the power goes down directly after erasing the
> > directory redboot can't start the firmware image anymore
> > since it can't read the directory.
> > >
> > ...
> >
> > I plan on looking at this next week (today I'm moving house).
> > However,
> > before we can consider such massive changes, we'll need copyright
> > assignment for this work. Have you applied for this already? If not,
> > please visit our website for the details.
>
> Hi Gary,
>
> the copyright assignement contract is now almost signed here.
> Do I need to do something special before sending it to you ?
> Should I also fax it so that you receive a copy faster than via snailmail ?
Please don't send it to me. eCosCentric is handling these interim
assignments and it should go to them.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
parent reply other threads:[~2004-11-01 12:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5A8A17126B73AC4C83968F6C4505E3C5013EFA04@JO-EX01.JENOPTIK.NET>]
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=1099311987.31163.1.camel@hermes \
--to=gary@mlbassoc.com \
--cc=Alexander.Neundorf@jenoptik.com \
--cc=ecos-maintainers@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).