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 23:40:24 +0100	[thread overview]
Message-ID: <5f992368c65d3d53003b0e9f2955ae79@kernel.crashing.org> (raw)
In-Reply-To: <1168288352.22458.198.camel@localhost.localdomain>

>>>                        For axon, thus, we have: "emac-axon","emac4"
>>
>> "ibm,emac-axon" etc. please.
>
> Why ?

To avoid name collisions.

> In the -content- of a compatible property ?

Yes.

> haven't seen that much before.

Didn't you read the OF spec?  All examples are like that.

I know that in "real life" (and esp. in Apple OF) this
isn't often done, sure -- but is there any reason for you
*not* to do the proper thing?

>>>  - local-mac-address : 6 bytes, MAC address
>>
>> Don't forget "mac-address", if the device is opened
>> in OF; and "max-frame-size" please.
>
> Yeah well, doesn't need to specify that, it's already specified :-) I'm
> talking about what the driver wants.

Oh okay, what the driver wants.  Please don't forget that
nuance when putting this stuff into the binding doc -- it
doesn't belong there ;-)

>>>  - 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?
>
> Propose one :-) There are various bits here or there where you have to
> know which EMAC in a chip you are talking about (clock control bits,
> that sort of thing).

So this is for accessing some shared SoC registers?  The emac
node has no business with that, you should have a separate
node for that (and you probably do already, you can use the
parent bus node in most such cases).

>>>  - 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.
>
> Except that I don't want OF to set anything dynamically here. This is a
> way to prevent EMAC to do jumbo frames in fact.

MTU is dynamic, max-frame-size isn't.  max-frame-size is just
the maximum packet size you can tell the network controller to
put on the wire, not counting protocol overhead etc.


Segher

  parent reply	other threads:[~2007-01-08 22:40 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 [this message]
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=5f992368c65d3d53003b0e9f2955ae79@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).