linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Roland Dreier <rdreier@cisco.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH v2 -- fixed changelog] [POWERPC] Add support for Rev. B of PowerPC 440SPe
Date: Wed, 15 Nov 2006 17:26:31 -0800	[thread overview]
Message-ID: <20061116012631.GA27724@gate.ebshome.net> (raw)
In-Reply-To: <ada3b8kuqzn.fsf@cisco.com>

On Wed, Nov 15, 2006 at 05:20:28PM -0800, Roland Dreier wrote:
>  > I think look-up tables are fine. It's not a fast path, is it?
> 
> Nope, that would be fine.  I'll definitely cut down on the code
> duplication -- I'm just not sure what will end up being cleanest.  I
> don't see that much difference between a switch and a look-up table
> for finding the base DCR index for a particular port.

OK, I was just wanted to make sure you were aware that mfdcr/mtdcr 
supported run-time specified DCR number (from that code it wasn't 
clear).

-- 
Eugene

  reply	other threads:[~2006-11-16  1:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 17:55 [PATCH] [POWERPC] Add support for Rev. B of PowerPC 440SPe Roland Dreier
2006-11-13 22:27 ` Wolfgang Denk
2006-11-13 22:29   ` jhon scoot
2006-11-13 22:31   ` Roland Dreier
2006-11-13 22:31 ` [PATCH v2 -- fixed changelog] " Roland Dreier
2006-11-14  9:01   ` Eugene Surovegin
2006-11-15 22:29     ` Roland Dreier
2006-11-16  1:14       ` Eugene Surovegin
2006-11-16  1:20         ` Roland Dreier
2006-11-16  1:26           ` Eugene Surovegin [this message]
2006-11-16  1:36             ` Roland Dreier

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=20061116012631.GA27724@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rdreier@cisco.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 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).