Date: Mon, 24 Nov 2025 10:46:24 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Timothy Pearson <tpearson@raptorengineering.com> Cc: Joseph Mingrone <jrm@freebsd.org>, Minsoo Choo <minsoochoo0122@proton.me>, "freebsd-arch@freebsd.org" <arch@freebsd.org>, Lance Albertson via RT <powerdev-request@osuosl.org> Subject: Re: What's the plan for powerpc64 in FreeBSD 16 Message-ID: <CAJ-VmomZ=TqGsMCGKcasNnWUb9YbTgdYK45HnR_p7wV%2BKYA%2BhA@mail.gmail.com> In-Reply-To: <2114477564.125177.1764004306543.JavaMail.zimbra@raptorengineeringinc.com> References: <CANCZdfrQthqYeGYD_9LRcH94JJZuF2%2BUxAqf7Lcoe6p5VzJf9g@mail.gmail.com> <CAFYkXjn%2BTWHevtMtPj9V7MLMHBChL%2BeqiBv1Puru0pkzRT14Vg@mail.gmail.com> <CY-i-pELVCQmckLJhTf0N-dArld84tgcWHIk6kdCByOWrGr4D2ukJaaXT8ryACKy3YAQDfgOwmAuWCb7_TshAEV6HG5hDG6jzvL_xfTmNx0=@proton.me> <86fra523cs.fsf@asn.ftfl.ca> <2114477564.125177.1764004306543.JavaMail.zimbra@raptorengineeringinc.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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! > > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, 24 Nov 2025 at 09:11, Timothy Pearson <<a href="mailto:tpearson@raptorengineering.com">tpearson@raptorengineering.com</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> 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.<br></blockquote><div><br></div><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 our wifi stack powering all those little ESP32 devices (apparently!)</div><div>So having a working big-endian platform will help us keep our code honest and clean.</div><div><br></div><div>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.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> > A group at the University of Oregon has some POWER systems available to us. If<br> > you are interested, please contact Lance Albertson, who is copied here, as soon<br> > as possible. He's been asking whether anyone is using the hardware and says we<br> > risk losing access if no one shows interest.<br> <br></blockquote><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> 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.<br> <br></blockquote><div><br></div><div>I've reached out to lance separately to ask what the current/future state of it all is. Thanks!</div><br class="gmail-Apple-interchange-newline"><div><br></div><div><br></div><div><br></div><div>-adrian</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Thanks!<br> <br> </blockquote></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomZ=TqGsMCGKcasNnWUb9YbTgdYK45HnR_p7wV%2BKYA%2BhA>