9front - general discussion about 9front
 help / color / mirror / Atom feed
From: v@9p.sdf.org
To: 9front@9front.org
Subject: Re: [9front] 19,21 ARM Dev Summit and porting to Solid-Run hardware
Date: Sun, 10 Oct 2021 19:56:36 +1100	[thread overview]
Message-ID: <1FEDF913F9FC55C72BF98FA67420A07B@9p.sdf.org> (raw)
In-Reply-To: <YWKZC52HBGExAK+O@wopr>

Quoth Kurt H Maier <khm@sciops.net>:
> I know a couple of
> us have i.MXM8MQ devices, but ARM ports in general suck because there
> is no standardization.

Pardon my French.  The MNT Reform (laptop of legacy standard parts) looks *shit*.

=> https://mntre.com/media/reform_md/2020-11-27-reform-production-update-nov-2020.html MNT Reform Laptop

Thank you for the pointer to the dev board, I can afford.

=> https://coral.ai/products/dev-board i.MX8M cheaper alternative to iMXM8MQ

What you say about industry practices is true from your point of view.  Maybe the 99% is invisible to you and the people in the small niches you know of.  I understand the Fujitsu Fugaku Arm chip tops HPC for now.  I know Tesla uses Red Hat, NASA and others use AWS, and you can't say Tesla has not transformed autotech.

For me a happy outcome would be to score resources from ARM and Solid-Run for 9front devs to work on, charming the marketing execs and their aspirated visions for the future we all want to have is fine by me.

Best,

-- 
v
9SDF Public Access Plan 9 System

  reply	other threads:[~2021-10-11  9:07 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
2021-10-10  8:56   ` v [this message]
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=1FEDF913F9FC55C72BF98FA67420A07B@9p.sdf.org \
    --to=v@9p.sdf.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).