From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] non-PC hardware
Date: Tue, 27 Mar 2007 20:06:22 -0400 [thread overview]
Message-ID: <949f4efc668a768d724d2b5399f49e7a@coraid.com> (raw)
In-Reply-To: <p0624081bc22f52bb96dd@[192.168.127.192]>
> Despite having just sold off the X-Scale embedded to Marvel, I expect Intel to get back into the embedded game with ultra low power X86 chips. Alpha is gone, Sparc is Sun only, MIPs might survive as an embedded architecture.
intel still sells embedded xscale processors. i looked at this a while
back
http://www.intel.com/design/network/prodbrf/309430.htm
kind of looks like a network-cell processor, doesn't it?
> I think all of the Intel chips going forward are going have EM64T. So plan9 should have good support for that. Plus you get 8 more registers with EM64T, which the architecture could really use.
i'm not sure what advantage more registers present in modern (amd|intel)/x64
chips. a value in l1 cache is only 1 cycle away. so i'm not sure what the
practical difference is between something in a register and something in l1.
> Because the new Apple stuff is X86 based, ports shouldn't be too hard, delta chip support.
i'd agree with it not being hard. but that is a considerable amount of
work. granted, most architechtures are not as bad as the pee cee, but
one still has to interface with the boot rom, figure out how to find
and configure memory, set up interrupts, figure out how to talk to
the bus, how to print "hello, world", etc.
ignoring the pc, since it's a pig, here's how much code is in each of the
various ports (my somewhat out-of-date copy):
bitsy 15240
ppc 10315
mtx 7863
while new ports will be great, you need to be prepared for some heavy
lifting.
- erik
next prev parent reply other threads:[~2007-03-28 0:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 20:31 maht
2007-03-27 20:41 ` John Floren
2007-03-27 20:43 ` ron minnich
2007-03-27 20:54 ` Lorenzo Fernando Bivens de la Fuente
2007-03-27 21:09 ` Paul Lalonde
2007-03-27 21:57 ` ron minnich
2007-03-27 22:05 ` Paul Lalonde
2007-03-27 20:56 ` John Floren
2007-03-27 20:58 ` erik quanstrom
2007-03-28 15:42 ` Iruata Souza
2007-03-28 16:05 ` Jack Johnson
2007-03-28 16:14 ` David Arnold
2007-03-28 16:14 ` andrey mirtchovski
2007-03-28 16:19 ` andrey mirtchovski
2007-03-28 17:09 ` erik quanstrom
2007-03-28 17:22 ` Sape Mullender
2007-03-28 16:21 ` Francisco J Ballesteros
2007-03-28 16:36 ` Jack Johnson
2007-03-28 16:18 ` Tim Wiess
2007-03-29 10:55 ` Harri Haataja
2007-03-29 13:12 ` erik quanstrom
2007-03-27 23:34 ` Lawrence E. Bakst
2007-03-28 0:06 ` erik quanstrom [this message]
2007-03-28 4:19 ` William Josephson
2007-03-28 13:29 ` Charles Forsyth
2007-03-28 0:11 ` David Arnold
2007-03-28 9:28 ` Anel Philippe
[not found] ` <p0624081bc22f52bb96dd@192.168.127.192>
2007-03-28 16:14 ` Lluís Batlle
2007-03-28 16:17 ` Tim Wiess
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=949f4efc668a768d724d2b5399f49e7a@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).