Computer Old Farts Forum
 help / color / mirror / Atom feed
From: david at kdbarto.org (David Barto)
Subject: [COFF] [SPAM] Re: Architectures -- was [TUHS] 68k prototypes & microcode
Date: Fri, 5 Feb 2021 10:31:20 -0800	[thread overview]
Message-ID: <A5214B93-187F-4C6B-8B13-82F7330FF4E7@kdbarto.org> (raw)
In-Reply-To: <20210205145618.GE13916@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]


> On Feb 5, 2021, at 6:56 AM, Larry McVoy <lm at mcvoy.com> wrote:
> 
> If Intel doesn't want to make money off of the cheap, but very high
> volume, $20 SOC, Apple has shown that it has the chops to make a cheap,
> fast, and power sipping M1 chip.  Pretty impressive and if I were Intel,
> I'd be nervous.  Apple has shown they can switch architectures pretty
> painlessly repeatedly.  The x86 lock in isn't much of a lock in these
> days.

On my morning walk with a friend we discussed what iNtel is going to 
do about the M1 and coming M2, M3 chips from Apple. His contention
was that iNtel can’t do much because each vendor will want a different
configuration of the chip; more cores fewer GPU’s, more GPU’s fewer
cores, more of both, more/less RAM on board, etc.

It is unlikely that a SOC from iNtel can’t meet this varied selection so
it is unlikely to move into that market. It does have a solid lock on the
server market and it may just stick with that for the foreseeable future. 
The problem is that if the newer M2/M3 chips can perform at server
performance while retaining the low power consumption that the M1
has done, iNtel may see that its best days are past.

Disclaimer: I’ve got an M1 mini, and I have to say it is stunningly fast.

	David





  reply	other threads:[~2021-02-05 18:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1l5RL3-0002iv-Qv@tanda>
     [not found] ` <abf50209-5730-f5a0-0fd6-aec13ee68440@e-bbes.com>
     [not found]   ` <202102030759.1137x7C2013543@freefriends.org>
     [not found]     ` <CAHTagfHdykiYmqPCkhQkUQTU8fLqJBukPOyj-k1ef=Ur9rqH+Q@mail.gmail.com>
     [not found]       ` <202102030858.1138wuqd011051@freefriends.org>
     [not found]         ` <CAHTagfGOC7vgE2Os+kuP4oGzvot2kG3MERpQdLb2EoEhUoFpyg@mail.gmail.com>
     [not found]           ` <CAC20D2M_33YdQyuHdb7EM-UVNcdM0TXz9eJXpTftHekWxK0=Dg@mail.gmail.com>
2021-02-05  8:53             ` [COFF] [TUHS] AT&T 3B1 - Emulation available peter
2021-02-05 17:41               ` [COFF] " cym224
     [not found]             ` <27567.1612399305@hop.toad.com>
     [not found]               ` <bce2c77e-dd8d-a0f2-5b27-0f9239c76738@kilonet.net>
     [not found]                 ` <alpine.BSF.2.21.9999.2102041316080.70858@aneurin.horsfall.org>
     [not found]                   ` <4db6108e-73f0-6498-fe45-3fd422d1f389@kilonet.net>
     [not found]                     ` <alpine.BSF.2.21.9999.2102051312440.70858@aneurin.horsfall.org>
2021-02-05  2:53                       ` [COFF] [TUHS] 68k prototypes & microcode lm
     [not found]                 ` <20210204013356.GA16541@mcvoy.com>
2021-02-05  9:09                   ` peter
2021-02-05 14:36                   ` [COFF] Architectures -- was " clemc
2021-02-05 14:56                     ` [COFF] [SPAM] " lm
2021-02-05 18:31                       ` david [this message]
2021-02-05 22:02                       ` dave
2021-02-05 19:16                     ` [COFF] " athornton

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=A5214B93-187F-4C6B-8B13-82F7330FF4E7@kdbarto.org \
    --to=coff@minnie.tuhs.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).