linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Device tree aware EMAC driver
Date: Wed, 8 Aug 2007 11:18:23 +1000	[thread overview]
Message-ID: <20070808011823.GA20565@localhost.localdomain> (raw)
In-Reply-To: <20070807071539.6dbb49a5@weaponx.rchland.ibm.com>

On Tue, Aug 07, 2007 at 07:15:39AM -0500, Josh Boyer wrote:
> On Tue, 7 Aug 2007 16:22:31 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > Based on BenH's earlier work, this is a new version of the EMAC driver
> > for the built-in ethernet found on PowerPC 4xx embedded CPUs.  The
> > same ASIC is also found in the Axon bridge chip.  This new version is
> > designed to work in the arch/powerpc tree, using the device tree to
> > probe the device, rather than the old and ugly arch/ppc OCP layer.
> > 
> > This driver is designed to sit alongside the old driver (it lies in
> > drivers/net/ibm_emac and this one in drivers/net/ibm_newemac).  The
> > old driver is left in place to support arch/ppc until arch/ppc itself
> > reaches its final demise (not too long now, with luck).
> > 
> > This driver still has a number of things that could do with cleaning
> > up, but I think they can be fixed up after merging.  Specifically:
> > 	- Should be adjusted to properly use the dma mapping API.
> > Axon needs this.
> > 	- Probe logic needs reworking, in conjuction with the general
> > probing code for of_platform devices.  The dependencies here between
> > EMAC, MAL, ZMII etc. make this complicated.  At present, it usually
> > works, because we initialize and register the sub-drivers before the
> > EMAC driver itself, and (being in driver code) runs after the devices
> > themselves have been instantiated from the device tree.
> > 
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> 
> Hm.  Should this go through Jeff Garzik or Paul?  If it's the latter,
> I'll pull this into my git tree soon.

Through Jeff Garzik, I think.  I was planning to send it to him today
or tomorrow if there are no screams from the linuxppc-dev list.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-08-08  2:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07  6:22 Device tree aware EMAC driver David Gibson
2007-08-07 12:15 ` Josh Boyer
2007-08-08  1:18   ` David Gibson [this message]
2007-08-08  3:16 ` Tony Breeds
2007-08-08  5:09   ` David Gibson
2007-08-08  7:34     ` Benjamin Herrenschmidt
2007-08-08  7:33   ` Benjamin Herrenschmidt
2007-08-10 20:39   ` Segher Boessenkool
2007-08-13  1:05     ` David Gibson
2007-08-11  3:51 ` Olof Johansson
     [not found] <20070823035601.GL7042@localhost.localdomain>
2007-08-23  7:30 ` Benjamin Herrenschmidt
2007-09-14 22:37   ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2007-05-30  6:17 David Gibson

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=20070808011823.GA20565@localhost.localdomain \
    --to=dwg@au1.ibm.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).