From: arno@natisbad•org (Arnaud Ebalard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/4] ARM: mvebu: NETGEAR ReadyNAS 104 .dts file cleanup
Date: Mon, 25 Nov 2013 23:03:36 +0100 [thread overview]
Message-ID: <87vbzgf8av.fsf@natisbad.org> (raw)
In-Reply-To: <20131125194117.GA5413@obsidianresearch.com> (Jason Gunthorpe's message of "Mon, 25 Nov 2013 12:41:17 -0700")
Hi,
Jason Gunthorpe <jgunthorpe@obsidianresearch•com> writes:
> On Fri, Nov 22, 2013 at 11:22:33PM +0100, Arnaud Ebalard wrote:
>
>> and also the fact that *in my case* the kernel does its job
>> auto-detecting the PHY, I now also wonder how the kernel can
>> use that info and what I get by adding the compatible string.
>
> I think the main rational was to document what chip the phy is to
> people who don't have the hardware...
>
> You probably shouldn't delay your patch on this issue, document the
> phy chip model in a comment?
Will do that.
> Also, check if it is actually an S varient or not, they have the same
> phy-id.. ;)
On the chip, I have 88E1318-NNB2 (PNN1230_3JW 1209 A0P TW). I will see
if I can find more info.
Cheers,
a+
next prev parent reply other threads:[~2013-11-25 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 20:04 [PATCH 0/4] ARM: mvebu/kirkwood: NETGEAR ReadyNAS .dts files cleanup Arnaud Ebalard
2013-11-22 20:05 ` [PATCH 1/4] kirkwood: NETGEAR ReadyNAS Duo v2 .dts file cleanup Arnaud Ebalard
2013-11-22 20:06 ` [PATCH 2/4] ARM: mvebu: NETGEAR ReadyNAS 102 " Arnaud Ebalard
2013-11-22 20:07 ` [PATCH 3/4] ARM: mvebu: NETGEAR ReadyNAS 104 " Arnaud Ebalard
2013-11-22 21:36 ` Jason Gunthorpe
2013-11-22 22:22 ` Arnaud Ebalard
2013-11-25 19:41 ` Jason Gunthorpe
2013-11-25 22:03 ` Arnaud Ebalard [this message]
2013-11-25 22:08 ` Jason Gunthorpe
2013-12-04 3:31 ` Rob Herring
2013-11-22 20:07 ` [PATCH 4/4] ARM: NETGEAR ReadyNAS Duo v2 and RN102 .dts file whitespace cleanup Arnaud Ebalard
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=87vbzgf8av.fsf@natisbad.org \
--to=arno@natisbad$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.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