From: Jason Cooper <jason@lakedaemon.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Rob Herring <robh@kernel.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Fri, 16 May 2014 14:42:05 -0400 [thread overview]
Message-ID: <20140516184205.GL27822@titan.lakedaemon.net> (raw)
In-Reply-To: <1400265111.2647.54.camel@deadeye.wl.decadent.org.uk>
On Fri, May 16, 2014 at 07:31:51PM +0100, Ben Hutchings wrote:
> On Fri, 2014-05-16 at 00:10 -0400, Jason Cooper wrote:
> > Joking aside, I concede your point. It looks like the last two mvebu
> > legacy platforms (dove, mv78xx0) might get merged into mach-mvebu during
> > the next cycle. After that, we can reach out to the Debian and OpenWRT
> > guys and see what legacy platforms are in use or rotting. We can go
> > from there.
>
> I just removed ixp4xx from Debian as the kernel image wouldn't fit in
> the NSLU2's kernel partition any more (even after disabling quite a few
> features that are enabled in most other configurations). iop32x was
> removed for the same reason, a while ago.
Hmmm, I have two NSLU2's, they might make a good platform for the
tinification/IoT work. Small flash, small RAM, slow.
> Our 'legacy' (which I take to mean pre-v7) configurations are now
> kirkwood, mv78xx0, orion5x (all about to converge to mvebu) and
> versatile.
I'm not familiar with versatile, the others I've seen a few times. ;-)
Does Debian see any user activity with mv78xx0? I know your build
system used to have boards with that SoC family, but are there any other
users?
thx,
Jason.
next prev parent reply other threads:[~2014-05-16 18:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 3:00 Jason Cooper
2014-05-11 12:37 ` Jonathan Corbet
2014-05-11 13:59 ` Alexandre Belloni
2014-05-11 14:22 ` Olof Johansson
2014-05-15 12:15 ` Grant Likely
2014-05-15 13:38 ` Jason Cooper
2014-05-15 18:50 ` Rob Herring
2014-05-15 19:42 ` Jason Cooper
2014-05-16 3:30 ` Olof Johansson
2014-05-16 4:10 ` Jason Cooper
2014-05-16 18:31 ` Ben Hutchings
2014-05-16 18:42 ` Jason Cooper [this message]
2014-05-16 22:20 ` Ben Hutchings
2014-05-19 12:20 ` Arnd Bergmann
2014-05-19 22:41 ` Peter Maydell
2014-05-19 23:06 ` Rob Herring
2014-05-20 8:08 ` Arnd Bergmann
2014-05-22 14:44 ` Rob Herring
2014-05-23 13:48 ` Linus Walleij
2014-05-23 14:42 ` Arnd Bergmann
2014-05-23 13:46 ` Linus Walleij
2014-05-23 13:40 ` Linus Walleij
2014-05-23 13:57 ` Arnd Bergmann
2014-05-16 3:39 ` Olof Johansson
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=20140516184205.GL27822@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=ben@decadent.org.uk \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.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