From: "H . J . Lu" <hjl@lucon.org>
To: Brian Murphy <brian@murphy.dk>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Problems with mips2 compiled libc and linux 2.4.3
Date: Mon, 18 Jun 2001 11:22:53 -0700 [thread overview]
Message-ID: <20010618112253.A28744@lucon.org> (raw)
In-Reply-To: <3B2E4458.1637A08A@murphy.dk>; from brian@murphy.dk on Mon, Jun 18, 2001 at 08:11:36PM +0200
On Mon, Jun 18, 2001 at 08:11:36PM +0200, Brian Murphy wrote:
>
> it is linked with a glibc compiled with -mips2. It is the second if test
I patched my kernel to get around it.
>
> which fails if any of the high 4 bits in the flags are set. According to
> the
> specs these are set for the various mipsx (x != 1) flavors - this seems
> to mean
> that we do no allow anything higher than mips1 run on linux - can this
> be
> true? If so, why?
There is no very good reason. I think we should add a MIPS ISA level
field in the mips cpuinfo so that we can check what ISA the hardware
support at the run-time.
H.J.
next prev parent reply other threads:[~2001-06-18 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 18:11 Problems with mips2 compiled libc and linux 2.4.3 Brian Murphy
2001-06-18 18:22 ` Ralf Baechle
2001-06-18 18:50 ` Brian Murphy
2001-06-18 18:22 ` H . J . Lu [this message]
2001-06-18 19:41 ` Ralf Baechle
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=20010618112253.A28744@lucon.org \
--to=hjl@lucon.org \
--cc=brian@murphy.dk \
--cc=linux-mips@oss.sgi.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