mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@kernel.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Willy Tarreau <w@1wt.eu>,
	linux@weissschuh.net, linux-m68k@vger.kernel.org,
	geert@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: Add m68k support
Date: Sat, 26 Apr 2025 23:57:15 +1000	[thread overview]
Message-ID: <12166789-6c01-4c9d-b293-6fc5a4530971@kernel.org> (raw)
In-Reply-To: <CAFr9PXk5ycoZYce1eBOUBvnP_m7swPLT-giHDQSXaa4ywe7mZg@mail.gmail.com>

Hi Daniel,

On 26/4/25 23:06, Daniel Palmer wrote:
> Hi Greg,
> 
> On Sat, 26 Apr 2025 at 21:38, Greg Ungerer <gerg@kernel.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



      reply	other threads:[~2025-04-26 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26  4:12 Daniel Palmer
2025-04-26  5:14 ` Willy Tarreau
2025-04-26  6:16   ` Daniel Palmer
2025-04-26  6:56     ` Willy Tarreau
2025-04-26 13:09       ` Daniel Palmer
2025-04-26 12:37     ` Greg Ungerer
2025-04-26 13:06       ` Daniel Palmer
2025-04-26 13:57         ` Greg Ungerer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12166789-6c01-4c9d-b293-6fc5a4530971@kernel.org \
    --to=gerg@kernel.org \
    --cc=daniel@0x0f.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®