From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 22 Feb 2016 19:40:18 +0100 (CET) Received: from mail5.windriver.com ([192.103.53.11]:33281 "EHLO mail5.wrs.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S27011154AbcBVSkQYiZ1N (ORCPT ); Mon, 22 Feb 2016 19:40:16 +0100 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id u1MIe6TF008316 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK); Mon, 22 Feb 2016 10:40:06 -0800 Received: from [147.11.216.197] (147.11.216.197) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.248.2; Mon, 22 Feb 2016 10:40:06 -0800 Subject: Re: Does CN68XX still need DCache prefetch workaround? To: David Daney References: <56CB51CE.6070905@windriver.com> <56CB5595.1090505@gmail.com> CC: , From: Yang Shi Message-ID: <56CB5605.8070806@windriver.com> Date: Mon, 22 Feb 2016 10:40:05 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56CB5595.1090505@gmail.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 52159 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: yang.shi@windriver.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips 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 >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail5.windriver.com ([192.103.53.11]:33281 "EHLO mail5.wrs.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S27011154AbcBVSkQYiZ1N (ORCPT ); Mon, 22 Feb 2016 19:40:16 +0100 Subject: Re: Does CN68XX still need DCache prefetch workaround? References: <56CB51CE.6070905@windriver.com> <56CB5595.1090505@gmail.com> From: Yang Shi Message-ID: <56CB5605.8070806@windriver.com> Date: Mon, 22 Feb 2016 10:40:05 -0800 MIME-Version: 1.0 In-Reply-To: <56CB5595.1090505@gmail.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-Path: Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: David Daney Cc: david.daney@cavium.com, linux-mips@linux-mips.org Message-ID: <20160222184005.ABryNu8hFPGBOL-iYoi5SyIeKmNsJFIiUYmspchiWyw@z> 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 >> > >