All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Christian Rund <Christian.Rund@de.ibm.com>,
	Benjamin Herrenschmidt <benh@au1.ibm.com>,
	Murali N Iyer <mniyer@us.ibm.com>,
	Hartmut Penner <HPENNER@de.ibm.com>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: EMAC OF binding....
Date: Tue, 30 Jan 2007 11:54:47 +1100	[thread overview]
Message-ID: <20070130005447.GB20332@localhost.localdomain> (raw)
In-Reply-To: <7BADAAC7-D139-4C1A-A799-93F46508880E@kernel.crashing.org>

On Mon, Jan 29, 2007 at 06:45:30PM -0600, Kumar Gala wrote:
> 
> On Jan 29, 2007, at 6:25 PM, Benjamin Herrenschmidt wrote:
> 
> > On Mon, 2007-01-08 at 07:38 +0100, Segher Boessenkool wrote:
> >>>  - compatible        : compatible list, contains 2 entries, first is
> >>> "emac-CHIP" where
> >>>                        CHIP is the host ASIC (440gx, 405gp, axon)  
> >>> and
> >>> second is either
> >>>                        "emac" or "emac4".
> >>>                        For axon, thus, we have: "emac-axon","emac4"
> >>
> >> "ibm,emac-axon" etc. please.
> >
> > What would you do for things like 440gx ? ibm,440gx or amcc,440gx ?
> 
> Does emac really vary that much between the chips its in?  I know  
> chatting with Ben that axon did some evil things, but how much  
> difference exists on 4xx implementations?

Very little, I think, but I believe the idea is to include the
detailed information, just in case in future we discover some errata
or other peculiarities in one chip's version of emac.

-- 
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-01-30  0:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF7EF2F643.75F7008B-ON8625725D.00157658-8625725D.00167CB4@au1.ibm.com>
2007-01-08  6:09 ` EMAC OF binding Benjamin Herrenschmidt
2007-01-08  6:38   ` Segher Boessenkool
2007-01-08 20:32     ` Benjamin Herrenschmidt
2007-01-08 22:12       ` David Gibson
2007-01-08 23:34         ` Segher Boessenkool
2007-01-08 22:40       ` Segher Boessenkool
2007-01-08 22:47         ` Benjamin Herrenschmidt
2007-01-08 23:27           ` Segher Boessenkool
2007-01-09  0:30             ` Benjamin Herrenschmidt
2007-01-09 16:08               ` Segher Boessenkool
2007-01-09 21:45                 ` Benjamin Herrenschmidt
2007-01-09 21:57                   ` Segher Boessenkool
2007-01-09 22:04                     ` Benjamin Herrenschmidt
2007-01-09 22:17                       ` Segher Boessenkool
2007-01-09 22:41                         ` David Gibson
2007-01-09 22:42                         ` Benjamin Herrenschmidt
2007-01-09 23:05                           ` Segher Boessenkool
2007-01-30  0:25     ` Benjamin Herrenschmidt
2007-01-30  0:45       ` Kumar Gala
2007-01-30  0:54         ` David Gibson [this message]
2007-01-30  1:50         ` Benjamin Herrenschmidt
2007-01-30  2:49           ` Benjamin Herrenschmidt

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=20070130005447.GB20332@localhost.localdomain \
    --to=dwg@au1.ibm.com \
    --cc=Christian.Rund@de.ibm.com \
    --cc=HPENNER@de.ibm.com \
    --cc=benh@au1.ibm.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mniyer@us.ibm.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.