From: Jun Sun <jsun@mvista.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: memory for exception vectors
Date: Mon, 12 May 2003 10:44:08 -0700 [thread overview]
Message-ID: <20030512104408.C24045@mvista.com> (raw)
In-Reply-To: <20030512115641.F17151@ftp.linux-mips.org>; from ladis@linux-mips.org on Mon, May 12, 2003 at 11:56:41AM +0100
On Mon, May 12, 2003 at 11:56:41AM +0100, Ladislav Michl wrote:
> Could anyone tell me where is space for exception vectors reserved? Many boards
> (for example Alchemy Pb1000, Galileo EV96100 or Galileo EV64120A) simply
> registers all available RAM with add_memory_region call, but I didn't find code
> which reserves first 0x200 (on most CPUs) for exceptions vectors anywhere. I'd
> guess there is something obvious what I'm missing. Can you help me to see it?
>
Kernel only uses memory after the end of kernel image. In that sense, all
memory before LOADADDR (see arch/mips/Makefile) is reserved.
Jun
next prev parent reply other threads:[~2003-05-12 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 10:56 memory for exception vectors Ladislav Michl
2003-05-12 17:44 ` Jun Sun [this message]
2003-05-13 9:51 ` Ladislav Michl
2003-05-13 16:52 ` Jun Sun
2003-05-13 17:11 ` Ladislav Michl
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=20030512104408.C24045@mvista.com \
--to=jsun@mvista.com \
--cc=ladis@linux-mips.org \
--cc=linux-mips@linux-mips.org \
/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