From: Gary Thomas <gary@chez-thomas.org>
To: Tim Drury <tdrury@siliconmotorsports.com>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] at91hal_platform_setup.h question
Date: Thu, 20 Jun 2002 05:36:00 -0000 [thread overview]
Message-ID: <1024576608.4602.248.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <200206200039.08930.tdrury@siliconmotorsports.com>
On Wed, 2002-06-19 at 22:39, Tim Drury wrote:
>
> The following lines appear in hal_platform_setup.h:
>
> #if defined(CYG_HAL_STARTUP_ROMRAM)
> ldr r0,=0x01010000 // Relocate FLASH/ROM to on-chip RAM
> ldr r1,=0x02000000 // RAM base & length
> ldr r2,=0x02010000
> ...
>
> Is there any particular reason the RAM and ROM addresses and lengths
> are hard-coded here? Why not put the constants defined in
> mlt_arm_at91_eb40_ramrom.h in there?
A good idea - please send a patch :-)
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2002-06-20 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 21:40 Tim Drury
2002-06-20 5:36 ` 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=1024576608.4602.248.camel@hermes.chez-thomas.org \
--to=gary@chez-thomas.org \
--cc=ecos-discuss@sources.redhat.com \
--cc=tdrury@siliconmotorsports.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).