linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@au1.ibm.com>
Cc: Christian Rund <Christian.Rund@de.ibm.com>,
	Hartmut Penner <HPENNER@de.ibm.com>,
	Murali N Iyer <mniyer@us.ibm.com>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: EMAC OF binding....
Date: Mon, 8 Jan 2007 07:38:20 +0100	[thread overview]
Message-ID: <8ee3d13b73a511a785ac4744c268943e@kernel.crashing.org> (raw)
In-Reply-To: <1168236558.22458.187.camel@localhost.localdomain>

>  - 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.

>  - local-mac-address : 6 bytes, MAC address

Don't forget "mac-address", if the device is opened
in OF; and "max-frame-size" please.

>  - cell-index        : 1 cell, hardware index of the EMAC cell on a 
> given ASIC (typically
>                        0x00000000 and 0x00000001 for EMAC-0 and EMAC-1 
> on each Axon chip)

Can you find a better name?  What is this used for, anyway?

>  - max-mtu           : 1 cell, maximum MTU supported in bytes

See "max-frame-size", MTU is on a higher level than device
level and as such shouldn't be here; the OF networking layer
can set something like this if it wants.

>  - mal-burst-size    : 1 cell, MAL burst size (used to calculate 
> thresholds)

In bytes?


Segher

  reply	other threads:[~2007-01-08  6:38 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 [this message]
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
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=8ee3d13b73a511a785ac4744c268943e@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Christian.Rund@de.ibm.com \
    --cc=HPENNER@de.ibm.com \
    --cc=benh@au1.ibm.com \
    --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 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).