From: sunder ramani <sunder.svit@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org,
devicetree-discuss list <devicetree-discuss@ozlabs.org>,
afleming@freescale.com
Subject: Re: [PATCH 1/9] of: add of_parse_phandle() helper for parsing
Date: Thu, 19 Mar 2009 11:35:02 +0530 [thread overview]
Message-ID: <d90126080903182305n5fcd69b5o4014ea7d6d1fb731@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40903182301l63d9319r40a9e8e20f89af5a@mail.gmail.com>
Hi Grant,
Thanx a lot for the comments. I will start activities to bind the phy
type to the phy layer and post someting useful. But, to be honest,
please correct me on spot wherever i go wrong. I am new the open
source and this is very exciting!
thanx!
Sundar
On Thu, Mar 19, 2009 at 11:31 AM, Grant Likely
<grant.likely@secretlab.ca> wrote:
> On Wed, Mar 18, 2009 at 11:37 PM, sunder ramani <sunder.svit@gmail.com> wrote:
>> To Summarize, should not we have a phy_type flag in the OF tree which
>> will let the PHY layer do the various PHY tasks based on if it is a
>> copper/fiber interface. I really dont like my fix in my kernel and am
>> new to open source. Do you think it is a valid argument? If it so, I
>> would like to plan to introduce those changes and post to the
>> community.
>
> Yes, we probably do need some form of flag here for describing the PHY
> interface. Feel free to post a suggested binding for this.
>
> g.
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
>
prev parent reply other threads:[~2009-03-19 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d90126080903182237i6057e9afi9051723685bcb2d2@mail.gmail.com>
[not found] ` <d90126080903182237i6057e9afi9051723685bcb2d2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-19 6:01 ` [PATCH 1/9] of: add of_parse_phandle() helper for parsing Grant Likely
2009-03-19 6:05 ` sunder ramani [this message]
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=d90126080903182305n5fcd69b5o4014ea7d6d1fb731@mail.gmail.com \
--to=sunder.svit@gmail.com \
--cc=afleming@freescale.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--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