Re: Build breakage due to latest ARM fixes

From: Olof Johansson
Date: Sun Aug 04 2013 - 14:47:19 EST

On Sun, Aug 4, 2013 at 11:37 AM, Russell King - ARM Linux
<linux@xxxxxxxxxxxxxxxx> wrote:
> On Sun, Aug 04, 2013 at 11:20:21AM -0700, Olof Johansson wrote:
>> On Sun, Aug 4, 2013 at 5:53 AM, Russell King - ARM Linux
>> <linux@xxxxxxxxxxxxxxxx> wrote:
>> > On Sat, Aug 03, 2013 at 01:07:31AM +0100, Russell King - ARM Linux wrote:
>> >> I'll look into that. Obviously, I never build nommu because it isn't
>> >> part of the build system and the nommu platform I do have - OKI67001 -
>> >> doesn't have mainline kernel support. (And if it did, it would not be
>> >> DT, so I doubt it's submittable.)
>> >
>> > Okay, what I'm going to do is push the OKI67001 stuff into mainline
>> > irrespective of DT or not, so that I can then add noMMU build _and_
>> > boot tests to my build system, which should ensure that problems
>> > like that get detected before they're pushed upstream.
>> That seems like a step backwards. How have !MMU changes been handled
>> until now? Someone external has been relied on for testing?
> No, they've had no testing as far as I'm aware. noMMU never got to the
> stage when it was merged that it had any platforms before Hiyok went
> silent.
> 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?

> As for qemu, software emulations while nice and convenient don't
> accurately reflect real hardware.

Oh, agreed, it doesn't beat hardware-based testing but in the absence
of hardware it's better than nothing.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at