Hi Olivier,
On Fri, 2016-02-05 at 15:25 +0100, Olivier Blin wrote:
> Lubomir Rintel <lkundrak@xxxxx> writes:
>
> > diff --git a/arch/arm/boot/dts/bcm2836-rpi-2-b.dts
> > b/arch/arm/boot/dts/bcm2836-rpi-2-b.dts
> [...]
> > @@ -33,3 +37,17 @@
> > brcm,function = <BCM2835_FSEL_ALT0>;
> > };
> > };
> > +
> > +&usb {
> > + usb1@1 {
> > + compatible = "usb0424,9514";
> > + reg = <01>;
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + ethernet: usbether@1 {
> > + compatible = "usb0424,ec00";
> > + reg = <01>;
> > + };
> > + };
> > +};
>
> Hi,
>
> This works for me, after making sure that your u-boot patch gets a
> chance to be run (unset usbethaddr from u-boot).
Thanks for that.
> Though, I am not really DT-literate, but shouldn't the ethernet block
> use the PID from the ethernet device?
> The usbether device is 9514 on RPi2, while ec00 is the hub.
Are you sure? I didn't check on RPi2, but I check the Models B and B+
and the ethernet device was 0xec00 on both. The driver attaches to that
product ID:
[lkundrak@odvarok linux]$ modinfo smsc95xx |grep EC
alias: usb:v0424pEC00d*dc*dsc*dp*ic*isc*ip*in*
[lkundrak@odvarok linux]$ modinfo smsc95xx |grep 9514
[lkundrak@odvarok linux]$
> Your patch works, but this works as well after swapping the PIDs.
>
> Thanks
Take care
Lubo
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
