From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: mvebu: NETGEAR ReadyNAS 104 .dts file cleanup
Date: Mon, 25 Nov 2013 15:08:04 -0700 [thread overview]
Message-ID: <20131125220804.GA11260@obsidianresearch.com> (raw)
In-Reply-To: <87vbzgf8av.fsf@natisbad.org>
On Mon, Nov 25, 2013 at 11:03:36PM +0100, Arnaud Ebalard wrote:
> > 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.
That is the standard varient - I expect the S version is rare. NNB2
indicates the package option. The rest is the lot code.
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Arnaud Ebalard <arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Grant Likely
<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 3/4] ARM: mvebu: NETGEAR ReadyNAS 104 .dts file cleanup
Date: Mon, 25 Nov 2013 15:08:04 -0700 [thread overview]
Message-ID: <20131125220804.GA11260@obsidianresearch.com> (raw)
In-Reply-To: <87vbzgf8av.fsf-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org>
On Mon, Nov 25, 2013 at 11:03:36PM +0100, Arnaud Ebalard wrote:
> > 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.
That is the standard varient - I expect the S version is rare. NNB2
indicates the package option. The rest is the lot code.
Jason
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-25 22:08 UTC|newest]
Thread overview: 22+ 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:04 ` Arnaud Ebalard
2013-11-22 20:05 ` [PATCH 1/4] kirkwood: NETGEAR ReadyNAS Duo v2 .dts file cleanup Arnaud Ebalard
2013-11-22 20:05 ` Arnaud Ebalard
2013-11-22 20:06 ` [PATCH 2/4] ARM: mvebu: NETGEAR ReadyNAS 102 " Arnaud Ebalard
2013-11-22 20:06 ` Arnaud Ebalard
2013-11-22 20:07 ` [PATCH 3/4] ARM: mvebu: NETGEAR ReadyNAS 104 " Arnaud Ebalard
2013-11-22 20:07 ` Arnaud Ebalard
2013-11-22 21:36 ` Jason Gunthorpe
2013-11-22 21:36 ` Jason Gunthorpe
2013-11-22 22:22 ` Arnaud Ebalard
2013-11-22 22:22 ` Arnaud Ebalard
2013-11-25 19:41 ` Jason Gunthorpe
2013-11-25 19:41 ` Jason Gunthorpe
2013-11-25 22:03 ` Arnaud Ebalard
2013-11-25 22:03 ` Arnaud Ebalard
2013-11-25 22:08 ` Jason Gunthorpe [this message]
2013-11-25 22:08 ` Jason Gunthorpe
2013-12-04 3:31 ` Rob Herring
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
2013-11-22 20:07 ` 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=20131125220804.GA11260@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.