linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stuart Yoder <stuart.yoder@conformative.com>
Cc: 'linuxppc-dev list' <linuxppc-dev@ozlabs.org>
Subject: RE: PowerPC + SMP
Date: Wed, 27 Apr 2005 08:27:29 +1000	[thread overview]
Message-ID: <1114554449.7183.69.camel@gaston> (raw)
In-Reply-To: <054301c54a6f$d1cf82b0$2f010a0a@foundation.com>

On Tue, 2005-04-26 at 09:54 -0500, Stuart Yoder wrote:
> Thanks Ben.
> 
> That raises a question though-- how can I know what assumptions the
> kernel makes about the state of the CPU/system when it begins execution?
> Is this clearly documented anywhere?
> 
> I am using U-boot on my SMP system and U-boot is not SMP aware.  Do you
> know of other open source bootloaders for Linux that would set up the
> CPUs as the kernel expects.

No, it's up to you to configure the CPU properly. I'm surprised that
uBoot doesn't set it up properly though, but then, when you bringup a
board, you rarely use a bootloader like that "as-is" :)

In general, the kernel except the CPU to be in working condition, which
I consider meanings having necessary HID bits set for proper coherency
etc... on an SMP system :)

Ben.

  parent reply	other threads:[~2005-04-26 22:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 21:11 PowerPC + SMP Stuart Yoder
2005-04-26  3:36 ` Benjamin Herrenschmidt
2005-04-26 14:54   ` Stuart Yoder
2005-04-26 17:35     ` Wolfgang Denk
2005-04-26 19:07       ` Stuart Yoder
2005-04-26 22:27     ` Benjamin Herrenschmidt [this message]
2005-04-26 23:04     ` Paul Mackerras
  -- strict thread matches above, loose matches on Subject: below --
2005-04-27  4:37 Frank
2005-04-25 21:10 Stuart Yoder
2005-04-25 21:39 ` Kumar Gala
2005-04-26 19:16   ` Stuart Yoder
2005-04-26 19:23     ` Kumar Gala

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=1114554449.7183.69.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stuart.yoder@conformative.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 NNTP newsgroup(s).