public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	linux-kernel@vger.kernel.org,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform
Date: Wed, 25 Nov 2015 21:05:02 +0100	[thread overview]
Message-ID: <2762753.604XuTRa75@wuerfel> (raw)
In-Reply-To: <20151125183728.GO8644@n2100.arm.linux.org.uk>

On Wednesday 25 November 2015 18:37:28 Russell King - ARM Linux wrote:
> On Wed, Nov 25, 2015 at 05:09:37PM +0100, Andrew Lunn wrote:
> > Russell, you are the last known user of mach-dove. What are your
> > plans? You keep saying you have given up trying to mainline your Cubox
> > patches. Have you really given up? Can we remove mach-dove?
> 
> Right now, I'm developing etnaviv in spare time on the Cubox[*], which
> is still primarily running a non-DT kernel.
> 
> It's actually a kernel that I've hacked which is capable of booting
> both DT and non-DT, but even when booted in DT mode, I still require
> much of the arch/arm/mach-dove infrastructure to get things like
> armada-drm, etnaviv and other drivers running.  Especially because
> we're missing things like the high-speed clocks (the stuff above the
> tclk domain.)  I've not even started to work out how to get that
> into mainline, or how to integrate that with CCF.  Quite what can be
> done with the audio patches, I've no idea, that remains a bone of
> contention and stalemate, and currently isn't DT-able.  See the list
> of patches at the end of this message...

I think it's ok to keep mach-dove around for a longer time to keep the
board file, I'm way more interested in completing the multiplatform
work at last.

If I understand you right, being able to build mach-dove and mach-mvebu
together will actually help you remove one or more of your patches,
but of course will require a small bit of rebasing.

	Arnd

  parent reply	other threads:[~2015-11-25 20:05 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 15:49 [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform Arnd Bergmann
2015-11-25 15:49 ` [PATCH 1/5] ARM: orion: move watchdog setup to mach-orion5x Arnd Bergmann
2015-11-25 15:49 ` [PATCH 2/5] ARM: orion: always use MULTI_IRQ_HANDLER Arnd Bergmann
2015-11-25 15:49 ` [PATCH 3/5] ARM: orion: use SPARSE_IRQ everywhere Arnd Bergmann
2015-11-25 15:49 ` [PATCH 4/5] ARM: orion: clean up mach/*.h headers Arnd Bergmann
2015-11-25 15:49 ` [PATCH 5/5] ARM: orion: multiplatform support Arnd Bergmann
2015-11-25 16:09 ` [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform Andrew Lunn
2015-11-25 17:34   ` Gregory CLEMENT
2015-11-25 17:44     ` Andrew Lunn
2015-11-25 19:58       ` Arnd Bergmann
2015-11-26 14:50         ` Jason Cooper
2015-11-25 18:37   ` Russell King - ARM Linux
2015-11-25 19:16     ` Andrew Lunn
2015-11-25 19:29       ` Russell King - ARM Linux
2015-11-25 23:19       ` Russell King - ARM Linux
2015-11-25 20:05     ` Arnd Bergmann [this message]
2015-11-25 22:47       ` Russell King - ARM Linux
2015-11-25 20:14 ` Andrew Lunn
2015-11-30 13:37 ` Gregory CLEMENT
2015-12-01 22:51   ` Andrew Lunn
2015-12-01 22:55     ` Arnd Bergmann
2015-12-02 11:03     ` Gregory CLEMENT
2015-12-02 12:33   ` Russell King - ARM Linux
2015-12-02 15:49     ` Arnd Bergmann
2015-12-02 19:28       ` Russell King - ARM Linux
2015-12-02 19:37         ` Russell King - ARM Linux
2015-12-02 19:54           ` Arnd Bergmann
2015-12-02 19:51         ` Arnd Bergmann
2015-12-02 20:22           ` Russell King - ARM Linux
2015-12-02 20:38             ` Andrew Lunn
2015-12-02 21:03               ` Russell King - ARM Linux
2015-12-02 21:15               ` Arnd Bergmann
2015-12-02 23:59                 ` Andrew Lunn
     [not found]   ` <87wpsz61r7.fsf@free-electrons.com>
     [not found]     ` <20151201182226.ea7d860eb3a35086981cd18f@vollmann.ch>
     [not found]       ` <87fuzl2jm5.fsf@free-electrons.com>
2015-12-02 14:55         ` Andrew Lunn
     [not found]     ` <56697665.1070609@vollmann.ch>
2015-12-10 13:18       ` Arnd Bergmann
2015-12-10 13:43         ` Arnd Bergmann
     [not found]           ` <5669CC76.4030606@vollmann.ch>
2015-12-10 20:59             ` Arnd Bergmann
     [not found]               ` <5669EB31.4050700@vollmann.ch>
2015-12-10 21:29                 ` Arnd Bergmann
     [not found]                   ` <5669F5F8.5010005@vollmann.ch>
2015-12-10 23:10                     ` Arnd Bergmann
2015-12-11 13:36                       ` Jason Cooper
2015-12-11 14:46                         ` Arnd Bergmann
2015-12-11 14:55                           ` Jason Cooper
2015-12-11 18:27                         ` Josh Triplett
2015-12-11 18:46                           ` Jason Cooper
2015-12-11 19:08                             ` Josh Triplett
2015-12-11 19:14                               ` Jason Cooper
     [not found]         ` <5669808F.2050909@vollmann.ch>
2015-12-11 21:33           ` 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=2762753.604XuTRa75@wuerfel \
    --to=arnd@arndb.de \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=sebastian.hesselbarth@gmail.com \
    /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