From: "Joe Hamman" <joe.hamman@embeddedspecialties.com>
To: "'Kumar Gala'" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be configurable
Date: Tue, 14 Aug 2007 07:47:51 -0500 [thread overview]
Message-ID: <016c01c7de71$53f9d0a0$6f00a8c0@ESIDT> (raw)
In-Reply-To: <013b01c7de23$5baa7d70$6f00a8c0@ESIDT>
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-
> bounces+joe.hamman=embeddedspecialties.com@ozlabs.org [mailto:linuxppc-
> embedded-bounces+joe.hamman=embeddedspecialties.com@ozlabs.org] On Behalf
> Of Joe Hamman
> Sent: Monday, August 13, 2007 10:30 PM
> To: 'Kumar Gala'
> Cc: linuxppc-embedded@ozlabs.org
> Subject: RE: [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be
> configurable
>
>
> > -----Original Message-----
> > From: Kumar Gala [mailto:galak@kernel.crashing.org]
> > Sent: Monday, August 13, 2007 10:10 PM
> > To: joe.hamman@embeddedspecialties.com
> > Cc: linuxppc-embedded@ozlabs.org
> > 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 <joe.hamman@embeddedspecialties.com>
> > > ---
> > >
> > > 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:
>
> mdio@24520 {
> #address-cells = <1>;
> #size-cells = <0>;
> device_type = "mdio";
> compatible = "gianfar";
> reg = <24520 20>;
> phy0: ethernet-phy@0 {
> interrupt-parent = <&mpic>;
> interrupts = <a 1>;
> reg = <0>;
> device_type = "ethernet-phy";
> };
> phy1: ethernet-phy@1 {
> interrupt-parent = <&mpic>;
> interrupts = <a 1>;
> reg = <1>;
> device_type = "ethernet-phy";
> };
> phy2: ethernet-phy@2 {
> interrupt-parent = <&mpic>;
> interrupts = <a 1>;
> reg = <2>;
> device_type = "ethernet-phy";
> };
> phy3: ethernet-phy@3 {
> interrupt-parent = <&mpic>;
> interrupts = <a 1>;
> reg = <3>;
> device_type = "ethernet-phy";
> };
> tbi: ethernet-tbi@1f {
> reg = <1f>;
> device_type = "ethernet-tbi";
> };
> };
>
> Thanks,
> Joe
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2007-08-14 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 22:37 [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be configurable Joe Hamman
2007-08-14 3:09 ` Kumar Gala
2007-08-14 3:29 ` Joe Hamman
2007-08-14 12:47 ` Joe Hamman [this message]
2007-08-14 16:04 ` Andy Fleming
2007-08-14 16:16 ` Scott Wood
2007-08-14 16:50 ` Joe Hamman
2007-08-14 18:00 ` Scott Wood
2007-08-14 20:37 ` Andy Fleming
2007-08-14 21:01 ` Joe Hamman
2007-08-14 21:29 ` Andy Fleming
2007-08-14 21:41 ` Joe Hamman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='016c01c7de71$53f9d0a0$6f00a8c0@ESIDT' \
--to=joe.hamman@embeddedspecialties.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).