9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] 19,21 ARM Dev Summit and porting to Solid-Run hardware
Date: Sun, 10 Oct 2021 00:40:59 -0700	[thread overview]
Message-ID: <YWKZC52HBGExAK+O@wopr> (raw)
In-Reply-To: <240F6F848FEAD210F41264091C6BF9CD@9p.sdf.org>

On Sun, Oct 10, 2021 at 04:28:40PM +1100, v@9p.sdf.org wrote:
> Hello,
> 
> How good are the chances for 9front to reachout to Arm industry partners (two links below, see) and port Plan 9 operating system to new ARM cpu?  I just discovered 9front has ports to bcm and bcm64 but those are older arm cpu.
> 
> Best,
> 
> -- 
> v
> 9SDF Public Access Plan 9 System
> => https://devsummit.arm.com arm DevSummit Oct 19-21 Virtual
> => https://developer.solid-run.com
> 

Generally speaking, step 1 to porting 9front to a certain piece of
hardware involves 9front users owning that hardware.  I know a couple of
us have i.MXM8MQ devices, but ARM ports in general suck because there
is no standardization.

The ARM developer summit is a useless sales event; if you need evidence,
look to the presentations from Amazon Web Services about disrupting HPC
(a market where they have almost zero presence) and talks from Red Hat
about disrupting automotive tech (same).  It's all aspirational bullshit
that outside sales executives need to justify their jobs.

Anyway, if you're interested in porting to the i.MX8M hardware, but
don't have the resources to buy a MNT Reform, this device would probably
be a good starting point:

https://coral.ai/products/dev-board

khm

  reply	other threads:[~2021-10-10  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10  5:28 v
2021-10-10  7:40 ` Kurt H Maier [this message]
2021-10-10  8:56   ` v
2021-10-10 14:53     ` hiro
2021-10-10 22:16     ` 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=YWKZC52HBGExAK+O@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).