[PATCH 1/2] ARM: bcm2835: rebuild bcm2835_defconfig

Stephen Warren swarren at wwwdotorg.org
Tue Dec 17 18:16:16 PST 2013

On 12/16/2013 07:15 AM, Martin Sperl wrote:
> Hi Stephen!
> I have tried to move to your latest patch but I have hit a problem where
> USB is no longer working (and it was working before).
> Iat first I have just pulled your changes, but USB stopped to work,
> then I have started from scratch with your default-config: still the
> same effect - no USB!
> Here the commit I have started from:
> 5cc6862678458650cef3db485a3455f3665569ac in for-next

That's bcm2835's for-next branch. It's based on v3.13-rc1.

> with this USB does not work after:
> But with: d5d9894c47e6f91004aba28251b803b18084783c everything works fine
> on the USB side - network detected and such...

That's a commit from my dev branch, which I push to github. It's based
on next-20131125, and hence pulls in all the patches destined for 3.14
from (almost) all subsystems.

In particular, I made a change to the DWC2 USB driver that allows it to
be instantiated from device tree. That patch is in linux-next, but not
bcm2835's for-next branch, so that explains what you're seing.

More information about the linux-rpi-kernel mailing list