From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] build iso from arm64
Date: Fri, 6 May 2022 21:45:24 -0700 [thread overview]
Message-ID: <YnX5ZIcKY5LEyqdY@wopr> (raw)
In-Reply-To: <407f2cc8-b67b-43cf-849e-096dc141a21b@riseup.net>
On Sat, May 07, 2022 at 04:36:29AM +0000, mkf9 wrote:
> Is it a problem with arm itself,
> or we don't have code to have
> a unified arm kernel (bcm+omap+etc) yet?
It's a problem with ARM itself. Everyone pays ARM for processor designs
and then bolts random shit to it. Since the random shit is not subject
to any standardization effort, every device is a special snowflake.
khm
next prev parent reply other threads:[~2022-05-07 4:48 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 [this message]
2022-05-07 5:29 ` william
2022-05-07 13:51 ` Stanley Lieber
2022-05-07 15:14 ` Thaddeus Woskowiak
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=YnX5ZIcKY5LEyqdY@wopr \
--to=khm@sciops.net \
--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).