From: Vitaly Bordug <vbordug@ru•mvista.com>
To: Ben Warren <bwarren@qstreams•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Using fixed_phy with gianfar
Date: Wed, 10 Jan 2007 19:04:41 +0300 [thread overview]
Message-ID: <20070110190441.0f47a5ab@localhost.localdomain> (raw)
In-Reply-To: <880857.53326.qm@web308.biz.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Wed, 10 Jan 2007 06:22:40 -0800 (PST)
Ben Warren wrote:
> Thanks Vitaly!
>
> --- Vitaly Bordug <vbordug@ru•mvista.com> wrote:
>
> > No, you do not miss - this is an issue. In fact MDIO
> > bus was changed for numeric for gianfar-stuff, and
> > has been remaining string for fs_enet. I think it
> > makes sense to average this up, and will try to do
> > that once will get 8349-mitx which is gianfar+ fixed
> > user.
> >
> > The point is that fixed should be updated to numeric
> > MDIO address encoding. This has to come through
> > netdev, so I'll try to get it fixed by the next
> > merge window.
> >
> > --
> > Sincerely, Vitaly
> >
>
> Ideally (for me anyway), we'd be able to pass some
> fixed phy information via the device tree, for example
> speed and duplexity. This way a board could, for
> example, connect to one switch via RvMII @100FD and
> another via GMII @1000FD. Having parameters as
> numeric limits this capability, but presumably a
> simple encoding scheme could be make it work.
>
> I'm sure you've already thought of this, though...
Yes, I was thinking about something like 0:1001 or 0:101 where 1 at the end respects duplexity.
Putting it into devtree is good but we'll need to unify the interface first.
--
Sincerely, Vitaly
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-10 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 23:23 Using fixed_phy with gianfar Ben Warren
2007-01-10 13:11 ` Vitaly Bordug
2007-01-10 14:22 ` Ben Warren
2007-01-10 16:04 ` Vitaly Bordug [this message]
2007-01-10 17:01 ` Ben Warren
2007-01-10 22:41 ` Andy Fleming
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=20070110190441.0f47a5ab@localhost.localdomain \
--to=vbordug@ru$(echo .)mvista.com \
--cc=bwarren@qstreams$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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