From: w@1wt•eu (Willy Tarreau)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC] Add .dts file for Netgear ReadyNAS 102
Date: Wed, 3 Jul 2013 06:33:30 +0200 [thread overview]
Message-ID: <20130703043330.GF10215@1wt.eu> (raw)
In-Reply-To: <20130702232311.GA3949@localhost>
Hi Ezequiel,
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 quick hint. As far as I can recall, one of the first items in a
> TODO list should be:
>
> * adding bigger page support to pxa3xx (4 KiB, 8 KiB).
> Willy's posted driver might be helpful to accomplish this;
> provided your eyes don't melt when you look at it :-)
>
> * once the above is done, bad block management can/should be added.
>
> With these two we're almost there for R/W support.
Since the driver I posted is poorly commented, I'm not even sure it
will be easy to spot the relevant parts in it.
> > Since I'm now flashing a rootfs from within u-boot, support for the
> > NAND is of less importance to me than what it used to, but I have no
> > problem with helping with my very limited time. I have 3 machines
> > with this controller (mirabox, openblocks AX3, and an XP-GP, though
>
> With my latest patches pxa3xx-nand should at least *detect* the NAND
> device in XP-GP. Doesn't work for Mirabox, though.
OK good to know!
> > the AX3 only has NOR IIRC). I can do some tests if you manage to get
> > the driver to work again.
> >
> > Be very careful when playing with this, the driver expects the partition
> > table to be passed from u-boot as "armada_nand", and if it uses the wrong
> > partition layout, you can be certain that ubifs will destroy them at the
> > first mount attempt. That's how I initially bricked my mirabox and did so
> > repeatedly. Better keep a copy before booting the patched kernel!
> >
> > Another point, I had to add a new entry for the Micro 8Gb flash of the
> > mirabox, maybe you won't need it or maybe you'll need a different one.
>
> Just a note about this. You need that entry because your driver doesn't
> support ONFI-detected flash devices. You could workaround that, by
> adding support simple command. I did it for pxa3xx-nand recently:
>
> "mtd: nand: pxa3xx: Add address support for READID command"
> http://permalink.gmane.org/gmane.linux.drivers.mtd/46606
I remember having seen your patches, I didn't know that it allowed
to use such flashes and now it makes sense because I was surprized
about having to add entries for all possible devices while we're
not even certain that two consecutive versions of a board will use
the same brand of NAND devices.
Thanks for sharing these information, Ezequiel!
Willy
next prev parent reply other threads:[~2013-07-03 4:33 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 [this message]
2013-07-03 22:33 ` Ezequiel Garcia
2013-07-03 22:38 ` Willy Tarreau
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=20130703043330.GF10215@1wt.eu \
--to=w@1wt$(echo .)eu \
--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