Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Add .dts file for Netgear ReadyNAS 102
Date: Tue, 2 Jul 2013 15:14:07 +0200	[thread overview]
Message-ID: <20130702151407.01680d21@skate> (raw)
In-Reply-To: <20130702124639.GI19937@titan.lakedaemon.net>

Dear Jason Cooper,

On Tue, 2 Jul 2013 08:46:39 -0400, Jason Cooper wrote:

> > In the end, the main missing part is the NAND but I guess this is the
> > same for all Aramda 370/XP boards and this is not a big issue as it is
> > still possible to interact w/ it via u-boot and install a set of
> > uImage/uInitramfs that way. 
> 
> What's the big blocker for this?  Once this is done, debian should be
> able to add support for this board.  After all, upgrading the kernel and
> initrd from userspace is a desirable option.

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.

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.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-07-02 13:14 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 [this message]
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
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=20130702151407.01680d21@skate \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox