public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa•com>
To: linuxppc-dev@ozlabs•org
Subject: cpu_die on MPC8641D
Date: Sun, 04 Jan 2009 18:07:18 -0600	[thread overview]
Message-ID: <49614F36.2040406@genesi-usa.com> (raw)

I just built a kernel with a config very similar to the MPC8641HPCN 
defconfig and for some reason at the end of the build I got an error 
saying there was no symbol "cpu_die".

I can't work out what I missed here, I checked a few LXRs to 
cross-reference where the symbol might come from and there are things 
for 64-bit CPUs (kernel/setup_64.c) and for PowerMacs but there seems to 
be no "generic" SMP support for 32-bit/e600 cores at all?

I'm trying not to have any Mac drivers in the kernel, but it seems I 
need to make sure I build in the generic PowerMac platform support to 
get SMP? Why?

-- Matt Sealey <matt@genesi-usa•com>

             reply	other threads:[~2009-01-05  0:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05  0:07 Matt Sealey [this message]
2009-01-05  3:06 ` cpu_die on MPC8641D Matt Sealey
2009-01-05 13:05 ` [PATCH] powerpc: use common cpu_die Milton Miller
2009-01-06  0:47   ` Matt Sealey
2009-01-06 14:28     ` Milton Miller
2009-02-04  4:07   ` Benjamin Herrenschmidt
2009-02-06 17:02     ` Milton Miller

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=49614F36.2040406@genesi-usa.com \
    --to=matt@genesi-usa$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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