9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Shawn Rutledge <lists@ecloud.org>
To: 9front@9front.org
Subject: Re: [9front] Big endian hardware.
Date: Thu, 6 Mar 2025 17:35:04 +0100	[thread overview]
Message-ID: <D34ADD5D-0248-4275-8706-9B04DFAAB00E@ecloud.org> (raw)
In-Reply-To: <CA+sOHrzZe1negvYcSY+LQptJ=PixJmVP98+aGD2Qg5y-Z=fKpw@mail.gmail.com>


> On Mar 6, 2025, at 11:20, Pär Moberg <ghostdewolf@gmail.com> wrote:
> 
> Hello,
> With NetBSD release of a Wii version and that they have a big endian release for raspberry pi 1 to 3plus, I was wondering if there is any as easily available hardware that run big endian and has a 9front port?
> I have a fascination with big endian for some reason. 
> //Pär 

An old powermac maybe?  I have a G5 at the office for testing Qt on big-endian on Linux (not that I get around to it very often): it’s fine for that sort of thing, and those machines aren’t worth much anymore, despite being quite the beasts of their time.  And you can google and find out about the Plan 9 PPC porting, discussion about Power9 and so on.

It’s good that one endian won though, IMO, so maybe we can eventually forget about “network byte order” being big-endian, and stop flipping bytes around pointlessly, especially in new protocols.  9p is little-endian (from what I read): that seems like a good choice.


  reply	other threads:[~2025-03-06 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 10:20 Pär Moberg
2025-03-06 16:35 ` Shawn Rutledge [this message]
2025-03-06 17:12 ` Jacob Moody
2025-03-06 18:17   ` adventures in9
2025-03-06 18:50   ` Pär Moberg
2025-03-06 19:35     ` Jacob Moody

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=D34ADD5D-0248-4275-8706-9B04DFAAB00E@ecloud.org \
    --to=lists@ecloud.org \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).