From: WANG Xuerui <i.gentoo@xen0n.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port
Date: Thu, 7 Oct 2021 20:46:40 +0800 [thread overview]
Message-ID: <dd1a91ef-4487-9acc-9667-df391ec6be40@xen0n.name> (raw)
In-Reply-To: <b008ca13-896a-0a8f-3e9d-1be07cdd65d4@xen0n.name>
On 2021/8/12 00:39, WANG Xuerui wrote:
> Hi everyone,
>
> <snip>
>
> ## Gentoo porting plans
>
> I'm planning to take ARCH=loongarch for the port; and support the LP64
> ABI
> first. I'd like to support both LP64 and ILP32 ABIs, but that's not a
> priority.
>
> The ABI flag might be named "ABI_LOONGARCH" but that's IMO a bit long
> (pun
> semi-intended); ARCH=loong and ABI_LOONG might be better, I'm open to
> suggestions.
>
> Because much of the ABI and even some toolchain internals are going
> through
> VERY fierce debate and rework, obviously the port will remain
> experimental
> for a long time. Some minimal support should get in tree though; doing so
> would ease a lot of pain for experimentation. I already hacked my way to
> generate working crossdev toolchains, and is halfway towards a rootfs
> with
> working Python (and Portage). I've already independently ported
> strace, and
> plan to do the same to libffi in the coming days which would give me
> Python.
>
> I'll do all work in my own loongson-overlay first, and upstream these
> when
> appropriate. Eventually I hope to have working crossdev, qemu-user
> emulation
> and proper catalyst support.
>
Some kind of "progress update": I've successfully built stage3 and
minimal installation CD for ARCH=loong; ABI_LOONG is not implemented due
to Loongson retracting 32-bit support themselves, this port is 64-bit
only for now, and may remain so forever (depends on Loongson's
intentions). All modifications are made in loongson-overlay[1]; no
ad-hoc patches to main Portage tree is needed after all. My used
catalyst specs are put at [2]; currently all hard-coded and no automation.
I'm going to send patches for review gradually in the following days, as
the holiday here is over; however I'd like to know whether we need to
wait for the upstream merge of toolchain/kernel support before we can
take patches for ARCH=loong, or if there's more prerequisites.
[1]: https://github.com/xen0n/loongson-overlay
[2]: https://github.com/xen0n/releng/tree/loong
prev parent reply other threads:[~2021-10-07 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 16:39 [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port WANG Xuerui
2021-08-11 18:13 ` William Hubbs
2021-08-12 1:21 ` WANG Xuerui
2021-08-12 6:00 ` Michał Górny
2021-08-12 6:39 ` Ulrich Mueller
2021-08-24 3:30 ` WANG Xuerui
2021-08-24 8:46 ` Ulrich Mueller
2021-08-24 10:01 ` WANG Xuerui
2021-08-24 12:17 ` Ulrich Mueller
2021-08-12 9:55 ` Yixun Lan
2021-08-13 5:56 ` WANG Xuerui
2021-10-07 12:46 ` WANG Xuerui [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=dd1a91ef-4487-9acc-9667-df391ec6be40@xen0n.name \
--to=i.gentoo@xen0n.name \
--cc=gentoo-dev@lists.gentoo.org \
/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