From: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
To: "Hans Berglund" <hb@spacetec.no>
Cc: <ecos-discuss@sources.redhat.com>
Subject: AW: AW: [ECOS] FLASH access from user program
Date: Thu, 09 Jun 2005 10:19:00 -0000 [thread overview]
Message-ID: <5A8A17126B73AC4C83968F6C4505E3C50238B375@JO-EX01.JENOPTIK.NET> (raw)
Hi,
> Von: Hans Berglund [mailto:hb@spacetec.no]
>
> Hi again
>
> I have read the thread, and found that this is what I need.
> The virtual vector interface currently implements read only.
>
> But what was the conclusion of the thread? Is it now implemented in
The conclusion was: it should be implemented using the VV interface.
> eCos, or do I have to get some files from you to add to my
> application?
>
> I read a suggestion of putting the flash updating into the virtual
> vector interface. Is this implemented?
Not yet.
And right now I'm unsure what to do.
Transferring all the functionality into redboot and calling it via VV means adding a lot of opportunities for errors. Right now the code is simple: the fis table is directly accessed and manipulated. Using the VV for everything will introduce some indirections, which will make the code much less obvious and straightforward.
Having to define some constants manually (e.g. the fis table location) is a bad thing. At least some config informations should move to the VV.
And I also don't want to press fis manipulation into a rw-filesystem, since that's not the intended use. It's a ro-filesystem, which can be updated when the firmware of the device is updated.
> BTW: It seems that a lot of effort is put into this to get it safe.
Yes, and it works absolutely reliable for us.
Alex
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2005-06-09 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5A8A17126B73AC4C83968F6C4505E3C50238B375@JO-EX01.JENOPTIK.NET \
--to=alexander.neundorf@jenoptik.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=hb@spacetec.no \
/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).