From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 519C2C3A5A9 for ; Thu, 5 Sep 2019 03:17:37 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 93D1320820 for ; Thu, 5 Sep 2019 03:17:36 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 93D1320820 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 46P5Tp0skLzDr1Y for ; Thu, 5 Sep 2019 13:17:34 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [203.11.71.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 46P5R311MhzDqkT for ; Thu, 5 Sep 2019 13:15:11 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: by ozlabs.org (Postfix) id 46P5R23b5zz9sDB; Thu, 5 Sep 2019 13:15:10 +1000 (AEST) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 46P5R15544z9s3Z; Thu, 5 Sep 2019 13:15:09 +1000 (AEST) From: Michael Ellerman To: Oliver O'Halloran Subject: Re: [PATCH v5 19/31] powerpc/fadump: Update documentation about OPAL platform support In-Reply-To: References: <156630261682.8896.3418665808003586786.stgit@hbathini.in.ibm.com> <156630278711.8896.9799921270260662672.stgit@hbathini.in.ibm.com> <87y2z4p9dh.fsf@mpe.ellerman.id.au> Date: Thu, 05 Sep 2019 13:15:09 +1000 Message-ID: <87h85rph6q.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ananth N Mavinakayanahalli , Mahesh J Salgaonkar , Vasant Hegde , linuxppc-dev , Nicholas Piggin , Hari Bathini , Daniel Axtens Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" "Oliver O'Halloran" writes: > On Wed, Sep 4, 2019 at 9:51 PM Michael Ellerman wrote: >> Hari Bathini writes: ... >> > diff --git a/Documentation/powerpc/firmware-assisted-dump.rst b/Documentation/powerpc/firmware-assisted-dump.rst >> > index d912755..2c3342c 100644 >> > --- a/Documentation/powerpc/firmware-assisted-dump.rst >> > +++ b/Documentation/powerpc/firmware-assisted-dump.rst >> > @@ -96,7 +97,9 @@ as follows: >> > >> > Please note that the firmware-assisted dump feature >> > is only available on Power6 and above systems with recent >> > -firmware versions. >> >> Notice how "recent" has bit rotted. >> >> > +firmware versions on PSeries (PowerVM) platform and Power9 >> > +and above systems with recent firmware versions on PowerNV >> > +(OPAL) platform. >> >> Can we say something more helpful here, ie. "recent" is not very useful. >> AFAIK it's actually wrong, there isn't a released firmware with the >> support yet at all, right? >> >> Given all the relevant firmware is open source can't we at least point >> to a commit or release tag or something? > > Even if we can quote a git sha it's not terrible useful or user > friendly. We already gate the feature behind DT nodes / properties > existing, so why not just say "fadump requires XYZ firmware feature, > as indicated by device-tree property." But how does that help someone who's got a Talos/Blackbird and wants to test this stuff? cheers