From: Grant Grundler <grundler@puffin.external.hp.com>
To: Nicolas THOMAS <thomas@ispserv.grenoble.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Interoperability
Date: Thu, 22 Mar 2001 17:54:36 -0700 [thread overview]
Message-ID: <200103230054.RAA24759@puffin.external.hp.com> (raw)
In-Reply-To: Your message of "22 Mar 2001 13:22:03 +0100." <o051yrqc7tg.fsf@debian.grenoble.hp.com>
Nicolas THOMAS wrote:
> Does anyone of you have references/URL/opinion.... on interoperabilty
> purpose?
Could you provide details on what you mean by "interoperability"?
(Or specific applications that you need to run if you don't need
to build them from scratch)
> The systems I would like to be able to interoperate are :
> - Linux x86
> - Linux PA-risc 32bits
> - Linux PA-risc 64bits
> - HP-UX 11 64bits
Obviously not all four can run the same application binaries.
I do expect a pretty good level of source compatibility (90%+).
On the PARISC OS's, even a degree of binary compatibility.
Provided details, I can forward things not covered by HPUX to the
right people (caveat: no guarantee they will get fixed...). And
you are welcome to post patches for stuff in either 32 or 64-bit
parisc-linux kernels here.
(Or submit bug reports to bugs.parisc-linu.org.)
> I already know the STK: http://devresource.hp.com/STK/
Also try:
http://devresource.hp.com/OpenSource/Tools/OpenSourceLib.html
(I think this might be the same/related to the STK)
http://devresource.hp.com/LPK/
The LPK (Linux Porting Kit) seems to be pretty good (though not perfect).
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-03-23 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 12:22 [parisc-linux] Interoperability Nicolas THOMAS
2001-03-23 0:54 ` Grant Grundler [this message]
2001-03-23 10:06 ` Nicolas THOMAS
2001-03-23 16:29 ` Matthew Wilcox
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=200103230054.RAA24759@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=thomas@ispserv.grenoble.hp.com \
/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