linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Configuring Freecale ucc_geth without a PHY
@ 2008-01-29 17:08 Steven Hein
  2008-01-29 17:43 ` Kim Phillips
  0 siblings, 1 reply; 4+ messages in thread
From: Steven Hein @ 2008-01-29 17:08 UTC (permalink / raw)
  To: linuxppc-embedded

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?

Thanks,
Steve

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com)              Engineering Diagnostics/Software
Silicon Graphics, Inc.                          
1168 Industrial Blvd.                 Phone: (715) 726-8410
Chippewa Falls, WI 54729              Fax:   (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Configuring Freecale ucc_geth without a PHY
  2008-01-29 17:08 Configuring Freecale ucc_geth without a PHY Steven Hein
@ 2008-01-29 17:43 ` Kim Phillips
  2008-01-31 13:38   ` Steven Hein
  0 siblings, 1 reply; 4+ messages in thread
From: Kim Phillips @ 2008-01-29 17:43 UTC (permalink / raw)
  To: Steven Hein; +Cc: linuxppc-embedded

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Configuring Freecale ucc_geth without a PHY
  2008-01-29 17:43 ` Kim Phillips
@ 2008-01-31 13:38   ` Steven Hein
  2008-01-31 16:51     ` Jon Loeliger
  0 siblings, 1 reply; 4+ messages in thread
From: Steven Hein @ 2008-01-31 13:38 UTC (permalink / raw)
  To: Kim Phillips; +Cc: linuxppc-embedded

Kim Phillips wrote:
> 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
>   
Thanks for the pointer Kim!     Using the "fixed-link" property
code already in the tree, and adding the glue in ucc_geth.c to
use it (modeled after the code in gianfar fix-link support
in fsl_soc.c), I was able to get this working with me 8360 board.

Is there a document anywhere that describes how to submit
patches for the powerpc kernel?    Or do I just create the patch
(I'm learning about git right now...) again the paulus/powerpc.git
tree, and send it to this list?

Thanks,
Steve

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com)              Engineering Diagnostics/Software
Silicon Graphics, Inc.                          
1168 Industrial Blvd.                 Phone: (715) 726-8410
Chippewa Falls, WI 54729              Fax:   (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Configuring Freecale ucc_geth without a PHY
  2008-01-31 13:38   ` Steven Hein
@ 2008-01-31 16:51     ` Jon Loeliger
  0 siblings, 0 replies; 4+ messages in thread
From: Jon Loeliger @ 2008-01-31 16:51 UTC (permalink / raw)
  To: Steven Hein; +Cc: linuxppc-embedded

Steven Hein wrote:


> Is there a document anywhere that describes how to submit
> patches for the powerpc kernel?    Or do I just create the patch
> (I'm learning about git right now...) again the paulus/powerpc.git
> tree, and send it to this list?
> 

Correct.  Don't just lean toward git, actually use it.
And paulus/powerpc.git is the right basis.

Send it to the linuxppc-dev@ozlabs.org list, not here.

jdl

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-01-31 16:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-29 17:08 Configuring Freecale ucc_geth without a PHY Steven Hein
2008-01-29 17:43 ` Kim Phillips
2008-01-31 13:38   ` Steven Hein
2008-01-31 16:51     ` Jon Loeliger

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).