From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Tell R4k SC and MC variations apart
Date: Wed, 25 Sep 2013 13:02:31 +0200 [thread overview]
Message-ID: <20130925110231.GM31185@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.03.1309250019490.17450@linux-mips.org>
On Wed, Sep 25, 2013 at 12:37:42AM +0100, Maciej W. Rozycki wrote:
> > My reservations may have been about userland reading /proc/cpuinfo and
> > looking at the CPU type. Some software may know how to handle the
> > PC/SC variants but not the MC versions. But this seems to be a fairly
> > weak concern - and I trust you checked gcc's parsing of /proc/cpuinfo.
>
> Actually I wasn't actually aware GCC's got /proc/cpuinfo-based native
> arch support for the MIPS target these days, thanks for the hint.
>
> I have now checked the relevant source file and support is pretty weak
> there, only half a dozen processors are recognised and no R4k model is
> among them. In any case strstr is used to check for matches there so I'd
> expect strings like "R4000" or "R4400" without a further suffix to be
> chosen.
It'd be worth a change in particular for users how higher end CPUs and
enhanced ISAs such as Octeons.
Or should we just default to O32 w/ MIPS I + LL/SC as the MIPS Esperanto
forever ...
Ralf
prev parent reply other threads:[~2013-09-25 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 22:30 [PATCH] MIPS: Tell R4k SC and MC variations apart Maciej W. Rozycki
2013-09-23 11:37 ` Jonas Gorski
2013-09-23 12:35 ` [PATCH v2] " Maciej W. Rozycki
2013-09-23 12:41 ` Jonas Gorski
2013-09-23 13:01 ` [PATCH v3] " Maciej W. Rozycki
2013-09-24 9:11 ` Ralf Baechle
2013-09-24 8:48 ` [PATCH] " Ralf Baechle
2013-09-24 23:37 ` Maciej W. Rozycki
2013-09-25 11:02 ` Ralf Baechle [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=20130925110231.GM31185@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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.