From: Stanley Lieber <firstname.lastname@example.org>
Subject: Re: [9front] build iso from arm64
Date: Sat, 7 May 2022 09:51:25 -0400 [thread overview]
Message-ID: <F7B9DA1E-47BB-4B7E-9440-7F458992952C@stanleylieber.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
a few of us have these things. cinap has it booting to userspace over serial connection, but nobody has graphics working yet. i don’t think anything has been committed yet.
> On May 7, 2022, at 1:30 AM, email@example.com wrote:
> Quoth Kurt H Maier <firstname.lastname@example.org>:
>>> 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.
> Good to know. I'm glad I didn't waste too much time and getting further lost.
> Basically I need to pour through the different arm repo's and puzzle what I can for
> NXP/Freescale i.MX8MQ with 4x ARM Cortex-A53 cores (1.5 GHz), 1x Cortex-M4F core.
> not familiar with paqfs. So that was interesting but I could comment all that out.
> This is an MNT reform laptop. After putting it together it seems pretty stable and I'm interest
> in porting plan9 to this thing. I expect I might need to dig into the ARM® Cortex®-A53 MPCore Processor
> Revision: r0p3 and try to figure this thing out.
> But before I do this has anyone made any headway in this area? I'm enjoying the laptop. The keyboard
> is a bit funky the mapping is different but all in all its enjoyable laptop and a bit sturdy.
> Recommendations greatly welcomed.
[-- Attachment #2: Type: text/html, Size: 3109 bytes --]
next prev parent reply other threads:[~2022-05-07 13:53 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 [this message]
2022-05-07 15:14 ` Thaddeus Woskowiak
2022-05-07 18:49 ` Kurt H Maier
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).