linux-kernel - Re: [PATCH] tools/nolibc: Add m68k 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: <7bc208b3-5d28-4f25-8a59-c17f3ffa1907@kernel.org>
Date: Sat, 26 Apr 2025 22:37:56 +1000
From: Greg Ungerer <gerg@...nel.org>
To: Daniel Palmer <daniel@...f.com>, Willy Tarreau <w@....eu>
Cc: linux@...ssschuh.net, linux-m68k@...r.kernel.org, geert@...ux-m68k.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools/nolibc: Add m68k support

Hi Daniel,

On 26/4/25 16:16, Daniel Palmer wrote:
> Hi Willy,
> 
> On Sat, 26 Apr 2025 at 14:14, Willy Tarreau <w@....eu> wrote:
>> Nice, thank you! Could you please also add support for it to
>> tools/testing/selftests/nolibc/ and verify that it works ?
> 
> Sure, doing that now. For now it'll be using the mmu enabled m68k virt
> machine that QEMU supports out of the box.
> 
>> changes. You may possible have to add a few ifndef, as I don't
>> think we've ever had a nommu platform yet. If you face too many
>> failures or just difficulties, please let us know so that we can
>> figure together a suitable solution.
> 
> I need to test actually building and running something for nommu but I
> will do that later today.
> Making nommu test automatically might be a bit difficult though as I
> think it only really works with some changes I have to linux and QEMU.

It works out-of-the-box for m68k qemu and a mainline kernel configured
for m5208evb_defconfig - when using the qemu "mcf5208evb" machine.
That is a nommu m68k/coldfire variant.

Regards
Greg