All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jody Bruchon <jbruchon@nc.rr.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: Porting to different architectures
Date: Tue, 01 Aug 2006 14:22:22 +0100	[thread overview]
Message-ID: <1154438542.15540.1.camel@localhost.localdomain> (raw)
In-Reply-To: <44CEE649.1000607@nc.rr.com>

Ar Maw, 2006-08-01 am 01:27 -0400, ysgrifennodd Jody Bruchon:
> On top of that, the 8088 isn't really even used in embedded stuff 
> anymore AFAIK.  From what I understand, the embedded Intel CPU of choice 
> is an i386EX and that likely can run Linux unmodified.

Some of the embedded 386 chips can some can't. Not all of them have a
paging MMU some have just segmentation. Nowdays the CPU of choice seems
to be either the VIA fanless processors or the AMD (ex Nat Semi) Geode
system on a chip, both of which are Pentium class or higher


  reply	other threads:[~2006-08-01 13:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 14:09 Porting to different architectures chriscureau
2006-07-31 15:00 ` Hans
2006-07-31 15:35   ` Richard Wallman
2006-07-31 16:03     ` David Given
2006-07-31 16:24       ` Richard Wallman
2006-07-31 16:32         ` David Given
2006-07-31 17:42     ` Jody Bruchon
2006-08-01  6:49       ` Richard Wallman
2006-08-01 17:15         ` Segin
2006-07-31 19:47     ` Javier Sedano
2006-07-31 21:44       ` Alan Cox
2006-08-01  2:57         ` Tom McCabe
2006-08-01  5:27           ` Jody Bruchon
2006-08-01 13:22             ` Alan Cox [this message]
2006-08-01 14:41               ` Vikas N Kumar
2006-08-01 15:28                 ` Hans
2006-07-31 15:16 ` Petr Koval
2006-07-31 15:29   ` CVS access Mattia Jona-Lasinio
2006-07-31 15:43     ` Petr Koval
2006-07-31 15:51     ` Petr Koval
2006-08-02 13:24       ` Mattia Jona-Lasinio

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=1154438542.15540.1.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jbruchon@nc.rr.com \
    --cc=linux-8086@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.