From: Sven Eckelmann <sven.eckelmann@open-mesh.com>
To: Matthew McClintock <mmcclint@codeaurora.org>
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 17:02:37 +0200 [thread overview]
Message-ID: <1477021.doPKiVyCTg@bentobox> (raw)
In-Reply-To: <FF6B3887-109A-4DC2-A57C-BDAE0AE8113A@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
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?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-28 15:02 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 [this message]
2016-06-28 15:57 ` Matthew McClintock
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=1477021.doPKiVyCTg@bentobox \
--to=sven.eckelmann@open-mesh.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marek.lindner@open-mesh.com \
--cc=mathieu@codeaurora.org \
--cc=mmcclint@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.