From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Stewart Smith <stewart@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/4] powerpc/powernv: panic() on OPAL < V3
Date: Fri, 27 Nov 2015 16:36:53 +1100 [thread overview]
Message-ID: <5657EBF5.2030602@au1.ibm.com> (raw)
In-Reply-To: <1448599526-31073-2-git-send-email-stewart@linux.vnet.ibm.com>
On 27/11/15 15:45, Stewart Smith wrote:
> The OpenPower Abstraction Layer firmware went through a couple
> of iterations in the lab before being released. What we now know
> as OPAL advertises itself as OPALv3.
>
> OPALv2 and OPALv1 never made it outside the lab, and the possibility
> of anyone at all ever building a mainline kernel today and expecting
> it to boot on such hardware is zero.
>
> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Comment below.
Reviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
> ---
> arch/powerpc/platforms/powernv/opal.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/arch/powerpc/platforms/powernv/opal.c b/arch/powerpc/platforms/powernv/opal.c
> index 4296d55e88f3..ad691fc15309 100644
> --- a/arch/powerpc/platforms/powernv/opal.c
> +++ b/arch/powerpc/platforms/powernv/opal.c
> @@ -103,11 +103,8 @@ int __init early_init_dt_scan_opal(unsigned long node,
> powerpc_firmware_features |= FW_FEATURE_OPALv2;
> powerpc_firmware_features |= FW_FEATURE_OPALv3;
> pr_info("OPAL V3 detected !\n");
> - } else if (of_flat_dt_is_compatible(node, "ibm,opal-v2")) {
> - powerpc_firmware_features |= FW_FEATURE_OPALv2;
> - pr_info("OPAL V2 detected !\n");
> } else {
> - pr_info("OPAL V1 detected !\n");
> + panic("OPAL != V3 detected, no longer supported.\n")
In the event of an OPAL v4 that is for some reason not backwards
compatible with V3, "*no longer* supported" might not make sense. This
isn't a huge problem of course.
--
Andrew Donnellan Software Engineer, OzLabs
andrew.donnellan@au1.ibm.com Australia Development Lab, Canberra
+61 2 6201 8874 (work) IBM Australia Limited
next prev parent reply other threads:[~2015-11-27 5:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 4:45 [PATCH 0/4] Remove OPAL pre-v3 support Stewart Smith
2015-11-27 4:45 ` [PATCH 1/4] powerpc/powernv: panic() on OPAL < V3 Stewart Smith
2015-11-27 5:36 ` Andrew Donnellan [this message]
2015-11-27 5:43 ` Stewart Smith
2015-11-27 5:56 ` Andrew Donnellan
2015-11-30 0:20 ` Andrew Donnellan
2015-11-27 7:13 ` kbuild test robot
2015-11-27 4:45 ` [PATCH 2/4] powerpc/powernv: Remove OPALv2 firmware define and references Stewart Smith
2015-11-27 5:31 ` Andrew Donnellan
2015-11-27 4:45 ` [PATCH 3/4] powerpc/powernv: remove FW_FEATURE_OPAL and just use FW_FEATURE_OPALv3 Stewart Smith
2015-11-27 5:45 ` Andrew Donnellan
2015-12-01 3:56 ` Michael Ellerman
2015-12-03 6:06 ` Stewart Smith
2015-12-03 8:55 ` Michael Ellerman
2015-11-27 4:45 ` [PATCH 4/4] powerpc/powernv: remove logic for pre-OPALv3 firmware Stewart Smith
2015-11-27 5:55 ` Andrew Donnellan
2015-12-09 6:18 ` [PATCH v2 0/3] Remove OPAL pre-v3 support Stewart Smith
2015-12-09 6:18 ` [PATCH v2 1/3] powerpc/powernv: panic() on OPAL < V3 Stewart Smith
2015-12-17 11:57 ` [v2,1/3] " Michael Ellerman
2015-12-09 6:18 ` [PATCH v2 2/3] powerpc/powernv: Remove OPALv2 firmware define and references Stewart Smith
2015-12-09 6:18 ` [PATCH v2 3/3] powerpc/powernv: remove FW_FEATURE_OPALv3 and just use FW_FEATURE_OPAL Stewart Smith
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=5657EBF5.2030602@au1.ibm.com \
--to=andrew.donnellan@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stewart@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.