From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Linux, Itanium and PA/RISC
Date: Mon, 24 Mar 2003 12:50:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705300@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705295@msgid-missing>
On Mon, Mar 24, 2003 at 01:23:32PM +0100, Adriano Galano wrote:
> If IPF support PA-RISC mapping is not easy to "port" the PA/RISC Linux,
> excluding architectural changes in the chipset or booting process?
Why would you want to? ia64 already has its own perfectly good Linux port.
> How HP/UX v 11.6 could be offer compatibility between PA/RISC and Itanium 2
> systems?
That's `11i v1.6'. Quoting from
http://www.hp.com/products1/unix/operating/choice/hp-ux11i_details.html
PA-RISC binary compatibility
HP-UX 11i version 1.6 includes the Aries dynamic code translation
technology as an integrated component. Aries is built on the close
relationship between the PA-RISC and Intel Itanium instruction sets
and provides binary compatibility for PA-RISC binaries on the Itanium
processor family. Aries can be used where performance is not critical
or where it is not possible to create a native Itanium processor
family binary.
> How "exact" is the PA-RISC mapping on the IA-64 core?
Not particularly close. If you look at the assembly language level,
there's a lot of similarities, but there's a lot of differences too.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-03-24 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 10:41 [Linux-ia64] Linux, Itanium and PA/RISC Adriano Galano
2003-03-24 12:10 ` Matthew Wilcox
2003-03-24 12:23 ` Adriano Galano
2003-03-24 12:50 ` Matthew Wilcox [this message]
2003-03-24 19:19 ` David Mosberger
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-105590723705300@msgid-missing \
--to=willy@debian.org \
--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.