From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] maintainership update for the Marvell Orion family of SOCs
Date: Mon, 30 Apr 2012 23:53:12 +0200 [thread overview]
Message-ID: <87mx5sanuf.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <201204302124.28892.arnd@arndb.de> (Arnd Bergmann's message of "Mon, 30 Apr 2012 21:24:28 +0000")
Arnd Bergmann <arnd@arndb.de> writes:
> On Monday 30 April 2012, Arnaud Patard wrote:
>> Sorry to hijack a little bit this thread, but I got a few days ago a
>> 88ap510/dove device so I was wondering if the work currently done on
>> kirkwood would allow us the same kernel binary at least on dove and
>> kirkwood ? [1] If so, when it'll be possible, will it be considered to
>> move the corresponding board setup from
>> arch/arm/mach-{dove,kirkwood,...} into a new directory, like what was
>> done on recently on imx ?
>>
>> [1] I'm only talking of kirkwood and dove because it's only what I can
>> test. Of course, if it can be a single kernel binary for
>> dove/kirkwood/mv78xx0/orion5x, it'll be even better.
>
> While I don't know of anyone working on this currently, I've also thought
> about it being doable, but I would defer it until we can probe all
> the devices using the device tree, because at that point it will get
> much simpler. We might just move all the DT based board support into
ok.
> the plat-orion directory and leave the other directories for the classic
> probing, eventually to be removed when the new stuff can handle all the
> machines that someone cares about.
I'm not sure we'll be able to remove any machine without being sure it's
working and it can take quite some time. orion/kirkwood/... are used on
NAS boxes so I guess people are not necessary updating their kernel on a
regular basis.
>
> Note that dove is fundamentally incompatible with the others at runtime,
> being ARMv7 based instead of ARMv5, but it could still live in the same
> directory, like we do for other platforms.
oh, right. I guess I need some sleep.
Arnaud
next prev parent reply other threads:[~2012-04-30 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:44 [PATCH] maintainership update for the Marvell Orion family of SOCs Nicolas Pitre
2012-04-30 17:48 ` Jason Cooper
2012-04-30 18:33 ` Arnd Bergmann
2012-04-30 18:38 ` Andrew Lunn
2012-04-30 20:48 ` Arnaud Patard (Rtp)
2012-04-30 21:24 ` Arnd Bergmann
2012-04-30 21:53 ` Arnaud Patard (Rtp) [this message]
2012-04-30 22:17 ` Arnd Bergmann
2012-05-01 8:48 ` Andrew Lunn
2012-05-02 13:05 ` Arnd Bergmann
2012-05-02 13:05 ` Arnd Bergmann
2012-04-30 21:25 ` Arnd Bergmann
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=87mx5sanuf.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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.