9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Thaddeus Woskowiak <tswoskowiak@gmail.com>
To: 9front <9front@9front.org>
Subject: Re: [9front] build iso from arm64
Date: Sat, 7 May 2022 11:14:37 -0400	[thread overview]
Message-ID: <CAG3JMtadAge5B04e5r2-tqO5edV7EE0sTzLEzhSeH2cyTX-0ug@mail.gmail.com> (raw)
In-Reply-To: <F7B9DA1E-47BB-4B7E-9440-7F458992952C@stanleylieber.com>

I dont think it's fair to blame Arm as no one bothered to build a
standard Arm platform in the same vein as the PC. Before the IBM PC XT
and later AT standard existed the home computer industry was in a
similar situation with random intel, wd, zilog, motorola systems
kicking about with incompatibilities between them. IBM was very
influential and relevant at the time so it stands to reason that the
PC was in a unique position to take off. Who is going to IBM the Arm
platform? Microsoft? Amazon? Google? Facebook? They're too busy
building ant farms.

The PC platform is an agreement between manufacturers to use a
standard boot firmware (bios/uefi), standard hardware interfaces (e.g.
pci, ata, vesa, etc, ac97/hda), and booting procedures (mbr/gpt).
Hardware is wired predictably so video, keyboard, com ports, timers,
etc are always on the same addresses, interrupt and dma ports meaning
drivers don't have to be tweaked or re-written between vendors.
Nowadays we have such complex (batshit even) hardware that we need to
manage it via a subsystem which we know as acpi that adds a whole
layer of abstraction to talk to fans and firmwares.

The closest we have had is the Microsoft Windows RT Surface which
bolted wintel PC baggage to Arm such as uEFI and ACPI. Basically an
Arm PC. Raspberry pi is an honorable mention by fitting their firmware
with pc like booting from usb, pxe and so on but pi firmware isn't
portable as the pi hardware is batshit wherein the gpu handles the
bootstrapping, not the Arm cpus....

It would be nice to have a platform controller, firmware and api using
9p so we can mount and walk the platform controller on boot then find
and configure what we need. Though, for anything to succeed, it would
need the weight of an IBM behind it.

  reply	other threads:[~2022-05-07 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  3:47 william
2022-05-06 15:34 ` ori
2022-05-07  3:31   ` william
2022-05-07  3:45     ` ori
2022-05-07  4:03     ` ori
2022-05-07  4:36       ` mkf9
2022-05-07  4:45         ` Kurt H Maier
2022-05-07  5:29           ` william
2022-05-07 13:51             ` Stanley Lieber
2022-05-07 15:14               ` Thaddeus Woskowiak [this message]
2022-05-07 18:49                 ` Kurt H Maier

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=CAG3JMtadAge5B04e5r2-tqO5edV7EE0sTzLEzhSeH2cyTX-0ug@mail.gmail.com \
    --to=tswoskowiak@gmail.com \
    --cc=9front@9front.org \
    --subject='Re: [9front] build iso from arm64' \
    /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

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).