linux-kernel - Re: [RFC PATCH 01/10] powerpc/chrp: Remove CHRP 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <acec6edb-59a0-4c9e-91ca-b152381a6542@app.fastmail.com>
Date: Thu, 14 Nov 2024 16:43:28 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Geert Uytterhoeven" <geert@...ux-m68k.org>,
 "Michael Ellerman" <mpe@...erman.id.au>
Cc: linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 01/10] powerpc/chrp: Remove CHRP support

On Thu, Nov 14, 2024, at 15:31, Geert Uytterhoeven wrote:
> On Thu, Nov 14, 2024 at 2:11 PM Michael Ellerman <mpe@...erman.id.au> wrote:
>> CHRP (Common Hardware Reference Platform) was a standard developed by
>> IBM & Apple for PowerPC-based systems.
>>
>> The standard was used in the development of some machines but never
>> gained wide spread adoption.
>>
>> The Linux CHRP code only supports a handful of machines, all 32-bit, eg.
>> IBM B50, bplan/Genesi Pegasos/Pegasos2, Total Impact briQ, and possibly
>> some from Motorola? No Apple machines should be affected.
>>
>> All of those mentioned above are over or nearing 20 years old, and seem
>> to have no active users.
>>
>> So remove the CHRP support. If there's interest in still supporting some
>> of the machines that can be brought back from the git history.
>>
>> Note there are still some references to CHRP/chrp in various comments
>> and some in the code, because later standards (eg. RPA, PAPR) used some
>> elements of CHRP or copied the CHRP behaviour. These will need to be
>> cleaned up on a case-by-case basis to either refer to newer standards or
>> left as-is when that's correct.
>>
>> The CHRP code was copied from arch/ppc, and before that it mostly
>> predates git, so the original authorship is largely lost. If anyone
>> wrote any of this code and would like a CREDITS entry just let me know.
>>
>> Signed-off-by: Michael Ellerman <mpe@...erman.id.au>
>
> Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
>

Whole series

Acked-by: Arnd Bergmann <arnd@...db.de>