From: Kalle Valo <kvalo@codeaurora.org>
To: Devin Bayer <dev@doubly.so>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: ath11k with QCA6391
Date: Tue, 03 Nov 2020 15:56:58 +0200 [thread overview]
Message-ID: <87d00uo85x.fsf@codeaurora.org> (raw)
In-Reply-To: <5f3ee526-e96f-3c88-a17e-e7ebf9703ed1@doubly.so> (Devin Bayer's message of "Tue, 3 Nov 2020 11:53:55 +0100")
Devin Bayer <dev@doubly.so> writes:
> On 02/11/2020 19.51, Kalle Valo wrote:
>>
>> To my knowledge, from ath11k point of view, QCA6391 should look the same
>> as QCA6390 but most likely the board file for QCA6391 is different.
>>
>
> Thanks. If I get to that point, I have been given firmware files from the
> vendor:
>
> 4076546464 3602624 amss.bin
> 1400223385 57936 bdwlan.bin
> 1400223385 57936 bdwlan.e0102
> 1400223385 57936 bdwlan.e0104
> 1400223385 57936 bdwlan.elf
> 691636418 57936 bdwlan01.e01
> 1400223385 57936 bdwlan01.e02
> 691636418 57936 bdwlan01.e03
> 3117335203 57936 bdwlan01.e04
> 1014175487 266684 m3.bin
>
> They are different than those from your repo, but maybe I can use
> bdwlan01.e04 as the board file.
Yes, that's what I would also suggest to test first: take the firmware
from ath11k-firmware.git and the board file from the vendor.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Devin Bayer <dev@doubly.so>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: ath11k with QCA6391
Date: Tue, 03 Nov 2020 15:56:58 +0200 [thread overview]
Message-ID: <87d00uo85x.fsf@codeaurora.org> (raw)
In-Reply-To: <5f3ee526-e96f-3c88-a17e-e7ebf9703ed1@doubly.so> (Devin Bayer's message of "Tue, 3 Nov 2020 11:53:55 +0100")
Devin Bayer <dev@doubly.so> writes:
> On 02/11/2020 19.51, Kalle Valo wrote:
>>
>> To my knowledge, from ath11k point of view, QCA6391 should look the same
>> as QCA6390 but most likely the board file for QCA6391 is different.
>>
>
> Thanks. If I get to that point, I have been given firmware files from the
> vendor:
>
> 4076546464 3602624 amss.bin
> 1400223385 57936 bdwlan.bin
> 1400223385 57936 bdwlan.e0102
> 1400223385 57936 bdwlan.e0104
> 1400223385 57936 bdwlan.elf
> 691636418 57936 bdwlan01.e01
> 1400223385 57936 bdwlan01.e02
> 691636418 57936 bdwlan01.e03
> 3117335203 57936 bdwlan01.e04
> 1014175487 266684 m3.bin
>
> They are different than those from your repo, but maybe I can use
> bdwlan01.e04 as the board file.
Yes, that's what I would also suggest to test first: take the firmware
from ath11k-firmware.git and the board file from the vendor.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-11-03 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 15:14 ath11k with QCA6391 Devin Bayer
2020-10-22 15:14 ` Devin Bayer
2020-11-02 18:51 ` Kalle Valo
2020-11-02 18:51 ` Kalle Valo
2020-11-03 10:53 ` Devin Bayer
2020-11-03 10:53 ` Devin Bayer
2020-11-03 13:56 ` Kalle Valo [this message]
2020-11-03 13:56 ` Kalle Valo
2020-11-25 13:22 ` Devin Bayer
2020-11-25 13:22 ` Devin Bayer
2020-11-26 10:04 ` Kalle Valo
2020-11-26 10:04 ` Kalle Valo
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=87d00uo85x.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=dev@doubly.so \
--cc=linux-wireless@vger.kernel.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.