From: Hans Berglund <hb@spacetec.no>
To: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: AW: [ECOS] FLASH access from user program
Date: Tue, 07 Jun 2005 08:28:00 -0000 [thread overview]
Message-ID: <42A55AB2.7050802@spacetec.no> (raw)
In-Reply-To: <5A8A17126B73AC4C83968F6C4505E3C502304E95@JO-EX01.JENOPTIK.NET>
Hi
Thank you for the information. It was a long thread, and I haven't read
it all yet. It looks like what I am looking for. What is the difference
in this mechanism and the CYGNUM_CALL_IF_FLASH_FIS_OP virtual vector?
Hans
Neundorf, Alexander wrote:
> Hi,
>
>
>>Von: ecos-discuss-owner@ecos.sourceware.org
>>
>>I would like to do functions similar to "fis delete" and "fis create"
>>from an eCos user program.
>>
>>How can I get access to the FLASH?
>>Are there system calls for this, or do I have to move a lot of RedBoot
>>code into my program?
>>
>>Or are there other possibilities?
>>
>>All input is welcome.
>
>
>
> please have a look at the thread "contributing a failsafe update meachanism for FIS from within ecos applications"
> on this page http://ecos.sourceware.org/ml/ecos-devel/2004-10/ .
> Is this the type of functionality you need ?
>
> Bye
> 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
next prev parent reply other threads:[~2005-06-07 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 10:11 Neundorf, Alexander
2005-06-06 10:32 ` [ECOS] Thread not starting! Raja Mallik
2005-06-06 10:44 ` Gary Thomas
2005-06-06 11:40 ` Raja Mallik
2005-06-06 12:21 ` Gary Thomas
2005-06-06 12:03 ` Raja Mallik
2005-06-06 12:24 ` Gary Thomas
2005-06-07 4:43 ` Raja Mallik
2005-06-07 8:28 ` Hans Berglund [this message]
2005-06-07 9:36 ` AW: [ECOS] FLASH access from user program Hans Berglund
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=42A55AB2.7050802@spacetec.no \
--to=hb@spacetec.no \
--cc=Alexander.Neundorf@jenoptik.com \
--cc=ecos-discuss@sources.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).