From: Matthew McClintock <mmcclint@codeaurora.org>
To: Sven Eckelmann <sven.eckelmann@open-mesh.com>
Cc: linux-arm-msm@vger.kernel.org,
Mathieu Olivari <mathieu@codeaurora.org>,
Marek Lindner <marek.lindner@open-mesh.com>
Subject: Re: QCA IPQ4019 support in mainline linux
Date: Tue, 28 Jun 2016 10:57:00 -0500 [thread overview]
Message-ID: <DD3C1E05-38EF-495A-B210-A413EED2942E@codeaurora.org> (raw)
In-Reply-To: <1477021.doPKiVyCTg@bentobox>
> On Jun 28, 2016, at 10:02 AM, Sven Eckelmann <sven.eckelmann@open-mesh.com> wrote:
>
> On Monday 27 June 2016 11:08:04 Matthew McClintock wrote:
>>
>>> On Jun 27, 2016, at 10:44 AM, Sven Eckelmann <sven.eckelmann@open-mesh.com> wrote:
>>>
>>>> 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.
>>
>> Fair enough, checkout this tree as well: https://source.codeaurora.org/quic/qsdk/mmcclint-qca/log/?h=for-next
>
> Just tried the branch you gave me. But it has the two exact same problems.
>
> Do you have by any chance the .config which you've used to build the
> working kernel?
I don’t anymore, can you share yours and I can look over it?
-M
prev parent reply other threads:[~2016-06-28 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 16:20 QCA IPQ4019 support in mainline linux Sven Eckelmann
2016-06-23 16:55 ` Matthew McClintock
2016-06-24 7:24 ` Sven Eckelmann
2016-06-24 16:37 ` Matthew McClintock
2016-06-27 7:59 ` Sven Eckelmann
2016-06-27 15:18 ` Matthew McClintock
2016-06-27 15:44 ` Sven Eckelmann
2016-06-27 16:08 ` Matthew McClintock
2016-06-28 15:02 ` Sven Eckelmann
2016-06-28 15:57 ` Matthew McClintock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DD3C1E05-38EF-495A-B210-A413EED2942E@codeaurora.org \
--to=mmcclint@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marek.lindner@open-mesh.com \
--cc=mathieu@codeaurora.org \
--cc=sven.eckelmann@open-mesh.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox