linux-kernel - Re: [PATCH v2 0/2] MIPS: BMIPS: Improved early panic support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220717134932.GA17494@alpha.franken.de>
Date:   Sun, 17 Jul 2022 15:49:32 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     linux-mips@...r.kernel.org,
        Broadcom internal kernel review list 
        <bcm-kernel-feedback-list@...adcom.com>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] MIPS: BMIPS: Improved early panic support

On Fri, Jul 15, 2022 at 02:37:45PM -0700, Florian Fainelli wrote:
> Hi Thomas,
> 
> This patch series adds support for cfe_die() which can be used during
> early platform initialization when we do not yet have a valid DTB to
> infer an earlycon console from. This is useful while bringing up new
> platforms/DTBs as well.
> 
> Thanks!
> 
> Changes in v2:
> 
> - ensure that we do not break multi-CPU builds by reading the CPU's PrID
>   to perform the appropriate XKS01 disabling before handing over to CFE
> 
> Florian Fainelli (2):
>   MIPS: CFE: Add cfe_die()
>   MIPS: BMIPS: Utilize cfe_die() for invalid DTB
> 
>  arch/mips/Kconfig                      |  1 +
>  arch/mips/bmips/setup.c                | 14 +++++-
>  arch/mips/fw/cfe/cfe_api.c             | 68 +++++++++++++++++++++++++-
>  arch/mips/include/asm/fw/cfe/cfe_api.h |  2 +
>  4 files changed, 83 insertions(+), 2 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]