From: Jonathan Larmour <jlarmour@redhat.com>
To: Raymund Hofmann <rhofmann@raygmbh.de>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] HAL virtual vectors / 1.3.1 board package
Date: Fri, 20 Jul 2001 06:06:00 -0000 [thread overview]
Message-ID: <3B582CC3.2FC1C9C5@redhat.com> (raw)
In-Reply-To: <002201c11124$3d22cbf0$fe78a8c0@raypc2>
Raymund Hofmann wrote:
>
> Maybe somebody can give me clues or pointers to get a clearer picture about
> the newly incorporated virtual vectors in ecos, so that i have a chance of
> successfully doing the changes.
The best documentation in a sense, as ever, is other examples in other
HALs. But there's also
http://sources.redhat.com/ecos/docs-latest/porting/hal-calling-if.html
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
prev parent reply other threads:[~2001-07-20 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 6:00 Raymund Hofmann
2001-07-20 6:06 ` Jonathan Larmour [this message]
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=3B582CC3.2FC1C9C5@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=rhofmann@raygmbh.de \
/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).