From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Definitely unslung
Date: Wed, 6 Jun 2007 20:03:41 -0500 [thread overview]
Message-ID: <012f01c7a89f$b0adb8f0$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070606195406.GB14562@grml>
There is nothing wrong with Intel. The discussion was comparing
x86 compatible with ARM, two different animals that serve two
different purposes. The x86 architecture is CISC and has more
instructions and generally many more transistors and higher clock
speed, more RAM, more peripherals, and requires a lot of power
relative to ARM which uses RISC, less instructions, simpler bus
architectures, lower clock speed, usually much less transitors
and therefor much lower power and less heat generated.
The x86 architecture is actually preferrable if you can deal with
the power and heat requirements, especially for the application
compatibility reasons. Linux on ARM works great but you can't
expect drivers, and therefore many applications to just work.
At minimal they need to be compiled, and in many cases they
will not work without re-writing drivers. There is no ISA or PCI
bus on ARM, you have ABI or EABI or some proprietary bus
depending on manufacturer. Most phones use ARM processor
in fact ARM owns that whole space. ARM is desireable for
small portable devices, but in the sub-notebook category it
still makes sense to use x86.
I am working with ARM specifically for the low power and
low heat benefits, but as I said it's a completely different class
of applications. Even if you're not dealing with graphics like
x-windows, there is little source compatibility, except where
no hardware specific drivers are involved. There is no such
thing as BIOS on ARM, most systems boot from a kernel
loaded onto flash with embedded file system and scaled
down versions of standard tools for example busybox.
There is lots to learn and more work to do when developing
software, setting up a cross platform development toolchain,
often JTAG is required to flash the kernel, you're generally
much more concerned about memory limitations and other
implications of using a smaller scale architecture.
Also, Intel is a brand name, they made StrongARM which
evolved to X-Scale, also RISC and uses the original ARM
as core with Intel specific extensions. So using the name
Intel is only a brand, the discussion was x86 versus ARM,
in general x86 is preferrable for anything larger than PDA,
ARM for PDA and smaller.
-- Doug
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
Georgina Joyce
` C.M. Brannon
` Kerry Hoath
` Doug Sutherland
` Buddy Brannan
` Kerry Hoath
` Travis Siegel
` Buddy Brannan
` David Poehlman
` Buddy Brannan
` David Poehlman
` Travis Siegel
` Alex Snow
` Doug Smith
` Gregory Nowak
` Travis Siegel
` Doug Smith
` Travis Siegel
` David Poehlman
` Doug Sutherland [this message]
` Doug Smith
` Doug Sutherland
` Doug Sutherland
` Travis Siegel
` Gregory Nowak
` Travis Siegel
` Luke Yelavich
` Alex Snow
` Travis Siegel
` David Poehlman
` David Poehlman
` Alex Snow
` Georgina Joyce
` Travis Siegel
` Buddy Brannan
` Travis Siegel
` Buddy Brannan
` Kirk Reiser
` Georgina Joyce
` Georgina Joyce
` Alex Snow
` C.M. Brannon
` Doug Sutherland
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='012f01c7a89f$b0adb8f0$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).