From: Dave Taht <dave@taht.net>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] pixel 3 wifi chip stuff
Date: Sun, 25 Nov 2018 14:54:31 -0800 [thread overview]
Message-ID: <871s784vko.fsf_-_@taht.net> (raw)
In-Reply-To: <kdrag0n/proton_bluecross/issues/1/441409964@github.com> (Khronodragon's message of "Sat, 24 Nov 2018 18:15:09 -0800")
Khronodragon <notifications@github.com> writes:
>
> Cool! If you're looking to implement this for qcacld-3.0, I'd
> recommend you to base it off the original from Qualcomm on CodeAurora
> instead of Google's downstream version. The tag that correlates to the
> chipset used in this kernel and Google's would be
> LA.UM.7.3.r1-06300-sdm845.0.
https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
parent reply other threads:[~2018-11-25 22:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <kdrag0n/proton_bluecross/issues/1/441409964@github.com>]
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s784vko.fsf_-_@taht.net \
--to=dave@taht.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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