public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1] arm: armada: Add .dts file for Netgear ReadyNAS 102
Date: Sat, 6 Jul 2013 09:38:48 -0400	[thread overview]
Message-ID: <20130706133848.GK2569@titan.lakedaemon.net> (raw)
In-Reply-To: <87a9m0dpvx.fsf@natisbad.org>

On Sat, Jul 06, 2013 at 11:00:34AM +0200, Arnaud Ebalard wrote:
> Hi,
> 
> Jason Cooper <jason@lakedaemon.net> writes:
> 
> > On Thu, Jul 04, 2013 at 11:16:46PM +0200, Arnaud Ebalard wrote:
> >> 
> >> All hardware parts of the (Armada 370 based) NETGEAR ReadyNAS 102 are
> >> supported by mainline kernel (USB 3.0 rear ports, USB 2.0 front port,
> >> Gigabit controller and PHY, serial port, leds, buttons, SATA ports,
> >> G762 fan controller) except for:
> >> 
> >>  - the Intersil ISL12057 I2C RTC Chip,
> >>  - the Armada NAND controller.
> >> 
> >> Support for both of those is currently work in progress and does not
> >> prevent boot.
> >> 
> >> Signed-off-by: Arnaud Ebalard <arno@natisbad.org>
> >> ---
> >> Hi Jason and Andrew,
> >> 
> >> As requested
> >> 
> >>  - this version is tested against current head of linus tree (+ I2C
> >>    fixes for a race condition; for details, see message #94 of
> >>    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622325).
> >>  - nand layout entry and ISL12057 entry have been removed until support
> >>    is available in mainline kernel for eahc of those
> >>  - clock, gpio led and keys have been made siblings of soc, memory and
> >>    chosen (reported by Sebastian).
> >> 
> >> Is it still acceptable for current merge window or am I too late?
> >
> > Unfortunately, it's too late for v3.11.  The arm-soc cutoff is typically
> > -rc6 or so.  Which usually means we need to see it on lakml by -rc5.
> > So, you're ahead of schedule for v3.12 :-P
> >
> > However, with any luck, maybe Ezequiel will have something ready for the
> > nand driver in time as well...
> 
> ok, no problem. That may be better in the end. And regarding the
> addition of G762 entries to ReadyNAS Duo v2 .dts file you queued a few
> days ago? I was unable to find it in one of your branches and just
> wonder where it went and hide. 

It's hiding in ~/.maildir/.TODO.linux-next/ :-)  atm, there's really
nothing stable to base a branch off of.  Once -rc1 lands, I'll create
new branches with all the stuff I have so far for v3.12.  I'll also
rebuild for-next with that same material.

hth,

Jason.

  reply	other threads:[~2013-07-06 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 21:16 [PATCHv1] arm: armada: Add .dts file for Netgear ReadyNAS 102 Arnaud Ebalard
2013-07-05 14:29 ` Jason Cooper
2013-07-06  9:00   ` Arnaud Ebalard
2013-07-06 13:38     ` Jason Cooper [this message]
2013-07-25 18:41 ` Jason Cooper
2013-08-05 13:25 ` Gregory CLEMENT
2013-08-05 13:44   ` Jason Cooper
2013-08-05 18:35     ` 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=20130706133848.GK2569@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --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