From: syoder at austin.rr.com <syoder@austin.rr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot + Linux + SMP question
Date: Fri, 25 Mar 2005 16:02:55 -0600 [thread overview]
Message-ID: <6c44b46c58b9.6c58b96c44b4@texas.rr.com> (raw)
I have a high level question about how U-boot interacts with the Linux kernel on a PowerPC SMP system.
CPU 0 starts at the boot vector in U-boot, configures system, boots the Linux kernel. In the kernel, CPU 0 takes action to start CPU 1 and waits for CPU 1 to start.
CPU 1 also starts execution at the boot vector. Does CPU 1 take a different execution path through U-boot? Does CPU 1 also decompress the kernel into SDRAM (over top of the one put there by CPU0)?
The CONFIG_SMP define in u-boot seems be isolated mostly to the asm-ppc/bitops.h header file.
Any pointers to where I could find info on this would be appreciated.
Thanks,
Stuart Yoder
next reply other threads:[~2005-03-25 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 22:02 syoder at austin.rr.com [this message]
2005-03-26 0:35 ` [U-Boot-Users] U-boot + Linux + SMP question Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-03-27 0:18 Frank
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=6c44b46c58b9.6c58b96c44b4@texas.rr.com \
--to=syoder@austin.rr.com \
--cc=u-boot@lists.denx.de \
/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