Hi Kumar, Or do you think it should be added to gianfar_mdio_data? Easier, but does it belong there?
Thanks, Joe > -----Original Message----- > From: linuxppc-embedded- > [EMAIL PROTECTED] [mailto:linuxppc- > [EMAIL PROTECTED] On Behalf > Of Joe Hamman > Sent: Monday, August 13, 2007 10:30 PM > To: 'Kumar Gala' > Cc: [email protected] > Subject: RE: [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be > configurable > > > > -----Original Message----- > > From: Kumar Gala [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 13, 2007 10:10 PM > > To: [EMAIL PROTECTED] > > Cc: [email protected] > > Subject: Re: [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be > > configurable > > > > > > On Aug 13, 2007, at 5:37 PM, Joe Hamman wrote: > > > > > Allow the address of the Ten Bit Interface (TBI) to be changed in the > > > event of a conflict with another device. > > > > > > Signed-off by: Joe Hamman <[EMAIL PROTECTED]> > > > --- > > > > > > Please ignore the last patch - I missed a cut & paste error on the > > > range > > > that my testing didn't catch. > > > > I think we'd rather this came from the device tree. > > > Duh, that makes sense ;-) > > Has there been any discussion yet? Maybe something like this: > > [EMAIL PROTECTED] { > #address-cells = <1>; > #size-cells = <0>; > device_type = "mdio"; > compatible = "gianfar"; > reg = <24520 20>; > phy0: [EMAIL PROTECTED] { > interrupt-parent = <&mpic>; > interrupts = <a 1>; > reg = <0>; > device_type = "ethernet-phy"; > }; > phy1: [EMAIL PROTECTED] { > interrupt-parent = <&mpic>; > interrupts = <a 1>; > reg = <1>; > device_type = "ethernet-phy"; > }; > phy2: [EMAIL PROTECTED] { > interrupt-parent = <&mpic>; > interrupts = <a 1>; > reg = <2>; > device_type = "ethernet-phy"; > }; > phy3: [EMAIL PROTECTED] { > interrupt-parent = <&mpic>; > interrupts = <a 1>; > reg = <3>; > device_type = "ethernet-phy"; > }; > tbi: [EMAIL PROTECTED] { > reg = <1f>; > device_type = "ethernet-tbi"; > }; > }; > > Thanks, > Joe > > > _______________________________________________ > Linuxppc-embedded mailing list > [email protected] > https://ozlabs.org/mailman/listinfo/linuxppc-embedded _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
