From: Markus Schaber <markus.schaber@student.uni-ulm.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [parisc-linux] Re: [Linux-ia64] Linux, Itanium and PA/RISC
Date: Wed, 26 Mar 2003 12:32:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705317@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705314@msgid-missing>
Hi,
m.delahaye@esiee.fr (Matthieu Delahaye) wrote:
> > [...]
> > As far as I know, the PA-Risc instruction mapping is done with lots
> > of software help. The concept is a bit like JIT-Compilers in Java.
> > (It is easier to do this when having a RISC code with equal
> > instruction length compared to ugly X86 code.) As long as my
> > knowledge is correct, you therefore cannot run any PA-RISC OS
> > directly on the Hardware, but you can run PA-RISC Software in any OS
> > that supports the instruction mapping, maybe one can even run a
> > PA-RISC OS inside a virtual PA-RISC Machine on Itaniums. (However I
> > don't know any such VM.)
>
> AFAIK, your knowledge correspond to what I know.
[...]
> But perhaps I didn't understand and you told me you already try it
> following David's explanation ?
I didn't want to argue against you, because I think you're right. :-)
I just wanted to clarify the difference between both "legacy"
Architectures that the Itanium claims to support.
Markus
next prev parent reply other threads:[~2003-03-26 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 10:07 [parisc-linux] Re: [Linux-ia64] Linux, Itanium and PA/RISC Matthieu Delahaye
2003-03-26 11:51 ` Markus Schaber
2003-03-26 12:09 ` Matthieu Delahaye
2003-03-26 12:32 ` Markus Schaber [this message]
2003-03-26 16:25 ` n0ano
2003-03-26 16:51 ` Grant Grundler
2003-03-26 17:20 ` Christian Groessler
2003-03-26 17:56 ` n0ano
2003-03-26 17:59 ` Adriano Galano
2003-03-26 18:10 ` Matthieu Delahaye
2003-03-26 18:14 ` Markus Schaber
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-105590723705317@msgid-missing \
--to=markus.schaber@student.uni-ulm.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox