From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc64: actually call prom_send_capabilities
Date: Wed, 01 Jun 2005 09:41:46 +1000 [thread overview]
Message-ID: <1117582907.5826.69.camel@gaston> (raw)
In-Reply-To: <200505311612.j4VGCWC8005159@hera.kernel.org>
>
> Index: arch/ppc64/kernel/prom_init.c
> ===================================================================
> --- 3ac19ebb77c3cd8a1df31b7170c6eaf9e1afb1a4/arch/ppc64/kernel/prom_init.c (mode:100644 sha1:6f79b7b9b445e8669411e34b48c1ea8ce5135965)
> +++ 11f504429d5e6708259f376b76e96cafd3bf9215/arch/ppc64/kernel/prom_init.c (mode:100644 sha1:bc53967a86436d6b3f4a4f324273e01fdab934b3)
> @@ -1881,6 +1881,12 @@ unsigned long __init prom_init(unsigned
> &getprop_rval, sizeof(getprop_rval));
>
> /*
> + * On pSeries, inform the firmware about our capabilities
> + */
> + if (RELOC(of_platform) & PLATFORM_PSERIES)
> + prom_send_capabilities();
> +
> + /*
> * On pSeries, copy the CPU hold code
> */
> if (RELOC(of_platform) & PLATFORM_PSERIES)
> -
/* Platforms supported by PPC64 */
#define PLATFORM_PSERIES 0x0100
#define PLATFORM_PSERIES_LPAR 0x0101
#define PLATFORM_ISERIES_LPAR 0x0201
#define PLATFORM_LPAR 0x0001
#define PLATFORM_POWERMAC 0x0400
#define PLATFORM_MAPLE 0x0500
Hrm... this will trigger on Maple too... Should I change Maple
definition ? That would break kexec of maple from existing to newer
kernels though.
next parent reply other threads:[~2005-05-31 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505311612.j4VGCWC8005159@hera.kernel.org>
2005-05-31 23:41 ` Benjamin Herrenschmidt [this message]
2005-05-31 7:01 Paul Mackerras
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=1117582907.5826.69.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®