From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: linux-arm-msm@vger.kernel.org
Cc: simon.wunderlich@openmesh.com
Subject: IPQ8068 support
Date: Wed, 26 Apr 2017 10:26:59 +0200 [thread overview]
Message-ID: <2798304.oiRXTY8cqN@bentobox> (raw)
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
Hi,
(the next paragraph is just an explanation of the situation - can be skipped
to get to the actual question)
I've received a board (either called EWS370 or EWS870AP in their firmware)
which was announced as AP148 based. But the initial booting up with LEDE
wasn't working and even the serial port didn't start up. And some tests with
the standard earlycon registers for the IPQ8064 also didn't work. But then I
saw that the original firmware used some registers at 0x16640000 for ttyHSL0.
A quick test showed that this is really the correct address for the serial
console. I found in the Linux sources that apq8064 is the only one which
actually uses this register offset. Unsure whether this is actually an APQ8064,
I've removed the antennas, heatsinks and shielding to find a CPU with the name
IPQ8068 on it.
It looks like the support for this CPU was never upstreamed by QCA. A quick
search in the linux-msm tree in codeaurora also showed only uninteresting
mentions of this CPU [1]. I already know from Dakota that the upstreaming
effort from some QCA developers were suddenly stopped. Some of the Dakota
drivers were therefore waiting in some branch of some repository [2] or
hanging around in an unfinished state on some mailing list. So maybe there are
similar things somewhere for the IPQ8068. Can someone maybe point me in the
right direction?
Kind regards,
Sven
[1] https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=1fc998bf276c7407e03953d8c306cda25b29b6b5
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=5ae236e30ff401f4600125ad452e93973ddc205b
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=613c5a41ed666383c778129c7b172987aa16f31c
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=4aa6962af93bf32dd5c5e6b2313c80f4732b3286
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=8b2089087088e08f5e68b83ba04af44ecc3f9e9d
[2] https://source.codeaurora.org/quic/qsdk/mmcclint-qca/log/?h=for-next
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-04-26 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 8:26 Sven Eckelmann [this message]
2017-04-26 11:18 ` IPQ8068 support Sricharan R
2017-04-26 12:57 ` Sven Eckelmann
2017-04-27 14:26 ` Sricharan R
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=2798304.oiRXTY8cqN@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=simon.wunderlich@openmesh.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 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.