On Thursday 24 December 2015, Guenter Roeck wrote:I managed to get versatile_defconfig to work using the available dtb files
Hi all,Just to be sure to rule out the obvious: are you using the dtb files from
various versatile and realview configurations fail to run for me with
qemu (2.5) in linux-next. Some of those are qemu configurations
I collected from various sources, so I guess I am on my own there.
However, the following standard configurations no longer work.
arm:versatileab:versatile_defconfig
arm:versatilepb:versatile_defconfig
the kernel, or do you have your own?
I can no longer get realview-eb-mpcore and realview-eb to work either,These are still based on board files, right? Do the normal defconfigs
but, again, that is with a qemu specific configuration.
work?
I think the mystery is resolved with the above results. My old configurationI tried to bisect, but there have been too many related changes in the codePlease start with the next/multiplatform branch in arm-soc, which has the
for it to succeed; some of the bisect attempts don't even compile, others fail
due to different problems. Is it known if versatile_defconfig in linux-next runs
on a real system ? If so, any idea what it might take to get it to work again
with qemu ?
conversion to devicetree. Let's first see if that works by itself. I would
hope that all commits on that branch build, but something may have gone wrong.