From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] amd64 port
Date: Wed, 13 Oct 2010 16:42:07 -0700 [thread overview]
Message-ID: <AANLkTin+Edaq6Sx9MMvqtf6X7ATBYrKMERTYQ-NnUs-W@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=uR06MsL42=i9b3MALMm-6h+2QnEaCr_3VrP9q@mail.gmail.com>
ppc64 and amd64 support exists. the ppc64 port is partial and is
available publically. It is my understanding that the amd64 is
partial and available to those who ask. Things which are missing are
devices and other bits to make it actually useful, but the core
changes for 64-bit support are in place and there are 64 bit
compilers.
-eric
On Wed, Oct 13, 2010 at 4:28 PM, Tharaneedharan Vilwanathan
<vdharani@gmail.com> wrote:
> hi all,
>
> i am just posting a question that has been in my mind for a while.
>
> to me, it looks like 64-bit computing has caught up very well. even
> smaller processors like atom supports 64-bit instruction set.
>
> on the contrary, while plan9 supported 32-bit processors ahead of
> other OSes, it is yet to support 64-bit.
>
> i am happy to see the plan9 port to many platforms (sheevaplug,
> beagleboard, etc) but i am also wondering if they are really as
> practical and widely usable as, say amd64 platform. (for e.g. i bought
> a sheevaplug long back, ran plan9 then kept aside waiting for more
> support).
>
> so i am wondering if we should make plan9/inferno support 64-bit at a
> higher priority. to me, it looks like 64-bit and VM support (vmware,
> parallels, etc) will be key for plan9/inferno to go a long way. am i
> right?
>
> please pass your opinion.
>
> thanks
> dharani
>
>
next prev parent reply other threads:[~2010-10-13 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 23:28 Tharaneedharan Vilwanathan
2010-10-13 23:42 ` Eric Van Hensbergen [this message]
2010-10-13 23:54 ` John Floren
2010-10-14 4:17 ` David Leimbach
2010-10-15 5:29 ` Tharaneedharan Vilwanathan
2010-10-15 17:01 ` Eric Van Hensbergen
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=AANLkTin+Edaq6Sx9MMvqtf6X7ATBYrKMERTYQ-NnUs-W@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
/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).