This is the mail archive of the
mailing list for the eCos project.
Re: AW: contributing a failsafe update meachanism for FIS from within ecos applications
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- Cc: Slawek <sgp at telsatgp dot com dot pl>, ecos-devel at sources dot redhat dot com
- Date: Thu, 28 Oct 2004 10:26:08 +0200
- Subject: Re: AW: contributing a failsafe update meachanism for FIS from within ecos applications
- References: <5A8A17126B73AC4C83968F6C4505E3C5013A3936@JO-EX01.JENOPTIK.NET>
On Tue, Oct 26, 2004 at 06:37:26PM +0200, Neundorf, Alexander wrote:
> here comes the next try, I hope I fixed all known issues.
+ // Ensure [quietly] that the directory is locked after the update
+ flash_lock((void *)fis_addr, flash_block_size, (void **)&err_addr);
This should be (void *)redundant_fis_addr. My error i think....
> An adapted version of my current fisfs implementation is also
> attached. It would be nice if the fisfs-implementation could get
> the information about the two flash blocks reserved for the two fis
> tables somehow from redboot during runtime. Is there a way to do
> this ?
You should take a look what the virtual vectors supports. There are a
couple of examples of it being used in:
packages/io/flash/current/src/flashiodev.c:flashiodev_init() and see
As i said before, i think this is the way the FISFS should work,
redboot doing most of the work using VV as the interface between the
application and redboot.