linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: Please pull 'for-2.6.26' branch of 4xx tree
Date: Wed, 16 Apr 2008 09:02:35 -0500	[thread overview]
Message-ID: <20080416090235.18c574f6@zod.rchland.ibm.com> (raw)
In-Reply-To: <1208354567.6958.289.camel@pasglop>

On Thu, 17 Apr 2008 00:02:47 +1000
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:

> 
> On Wed, 2008-04-16 at 08:43 -0500, Josh Boyer wrote:
> > 
> > For a final solution, we're going to have to come up with a more
> > clever
> > way of doing the clocking stuff in ibm_newemac.  The SDRs are board
> > specific and completely outside of EMAC/MAL itself.  So doing a
> > dcr_map
> 
> Not board specific... chip specific.

Yes, right.  Sorry.

> > on it becomes a bit more difficult, since there really isn't an SDR
> > node in the device tree at the moment.
> 
> That is why I tried hard to avoid the bloody workarounds...
> unfortunatly, the HW is crap enough that we have no real choice here.

Right.

josh

  reply	other threads:[~2008-04-16 14:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 15:27 Please pull 'for-2.6.26' branch of 4xx tree Josh Boyer
2008-04-16 12:27 ` Josh Boyer
2008-04-16 12:31   ` Josh Boyer
2008-04-16 12:50     ` Benjamin Herrenschmidt
2008-04-16 13:43       ` Josh Boyer
2008-04-16 14:02         ` Benjamin Herrenschmidt
2008-04-16 14:02           ` Josh Boyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-11 11:48 Josh Boyer
2008-05-19 14:48 Josh Boyer
2008-05-06 19:57 Josh Boyer
2008-04-06 12:41 Josh Boyer
2008-03-27 12:24 Josh Boyer

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=20080416090235.18c574f6@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --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).