public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@redhat.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] RedBoot porting
Date: Mon, 08 Jan 2001 08:07:00 -0000	[thread overview]
Message-ID: <XFMail.20010108090728.gthomas@redhat.com> (raw)
In-Reply-To: <20010108165906.S10158@biferten.ma.tech.ascom.ch>

On 08-Jan-2001 Andrew Lunn wrote:
>> Have you looked at the flash drivers we already have?  They have 
>> techniques (running just the flash access functions in RAM) for this.
>> The only complication is when trying to [re]program the flash that
>> is actually executing, i.e. the RedBoot code itself.  For that, we
>> use a version of RedBoot designed to run from RAM.
> 
> This is ok for development, but not ok for in field upgrades by
> customers/installation people. Do you want me to teach my customers
> how to run a RAM copy of redboot so that they can then upgrade the ROM
> copy? I think not. Customers need something simple like. Boot the
> system as normal, TFTP put this image and press the reset button. 

I agree that it needs to be simple.  However, there's no reason that
simple [from user's perspective] has to work in any particular fashion.

I could imagine [and I have!] a special RedBoot command which does
all of the steps automatically, including rebooting from the RAM based
version, updating the FLASH and then rebooting the entire system.  This
could be done in a fail-safe fashion such that if any step failed, the
system reverts to totally normal operation [all changes reverted].

  reply	other threads:[~2001-01-08  8:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  9:49 Grant Edwards
2001-01-05 15:41 ` Jonathan Larmour
2001-01-08  0:08 ` Jesper Skov
2001-01-08  0:29 ` Andrew Lunn
2001-01-08  1:09   ` Jesper Skov
2001-01-08  2:36     ` Andrew Lunn
2001-01-08  3:04       ` Jesper Skov
2001-01-08  7:31   ` Grant Edwards
2001-01-08  7:40     ` Lewin A.R.W. Edwards
2001-01-08  8:24       ` Grant Edwards
2001-01-08  7:42     ` Gary Thomas
2001-01-08  7:57       ` Grant Edwards
2001-01-08  7:59       ` Andrew Lunn
2001-01-08  8:07         ` Gary Thomas [this message]
2001-01-08 14:42 ` Grant Edwards
2001-01-08 16:26   ` Gary Thomas
2001-01-09  7:33     ` Grant Edwards
2001-01-08  4:36 Doug Fraser
2001-01-08  4:54 ` Jesper Skov
2001-01-08  7:34 ` Grant Edwards
2001-01-08  5:32 Doug Fraser
     [not found] <20010108171508.U10158@biferten.ma.tech.ascom.ch>
     [not found] ` <XFMail.20010108095423.gthomas@redhat.com>
2001-01-09  0:50   ` Andrew Lunn
2001-01-09  8:57     ` Grant Edwards
2001-01-09  9:05       ` Andrew Lunn
2001-01-09  9:12         ` Grant Edwards
2001-01-09  9:09       ` Gary Thomas
2001-01-09  9:24         ` Grant Edwards
2001-01-09  9:47         ` Andrew Lunn
2001-01-09 10:08           ` Lewin A.R.W. Edwards
2001-01-09 10:30             ` Grant Edwards
2001-01-09 10:39             ` Andrew Lunn
2001-01-09 11:24               ` Grant Edwards
2003-09-16  2:55 [ECOS] redboot porting yu weiping

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=XFMail.20010108090728.gthomas@redhat.com \
    --to=gthomas@redhat.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-discuss@sourceware.cygnus.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).