9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 386
Date: Sun, 30 Oct 2005 13:34:10 -0700	[thread overview]
Message-ID: <9ab217670510301234p506ae1e3j@mail.gmail.com> (raw)
In-Reply-To: <20051030201222.GD23235@server4.lensbuddy.com>

2005/10/30, Uriel <uriell@binarydream.org>:
> On Sun, Oct 30, 2005 at 03:02:34PM -0500, jmk@plan9.bell-labs.com wrote:
> > Seems to me the concensus on this list is that we
> > should keep the support so that Plan 9 will continue
> > to run on all the broken non-Intel hardware clones
> > and emulators.
> Do really those emulators and clones require 386 support? From this
> thread my conclusion was that it is not an issue.

They don't. FreeBSD without 386 support runs in VMWare and qemu. Bochs
is dying as far as I can tell. I feel that removing support for 386 is
fine, and my understanding after reading this thread is that we're
worried about embedded platforms, and it seems that most of these that
we run on are already 486 or higher.

With regard to the instruction set clones, I've run post-386-debacle
FreeBSD (and seen it run) on several clone boards including the Via
embedded stuff and Geode stuff.

My understanding of how this got into the embedded chipset stuff was
that a suggestion was made to deprecate 486 as well, which I don't
think we should do at all. Get rid of 386, support 486+.

> I seriously doubt requiring Pentium would be a problem for most
> emulators or recent embedded hardware.

It is a big problem for recent embedded hardware. Until the
pentium-based embedded boards get cheaper, it's still nice to have
cheap-ish 486 boards, and these will _not_ go anywhere for a while,
especially since their price will fall more if the pentium boards get
cheaper.

> Hell, qemu(the only emulator that matters this days as far as Plan 9 is
> concerned) can even emulate x86_64:
>
> http://fabrice.bellard.free.fr/qemu/status.html
>
> uriel

--Devon


  reply	other threads:[~2005-10-30 20:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 15:08 Russ Cox
2005-10-29 15:26 ` Lucio De Re
2005-10-29 19:07 ` William Josephson
2005-10-29 20:01   ` jmk
2005-10-29 20:06     ` Lucio De Re
2005-10-29 21:07     ` Uriel
2005-10-29 21:18       ` jmk
2005-10-29 21:51     ` Ronald G Minnich
2005-10-29 22:31       ` Francisco J Ballesteros
2005-10-30  0:50         ` Ronald G Minnich
2005-10-30  5:41           ` Jack Johnson
2005-10-30 16:15             ` Ronald G Minnich
2005-10-30 20:02             ` jmk
2005-10-30 20:12               ` Uriel
2005-10-30 20:34                 ` Devon H. O'Dell [this message]
2005-10-30 20:52                   ` jmk
2005-10-30 21:15                     ` Devon H. O'Dell
2005-10-30 22:56                       ` jmk
2005-10-31  0:20                         ` Ronald G Minnich
2005-10-31  0:49                           ` Russ Cox
2005-10-31 21:26                             ` Dave Eckhardt
2005-10-30 21:27                     ` Mike Haertel
2005-10-31 10:06                       ` Charles Forsyth
2005-10-30 22:11                     ` Ronald G Minnich
2005-10-30 21:16                       ` Francisco J Ballesteros
2005-10-30 21:53               ` Ronald G Minnich
2005-10-29 23:45       ` John DeGood
2005-10-30  0:04         ` William Josephson
2005-10-30 12:59       ` Brantley Coile
2005-10-30  1:14     ` geoff
2005-10-29 20:22 ` Christopher Nielsen

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=9ab217670510301234p506ae1e3j@mail.gmail.com \
    --to=devon.odell@gmail.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).