From: Jonathan Austin <jonathan.austin@arm.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Olof Johansson <olof@lixom.net>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Build breakage due to latest ARM fixes
Date: Mon, 05 Aug 2013 10:45:41 +0100 [thread overview]
Message-ID: <51FF7445.9080602@arm.com> (raw)
In-Reply-To: <20130804193647.GD6104@pengutronix.de>
On 04/08/13 20:36, Uwe Kleine-König wrote:
> Hello,
>
> On Sun, Aug 04, 2013 at 11:47:04AM -0700, Olof Johansson wrote:
>> On Sun, Aug 4, 2013 at 11:37 AM, Russell King - ARM Linux
>>> The only real testing I'm aware of is when I recreated the OKI67001
>>> support a while back and got my board to boot.
>>
>> Uwe has been busy pushing various patches for M3/M4 support, I don't
>> know how far it is from having some real hardware usable though. Uwe?
> On my efm32 devboard I have 3.11-rc running. The missing bits are
> available in my efm32 branch at
>
> git://git.pengutronix.de/git/ukl/linux.git efm32
> http://git.pengutronix.de/?p=ukl/linux.git;a=shortlog;h=refs/heads/efm32
>
> . It's not yet in a form ready for mainline but there isn't much
> missing. There is one problem I didn't debug yet (/proc/devicetree
> doesn't appear although I have the respective Kconfig symbol on); other
> than that I didn't notice any no-mmu problems. Also Jonathan Austin does
> some no-MMU work.
>
We use !MMU internally here for R-class stuff (see the recently added
Cortex-R7 support).
Our CONFIG_MMU=n testing all happens on Versatile Express, and it should
even be possible to run !MMU on TC2 (IE with an A-class processor).
Perhaps if we feel that it isn't easy enough for people to test these
configurations I can submit a vexpress_nommu defconfig or similar? It
might need some additional patches to complete the story, but if it
makes it easier to catch these breakages early then maybe it is worth it?
Jonny
prev parent reply other threads:[~2013-08-05 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 23:41 Build breakage due to latest ARM fixes Olof Johansson
2013-08-03 0:07 ` Russell King - ARM Linux
2013-08-03 0:24 ` Olof Johansson
2013-08-03 0:41 ` Russell King - ARM Linux
2013-08-03 0:48 ` Russell King - ARM Linux
2013-08-03 2:14 ` Olof Johansson
2013-08-03 0:57 ` Russell King - ARM Linux
2013-08-04 12:53 ` Russell King - ARM Linux
2013-08-04 18:20 ` Olof Johansson
2013-08-04 18:37 ` Russell King - ARM Linux
2013-08-04 18:47 ` Olof Johansson
2013-08-04 19:01 ` Russell King - ARM Linux
2013-08-04 19:19 ` Olof Johansson
2013-08-04 19:36 ` Uwe Kleine-König
2013-08-05 9:45 ` Jonathan Austin [this message]
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=51FF7445.9080602@arm.com \
--to=jonathan.austin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=u.kleine-koenig@pengutronix.de \
/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