On Monday 27 June 2016 10:18:12 Matthew McClintock wrote: [..] > This is an upstream clean tree, but I did not realize the log was crashing though also that it was a back port to 3.18. I’m searching on gists for a working log here since I don’t have access to a board. Here is one that might be relevant: > > https://gist.github.com/anonymous/97d752ff8d50f45b8bbc > > > But I've tried your bootargs. These broke the earlyprintk and didn't boot with > > v4.7-rc3. So the difference here doesn't seem to be the fdt load address. > > I’m sure this command line works around the 4.6 timeframe. Ok, will test again tomorrow with an older kernel version. But it is just really odd that your arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi + qcom-ipq4019-ap.dk01.1-c1.dts was added with v4.7-rc1 and now the board should already have worked with a clean(?) Linux-4.5.0-rc4. > Are you sure you need the earlyprintk cmdline bit? At least I need it to see anything on the serial (until it starts to hang somewhere in the page code - or earlier without the reserved memory dts snipped posted in the first mail). Back to the second part of the question: Is there a roadmap for Dakota support in upstream kernel.org support? And is there a list of things which still have to be integrated in the kernel.org Linux kernel? Kind regards, Sven
Attachment:
signature.asc
Description: This is a digitally signed message part.
