linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: linuxppc <linuxppc-dev@ozlabs.org>
Subject: Re: Relocating interrupt vectors in ppc440?
Date: Thu, 27 Jan 2005 12:18:45 -0800	[thread overview]
Message-ID: <c3d0340b050127121826b92395@mail.gmail.com> (raw)
In-Reply-To: <20050127111615.A4266@cox.net>

First thank you for your valuable response.

> > Assumed that the interrupt vectors locate at the low address space
> > physically and given that there is 2GB SDRAM shared by two ppc440
> > cores, can one of linux kernels run at the top of 1GB space? This
> > means the interrupt vectors for this copy need to move to upper 1GB.
> > Each core runs a copy of linux kernel independently.
> 
> Yes, you'd have to do something like the APUS code does by settings
> PPC_MEMSTART appropriately for the second processor. Also, of course

I guess the value set to PPC_MEMSTART should be the offset to the
physical starting address of 2GB SDRAM not the absolute physical
address, right?

> limiting the memory on the first processor to 1GB. There's probably

Limiting the memory on the first processor to 1GB can be done by
setting the mem size to 1GB in boot arguments (mem=1024MB)?

> One idea is that if you really don't have to do it, then don't. :)

The SoC is designed in this way that two cores share the DDR but it's
not SMP. Two kernels have to run independently. Relocating interrupt
vectors to upper 1GB memory means that another copy of kernel can run
at upper memory, right. So I'm afraid I have to do that. :(

Thanks,
-Shawn.

  reply	other threads:[~2005-01-27 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 18:05 Relocating interrupt vectors in ppc440? Shawn Jin
2005-01-27 18:16 ` Matt Porter
2005-01-27 20:18   ` Shawn Jin [this message]
2005-01-27 20:41     ` Matt Porter
2005-01-28  1:55       ` Shawn Jin

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=c3d0340b050127121826b92395@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).