From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andy Fleming <afleming@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties
Date: Mon, 23 Apr 2007 23:24:04 +0200 [thread overview]
Message-ID: <e58f755b0bf5535c99dd1ef2f603d5f7@kernel.crashing.org> (raw)
In-Reply-To: <3C290CCE-1B71-448A-8454-0C08BCF93279@freescale.com>
>> On some configurations, what PHY to use is a runtime
>> decision, not a static thing. No device tree change
>> is necessary then.
>
> 1) Could you give me an example?
Some older (plugin) cards are like that. I don't have
model numbers handy, sorry.
> 2) So you'd be having Linux ignore the phandle, then?
No, Linux would find all the PHYs connected, via the
device tree, and handle them all within the driver.
Segher
next prev parent reply other threads:[~2007-04-23 21:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 6:25 [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties Kim Phillips
2007-04-13 17:00 ` Kumar Gala
2007-04-13 17:36 ` Kim Phillips
2007-04-13 17:42 ` Kumar Gala
2007-04-13 17:52 ` Kim Phillips
2007-04-13 17:59 ` Kumar Gala
2007-04-13 19:02 ` Segher Boessenkool
2007-04-16 15:25 ` Kim Phillips
2007-04-16 15:34 ` Kumar Gala
2007-04-16 15:47 ` Segher Boessenkool
2007-04-16 16:57 ` Kim Phillips
2007-04-16 23:18 ` Segher Boessenkool
2007-04-17 0:31 ` Kim Phillips
2007-04-17 10:25 ` Segher Boessenkool
2007-04-17 20:27 ` Kim Phillips
2007-04-17 23:18 ` Segher Boessenkool
2007-04-18 1:13 ` Kim Phillips
2007-04-18 10:34 ` Segher Boessenkool
2007-04-18 21:48 ` Kim Phillips
2007-04-20 8:34 ` Segher Boessenkool
2007-04-20 19:13 ` Andy Fleming
2007-04-21 17:22 ` Segher Boessenkool
2007-04-23 16:58 ` Andy Fleming
2007-04-23 21:24 ` Segher Boessenkool [this message]
2007-04-16 18:40 ` Andy Fleming
2007-04-16 23:25 ` Segher Boessenkool
2007-04-17 7:04 ` Andy Fleming
2007-04-17 10:40 ` Segher Boessenkool
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=e58f755b0bf5535c99dd1ef2f603d5f7@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
/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).