From: Gary Thomas <gthomas@cygnus.co.uk>
To: Perry Wang <perrywang@nmnc.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] adding memory segment for AEB-1C
Date: Fri, 17 Dec 1999 18:47:00 -0000 [thread overview]
Message-ID: <XFMail.991217195555.gthomas@cygnus.co.uk> (raw)
In-Reply-To: <NDBBKBNDILCIAEJMGDCGKEECCBAA.perrywang@nmnc.com>
On 18-Dec-99 Perry Wang wrote:
> Hi, all.
>
> Sorry to repost the question but just in case everyone missed my question
> earlier.
>
> Is there a "proper" way to add an additional mem segment to the sharp
> processor in AEB-1C without changing the original hal_platform_setup.h?
>
> Basically I like to map my FPGA registers to e0000000 - e0010000 without
> changing the eCos HAL source.
>
If you don't want to change the HAL then the best place to put this would
be in your application code.
I'd probably add it in 'cyg_start()', 'cyg_user_start()' or 'main()'
based on which style of startup you are using.
prev parent reply other threads:[~1999-12-17 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-17 17:38 Perry Wang
1999-12-17 18:47 ` Gary Thomas [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=XFMail.991217195555.gthomas@cygnus.co.uk \
--to=gthomas@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=perrywang@nmnc.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).