linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: netdev@oss.sgi.com, Jeff Garzik <jgarzik@pobox.com>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: Device tree aware EMAC driver
Date: Thu, 23 Aug 2007 09:30:36 +0200	[thread overview]
Message-ID: <1187854236.5972.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20070823035601.GL7042@localhost.localdomain>

On Thu, 2007-08-23 at 13:56 +1000, David Gibson wrote:
> 
> 
> Jeff, I've discussed this with BenH, and although there are some
> problems with the driver still, we think it's good enough to merge in
> 2.6.24, the warts can be fixed up later.  Please apply...

Or to be more precise:

This driver will work well for 4xx platforms and will allow us to move a
big step toward getting rid of arch/ppc. The issues with DMA mapping
really only concern the case where this is used within the cell "Axon"
southbridge, which doesn't happen on any released product at this stage.

Ben.

       reply	other threads:[~2007-08-23  7:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070823035601.GL7042@localhost.localdomain>
2007-08-23  7:30 ` Benjamin Herrenschmidt [this message]
2007-09-14 22:37   ` Device tree aware EMAC driver Josh Boyer
2007-08-07  6:22 David Gibson
2007-08-07 12:15 ` Josh Boyer
2007-08-08  1:18   ` David Gibson
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
  -- 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=1187854236.5972.6.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=jgarzik@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@oss.sgi.com \
    --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).