All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] First Step
Date: Mon, 24 Sep 2001 20:32:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805246@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805239@msgid-missing>

>>>>> On Fri, 21 Sep 2001 13:31:24 -0700, cfk@pacbell.net said:

  Charles> Gentlemen, please pardon if a newbie for a bit. I have the
  Charles> hp cd now with the various rpm files (NUE-1_1, NUE_FS-1,
  Charles> SDI-0_94 & SKI_LINU). I have a reasonable amount of
  Charles> experience in Linux from the x86 viewpoint, but I would
  Charles> like to understand IA-64. So, I would appreciate a few
  Charles> pointers on how to get started.

  Charles> Do I try to rpm install these on a X86 system, probably
  Charles> not.

Yes, the Ski and NUE RPMS are indeed for x86 systems.  Once installed,
you can issue the "nue" command and that will put you in a virtual
environment that looks like an IA-64 machine).

  Charles> I don't yet know how to get an IA-32 system up and
  Charles> running.

Note that IA-32 is just a different name for x86.  They are the same
thing.

  Charles> Assuming I can use one of my existing computers to learn
  Charles> how to do IA-32 and IA-64 work, what is the series of
  Charles> steps.

Since you already know x86, there is nothing you need to do to learn
IA-32.

As for IA-64: NUE and Ski will allow you to do just that.  Since it's
based on a simulator, it will be too slow to run complicated apps, but
for learning the architecture and development and debugging, it's
quite useful.  We even continue to use it for Linux kernel
development.

	--david


      reply	other threads:[~2001-09-24 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-21 20:31 [Linux-ia64] First Step cfk
2001-09-24 20:32 ` David Mosberger [this message]

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=marc-linux-ia64-105590698805246@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@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.