All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Scott Wood'" <scottwood@freescale.com>,
	"'Rune Torgersen'" <runet@innovsys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Porting to /arch/powerpc
Date: Fri, 26 Oct 2007 00:26:17 +0200	[thread overview]
Message-ID: <020001c81756$0fc78760$5267a8c0@Jocke> (raw)
In-Reply-To: <472113CC.5020409@freescale.com>

> -----Original Message-----
> From: 
> linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se@ozlabs.
> org 
> [mailto:linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se
> @ozlabs.org] On Behalf Of Scott Wood
> Sent: den 26 oktober 2007 00:08
> To: Rune Torgersen
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: Porting to /arch/powerpc
> 
> Rune Torgersen wrote:
> > Is there a good platform/documents to look at for doing a board port
> > from arch/ppc to arch/powerpc?
> > I'm porting a 8266/8280 based board with PCI and 2 FCC ethernets
> > connected phy-less to a switch.
> 
> Look at head-of-tree for 82xx stuff (lots of changes since 2.6.23)... 
> any of the 82xx boards in arch/powerpc should be good to look at.
> 
> The fs_enet driver doesn't currently support phy-less 
> directly, but you 
> may be able to do something with the fixed phy driver.

How is PHY less support supposed to be impl.? I would like
to do the same for ucc_geth. I once sent a patch that made
the PHY optional, but it never made into the driver.

   Jocke

> 
> -Scott

  reply	other threads:[~2007-10-25 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 21:59 Porting to /arch/powerpc Rune Torgersen
2007-10-25 22:08 ` Scott Wood
2007-10-25 22:26   ` Joakim Tjernlund [this message]
2007-10-26 18:10     ` Scott Wood
2007-10-26 19:03       ` Joakim Tjernlund

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='020001c81756$0fc78760$5267a8c0@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=runet@innovsys.com \
    --cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.