[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1454570293.25750.23.camel@v3.sk>
Date: Thu, 04 Feb 2016 08:18:13 +0100
From: Lubomir Rintel <lkundrak@...sk>
To: Peter Chen <peter.chen@....com>, Olivier Blin <dev@...no.org>
Cc: "linux-rpi-kernel@...ts.infradead.org"
<linux-rpi-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Peter Chen <peter.chen@...escale.com>
Subject: Re: [PATCH 2/2] ARM: bcm2835: dt: Add the ethernet to the device
tree
On Thu, 2016-02-04 at 06:28 +0000, Peter Chen wrote:
>
> > Lubomir Rintel <lkundrak@...sk> writes:
> >
> > > diff --git a/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> > > b/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> > > index ef54050..32bbd2a 100644
> > > --- a/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> > > +++ b/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> >
> > Hi,
> >
> > Shouldn't this be common to all RPi1 B and RPi2 models, instead of
> > being
> > specific to just RPi B+?
> >
> > > +&usb {
> > > + usb1@01 {
> > > + compatible = "usb1d6b,0002";
> > > + reg = <01>;
> > > + #address-cells = <1>;
> > > + #size-cells = <0>;
> > > +
> > > + ethernet: usbether@01 {
> > > + compatible = "usb0424,9514";
> > > + reg = <01>;
> > > + };
> > > + };
> > > +};
> >
> > For reference, on RPi2:
>
> Using "lsusb -t" you may get bus topology.
>
> > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
> > SMSC9512/9514 Fast Ethernet Adapter
>
> It is the ethernet device, you may need to change vid/pid in dts.
>
> > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
> > SMC9514 Hub
>
> It is the hub device, you may need to change vid/pid in dts.
>
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >
>
> It is root hub, it doesn't need to be described at dts.
Thank you; neither of the vid/pid pairs in the original submission is
okay. I'll follow up with an updated version.
I've also checked this on RPi B rev2; and I'll be including that one,
and the RPI2 too.
I can't find my rev1 RPi B; but maybe I can just do the same for the
same board. It would likely work, but I may get the vid/pid wrong if
it's different from rev2.
> Best regards,
> Peter
Thanks
Lubo
Powered by blists - more mailing lists