From: "Raymund Hofmann" <rhofmann@raygmbh.de>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] HAL virtual vectors / 1.3.1 board package
Date: Fri, 20 Jul 2001 06:00:00 -0000 [thread overview]
Message-ID: <002201c11124$3d22cbf0$fe78a8c0@raypc2> (raw)
As i have a Board package for 1.3.1 I'm trying to port it to the current
ecos cvs, I came to this point:
At first i discovered that in the boardspecific function
'hal_hardware_init', the common hal function 'hal_if_init' should be called,
so that the virtual vectors get initialized.
After including this call into the board hal file 'misc.c' I discovered
more:
there should also be a function 'cyg_hal_plf_comms_init' in the board hal
for the common/hal_if.c to call.
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.
Raymund Hofmann
RAY Electronic-Design GmbH
Lagerstrasse 49
64807 Dieburg, Germany
Tel ++49 6071-986000
Fax ++49 6071-9860098
next reply other threads:[~2001-07-20 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 6:00 Raymund Hofmann [this message]
2001-07-20 6:06 ` Jonathan Larmour
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='002201c11124$3d22cbf0$fe78a8c0@raypc2' \
--to=rhofmann@raygmbh.de \
--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).