From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sven Eckelmann Subject: Re: QCA IPQ4019 support in mainline linux Date: Mon, 27 Jun 2016 17:44:15 +0200 Message-ID: <4381868.vZcqYCaM2U@bentobox> References: <3882585.su10hvamp7@bentobox> <1753251.H5jI7Pa1kM@bentobox> <66493E0B-CA70-4B63-B95C-7CA3D2DF2B04@codeaurora.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1898041.rFXc1eEKyu"; micalg="pgp-sha512"; protocol="application/pgp-signature" Return-path: Received: from mail-wm0-f42.google.com ([74.125.82.42]:38096 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751385AbcF0PoT (ORCPT ); Mon, 27 Jun 2016 11:44:19 -0400 Received: by mail-wm0-f42.google.com with SMTP id r201so121238237wme.1 for ; Mon, 27 Jun 2016 08:44:18 -0700 (PDT) In-Reply-To: <66493E0B-CA70-4B63-B95C-7CA3D2DF2B04@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Matthew McClintock Cc: linux-arm-msm@vger.kernel.org, Mathieu Olivari , Marek Lindner --nextPart1898041.rFXc1eEKyu Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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 cra= shing though also that it was a back port to 3.18. I=E2=80=99m searchin= g on gists for a working log here since I don=E2=80=99t have access to = a board. Here is one that might be relevant: >=20 > https://gist.github.com/anonymous/97d752ff8d50f45b8bbc >=20 > > But I've tried your bootargs. These broke the earlyprintk and didn'= t boot with=20 > > v4.7-rc3. So the difference here doesn't seem to be the fdt load ad= dress. >=20 > I=E2=80=99m 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, =09Sven --nextPart1898041.rFXc1eEKyu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCgAGBQJXcUnPAAoJEF2HCgfBJntGS3QP/0cEuGUCgW/4jttOwm4KTVj+ A/EbcMVgrn17qCGq2EYQUDLnNuLBeBekZCsNhX1Gz+KEqPsfaRcvQAkx0Bjs+QKT htNfpU3doNlgbgW6Gj4uJJEPMMii+pD7SbEep05CmF+/QY7m8InP5ju6li1PLeqx eZq7jbKsHUUb5uqqFJhwlCEPAwvMpGwiCxBiY8192gc6iXYTJymaqt1j68uSt+7g s98QOVyE3FYYEvOc6wA+XuZ584JG4W8HeF4FZ6giCaUkrwBzLoaDXPr2rurm5Wry Kwgd/X7MCUsVLSrReVcfCDgmuoGGhTdbAYy5jYLJTkbymxsFJVIjAEILCmF0N+x/ G4Rt/EJDPHtE46dT+oOJx9CFMpM6ZJi0l1yyM9LSpNKlCFkt9sskdPOQOmSLjVhY 8juuY56czyEh6blxc7GoPbxhHT2yCqTthFk/iCQc+pomzOfVQysws2himsvWzUBM baiM1WshItlJJF75qfXjD5jvqoG9wWR4lYJTYJhfpgtumyrBduigaHrsaF94cEPn sAh1AULJWNIjTtMGCiCl59yBUqTSnbPgH+kCr2PJQ9BsvWdLZqEPbu83LRNQhA+S iV8EbJyDfQfxVFhyPrSNhjoZ6jUPoxfWx15BuJznV7eau3FneSlIrocxBan1sSSa up3lTPuG1VoNMyJmv1Be =LRa7 -----END PGP SIGNATURE----- --nextPart1898041.rFXc1eEKyu--