On 25 November 2015 at 16:01, bartlomiej.grzeskowiak
wrote:
> Hi,
>
> Our embedded device works with 3.10 kernel. Since it is not within our
> responsibility it is not easy to upgrade the whole kernel. We would like to
> use the WLAN card with QCA6174 chipset.
>
Hi,
Our embedded device works with 3.10 kernel. Since it is not within our
responsibility it is not easy to upgrade the whole kernel. We would like to
use the WLAN card with QCA6174 chipset.
I have found out, that QCA6174 chipset is first supported in 3.20 kernel.
ath10k driver that
It complains about not being able to find firmware-3.bin. I'm not sure about the
order. I'll try again with firmware-3.bin in the firmware directory.
-- Regards Joerg
> Kalle Valo schrieb am 9:21 Mittwoch, 25.November
> 2015:
> > Joerg Pommnitz
Hi,
Thanks for your answer.
> >>>
> >>> Hi,
> >>>
> >>> I have a simple test platform.
> >>> One PC connected to an equipment. This equipment is set in
> >>> AP mode.
> >>> Another PC connected to another equipment. This equipment
> >>> is set in STA + WDS
Felix Fietkau writes:
>>> However, on the device that I'm testing on
>>> (IPQ806x based), this patch makes the difference between working and
>>> non-working wifi, fixing the regression introduced by your pre-allocated
>>> coherent memory patch.
>>
>> Thank you for the catch
Joerg Pommnitz writes:
> It complains about not being able to find firmware-3.bin. I'm not sure about
> the
> order. I'll try again with firmware-3.bin in the firmware directory.
It should try firmware-3.bin first and then try firmware-2.bin.
--
Kalle Valo
Joerg Pommnitz writes:
> Thanks for the clarification.
> Somebody should update
>
>
>
> https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware
>
> It states, that 10.2 is for 3.18.
I just checked, 3.18 should try firmware-3.bin first and hence it should
support
Sorry for my late answer.
Sadly the AP's im connecting to, are part of my universities wifi so i can't
tell you the excat chipset they use.
I tried to connect without the network manager so i followed the instructions
and did a try with wpa_supplicant.
I attached you the log i got, but sadly
(fixing quotes)
Peter Oh writes:
>> In file included from include/linux/bitops.h:36:0,
>> from include/linux/kernel.h:10,
>> from include/asm-generic/bug.h:13,
>> from arch/m68k/include/asm/bug.h:28,
>>
This is to make it easier to split them later and also make room for crc32
checksums.
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/debug.c | 29 ++---
1 file changed, 18 insertions(+), 11 deletions(-)
diff --git
When debugging firmware problems it's useful to check checksums of each
component. Add a debugfs interface to retrieve crc32 checksums:
# cat /sys/kernel/debug/ieee80211/phy0/ath10k/fw_checksums
firmware-N.bin cc3fb466
athwlan c0089f21
otp f3efeb4f
but consider to ignore the result. this code will still fail on all IPQ
SOC's with embedded QCA99XX cards.
they do not contain any valid otp and this function will always fail. so
the result must be ignored.
this problem has been seen on Linksys EA8500, Netgear R7500 and Trendnet
TEW827
so far
We check board id from all board types, not just qca99x0, so the error message
was misleading.
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
That way we can split the messages to be printed in different stages of
device initialisation.
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/debug.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
On 18 November 2015 at 16:56, Pratik Singhal wrote:
> Hello, I am running ubuntu 15.10 with kernel 4.3.0-040300-generic.
> My device id is Network controller [0280]: Qualcomm Atheros Device
> [168c:0041] (rev 20)
>
> I have succesfully copied firmware into
>
15 matches
Mail list logo