lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 3 Feb 2016 12:13:48 -0800 From: santosh shilimkar <santosh.shilimkar@...cle.com> To: Murali Karicheri <m-karicheri2@...com>, Arnd Bergmann <arnd@...db.de>, "Franklin S Cooper Jr." <fcooper@...com> Cc: netdev@...r.kernel.org, w-kwok2@...com, davem@...emloft.net Subject: Re: Keystone 2 boards boot failure 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
Powered by blists - more mailing lists