public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ling Su" <lingsu@palmmicro.com>
To: "Ling Su" <lingsu@palmmicro.com>, "Nick Garnett" <nickg@cygnus.co.uk>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Porting eCos to DDB-VRC4375(Memory mapping)
Date: Tue, 30 Jan 2001 12:01:00 -0000	[thread overview]
Message-ID: <015101c08af7$604454e0$0201a8c0@raccoon> (raw)
In-Reply-To: <014501c08af4$ce8e27d0$0201a8c0@raccoon>

Sorry, I checked out the newest CVS version, I found it is correct. So
following question is invalid. :)

Rgds,
-Ling
----- Original Message -----
From: "Ling Su" <lingsu@palmmicro.com>
To: "Nick Garnett" <nickg@cygnus.co.uk>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Tuesday, January 30, 2001 11:42 AM
Subject: Re: [ECOS] Porting eCos to DDB-VRC4375(Memory mapping)


> Dear Nick,
>
> Thanks a lot for you helpful explaination! I found it is not consistent
for
> the mlt_mips_vr4300_vrc4373_rom.ldi, mlt_mips_vr4300_vrc4373_rom.mlt, and
> mlt_mips_vr4300_vrc4373_rom.h. Supposely the *.ldi and *.h are both
> generated by *.mlt, right? but in in mlt_mips_vr4300_vrc4373_rom.ldi and
> mlt_mips_vr4300_vrc4373_rom.h, we can find the ram ORIGIN is 0x80000200
> LENGTH is 0x7fe00. Any particular reason for this? I am a little bit
> confused.
>
> Regards,
> -Ling
>
>
> >
> > <2>. In the mlt_mips_vr4300_vrc4373_rom.ldi,
> > MEMORY
> > {
> >     ram: ORIGIN = 0x80000800, LENGTH = 0x7F800
> >     rom: ORIGIN = 0xBFC0000, LENGTH = 0x80000
> > }
> > I don't quite understand the ram LENGTH setting, why we just use 512KB
ram
> > in rom start up setting? Can we set the ram LENGTH to larger. Another
> thing
> > is why its ORIGIN is 0x80000800?
>
> Again, the RAM length is probably just left over from an earlier
> version of the code. Generally we use the ROMRAM startup for all
> VRC4373 non-RAM configurations, I suspect that the ROM startup has not
> been used for a long time and has not been kept up to date.
>
> The RAM starts at 0x80000800 because we have various tables defined to
> go into low RAM. Below 0x80000400 there are hardware defined interrupt
> vectors. We have the VSR table at 0x80000400 and the vector table at
> 0x80000600.
>
>
>
>

      reply	other threads:[~2001-01-30 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 18:19 Ling Su
2001-01-30  3:16 ` Nick Garnett
2001-01-30 11:42   ` Ling Su
2001-01-30 12:01     ` Ling Su [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='015101c08af7$604454e0$0201a8c0@raccoon' \
    --to=lingsu@palmmicro.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=nickg@cygnus.co.uk \
    /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).