public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Arthur Zamarin <arthurzam@gentoo.org>
Subject: riscv, was: Re: [gentoo-dev] Arch Status and Future Plans
Date: Wed, 26 Jun 2024 22:24:21 +0200	[thread overview]
Message-ID: <3755379.MHq7AAxBmi@pinacolada> (raw)
In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

> ======== riscv ========
> 
> Dev arch. I don't have much info on it, but I heard some mess with
> riscv32 and riscv64, so maybe time to split it? I leave it to riscv arch
> team, which works quite well, but I'll be happy to open discussion for it.

riscv is something new and growing, but for now hardware is still quite slow.
We do not have any hardware devbox so far.

In its very beginning I proposed to use different keywords for 32bit and 64bit
(if not for that, for what then???), but enthusiasm was limited.
** Reminder, people actually have to do the keywording and maybe stabilization,
and more keywords means more work. **

If we split it, then please let's keep riscv for 64bit and e.g. use riscv32 
and one day in the futre riscv128 for the other variants...

Also, this is a potential candidate for a future stable arch (i.e. having stable
keywords and stabilization).

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2024-06-26 20:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 17:33 [gentoo-dev] Arch Status and Future Plans Arthur Zamarin
2024-06-25 21:40 ` matoro
2024-06-25 22:55 ` James Le Cuirot
2024-06-26  0:06 ` Notion of stable depgraph vs stable keywords (Re: [gentoo-dev] Arch Status and Future Plans) Sam James
2024-06-28  4:17   ` [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: " Duncan
2024-06-28  5:16     ` Sam James
2024-06-26  0:14 ` Misc arch plans (Re: [gentoo-dev] " Sam James
2024-06-26 20:29   ` ia64, was: " Andreas K. Huettel
2024-06-26 20:45     ` matoro
2024-06-26  0:17 ` On the value (or not?) of stable keywords " Sam James
2024-06-26  0:19 ` time64 & LFS for 32-bit arches " Sam James
2024-06-26  0:20 ` x86 FP issues " Sam James
2024-06-28  5:20   ` Michał Górny
2024-06-26  7:38 ` [gentoo-dev] Re: Arch Status and Future Plans Florian Schmaus
2024-06-26  8:29   ` Christian Bricart
2024-06-26 20:44   ` Immolo
2024-06-26 19:47 ` nomenclature, was: Re: [gentoo-dev] " Andreas K. Huettel
2024-06-26 20:18 ` Andreas K. Huettel
2024-06-26 20:24 ` Andreas K. Huettel [this message]
2024-06-26 21:08 ` 32bit vs 64bit, was: " Andreas K. Huettel
2024-06-28 16:12 ` splitting keywords, " Andreas K. Huettel

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=3755379.MHq7AAxBmi@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --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