mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	Willy Tarreau <w@1wt.eu>,
	John David Anglin <dave.anglin@bell.net>,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH 3/3] tools/nolibc: add support for 32-bit parisc
Date: Tue, 7 Apr 2026 20:40:39 +0200	[thread overview]
Message-ID: <4c1c0d5c-d05c-4b98-bfbb-bbb2650c0fab@gmx.de> (raw)
In-Reply-To: <9477a477-6abc-4de3-bb9b-1080e0cefc80@t-8ch.de>

On 4/7/26 20:14, Thomas Weißschuh wrote:
> On 2026-04-07 19:33:05+0200, Helge Deller wrote:
>> On 4/7/26 18:37, Thomas Weißschuh wrote:
>>> Extend nolibc to target the 32-bit parisc architecture.
>>> 64-bit is not yet supported.
>>
>> Adding 64-bit would be very cool.
> 
> It is on my roadmap. But the 64-bit kernel I tried didn't seem to boot.

Just in case you used qemu, you need to use "-machine C3700" or "-machine A400".
The default B160L is a 32-bit only machine.

> Also it would be nice if CONFIG_COMPAT could be disabled.

Ah... never thought about that. Will check, but I don't think
the kernel will become much smaller.

>> Dave Anglin is currently working on adding 64-bit userspace support
>> to gcc/glibc (dynamic loader), but that takes some time.
>> In the meantime a 64-bit nolibc would be cool for testing.
> 
> Nice. Do you have instructions to run the 64-bit kernel in QEMU?

As mentioned above, I think the "-machine C3700" should be sufficient.
Some more info is at: https://parisc.docs.kernel.org/en/latest/qemu.html

> Is qemu-user support planned?
32-bit qemu user works great and is used on many debian buildd machines.
64-bit is on my todo list, I just need time to do it :-)

Helge

  reply	other threads:[~2026-04-07 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 16:37 [PATCH 0/3] " Thomas Weißschuh
2026-04-07 16:37 ` [PATCH 1/3] parisc: Makefile: use the regular compiler to build a native 32-bit vDSO Thomas Weißschuh
2026-04-07 17:14   ` Helge Deller
2026-04-07 18:06     ` Thomas Weißschuh
2026-04-07 19:27       ` Helge Deller
2026-04-07 20:20         ` Helge Deller
2026-04-07 21:27           ` Thomas Weißschuh
2026-04-07 22:33             ` Helge Deller
2026-04-07 16:37 ` [PATCH 2/3] selftests/nolibc: avoid function pointer comparisons Thomas Weißschuh
2026-04-07 17:20   ` Helge Deller
2026-04-07 18:11     ` Thomas Weißschuh
2026-04-07 16:37 ` [PATCH 3/3] tools/nolibc: add support for 32-bit parisc Thomas Weißschuh
2026-04-07 17:33   ` Helge Deller
2026-04-07 18:14     ` Thomas Weißschuh
2026-04-07 18:40       ` Helge Deller [this message]
2026-04-07 18:50         ` Thomas Weißschuh

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=4c1c0d5c-d05c-4b98-bfbb-bbb2650c0fab@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@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®