From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Add .dts file for Netgear ReadyNAS 102
Date: Tue, 2 Jul 2013 15:49:47 +0200 [thread overview]
Message-ID: <20130702134947.GC6740@1wt.eu> (raw)
In-Reply-To: <20130702134421.GC17110@titan.lakedaemon.net>
On Tue, Jul 02, 2013 at 09:44:21AM -0400, Jason Cooper wrote:
> On Tue, Jul 02, 2013 at 03:38:25PM +0200, Thomas Petazzoni wrote:
> > Dear Jason Cooper,
> >
> > On Tue, 2 Jul 2013 09:33:37 -0400, Jason Cooper wrote:
> >
> > > > The big blocker is that no-one has written the driver for it. It is
> > > > still on our (Free Electrons) TODO-list, but not as a top-priority item
> > > > for the moment.
> > >
> > > Ok.
> > >
> > > > Ezequiel had started to do some preliminary cleanup work on the
> > > > pxa3xx-nand driver, with the ultimate goal of making it support Armada
> > > > 370/XP (because the IP in the Armada 370/XP is apparently an evolution
> > > > of the PXA3xx NAND controller), but our priorities shifted to those
> > > > other topics. We will back on it some day, but I can't say when at the
> > > > moment.
> > >
> > > Is this under contract? If so, I don't want to take it from you. If it
> > > isn't, perhaps Ezequiel and Arnaud could mind-meld?
> >
> > The big problem is that the Armada 370 and Armada XP datasheets are
> > still only available under NDA, so it's quite hard for someone to step
> > up and do this, without access to those datasheets.
>
> bummer.
>
> > It used to be on our TODO-list, but isn't any longer, and I have no
> > informations about when it will re-appear on our TODO-list at this
> > point.
>
> So, Arnaud, how do you feel about tackling the nand driver based on the
> sources you have and the pointers above?
BTW if that can help, I already have a working port of the driver that is
present in Marvell's kernel. The port is absolutely ugly, it's plain copy
paste of the HAL parts that I needed until it built and booted. It worked
on my mirabox with 3.8. I know it doesn't work since recently (I believe
since introduction of the mbus driver) though I haven't had time to check
why yet. The advantage of such an ugly work is that I'm sure that it will
never be merged into mainline :-)
Regards,
Willy
next prev parent reply other threads:[~2013-07-02 13:49 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 [this message]
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
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=20130702134947.GC6740@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 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.