From: Benjamin Herrenschmidt <benh@au1•ibm.com>
To: Segher Boessenkool <segher@kernel•crashing.org>
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: Tue, 09 Jan 2007 11:30:07 +1100 [thread overview]
Message-ID: <1168302607.22458.242.camel@localhost.localdomain> (raw)
In-Reply-To: <27d6554d600437ed39853784c0cf96fd@kernel.crashing.org>
> Oh you misunderstand what I mean. I'm just saying the
> registers that are shared are in some other node (having
> the same regs in two nodes can't happen).
>
> Let's hope the hardware is sane enough that you can
> describe it in a sane way.
>
> You would probably end up with properties in the SoC
> node like "emac-#0" containing the phandle of the first
> emac, or something like that -- the number of the emac
> on the SoC is not a property of the emac, but of the SoC
> itself.
>
> I don't know the exact programming interface so I'm not
> completely sure of course, but please consider.
I'm not sure I follow you... for example, I may have some clock contro
register somewhere with one bit enabling EMAC 0 clock and one bit
enabling EMAC 1 clock...
Easier to call some platform clock management giving my device-node as
an argument and have that code extract the EMAC "index" from the DT from
my node.
> >> 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.
> >
> > Ah ok.
>
> It sounds like max-frame-size is exactly what you wanted
> this new max-mtu property for, right? [Oh and btw, max-mtu
> is a really bad name -- "max-max-tu" heh].
Hehe, yes ok, I'll have a look at the spec to be sure.
Ben.
next prev parent reply other threads:[~2007-01-09 0:30 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 [this message]
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=1168302607.22458.242.camel@localhost.localdomain \
--to=benh@au1$(echo .)ibm.com \
--cc=Christian.Rund@de$(echo .)ibm.com \
--cc=HPENNER@de$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mniyer@us$(echo .)ibm.com \
--cc=segher@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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