linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Steven Hein <ssh@sgi.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Configuring Freecale ucc_geth without a PHY
Date: Tue, 29 Jan 2008 11:43:10 -0600	[thread overview]
Message-ID: <20080129114310.3109caaa.kim.phillips@freescale.com> (raw)
In-Reply-To: <479F5D9B.8040403@sgi.com>

On Tue, 29 Jan 2008 11:08:43 -0600
Steven Hein <ssh@sgi.com> wrote:

> Hi all,
> 
> I have a custom board with an MPC8358 (our board is based
> off of the MPC8360E-MDS development board) that has its eth's
> directly connected (GMII) to a Broadcom network switch
> part on the same board, with no PHYs between them.
> We've have been using a 2.6.16.18 kernel (from TimeSys) up
> until now, and I hacked in some crude support for no-phy
> configs forced to 100Mbit and 1Gbit speeds.   Now I'm
> moving to 2.6.22 (with 8360 the patches from bitshrine.org),
> and I'm trying to understand how I should do this with
> device trees, the new PHY infrastructure, etc.   Has anyone
> else needed this support?   Does anyone have any suggestions
> as to how to tackle it?

check out the "fixed-link" property and associated code.  This
implementation came about after 2.6.22 though (it's commit-ish
v2.6.23-10096-ga21e282).

Kim

  reply	other threads:[~2008-01-29 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 17:08 Configuring Freecale ucc_geth without a PHY Steven Hein
2008-01-29 17:43 ` Kim Phillips [this message]
2008-01-31 13:38   ` Steven Hein
2008-01-31 16:51     ` Jon Loeliger

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=20080129114310.3109caaa.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=ssh@sgi.com \
    /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).