From: Nigel Stephens <nigel@mips.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
yshi <yang.shi@windriver.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] malta4kec hang in calibrate_delay fix
Date: Tue, 04 Sep 2007 13:04:09 +0100 [thread overview]
Message-ID: <46DD49B9.2090306@mips.com> (raw)
In-Reply-To: <20070904115527.GA848@networkno.de>
Thiemo Seufer wrote:
> Kevin D. Kissell wrote:
>
>>> ??? 2007-09-04?????? 12:03 +0200???Kevin D. Kissell?????????
>>>
>>>> The 4KEc is a MIPS32 Release 2 processor, for which the implementation
>>>> of the Cause.TI bit (bit 30) is required. You may have a defective board
>>>> or a bad FPGA bitfile. Please work with your support contacts at MIPS
>>>> to verify that this is not the case. It may also be that there's something more
>>>> subtle going on in the interrupt processing, such that the Cause.TI bit is being
>>>> cleared before it can be sampled by the code you've changed. But while the
>>>> patch below presumably solves the symptoms of your problem, I really
>>>> don't think that a kernel hack based on detecting CoreFPA3 is an appropriate
>>>> solution. I work every day with Malta/CoreFPGA3 bitfiles and have not
>>>> seen Cause.TI fail to function in any of the Release 2 core bitfiles I've used.
>>>>
>>> My board's core is Release 1 core. So Cause.TI bit always is zero. Maybe
>>> I need update this patch to reflect this, i.e add #ifdef to distinguish
>>> Release 1 and Release 2. Thanks.
>>>
>> In that case, your core is a 4Kc and not a 4KEc.
>>
>
> Not quite true, early revisions of the 4KEc were only release 1. This
> seems to be a bug in arch/mips/cpu-probe.c:
>
> static inline void cpu_probe_mips(struct cpuinfo_mips *c)
> {
> decode_configs(c);
> switch (c->processor_id & 0xff00) {
> case PRID_IMP_4KC:
> c->cputype = CPU_4KC;
> break;
> case PRID_IMP_4KEC:
> c->cputype = CPU_4KEC;
> break;
> case PRID_IMP_4KECR2:
> c->cputype = CPU_4KEC;
> break;
> ...
>
> The type for PRID_IMP_4KEC should be CPU_4KC.
>
>
Maybe the probing code should read the ISA revision level from the AR
bits (12:10) of the Config0 register to figure out which revision of the
ISA is implemented.
Nigel
next prev parent reply other threads:[~2007-09-04 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 8:52 [PATCH] malta4kec hang in calibrate_delay fix yshi
2007-09-04 10:03 ` Kevin D. Kissell
2007-09-04 10:03 ` Kevin D. Kissell
2007-09-04 10:32 ` yshi
2007-09-04 11:21 ` Kevin D. Kissell
2007-09-04 11:21 ` Kevin D. Kissell
2007-09-04 11:33 ` Thomas Bogendoerfer
2007-09-04 11:47 ` Kevin D. Kissell
2007-09-04 11:47 ` Kevin D. Kissell
2007-09-04 11:55 ` Thiemo Seufer
2007-09-04 12:04 ` Nigel Stephens [this message]
2007-09-04 12:19 ` Kevin D. Kissell
2007-09-04 12:19 ` Kevin D. Kissell
2007-09-04 12:42 ` Thiemo Seufer
2007-09-04 12:44 ` Ralf Baechle
2007-09-05 5:51 ` yshi
2007-09-05 10:49 ` Chris Dearman
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=46DD49B9.2090306@mips.com \
--to=nigel@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
--cc=yang.shi@windriver.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