* fixed phy -- how do we decide to use this code?
@ 2009-04-15 15:54 Kumar Gala
2009-04-15 16:17 ` Anton Vorontsov
0 siblings, 1 reply; 4+ messages in thread
From: Kumar Gala @ 2009-04-15 15:54 UTC (permalink / raw)
To: Vitaly Bordug, Anton Vorontsov; +Cc: Linuxppc-dev Development, netdev
Vitaly, Anton
You guys have used this code.. I was wondering how we decide to used
the fixed phy vs another phy. Is this a runtime decision based on
something in the device tree or purely at compile time?
- k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fixed phy -- how do we decide to use this code?
2009-04-15 15:54 fixed phy -- how do we decide to use this code? Kumar Gala
@ 2009-04-15 16:17 ` Anton Vorontsov
2009-04-15 17:20 ` Kumar Gala
0 siblings, 1 reply; 4+ messages in thread
From: Anton Vorontsov @ 2009-04-15 16:17 UTC (permalink / raw)
To: Kumar Gala; +Cc: netdev, Linuxppc-dev Development
On Wed, Apr 15, 2009 at 10:54:40AM -0500, Kumar Gala wrote:
> Vitaly, Anton
>
> You guys have used this code.. I was wondering how we decide to used the
> fixed phy vs another phy. Is this a runtime decision based on something
> in the device tree or purely at compile time?
It's specified via fixed-link property in the device tree.
The bindings described in Documentation/powerpc/dts-bindings/fsl/tsec.txt.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fixed phy -- how do we decide to use this code?
2009-04-15 16:17 ` Anton Vorontsov
@ 2009-04-15 17:20 ` Kumar Gala
2009-04-15 17:25 ` Anton Vorontsov
0 siblings, 1 reply; 4+ messages in thread
From: Kumar Gala @ 2009-04-15 17:20 UTC (permalink / raw)
To: avorontsov; +Cc: netdev, Linuxppc-dev Development
On Apr 15, 2009, at 11:17 AM, Anton Vorontsov wrote:
> On Wed, Apr 15, 2009 at 10:54:40AM -0500, Kumar Gala wrote:
>> Vitaly, Anton
>>
>> You guys have used this code.. I was wondering how we decide to
>> used the
>> fixed phy vs another phy. Is this a runtime decision based on
>> something
>> in the device tree or purely at compile time?
>
> It's specified via fixed-link property in the device tree.
> The bindings described in Documentation/powerpc/dts-bindings/fsl/
> tsec.txt.
Ok, I want to make sure I can build a platform that uses a normal PHY
that is detected (like a marvell PHY) and and have another platform
that is fixed-link in the same kernel image. Sounds like we'll be ok.
- k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: fixed phy -- how do we decide to use this code?
2009-04-15 17:20 ` Kumar Gala
@ 2009-04-15 17:25 ` Anton Vorontsov
0 siblings, 0 replies; 4+ messages in thread
From: Anton Vorontsov @ 2009-04-15 17:25 UTC (permalink / raw)
To: Kumar Gala; +Cc: netdev, Linuxppc-dev Development
On Wed, Apr 15, 2009 at 12:20:14PM -0500, Kumar Gala wrote:
>
> On Apr 15, 2009, at 11:17 AM, Anton Vorontsov wrote:
>
>> On Wed, Apr 15, 2009 at 10:54:40AM -0500, Kumar Gala wrote:
>>> Vitaly, Anton
>>>
>>> You guys have used this code.. I was wondering how we decide to used
>>> the
>>> fixed phy vs another phy. Is this a runtime decision based on
>>> something
>>> in the device tree or purely at compile time?
>>
>> It's specified via fixed-link property in the device tree.
>> The bindings described in Documentation/powerpc/dts-bindings/fsl/
>> tsec.txt.
>
> Ok, I want to make sure I can build a platform that uses a normal PHY
> that is detected (like a marvell PHY) and and have another platform that
> is fixed-link in the same kernel image. Sounds like we'll be ok.
Yep, that will work.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-04-15 17:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-15 15:54 fixed phy -- how do we decide to use this code? Kumar Gala
2009-04-15 16:17 ` Anton Vorontsov
2009-04-15 17:20 ` Kumar Gala
2009-04-15 17:25 ` Anton Vorontsov
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).