From: Aaron Pace <kodiakuppercut@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: DTS format for direct SGMII TSEC link?
Date: Mon, 2 Mar 2009 15:09:33 -0700 [thread overview]
Message-ID: <bc81dc640903021409s49032382t6700cbfb416922e3@mail.gmail.com> (raw)
Hello,
I am working with a Freescale 8572 board which uses direct SGMII
connections (no real PHY) for three of the four TSECs. I have been
trying to figure out the appropriate DTS elements to set this up, but
haven't yet managed to figure it out. Everything works great in
u-boot, so I know that the connections & hardware are functional.
I've tried setting up dummy physical phys, using only the tbi-phy, and
using the 'fixed-link' property, none of which have achieved the
desired result.
I realize I'm taking the lazy way out by not digging into the gianfar
code, but I was hoping that this problem had already been seen and
addressed and could be handled with the right text in the DTS file.
Thanks,
Aaron Pace
reply other threads:[~2009-03-02 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bc81dc640903021409s49032382t6700cbfb416922e3@mail.gmail.com \
--to=kodiakuppercut@gmail.com \
--cc=linuxppc-dev@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).