From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh shilimkar Subject: Re: Keystone 2 boards boot failure Date: Wed, 3 Feb 2016 12:13:48 -0800 Message-ID: <56B25F7C.4060507@oracle.com> References: <56B0DE61.2000704@ti.com> <10700980.gTvMTB9pzv@wuerfel> <56B15591.7080409@ti.com> <1682165.IJ7dHXqc6L@wuerfel> <56B233F3.40000@oracle.com> <56B24B3F.2070906@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, w-kwok2@ti.com, davem@davemloft.net To: Murali Karicheri , Arnd Bergmann , "Franklin S Cooper Jr." Return-path: Received: from aserp1040.oracle.com ([141.146.126.69]:19417 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753915AbcBCUN6 (ORCPT ); Wed, 3 Feb 2016 15:13:58 -0500 In-Reply-To: <56B24B3F.2070906@ti.com> Sender: netdev-owner@vger.kernel.org List-ID: On 2/3/2016 10:47 AM, Murali Karicheri wrote: > On 02/03/2016 12:08 PM, santosh shilimkar wrote: >> On 2/3/2016 8:35 AM, Arnd Bergmann wrote: [..] >>> It would be nice to give this a go once the network driver problem >>> is solved. >>> >> Big endian kernel has worked on Keystone in past. > > Yes, this was on a v3.10.x baseline, not in the upstream. > Thats what I mean in past. That time upstream didn't have ARM BE patches o.w there was no other depedency. >> Yes, above secondary hook needs to be modified along with >> drivers endian macro conversion was what was needed IIRC. >> > > To support BE, it may be more than Netcp driver. Do you recall, what > changes you did to get BE working on Keystone? Is it just NetCP driver? > IIRC it was Navigator (QMSS, DMA), NETCP, SPI and couple of of more drivers. Driver update was a massive patch done by Prabhu. Regards, Santosh