From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jason Cooper <jason@lakedaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
linux-leds@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 00/13] Remove mach-kirkwood and mach-dove
Date: Sun, 29 Jun 2014 22:35:11 +0100 [thread overview]
Message-ID: <20140629213510.GR32514@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1404075603-31838-1-git-send-email-andrew@lunn.ch>
On Sun, Jun 29, 2014 at 10:59:47PM +0200, Andrew Lunn wrote:
> This patchset removes arch/arm/mach-kirkwood and arch/arm/mach-dove.
> These SoCs are now supported in arch/arm/mach-mvebu using device tree.
>
> Change the dependencies for a number of drivers, either to use
> ARCH_MVEBU where the drivers are generic, or MACH_KIRKWOOD and
> MACH_DOVE where the drivers are specific to a SoC.
>
>
> Andrew Lunn (13):
> ARM: Kirkwood: Remove mach-kirkwood
> ARM: Dove: Remove mach-dove
There is actually a cubox regression which has yet to be tracked down.
Running with my kernel (which is not-DT based) runs perfectly. With
DT, HDMI output can be unstable.
One of the problems is that it's /very/ difficult to reproduce, but it
is reproducable. I've seen it on two days over many reboots, and I've
proved it by switching back and forth. DT sometimes suffers from the
problem, whereas non-DT /never/ does.
Sebastian is aware of this, and as yet we haven't found a solution,
nor have we found a way to reliably reproduce it.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-29 21:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 20:59 [PATCH 00/13] Remove mach-kirkwood and mach-dove Andrew Lunn
2014-06-29 20:59 ` [PATCH 09/13] PCI: Remove ARCH_KIRKWOOD and ARCH_DOVE dependency Andrew Lunn
2014-07-05 17:54 ` Bjorn Helgaas
2014-07-05 17:52 ` Andrew Lunn
2014-06-29 21:35 ` Russell King - ARM Linux [this message]
2014-06-30 7:16 ` [alsa-devel] [PATCH 00/13] Remove mach-kirkwood and mach-dove Jean-Francois Moine
2014-06-30 8:49 ` Russell King - ARM Linux
2014-06-30 9:47 ` Jean-Francois Moine
2014-06-30 10:00 ` Russell King - ARM Linux
2014-06-30 12:15 ` Sebastian Hesselbarth
2014-06-30 12:43 ` Russell King - ARM Linux
2014-06-30 13:22 ` Sebastian Hesselbarth
2014-06-30 14:25 ` Russell King - ARM Linux
2014-06-30 15:35 ` Sebastian Hesselbarth
2014-06-30 16:56 ` Russell King - ARM Linux
2014-06-30 17:31 ` Sebastian Hesselbarth
2014-06-30 19:35 ` Russell King - ARM Linux
2014-06-30 17:43 ` Andrew Lunn
2014-06-30 18:08 ` Russell King - ARM Linux
2014-06-30 18:16 ` Andrew Lunn
2014-07-06 9:49 ` [rtc-linux] " Alexander Holler
2014-06-30 22:21 ` Ezequiel Garcia
2014-07-08 12:13 ` Jason Cooper
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=20140629213510.GR32514@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=a.zummo@towertech.it \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=cooloney@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rpurdie@rpsys.net \
--cc=rtc-linux@googlegroups.com \
--cc=rui.zhang@intel.com \
--cc=sebastian.hesselbarth@googlemail.com \
--cc=tj@kernel.org \
--cc=wim@iguana.be \
/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;
as well as URLs for NNTP newsgroup(s).