* Re: ath10k drivers on t1024 freescale board
2016-01-12 8:04 ` Michal Kazior
@ 2016-01-12 8:09 ` B R Manjula
2016-01-12 8:17 ` B R Manjula
` (2 subsequent siblings)
3 siblings, 0 replies; 10+ messages in thread
From: B R Manjula @ 2016-01-12 8:09 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k@lists.infradead.org
There are so many releases which one is suitable for our linux kernel 3.12
On Tue, 12 Jan 2016 09:04:57 +0100, Michal Kazior wrote
> On 12 January 2016 at 08:05, B R Manjula <brm@cdot.in> wrote:
> > Hello ,
> >
> > We are using kernel 3.11 on FREESCALE reference board T1024RDB-64bit board trying to
> > bringup ath10k drivers we are using WLE-900VX-7AA (11ac pcie mini card) we
downloaded
> > the
> > firmware from the following site:
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/main/firmware-
> > 2.bin_999.999.0.636
> > replaced as firmware.bin in the directory /lib/firmware/ath10k/QCA988X/hw2.0
> >
> > board.bin is downloaded from
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/board.bin
> >
> > and otp.bin was not found we just placed some file in the name as otp.bin
> >
> > we are getting the following issue:
> >
> > ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0xc00000000-0xc001fffff 64bit]
> > ath10k: MSI-X didn't succeed (1), trying MSI
> > ath10k: MSI interrupt handling
> > ath10k: Hardware name qca988x hw2.0 version 0x4100016c
> > ath10k: early firmware event indicated
> > ath10k: unable to write to the device
> > ath10k: could not write otp (-110)
> > ath10k: could not init core (-110)
> > ath10k: could not probe fw (-110)
> > ath10k: could not register driver core (-110)
> > ath10k_pci: probe of 0000:01:00.0 failed with error -110
> >
> > what could be the reason.
>
> You can't just go about and use FW API2 firmware as FW API1 one. No
> wonder device crashed.
>
> Also you can't just place any file instead of otp.bin.
>
> Moreover you're using an arcane version of ath10k. It's wasteful if
> you're going to report problems that were already fixed. Please
> upgrade the kernel or use backports:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking
any action in reliance on the contents of this information is strictly prohibited. The
sender does not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail t
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: ath10k drivers on t1024 freescale board
2016-01-12 8:04 ` Michal Kazior
2016-01-12 8:09 ` B R Manjula
@ 2016-01-12 8:17 ` B R Manjula
2016-01-12 12:02 ` Michal Kazior
2016-01-12 11:29 ` B R Manjula
2016-01-12 12:04 ` B R Manjula
3 siblings, 1 reply; 10+ messages in thread
From: B R Manjula @ 2016-01-12 8:17 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k@lists.infradead.org
Thanks for your input which version of the backport to be taken for kernel 3.12
backports-4.2.6-1 signed
backports-4.1.1-1 signed
backports-4.0.1-1 signed
backports-3.19-rc1-1 signed
backports-3.18.1-1 signed
backports-3.17.1-1 signed
backports-3.16.2-1 signed
backports-3.15.9-1 signed
backports-3.14-1 signed
backports-3.12.8-1 signed
backports-3.10.19-1 signed
where do we get otp.bin file
On Tue, 12 Jan 2016 09:04:57 +0100, Michal Kazior wrote
> On 12 January 2016 at 08:05, B R Manjula <brm@cdot.in> wrote:
> > Hello ,
> >
> > We are using kernel 3.11 on FREESCALE reference board T1024RDB-64bit board trying to
> > bringup ath10k drivers we are using WLE-900VX-7AA (11ac pcie mini card) we
downloaded
> > the
> > firmware from the following site:
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/main/firmware-
> > 2.bin_999.999.0.636
> > replaced as firmware.bin in the directory /lib/firmware/ath10k/QCA988X/hw2.0
> >
> > board.bin is downloaded from
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/board.bin
> >
> > and otp.bin was not found we just placed some file in the name as otp.bin
> >
> > we are getting the following issue:
> >
> > ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0xc00000000-0xc001fffff 64bit]
> > ath10k: MSI-X didn't succeed (1), trying MSI
> > ath10k: MSI interrupt handling
> > ath10k: Hardware name qca988x hw2.0 version 0x4100016c
> > ath10k: early firmware event indicated
> > ath10k: unable to write to the device
> > ath10k: could not write otp (-110)
> > ath10k: could not init core (-110)
> > ath10k: could not probe fw (-110)
> > ath10k: could not register driver core (-110)
> > ath10k_pci: probe of 0000:01:00.0 failed with error -110
> >
> > what could be the reason.
>
> You can't just go about and use FW API2 firmware as FW API1 one. No
> wonder device crashed.
>
> Also you can't just place any file instead of otp.bin.
>
> Moreover you're using an arcane version of ath10k. It's wasteful if
> you're going to report problems that were already fixed. Please
> upgrade the kernel or use backports:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking
any action in reliance on the contents of this information is strictly prohibited. The
sender does not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail t
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: ath10k drivers on t1024 freescale board
2016-01-12 8:17 ` B R Manjula
@ 2016-01-12 12:02 ` Michal Kazior
2016-01-12 16:56 ` B R Manjula
0 siblings, 1 reply; 10+ messages in thread
From: Michal Kazior @ 2016-01-12 12:02 UTC (permalink / raw)
To: B R Manjula; +Cc: ath10k@lists.infradead.org
On 12 January 2016 at 09:17, B R Manjula <brm@cdot.in> wrote:
> Thanks for your input which version of the backport to be taken for kernel 3.12
>
> backports-4.2.6-1 signed
> backports-4.1.1-1 signed
> backports-4.0.1-1 signed
> backports-3.19-rc1-1 signed
> backports-3.18.1-1 signed
> backports-3.17.1-1 signed
> backports-3.16.2-1 signed
> backports-3.15.9-1 signed
> backports-3.14-1 signed
> backports-3.12.8-1 signed
> backports-3.10.19-1 signed
All of them should work. That's how backports work:
https://backports.wiki.kernel.org/index.php/Documentation
> where do we get otp.bin file
You don't. It's embedded in FW API2 firmware blobs. FW API1 is very
old and I would discourage using a driver which requires it. FYI You
can still get it either by extracting it or using older git checkout:
https://github.com/kvalo/ath10k-firmware/tree/9374d42c01bd84487855af9f9bffc622c50e7331/ath10k/QCA988X/hw2.0
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: ath10k drivers on t1024 freescale board
2016-01-12 12:02 ` Michal Kazior
@ 2016-01-12 16:56 ` B R Manjula
0 siblings, 0 replies; 10+ messages in thread
From: B R Manjula @ 2016-01-12 16:56 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k@lists.infradead.org
thanks for input...
On Tue, 12 Jan 2016 13:02:29 +0100, Michal Kazior wrote
> On 12 January 2016 at 09:17, B R Manjula <brm@cdot.in> wrote:
> > Thanks for your input which version of the backport to be taken for kernel 3.12
> >
> > backports-4.2.6-1 signed
> > backports-4.1.1-1 signed
> > backports-4.0.1-1 signed
> > backports-3.19-rc1-1 signed
> > backports-3.18.1-1 signed
> > backports-3.17.1-1 signed
> > backports-3.16.2-1 signed
> > backports-3.15.9-1 signed
> > backports-3.14-1 signed
> > backports-3.12.8-1 signed
> > backports-3.10.19-1 signed
>
> All of them should work. That's how backports work:
>
> https://backports.wiki.kernel.org/index.php/Documentation
>
> > where do we get otp.bin file
>
> You don't. It's embedded in FW API2 firmware blobs. FW API1 is very
> old and I would discourage using a driver which requires it. FYI You
> can still get it either by extracting it or using older git checkout:
>
> https://github.com/kvalo/ath10k-
firmware/tree/9374d42c01bd84487855af9f9bffc622c50e7331/ath10k/QCA988X/hw2.0
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking
any action in reliance on the contents of this information is strictly prohibited. The
sender does not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail t
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: ath10k drivers on t1024 freescale board
2016-01-12 8:04 ` Michal Kazior
2016-01-12 8:09 ` B R Manjula
2016-01-12 8:17 ` B R Manjula
@ 2016-01-12 11:29 ` B R Manjula
2016-01-12 12:06 ` Michal Kazior
2016-01-12 12:04 ` B R Manjula
3 siblings, 1 reply; 10+ messages in thread
From: B R Manjula @ 2016-01-12 11:29 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k@lists.infradead.org
Please can you provide useful links to cross-compilation we are getting issues while
cross-compiling for target:
Though I am cross-compiling it is giving following error:
The conf is not executing on the host:
make defconfig-ath10k
powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux -Wall -Wmissing-prototypes -
Wstrict-prototypes -O2 -fomit-frame-pointer -c -o conf.o conf.c
powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux -Wall -Wmissing-prototypes -
Wstrict-prototypes -O2 -fomit-frame-pointer -c -o zconf.tab.o zconf.tab.c
In file included from zconf.tab.c:2503:0:
menu.c: In function 'get_symbol_str':
menu.c:561:18: warning: 'jump' may be used uninitialized in this function [-Wmaybe-
uninitialized]
jump->offset = r->len - 1;
^
menu.c:515:19: note: 'jump' was declared here
struct jump_key *jump;
^
powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux conf.o zconf.tab.o -o conf
./kconf/conf: ./kconf/conf: cannot execute binary file
make[1]: *** [defconfig-ath10k] Error 126
make: *** [defconfig-ath10k] Error 2
On Tue, 12 Jan 2016 09:04:57 +0100, Michal Kazior wrote
> On 12 January 2016 at 08:05, B R Manjula <brm@cdot.in> wrote:
> > Hello ,
> >
> > We are using kernel 3.11 on FREESCALE reference board T1024RDB-64bit board trying to
> > bringup ath10k drivers we are using WLE-900VX-7AA (11ac pcie mini card) we
downloaded
> > the
> > firmware from the following site:
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/main/firmware-
> > 2.bin_999.999.0.636
> > replaced as firmware.bin in the directory /lib/firmware/ath10k/QCA988X/hw2.0
> >
> > board.bin is downloaded from
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/board.bin
> >
> > and otp.bin was not found we just placed some file in the name as otp.bin
> >
> > we are getting the following issue:
> >
> > ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0xc00000000-0xc001fffff 64bit]
> > ath10k: MSI-X didn't succeed (1), trying MSI
> > ath10k: MSI interrupt handling
> > ath10k: Hardware name qca988x hw2.0 version 0x4100016c
> > ath10k: early firmware event indicated
> > ath10k: unable to write to the device
> > ath10k: could not write otp (-110)
> > ath10k: could not init core (-110)
> > ath10k: could not probe fw (-110)
> > ath10k: could not register driver core (-110)
> > ath10k_pci: probe of 0000:01:00.0 failed with error -110
> >
> > what could be the reason.
>
> You can't just go about and use FW API2 firmware as FW API1 one. No
> wonder device crashed.
>
> Also you can't just place any file instead of otp.bin.
>
> Moreover you're using an arcane version of ath10k. It's wasteful if
> you're going to report problems that were already fixed. Please
> upgrade the kernel or use backports:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking
any action in reliance on the contents of this information is strictly prohibited. The
sender does not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail t
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: ath10k drivers on t1024 freescale board
2016-01-12 11:29 ` B R Manjula
@ 2016-01-12 12:06 ` Michal Kazior
0 siblings, 0 replies; 10+ messages in thread
From: Michal Kazior @ 2016-01-12 12:06 UTC (permalink / raw)
To: B R Manjula; +Cc: ath10k@lists.infradead.org
On 12 January 2016 at 12:29, B R Manjula <brm@cdot.in> wrote:
> Please can you provide useful links to cross-compilation we are getting issues while
> cross-compiling for target:
>
> Though I am cross-compiling it is giving following error:
>
> The conf is not executing on the host:
>
> make defconfig-ath10k
> powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
> networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux -Wall -Wmissing-prototypes -
> Wstrict-prototypes -O2 -fomit-frame-pointer -c -o conf.o conf.c
> powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
> networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux -Wall -Wmissing-prototypes -
> Wstrict-prototypes -O2 -fomit-frame-pointer -c -o zconf.tab.o zconf.tab.c
> In file included from zconf.tab.c:2503:0:
> menu.c: In function 'get_symbol_str':
> menu.c:561:18: warning: 'jump' may be used uninitialized in this function [-Wmaybe-
> uninitialized]
> jump->offset = r->len - 1;
> ^
> menu.c:515:19: note: 'jump' was declared here
> struct jump_key *jump;
> ^
> powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
> networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux conf.o zconf.tab.o -o conf
> ./kconf/conf: ./kconf/conf: cannot execute binary file
> make[1]: *** [defconfig-ath10k] Error 126
> make: *** [defconfig-ath10k] Error 2
I'm no cross-compilation expert. At best I can refer you to:
https://backports.wiki.kernel.org/index.php/Documentation/packaging
The "cannot execute binary file" can mean:
- invalid libc linking
- missing +x permissions on file (unlikely)
- missing +x permissions on filesystem (e.g. due to "noexec" mount option)
- trying to run a binary destined to a different arch
You'll have to figure it out yourself.
As an alternative you might want to use QEMU and do emulated native
compilation (e.g. Debian with deboostrap) but I will not go into
detail how to do this as it's not trivial.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: ath10k drivers on t1024 freescale board
2016-01-12 8:04 ` Michal Kazior
` (2 preceding siblings ...)
2016-01-12 11:29 ` B R Manjula
@ 2016-01-12 12:04 ` B R Manjula
3 siblings, 0 replies; 10+ messages in thread
From: B R Manjula @ 2016-01-12 12:04 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k@lists.infradead.org
Please can you provide useful links to cross-compilation we are getting issues while
cross-compiling for target:
Though I am cross-compiling it is giving following error:
The conf is not executing on the host:
make defconfig-ath10k
powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux -Wall -Wmissing-prototypes -
Wstrict-prototypes -O2 -fomit-frame-pointer -c -o conf.o conf.c
powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux -Wall -Wmissing-prototypes -
Wstrict-prototypes -O2 -fomit-frame-pointer -c -o zconf.tab.o zconf.tab.c
In file included from zconf.tab.c:2503:0:
menu.c: In function 'get_symbol_str':
menu.c:561:18: warning: 'jump' may be used uninitialized in this function [-Wmaybe-
uninitialized]
jump->offset = r->len - 1;
^
menu.c:515:19: note: 'jump' was declared here
struct jump_key *jump;
^
powerpc64-fsl-linux-gcc -mhard-float -m64 -mcpu=e5500 --sysroot=/opt/fsl-
networking/QorIQ-SDK-V1.7/sysroots/ppc64e5500-fsl-linux conf.o zconf.tab.o -o conf
./kconf/conf: ./kconf/conf: cannot execute binary file
make[1]: *** [defconfig-ath10k] Error 126
make: *** [defconfig-ath10k] Error 2
On Tue, 12 Jan 2016 09:04:57 +0100, Michal Kazior wrote
> On 12 January 2016 at 08:05, B R Manjula <brm@cdot.in> wrote:
> > Hello ,
> >
> > We are using kernel 3.11 on FREESCALE reference board T1024RDB-64bit board trying to
> > bringup ath10k drivers we are using WLE-900VX-7AA (11ac pcie mini card) we
downloaded
> > the
> > firmware from the following site:
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/main/firmware-
> > 2.bin_999.999.0.636
> > replaced as firmware.bin in the directory /lib/firmware/ath10k/QCA988X/hw2.0
> >
> > board.bin is downloaded from
> > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/board.bin
> >
> > and otp.bin was not found we just placed some file in the name as otp.bin
> >
> > we are getting the following issue:
> >
> > ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0xc00000000-0xc001fffff 64bit]
> > ath10k: MSI-X didn't succeed (1), trying MSI
> > ath10k: MSI interrupt handling
> > ath10k: Hardware name qca988x hw2.0 version 0x4100016c
> > ath10k: early firmware event indicated
> > ath10k: unable to write to the device
> > ath10k: could not write otp (-110)
> > ath10k: could not init core (-110)
> > ath10k: could not probe fw (-110)
> > ath10k: could not register driver core (-110)
> > ath10k_pci: probe of 0000:01:00.0 failed with error -110
> >
> > what could be the reason.
>
> You can't just go about and use FW API2 firmware as FW API1 one. No
> wonder device crashed.
>
> Also you can't just place any file instead of otp.bin.
>
> Moreover you're using an arcane version of ath10k. It's wasteful if
> you're going to report problems that were already fixed. Please
> upgrade the kernel or use backports:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking
any action in reliance on the contents of this information is strictly prohibited. The
sender does not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail t
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 10+ messages in thread