From: "Joe Hamman" <joe.hamman@embeddedspecialties.com>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be configurable
Date: Tue, 14 Aug 2007 16:41:23 -0500 [thread overview]
Message-ID: <020b01c7debb$dc28a3d0$6f00a8c0@ESIDT> (raw)
In-Reply-To: <C7CBB1A9-C7F0-4673-87DE-0D655B6F2EBC@freescale.com>
> -----Original Message-----
> From: Andy Fleming [mailto:afleming@freescale.com]
> Sent: Tuesday, August 14, 2007 4:30 PM
> To: joe.hamman@embeddedspecialties.com
> Cc: 'Scott Wood'; linuxppc-embedded@ozlabs.org
> Subject: Re: [PATCH] [UPDATED] tsec: Allow Ten Bit Interface to be
> configurable
>
>
> On Aug 14, 2007, at 16:01, Joe Hamman wrote:
>
> > Hi Andy,
> >>
> >> I still think it should just be a property of the ethernet node. We
> >> aren't describing the TBI, we're describing a setting for the
> >> ethernet controller's register.
> >>
> >
> > Like this? Do we need to have one for each ethernet@xxxxxx?
>
>
> Scott and I have been talking, and right now it seems like a better
> idea might be to have the TBI address get assigned dynamically, based
> on where PHYs aren't.
>
> It's non-trivial to do (though not difficult), but this way we won't
> have to regret creating a bad interface. You just need to look at
> the mdio bus, and find out which addresses responded. Then you
> create a variable in the gfar_private structure to hold what it gets
> set to, and make sure that gfar_configure_serdes uses that value
> instead of the TBIPA constant.
Sounds like a good plan. I'll try to put something together and post for
comments.
Thanks,
Joe
prev parent reply other threads:[~2007-08-14 21:41 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
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 [this message]
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='020b01c7debb$dc28a3d0$6f00a8c0@ESIDT' \
--to=joe.hamman@embeddedspecialties.com \
--cc=afleming@freescale.com \
--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).