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] [day] [month] [year] [list]

Message-ID: <12166789-6c01-4c9d-b293-6fc5a4530971@kernel.org>
Date: Sat, 26 Apr 2025 23:57:15 +1000
From: Greg Ungerer <gerg@...nel.org>
To: Daniel Palmer <daniel@...f.com>
Cc: Willy Tarreau <w@....eu>, 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 23:06, Daniel Palmer wrote:
> Hi Greg,
> 
> On Sat, 26 Apr 2025 at 21:38, Greg Ungerer <gerg@...nel.org> wrote:
>>> 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.
> 
> Ok, I didn't realise there was any working nommu machine in mainline QEMU.
> Does direct kernel booting with a ramdisk work there? The tests for
> nolibc require that.
> Either way, I'll it out tomorrow.

Direct kernel booting with builtin root init ramfs works.
The defconfing is not configured that way, but I always run it
with CONFIG_INITRAMFS_SOUCRE set to a suitable rootfs.

Regards
Greg