public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Gary Thomas <gthomas@redhat.com>
Cc: eCos Disuss <ecos-discuss@sourceware.cygnus.com>,
	Andrew Lunn <andrew.lunn@ascom.ch>
Subject: Re: [ECOS] RedBoot porting
Date: Tue, 09 Jan 2001 09:24:00 -0000	[thread overview]
Message-ID: <20010109112751.B12365@visi.com> (raw)
In-Reply-To: <XFMail.20010109100923.gthomas@redhat.com>

On Tue, Jan 09, 2001 at 10:09:23AM -0700, Gary Thomas wrote:

> > That's one of my concerns about running RedBoot from ROM: If I
> > run RedBoot from ROM, then I can't allow the application to use
> > any of the virtual vector stuff.  The application needs to be
> > able to write to flash, and if RedBoot is running from flash
> > it's not going to be available during a flash burn.
> 
> This is only a problem if interrupts can occur while you're
> actually writing/erasing the flash (not a good idea in my
> mind).  

I suppose it would be simpler to just shut down the whole thing
for several seconds, but that's not a good option.  It's a
multitasking system: even though one task is busy burning
something into flash, the other tasks (miscellaneous network
stuff, background diagnostics, data transfer, web server) all
need to keep running.

I might have to pause the web server since it's pages are in
flash and I don't want to copy them into RAM.  That's
sub-optimal, but tolerable.  The other tasks have to keep
running.

> Otherwise, what would the flash access functions be doing
> calling virtual vector stuff?

Printing status info on the diagnostic output channel mainly.
My flash burn routine displays diagnostic info as it burns
flash.  Other tasks that are still running also need to display
status output, and I presume the network stack may need to call
virtual vector stuff for debug purposes.

-- 
Grant Edwards
grante@visi.com

  reply	other threads:[~2001-01-09  9:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08  5:32 [ECOS] RedBoot porting Doug Fraser
2001-01-08  4:36 Doug Fraser
2001-01-08  4:54 ` Jesper Skov
2001-01-08  7:34 ` Grant Edwards
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
2001-01-08 14:42 ` Grant Edwards
2001-01-08 16:26   ` Gary Thomas
2001-01-09  7:33     ` 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=20010109112751.B12365@visi.com \
    --to=grante@visi.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@redhat.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).