linux-kernel - Re: Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 18 Jul 2013 14:18:11 +0300
From:	Roger Quadros <rogerq@...com>
To:	Arend van Spriel <arend@...adcom.com>
CC:	<tony@...mide.com>, <linux-omap@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet

Hi Arend,

On 07/18/2013 11:41 AM, Arend van Spriel wrote:
> Hi Tony,
> 
> 
> We are using the panda board (es variant) for testing our SDIO based chips. For this we have an adapter card connection to expansion connector A. As this adapter is not publicly available we had internally patched board-omap4panda.c. Also we follow the -rc releases and use TFTP to boot the kernel image which requires USB.
> 
> Moving to 3.11-rc1 I found that the mentioned board file was removed by your commit:
> 
> commit b42b918194c4791510ac049e3d507169a7de8544
> Author: Tony Lindgren <tony@...mide.com>
> Date:   Thu May 30 12:53:05 2013 -0700
> 
>     ARM: OMAP2+: Remove board-omap4panda.c
> 
> As our patches on that file are internal I do not hold it against you. This is no regression and we need to fix it.
> 
> So my first step was to follow the recipe given in that commit. Beside that I noticed a thread about USB issue on LKML so I also applied the following commit:
> 
> commit 352f573e59050c7a604c35c58b4bbfc51edebbee
> Author: Roger Quadros <rogerq@...com>
> Date:   Tue Jun 18 19:04:47 2013 +0300
> 
>     ARM: OMAP2+: Provide alias to USB PHY clock
> 
> The attached kernel log seems to suggest that the device tree is picked up by the kernel, but the USB does not seem very active. No ethernet connectivity. This does seem a regression to me. Is there some other patch that I need to get it going again?
> 

I tried with your config and 3.11-rc1 kernel with the above commit on top and ethernet seems to
work for me. My boot log is attached.

Are you sure that you are building the DTB for panda-es and the bootloader is picking up the right file and
not an outdated one?

Why is the version of SPL loader and u-boot different in your log?
You need to use the MLO file generated by the u-boot build along with the uImage.

Just to be sure we are on the same setup could you please try with latest u-boot release (2013-04). Thanks.

cheers,
-roger

View attachment "panda-es-boot.log" of type "text/x-log" (24506 bytes)