Kirkwood, kernel 3.2, vmalloc region overlap, not starting up

[Andrew Lunn]

> Apart from my joy - the basic reason for that change would be still
> interesting? Does this only apply to Kirwoods or my special board?

I think the conversation fizzled out without coming to a conclusion
what is wrong. Look back in the archives and see what you can find.
The problem hits kirkwood, but i don't know if it also affects other
Orion based processors. u-boot also play a role in the problem...

      Andrew