public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mikpe@it.uu.se (Mikael Pettersson)
To: linux-arm-kernel@lists.infradead.org
Subject: Inte IOP Xscale updates
Date: Sat, 7 Sep 2013 12:45:12 +0200	[thread overview]
Message-ID: <21035.952.938696.169280@pilspetsen.it.uu.se> (raw)
In-Reply-To: <20130903134516.GH6617@n2100.arm.linux.org.uk>

Russell King - ARM Linux writes:
 > On Tue, Sep 03, 2013 at 02:01:45PM +0200, Linus Walleij wrote:
 > > Hi XScale folks,
 > > 
 > > I haven't really seen any functional patches or confirmation that the
 > > XScale machines in arch/arm/iop* are even booting since 2010 or
 > > so.
 > > 
 > > Can you confirm that you boot-test these machines regularly?
 > > 
 > > I am worried that we maintain code that is not used or even working
 > > see.
 > > 
 > > What are your thought about multiplatform and device tree? I am
 > > pretty certain that if the iop machines were converted to device tree
 > > we could collapse these machines into one directory with few files,
 > > but I may be wrong.
 > 
 > Just because code doesn't get touched doesn't mean it doesn't work.  In
 > some cases, that means that the code has reached stability.
 > 
 > The IOP platforms are in regular use.  IOP platforms include such
 > things as TheCUS machines such as the N2100 and others.  The two N2100s
 > I have here run 3.1.8 and 3.9.5.

I just booted 3.9, 3.10, and 3.11 on my N2100, without problems.

Compared to the Kirkwood Qnaps the N2100 is quite slow and noisy,
so I haven't actually used mine in years.

As long as they doesn't cause any maintenance problems I think we
should just leave the IOP platforms as-is.

  reply	other threads:[~2013-09-07 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 12:01 Inte IOP Xscale updates Linus Walleij
2013-09-03 13:45 ` Russell King - ARM Linux
2013-09-07 10:45   ` Mikael Pettersson [this message]
2013-09-07 11:14     ` Russell King - ARM Linux
2013-09-07 13:19       ` Mikael Pettersson
2013-09-09  6:37     ` Linus Walleij
2013-09-09 22:10 ` Dan Williams
2013-09-10  8:14   ` Linus Walleij
2013-09-10 12:58 ` Aaro Koskinen
2013-09-13  7:30   ` Linus Walleij

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=21035.952.938696.169280@pilspetsen.it.uu.se \
    --to=mikpe@it.uu.se \
    --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