From nobody Mon Nov 24 18:46:24 2025 X-Original-To: arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dFZY95cxpz6Hffc for ; Mon, 24 Nov 2025 18:46:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qv1-f54.google.com (mail-qv1-f54.google.com [209.85.219.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dFZY93c2Kz3K3n for ; Mon, 24 Nov 2025 18:46:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qv1-f54.google.com with SMTP id 6a1803df08f44-8804f1bd6a7so43803616d6.2 for ; Mon, 24 Nov 2025 10:46:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764009996; x=1764614796; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=CuDyAdP8CQEcu/4joStxtNVhtOwVQK/Siaiq7JDrujQ=; b=T+lqLLeA9eacYzbGpw49tZoAbl4cml96MZNi2J1BdXrWW0YHl98t7aAPQYXvKN9K+0 3cSIw0+prv0WApEq9EfPDDhtx+7rpXCMohEgrPk+X7F3SAyWGXH7W2SHAPtlVbS4qFtw 02sb6XasfV6oEsastzX0dunH5xGFTzIFg8akJHzoro8Y10pnil+HoG8/NhyUf7L8lETH LAJd9G5j+2P5FS83u1WE+gNn/jMWw/NIn4GtDivRPDtx23g9H3Oe/ZFG8Ts3KeU4tdLx FdppcnvWlyorNbMHpbuA9NGO4/X1n0TC4axkcAdtDaPCD1sK26h8h3B1ojFFkfUL7jtT eIhQ== X-Forwarded-Encrypted: i=1; AJvYcCXi2iOcyND82gred7FjN00nRnglHoGCX/u7ySz6vClkxSHgONu5mMLvtCPSPQz0F4Bm85zq@freebsd.org X-Gm-Message-State: AOJu0YyHmv+ql3vOuVR2bot9Fk7TVNdwqRHbVRhWjxzMSfW7Hq9d7TO3 WOK1f8Ii1cg1F1K3A3PCE4m6eNgKi+e0nSasyR1XBKMf2OOXdDePzbG/WYI3i38mV8bMd3WwE0Y 7LOQor6bTf4WUgIQrL6LOn7D0kmnTaKk= X-Gm-Gg: ASbGnctFlIsVHA+Rret5o7hhjY66aTuZzUeAPSe3GFpad3v2KDl3fGwhviWzJSAhSwS adKCV4s8Skdih94+m1TqQO5MLJYn2LXPh37PRoPQprQhi9R1LOr0aj9T/6gnHkKN7si+b0LYD8x dQnp361DqQ4HGwi+h5LBnOKCLI+6JyJpVNIwpOsmWGs8GJOXxbphLYi7YL76r3XpFakbv2lZdXh 2F/cEPywcieeZkSHE7XVqd/XwKIAcVkJIMAcSCEO7u4W9WJO4Ul5n2ia3J23MqfbHCaAZLqeTFl lmAAuIXiTNb2KWm0JjFoZRkrdetjjw== X-Google-Smtp-Source: AGHT+IFCWZ7nBo723YvxC1NqoO+acwn30fmS16iQ8j9XGWYenekCnGEa8eAwvb4kDzGy5ebxqHpK1Jtrq0vnMuFt/v4= X-Received: by 2002:a05:6214:2465:b0:87d:c7ab:e5d0 with SMTP id 6a1803df08f44-8847c535bbcmr195042856d6.55.1764009996616; Mon, 24 Nov 2025 10:46:36 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 References: <86fra523cs.fsf@asn.ftfl.ca> <2114477564.125177.1764004306543.JavaMail.zimbra@raptorengineeringinc.com> In-Reply-To: <2114477564.125177.1764004306543.JavaMail.zimbra@raptorengineeringinc.com> From: Adrian Chadd Date: Mon, 24 Nov 2025 10:46:24 -0800 X-Gm-Features: AWmQ_bldCa8Uy4K-qilgcKqfuOxIBtiorixtTaSw9hkkOXstVkEemxAtpVEcJis Message-ID: Subject: Re: What's the plan for powerpc64 in FreeBSD 16 To: Timothy Pearson Cc: Joseph Mingrone , Minsoo Choo , "freebsd-arch@freebsd.org" , Lance Albertson via RT Content-Type: multipart/alternative; boundary="0000000000003a87be06445b95e7" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dFZY93c2Kz3K3n --0000000000003a87be06445b95e7 Content-Type: text/plain; charset="UTF-8" On Mon, 24 Nov 2025 at 09:11, Timothy Pearson < tpearson@raptorengineering.com> wrote: > > While I agree, I do want to ensure everyone understands that powerpc64be > != powerpc64le; it's very easy to inadvertently lump them together for this > sort of discussion. I expect over time we will end up in a state where > powerpc64be is broken and powerpc64le is functioning normally; the latter > should block, the former should not in my opinion. > Our code ends up in all kinds of places that aren't 100% little endian, including our network stack being in MBED stuff, and our wifi stack powering all those little ESP32 devices (apparently!) So having a working big-endian platform will help us keep our code honest and clean. I've got some ppc big endian stuff coming soon, and I'll go step up efforts to make emulator environments "just work" again if they don't. > > > A group at the University of Oregon has some POWER systems available to > us. If > > you are interested, please contact Lance Albertson, who is copied here, > as soon > > as possible. He's been asking whether anyone is using the hardware and > says we > > risk losing access if no one shows interest. > > > For all those folks that would like to help and don't have hardware > access, this is a great alternative to the Raptor bare metal boxes. > Especially for items like application development (e.g. furthering the Go > port Raptor put together) these machines are a great resource -- I know > Lance as well, so if there's any issues getting access set up just let me > know. > > I've reached out to lance separately to ask what the current/future state of it all is. Thanks! -adrian > Thanks! > > --0000000000003a87be06445b95e7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, 24 Nov = 2025 at 09:11, Timothy Pearson <tpearson@raptorengineering.com> wrote:

While I agree, I do want to ensure everyone understands that powerpc64be != =3D powerpc64le; it's very easy to inadvertently lump them together for= this sort of discussion.=C2=A0 I expect over time we will end up in a stat= e where powerpc64be is broken and powerpc64le is functioning normally; the = latter should block, the former should not in my opinion.
<= div>
Our code ends up in all kinds of places that aren't = 100% little endian, including our network stack being in MBED stuff, and ou= r wifi stack powering all those little ESP32 devices (apparently!)
So having a working big-endian platform will help us keep our code honest= and clean.

I've got some ppc big endian stuff= coming soon, and I'll go step up efforts to make emulator environments= "just work" again if they don't.
=C2=A0

> A group at the University of Oregon has some POWER systems available t= o us.=C2=A0 If
> you are interested, please contact Lance Albertson, who is copied here= , as soon
> as possible.=C2=A0 He's been asking whether anyone is using the ha= rdware and says we
> risk losing access if no one shows interest.


=C2=A0
For all those folks that would like to help and don't have hardware acc= ess, this is a great alternative to the Raptor bare metal boxes.=C2=A0 Espe= cially for items like application development (e.g. furthering the Go port = Raptor put together) these machines are a great resource -- I know Lance as= well, so if there's any issues getting access set up just let me know.=


I've reached out to lance separate= ly to ask what the current/future state of it all is. Thanks!



-adrian
=C2=A0
Thanks!

--0000000000003a87be06445b95e7--