From: Yang Shi <yang.shi@windriver.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: <david.daney@cavium.com>, <linux-mips@linux-mips.org>
Subject: Re: Does CN68XX still need DCache prefetch workaround?
Date: Mon, 22 Feb 2016 10:40:05 -0800 [thread overview]
Message-ID: <56CB5605.8070806@windriver.com> (raw)
In-Reply-To: <56CB5595.1090505@gmail.com>
On 2/22/2016 10:38 AM, David Daney wrote:
> On 02/22/2016 10:22 AM, Yang Shi wrote:
>> I David,
>>
>> When I booted up 4.5-rc4 kernel on CN68xx board, both pass 1.1 and pass
>> 2.2 reports:
>>
>> Kernel panic - not syncing: OCTEON II DCache prefetch workaround not in
>> place (cfa00000).
>> Please build kernel with proper options (CONFIG_CAVIUM_CN63XXP1).
>>
>> According to the description of he option, it should just have impact on
>> 63xx pass 1.x. It looks confusing.
>>
>
> The name of the Kconfig variable is CAVIUM_CN63XXP1. It turns out
> that it is also needed for somethings that are not cn63xxP1. It is a
> bit confusing, but as of now we decided not to rename the Kconfig
> variable.
OK, however, it would sound better to add more comments or notes about
this in Kconfig help text?
>
>> Any hint is appreciated?
>
> Enable it and see what happens.
Once I enable it could bootup without problem.
Thanks,
Yang
>
>>
>> Thanks,
>> Yang
>>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Yang Shi <yang.shi@windriver.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: david.daney@cavium.com, linux-mips@linux-mips.org
Subject: Re: Does CN68XX still need DCache prefetch workaround?
Date: Mon, 22 Feb 2016 10:40:05 -0800 [thread overview]
Message-ID: <56CB5605.8070806@windriver.com> (raw)
Message-ID: <20160222184005.ABryNu8hFPGBOL-iYoi5SyIeKmNsJFIiUYmspchiWyw@z> (raw)
In-Reply-To: <56CB5595.1090505@gmail.com>
On 2/22/2016 10:38 AM, David Daney wrote:
> On 02/22/2016 10:22 AM, Yang Shi wrote:
>> I David,
>>
>> When I booted up 4.5-rc4 kernel on CN68xx board, both pass 1.1 and pass
>> 2.2 reports:
>>
>> Kernel panic - not syncing: OCTEON II DCache prefetch workaround not in
>> place (cfa00000).
>> Please build kernel with proper options (CONFIG_CAVIUM_CN63XXP1).
>>
>> According to the description of he option, it should just have impact on
>> 63xx pass 1.x. It looks confusing.
>>
>
> The name of the Kconfig variable is CAVIUM_CN63XXP1. It turns out
> that it is also needed for somethings that are not cn63xxP1. It is a
> bit confusing, but as of now we decided not to rename the Kconfig
> variable.
OK, however, it would sound better to add more comments or notes about
this in Kconfig help text?
>
>> Any hint is appreciated?
>
> Enable it and see what happens.
Once I enable it could bootup without problem.
Thanks,
Yang
>
>>
>> Thanks,
>> Yang
>>
>
>
next prev parent reply other threads:[~2016-02-22 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 18:22 Does CN68XX still need DCache prefetch workaround? Yang Shi
2016-02-22 18:22 ` Yang Shi
2016-02-22 18:38 ` David Daney
2016-02-22 18:40 ` Yang Shi [this message]
2016-02-22 18:40 ` Yang Shi
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=56CB5605.8070806@windriver.com \
--to=yang.shi@windriver.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox