From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Add .dts file for Netgear ReadyNAS 102
Date: Thu, 4 Jul 2013 00:38:58 +0200 [thread overview]
Message-ID: <20130703223858.GL16785@1wt.eu> (raw)
In-Reply-To: <20130703223323.GA21722@localhost>
Hi Ezequiel,
On Wed, Jul 03, 2013 at 07:33:24PM -0300, Ezequiel Garcia wrote:
> Hi everyone,
>
> On Wed, Jul 03, 2013 at 06:33:30AM +0200, Willy Tarreau wrote:
> >
> > On Tue, Jul 02, 2013 at 08:23:12PM -0300, Ezequiel Garcia wrote:
> > > > Yes and indeed I must say that when I read the driver I found some
> > > > similarities with pxa3xx, though it was done differently. I initially
> > > > wanted to try to merge them but of course without the spec it's a huge
> > > > waste of time, especially considering that this is still in the roadmap
> > > > of the Free Electrons guys even though low priority.
> > >
> > > I wish I could say I'm going to work on this soon but, as Thomas said,
> > > we have no idea when/if NAND will be prioritized.
> > >
> > > On the other side if you look at the driver Willy just posted, merging
> > > the juicy stuff into pxa3xx-nand driver is not for the faint of heart.
> > >
> > > Without the spec, is only tougher.
> >
> > Confirmed :-)
> >
>
> Just a note on the (lack of) documentation issue.
>
> If there's a brave soul reading this and longing to tackle this,
> the pxa3xx SoC documentation *is* publicly available:
>
> http://www.marvell.com/application-processors/pxa-family/assets/PXA3xx_Developers_Manual.zip
>
> The NAND specifications can be found in the "[...] Vol. II: Memory Controller" document,
> inside the above zip file. IMHO, that's the reading entry point in order to
> understand pxa3xx-nand driver better.
Yes I have this one as well, but initially since I was not really sure
about the ressemblance of the two controllers, I did not spend too much
time on it. Now probably it can be useful, especially if we use your
existing work as a complement of information :-)
Best regards,
Willy
next prev parent reply other threads:[~2013-07-03 22:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 20:59 [RFC] Add .dts file for Netgear ReadyNAS 102 Arnaud Ebalard
2013-07-02 12:46 ` Jason Cooper
2013-07-02 13:14 ` Thomas Petazzoni
2013-07-02 13:33 ` Jason Cooper
2013-07-02 13:38 ` Thomas Petazzoni
2013-07-02 13:44 ` Jason Cooper
2013-07-02 13:49 ` Willy Tarreau
2013-07-02 14:24 ` Jason Cooper
2013-07-02 17:22 ` Arnaud Ebalard
2013-07-02 17:41 ` Jason Cooper
2013-07-02 21:48 ` Arnaud Ebalard
[not found] ` <20130702220936.GC10215@1wt.eu>
2013-07-02 23:23 ` Ezequiel Garcia
2013-07-03 4:33 ` Willy Tarreau
2013-07-03 22:33 ` Ezequiel Garcia
2013-07-03 22:38 ` Willy Tarreau [this message]
2013-07-03 7:42 ` Thomas Petazzoni
2013-07-03 13:00 ` Ezequiel Garcia
2013-07-03 19:07 ` Willy Tarreau
2013-07-03 19:10 ` Jason Cooper
2013-07-03 19:38 ` Willy Tarreau
2013-07-03 19:39 ` Jason Cooper
2013-07-04 13:59 ` Thomas Petazzoni
2013-07-04 14:01 ` Willy Tarreau
2013-07-04 17:33 ` Jason Cooper
2013-07-03 20:21 ` Jason Cooper
2013-07-03 20:35 ` Willy Tarreau
2013-07-03 20:44 ` Jason Cooper
2013-07-03 21:14 ` Willy Tarreau
2013-07-03 22:23 ` Willy Tarreau
2013-07-03 22:58 ` Arnaud Ebalard
2013-07-04 6:15 ` Willy Tarreau
2013-07-03 21:05 ` Arnaud Ebalard
2013-07-02 17:21 ` Arnaud Ebalard
2013-07-02 17:38 ` Jason Cooper
2013-07-02 13:48 ` Sebastian Hesselbarth
2013-07-02 23:27 ` 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=20130703223858.GL16785@1wt.eu \
--to=w@1wt.eu \
--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 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).