* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
@ 2014-06-05 10:26 ` Kalle Valo
0 siblings, 0 replies; 39+ messages in thread
From: Kalle Valo @ 2014-06-05 10:26 UTC (permalink / raw)
To: Andy Lutomirski; +Cc: Linux Wireless List, Michal Kazior, ath10k
Andy Lutomirski <luto@amacapital.net> writes:
> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>> +ath10k@lists.infradead.org
>>
>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>> It dies with 'otp calibration failed: 2'.
>>>
>>> Some older version of the driver seemed to work fine.
>>
>> ath10k did not verify otp result before so it could load successfully
>> despite errors.
>>
>> Someone raised this problem yesterday on IRC. I'm not really sure how
>> we should deal with this properly.
>
> Ideally, someone from Atheros could figure out what the error is.
Michal already did. The error means that for some reason the
calibaration data was not found from OTP. OTP is the storage area where
the calibration data is normally stored within QCA9880.
> Barring that, the card seems to work okay without otp (I don't even
> know what otp is), so just warning and continuing to load might be
> better than bailing.
This means that your card is not properly calibrated and it doesn't
function in an optimal way (for example range or throughput is less than
what it could be).
Do you see that with all Archer C7 v2 devices or with just one? One
possibility is that the calibration data is actually stored outside of
QCA9880 board, for example in the host flash or similar. I don't have
that AP, can someone else see where the calibration data is stored?
I know that ath9k supports this kind of setup, most likely ath10k should
as well.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-05 10:26 ` Kalle Valo
@ 2014-06-05 16:04 ` Andy Lutomirski
-1 siblings, 0 replies; 39+ messages in thread
From: Andy Lutomirski @ 2014-06-05 16:04 UTC (permalink / raw)
To: Kalle Valo; +Cc: Michal Kazior, Linux Wireless List, ath10k
On Thu, Jun 5, 2014 at 3:26 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Andy Lutomirski <luto@amacapital.net> writes:
>
>> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>>> +ath10k@lists.infradead.org
>>>
>>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> It dies with 'otp calibration failed: 2'.
>>>>
>>>> Some older version of the driver seemed to work fine.
>>>
>>> ath10k did not verify otp result before so it could load successfully
>>> despite errors.
>>>
>>> Someone raised this problem yesterday on IRC. I'm not really sure how
>>> we should deal with this properly.
>>
>> Ideally, someone from Atheros could figure out what the error is.
>
> Michal already did. The error means that for some reason the
> calibaration data was not found from OTP. OTP is the storage area where
> the calibration data is normally stored within QCA9880.
Ah -- I misunderstood. I assumed that the OTP read was failing
mysteriously and that expert input was needed to resolve that mystery
:)
>
>> Barring that, the card seems to work okay without otp (I don't even
>> know what otp is), so just warning and continuing to load might be
>> better than bailing.
>
> This means that your card is not properly calibrated and it doesn't
> function in an optimal way (for example range or throughput is less than
> what it could be).
>
> Do you see that with all Archer C7 v2 devices or with just one? One
> possibility is that the calibration data is actually stored outside of
> QCA9880 board, for example in the host flash or similar. I don't have
> that AP, can someone else see where the calibration data is stored?
I only have one of these. I put a likely looking directory of the GPL
sources here:
http://web.mit.edu/luto/www/archerc7_gpl/atheros/
I'm not entirely sure what I'm looking for, but this might be it:
http://web.mit.edu/luto/www/archerc7_gpl/atheros/otp.c
I don't really know what I'm looking for, though.
--Andy
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
@ 2014-06-05 16:04 ` Andy Lutomirski
0 siblings, 0 replies; 39+ messages in thread
From: Andy Lutomirski @ 2014-06-05 16:04 UTC (permalink / raw)
To: Kalle Valo; +Cc: Linux Wireless List, Michal Kazior, ath10k
On Thu, Jun 5, 2014 at 3:26 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Andy Lutomirski <luto@amacapital.net> writes:
>
>> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>>> +ath10k@lists.infradead.org
>>>
>>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> It dies with 'otp calibration failed: 2'.
>>>>
>>>> Some older version of the driver seemed to work fine.
>>>
>>> ath10k did not verify otp result before so it could load successfully
>>> despite errors.
>>>
>>> Someone raised this problem yesterday on IRC. I'm not really sure how
>>> we should deal with this properly.
>>
>> Ideally, someone from Atheros could figure out what the error is.
>
> Michal already did. The error means that for some reason the
> calibaration data was not found from OTP. OTP is the storage area where
> the calibration data is normally stored within QCA9880.
Ah -- I misunderstood. I assumed that the OTP read was failing
mysteriously and that expert input was needed to resolve that mystery
:)
>
>> Barring that, the card seems to work okay without otp (I don't even
>> know what otp is), so just warning and continuing to load might be
>> better than bailing.
>
> This means that your card is not properly calibrated and it doesn't
> function in an optimal way (for example range or throughput is less than
> what it could be).
>
> Do you see that with all Archer C7 v2 devices or with just one? One
> possibility is that the calibration data is actually stored outside of
> QCA9880 board, for example in the host flash or similar. I don't have
> that AP, can someone else see where the calibration data is stored?
I only have one of these. I put a likely looking directory of the GPL
sources here:
http://web.mit.edu/luto/www/archerc7_gpl/atheros/
I'm not entirely sure what I'm looking for, but this might be it:
http://web.mit.edu/luto/www/archerc7_gpl/atheros/otp.c
I don't really know what I'm looking for, though.
--Andy
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-05 10:26 ` Kalle Valo
@ 2014-06-05 16:08 ` Ben Greear
-1 siblings, 0 replies; 39+ messages in thread
From: Ben Greear @ 2014-06-05 16:08 UTC (permalink / raw)
To: Kalle Valo; +Cc: Andy Lutomirski, Michal Kazior, Linux Wireless List, ath10k
On 06/05/2014 03:26 AM, Kalle Valo wrote:
> Andy Lutomirski <luto@amacapital.net> writes:
>
>> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>>> +ath10k@lists.infradead.org
>>>
>>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> It dies with 'otp calibration failed: 2'.
>>>>
>>>> Some older version of the driver seemed to work fine.
>>>
>>> ath10k did not verify otp result before so it could load successfully
>>> despite errors.
>>>
>>> Someone raised this problem yesterday on IRC. I'm not really sure how
>>> we should deal with this properly.
>>
>> Ideally, someone from Atheros could figure out what the error is.
>
> Michal already did. The error means that for some reason the
> calibaration data was not found from OTP. OTP is the storage area where
> the calibration data is normally stored within QCA9880.
I fought this with .387 firmware and WLE900VX NICs. If it's a common
problem with more than a single NIC (ie, not just a bad piece of
hardware), then one could load my firmware and my ath10k patches.
I have a way to effectively get text debug messages out of the
OTP firmware code and can probably debug this (eventually...busy
with other things currently).
If you know the basic hardware architecture of the NIC, then you can at least
make a better guess of the calibration data and choose an eeprom
table that is a better match than just total failure of OTP.
>> Barring that, the card seems to work okay without otp (I don't even
>> know what otp is), so just warning and continuing to load might be
>> better than bailing.
>
> This means that your card is not properly calibrated and it doesn't
> function in an optimal way (for example range or throughput is less than
> what it could be).
And, your MAC address will be wrong and identical to all other devices of this
type, which means the second one of these NICs
on your network will make everything go to hell.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
@ 2014-06-05 16:08 ` Ben Greear
0 siblings, 0 replies; 39+ messages in thread
From: Ben Greear @ 2014-06-05 16:08 UTC (permalink / raw)
To: Kalle Valo; +Cc: Linux Wireless List, Michal Kazior, ath10k, Andy Lutomirski
On 06/05/2014 03:26 AM, Kalle Valo wrote:
> Andy Lutomirski <luto@amacapital.net> writes:
>
>> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>>> +ath10k@lists.infradead.org
>>>
>>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> It dies with 'otp calibration failed: 2'.
>>>>
>>>> Some older version of the driver seemed to work fine.
>>>
>>> ath10k did not verify otp result before so it could load successfully
>>> despite errors.
>>>
>>> Someone raised this problem yesterday on IRC. I'm not really sure how
>>> we should deal with this properly.
>>
>> Ideally, someone from Atheros could figure out what the error is.
>
> Michal already did. The error means that for some reason the
> calibaration data was not found from OTP. OTP is the storage area where
> the calibration data is normally stored within QCA9880.
I fought this with .387 firmware and WLE900VX NICs. If it's a common
problem with more than a single NIC (ie, not just a bad piece of
hardware), then one could load my firmware and my ath10k patches.
I have a way to effectively get text debug messages out of the
OTP firmware code and can probably debug this (eventually...busy
with other things currently).
If you know the basic hardware architecture of the NIC, then you can at least
make a better guess of the calibration data and choose an eeprom
table that is a better match than just total failure of OTP.
>> Barring that, the card seems to work okay without otp (I don't even
>> know what otp is), so just warning and continuing to load might be
>> better than bailing.
>
> This means that your card is not properly calibrated and it doesn't
> function in an optimal way (for example range or throughput is less than
> what it could be).
And, your MAC address will be wrong and identical to all other devices of this
type, which means the second one of these NICs
on your network will make everything go to hell.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-05 16:08 ` Ben Greear
@ 2014-06-05 16:23 ` Andy Lutomirski
-1 siblings, 0 replies; 39+ messages in thread
From: Andy Lutomirski @ 2014-06-05 16:23 UTC (permalink / raw)
To: Ben Greear; +Cc: Kalle Valo, Michal Kazior, Linux Wireless List, ath10k
On Thu, Jun 5, 2014 at 9:08 AM, Ben Greear <greearb@candelatech.com> wrote:
> On 06/05/2014 03:26 AM, Kalle Valo wrote:
>> Andy Lutomirski <luto@amacapital.net> writes:
>>
>>> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>>>> +ath10k@lists.infradead.org
>>>>
>>>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>>>> It dies with 'otp calibration failed: 2'.
>>>>>
>>>>> Some older version of the driver seemed to work fine.
>>>>
>>>> ath10k did not verify otp result before so it could load successfully
>>>> despite errors.
>>>>
>>>> Someone raised this problem yesterday on IRC. I'm not really sure how
>>>> we should deal with this properly.
>>>
>>> Ideally, someone from Atheros could figure out what the error is.
>>
>> Michal already did. The error means that for some reason the
>> calibaration data was not found from OTP. OTP is the storage area where
>> the calibration data is normally stored within QCA9880.
>
> I fought this with .387 firmware and WLE900VX NICs. If it's a common
> problem with more than a single NIC (ie, not just a bad piece of
> hardware), then one could load my firmware and my ath10k patches.
No clue. I can buy another one of these things to find out, though,
if that would help.
>
> I have a way to effectively get text debug messages out of the
> OTP firmware code and can probably debug this (eventually...busy
> with other things currently).
Is this something you can send me? If not, and if you have time, I'd
be happy to mail you your very own Archer C7 v2.
OTOH, if this is likely to be it, then it might be a decent thing to play with:
http://web.mit.edu/luto/www/archerc7_gpl/atheros/otp.c
This hardware has two Atheros WLANs: a platform device ath9k and a
minipcie ath10k. Would ath9k also have something called 'OTP'?
>
> If you know the basic hardware architecture of the NIC, then you can at least
> make a better guess of the calibration data and choose an eeprom
> table that is a better match than just total failure of OTP.
>
I don't even know what that means. :(
>>> Barring that, the card seems to work okay without otp (I don't even
>>> know what otp is), so just warning and continuing to load might be
>>> better than bailing.
>>
>> This means that your card is not properly calibrated and it doesn't
>> function in an optimal way (for example range or throughput is less than
>> what it could be).
>
> And, your MAC address will be wrong and identical to all other devices of this
> type, which means the second one of these NICs
> on your network will make everything go to hell.
>
Heh. I'm already overriding the MAC address with a locally administered one.
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
--
Andy Lutomirski
AMA Capital Management, LLC
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
@ 2014-06-05 16:23 ` Andy Lutomirski
0 siblings, 0 replies; 39+ messages in thread
From: Andy Lutomirski @ 2014-06-05 16:23 UTC (permalink / raw)
To: Ben Greear; +Cc: Kalle Valo, Linux Wireless List, Michal Kazior, ath10k
On Thu, Jun 5, 2014 at 9:08 AM, Ben Greear <greearb@candelatech.com> wrote:
> On 06/05/2014 03:26 AM, Kalle Valo wrote:
>> Andy Lutomirski <luto@amacapital.net> writes:
>>
>>> On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>>>> +ath10k@lists.infradead.org
>>>>
>>>> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>>>>> It dies with 'otp calibration failed: 2'.
>>>>>
>>>>> Some older version of the driver seemed to work fine.
>>>>
>>>> ath10k did not verify otp result before so it could load successfully
>>>> despite errors.
>>>>
>>>> Someone raised this problem yesterday on IRC. I'm not really sure how
>>>> we should deal with this properly.
>>>
>>> Ideally, someone from Atheros could figure out what the error is.
>>
>> Michal already did. The error means that for some reason the
>> calibaration data was not found from OTP. OTP is the storage area where
>> the calibration data is normally stored within QCA9880.
>
> I fought this with .387 firmware and WLE900VX NICs. If it's a common
> problem with more than a single NIC (ie, not just a bad piece of
> hardware), then one could load my firmware and my ath10k patches.
No clue. I can buy another one of these things to find out, though,
if that would help.
>
> I have a way to effectively get text debug messages out of the
> OTP firmware code and can probably debug this (eventually...busy
> with other things currently).
Is this something you can send me? If not, and if you have time, I'd
be happy to mail you your very own Archer C7 v2.
OTOH, if this is likely to be it, then it might be a decent thing to play with:
http://web.mit.edu/luto/www/archerc7_gpl/atheros/otp.c
This hardware has two Atheros WLANs: a platform device ath9k and a
minipcie ath10k. Would ath9k also have something called 'OTP'?
>
> If you know the basic hardware architecture of the NIC, then you can at least
> make a better guess of the calibration data and choose an eeprom
> table that is a better match than just total failure of OTP.
>
I don't even know what that means. :(
>>> Barring that, the card seems to work okay without otp (I don't even
>>> know what otp is), so just warning and continuing to load might be
>>> better than bailing.
>>
>> This means that your card is not properly calibrated and it doesn't
>> function in an optimal way (for example range or throughput is less than
>> what it could be).
>
> And, your MAC address will be wrong and identical to all other devices of this
> type, which means the second one of these NICs
> on your network will make everything go to hell.
>
Heh. I'm already overriding the MAC address with a locally administered one.
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
--
Andy Lutomirski
AMA Capital Management, LLC
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-05 16:08 ` Ben Greear
@ 2014-06-06 6:39 ` Kalle Valo
-1 siblings, 0 replies; 39+ messages in thread
From: Kalle Valo @ 2014-06-06 6:39 UTC (permalink / raw)
To: Ben Greear; +Cc: Andy Lutomirski, Michal Kazior, Linux Wireless List, ath10k
Ben Greear <greearb@candelatech.com> writes:
>> Michal already did. The error means that for some reason the
>> calibaration data was not found from OTP. OTP is the storage area where
>> the calibration data is normally stored within QCA9880.
>
> I fought this with .387 firmware and WLE900VX NICs. If it's a common
> problem with more than a single NIC (ie, not just a bad piece of
> hardware), then one could load my firmware and my ath10k patches.
That's XB143, right? I think that's different as firmware started to
support XB143 only starting from 10.1.467.
--
Kalle Valo
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
@ 2014-06-06 6:39 ` Kalle Valo
0 siblings, 0 replies; 39+ messages in thread
From: Kalle Valo @ 2014-06-06 6:39 UTC (permalink / raw)
To: Ben Greear; +Cc: Linux Wireless List, Michal Kazior, ath10k, Andy Lutomirski
Ben Greear <greearb@candelatech.com> writes:
>> Michal already did. The error means that for some reason the
>> calibaration data was not found from OTP. OTP is the storage area where
>> the calibration data is normally stored within QCA9880.
>
> I fought this with .387 firmware and WLE900VX NICs. If it's a common
> problem with more than a single NIC (ie, not just a bad piece of
> hardware), then one could load my firmware and my ath10k patches.
That's XB143, right? I think that's different as firmware started to
support XB143 only starting from 10.1.467.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-06 6:39 ` Kalle Valo
@ 2014-06-06 16:05 ` Ben Greear
-1 siblings, 0 replies; 39+ messages in thread
From: Ben Greear @ 2014-06-06 16:05 UTC (permalink / raw)
To: Kalle Valo; +Cc: Andy Lutomirski, Michal Kazior, Linux Wireless List, ath10k
On 06/05/2014 11:39 PM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>>> Michal already did. The error means that for some reason the
>>> calibaration data was not found from OTP. OTP is the storage area where
>>> the calibration data is normally stored within QCA9880.
>>
>> I fought this with .387 firmware and WLE900VX NICs. If it's a common
>> problem with more than a single NIC (ie, not just a bad piece of
>> hardware), then one could load my firmware and my ath10k patches.
>
> That's XB143, right? I think that's different as firmware started to
> support XB143 only starting from 10.1.467.
Yes. My point is that I have the ability to get debug info out of
of the otp in my modified firmware, so it is possible to debug why
the otp is failing in the first place, and possibly fix otp to work
with that NIC.
I'll start begging to get my CT firmware support in upstream kernels
as soon as we get the firmware-crash stuff ironed out :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
@ 2014-06-06 16:05 ` Ben Greear
0 siblings, 0 replies; 39+ messages in thread
From: Ben Greear @ 2014-06-06 16:05 UTC (permalink / raw)
To: Kalle Valo; +Cc: Linux Wireless List, Michal Kazior, ath10k, Andy Lutomirski
On 06/05/2014 11:39 PM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>>> Michal already did. The error means that for some reason the
>>> calibaration data was not found from OTP. OTP is the storage area where
>>> the calibration data is normally stored within QCA9880.
>>
>> I fought this with .387 firmware and WLE900VX NICs. If it's a common
>> problem with more than a single NIC (ie, not just a bad piece of
>> hardware), then one could load my firmware and my ath10k patches.
>
> That's XB143, right? I think that's different as firmware started to
> support XB143 only starting from 10.1.467.
Yes. My point is that I have the ability to get debug info out of
of the otp in my modified firmware, so it is possible to debug why
the otp is failing in the first place, and possibly fix otp to work
with that NIC.
I'll start begging to get my CT firmware support in upstream kernels
as soon as we get the firmware-crash stuff ironed out :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-05 10:26 ` Kalle Valo
` (2 preceding siblings ...)
(?)
@ 2014-06-06 8:59 ` Matti Laakso
2014-06-06 9:09 ` Kalle Valo
-1 siblings, 1 reply; 39+ messages in thread
From: Matti Laakso @ 2014-06-06 8:59 UTC (permalink / raw)
To: ath10k
> ------------------------------------------------------------------------
> Andy Lutomirski <luto at amacapital.net <http://lists.infradead.org/mailman/listinfo/ath10k>> writes:
>
> >/ On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior at tieto.com <http://lists.infradead.org/mailman/listinfo/ath10k>> wrote:
> />>/ +ath10k at lists.infradead.org <http://lists.infradead.org/mailman/listinfo/ath10k>
> />>/
> />>/ On 28 May 2014 20:35, Andy Lutomirski <luto at amacapital.net <http://lists.infradead.org/mailman/listinfo/ath10k>> wrote:
> />>>/ It dies with 'otp calibration failed: 2'.
> />>>/
> />>>/ Some older version of the driver seemed to work fine.
> />>/
> />>/ ath10k did not verify otp result before so it could load successfully
> />>/ despite errors.
> />>/
> />>/ Someone raised this problem yesterday on IRC. I'm not really sure how
> />>/ we should deal with this properly.
> />/
> />/ Ideally, someone from Atheros could figure out what the error is.
> /
> Michal already did. The error means that for some reason the
> calibaration data was not found from OTP. OTP is the storage area where
> the calibration data is normally stored within QCA9880.
>
> >/ Barring that, the card seems to work okay without otp (I don't even
> />/ know what otp is), so just warning and continuing to load might be
> />/ better than bailing.
> /
> This means that your card is not properly calibrated and it doesn't
> function in an optimal way (for example range or throughput is less than
> what it could be).
>
> Do you see that with all Archer C7 v2 devices or with just one? One
> possibility is that the calibration data is actually stored outside of
> QCA9880 board, for example in the host flash or similar. I don't have
> that AP, can someone else see where the calibration data is stored?
>
> I know that ath9k supports this kind of setup, most likely ath10k should
> as well.
>
> --
> Kalle Valo
>
C7 v1 has the AR9550 calibration data in flash in the last 64 kiB,
likely C7 v2 as well. Could someone with v2 and OpenWrt use dd to dump
the contents of the "art" partition (/dev/mtdblock4 IIRC) and upload it
somewhere? I think it would be easy to see whether there is just the
calibration data for AR9550 or if there is also data for QCA9880.
Matti
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-06 8:59 ` Matti Laakso
@ 2014-06-06 9:09 ` Kalle Valo
2014-06-06 23:31 ` Kamal Koshy
0 siblings, 1 reply; 39+ messages in thread
From: Kalle Valo @ 2014-06-06 9:09 UTC (permalink / raw)
To: Matti Laakso; +Cc: ath10k
Moro,
Matti Laakso <malaakso@elisanet.fi> writes:
>> Do you see that with all Archer C7 v2 devices or with just one? One
>> possibility is that the calibration data is actually stored outside of
>> QCA9880 board, for example in the host flash or similar. I don't have
>> that AP, can someone else see where the calibration data is stored?
>>
>> I know that ath9k supports this kind of setup, most likely ath10k should
>> as well.
>
> C7 v1 has the AR9550 calibration data in flash in the last 64 kiB,
> likely C7 v2 as well.
Ok, then the chances are that QCA9880 calibration data is stored in the
flash as well.
> Could someone with v2 and OpenWrt use dd to dump the contents of the
> "art" partition (/dev/mtdblock4 IIRC) and upload it somewhere? I think
> it would be easy to see whether there is just the calibration data for
> AR9550 or if there is also data for QCA9880.
Good idea.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-06 9:09 ` Kalle Valo
@ 2014-06-06 23:31 ` Kamal Koshy
2014-06-07 5:36 ` Kalle Valo
0 siblings, 1 reply; 39+ messages in thread
From: Kamal Koshy @ 2014-06-06 23:31 UTC (permalink / raw)
To: ath10k
[-- Attachment #1: Type: text/plain, Size: 119 bytes --]
Attaching the result of dd if=/dev/mtd4 > ~/mtd4
Is there any documentation on the the format of calibration data ?
[-- Attachment #2: mtd4 --]
[-- Type: application/octet-stream, Size: 65536 bytes --]
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-06 23:31 ` Kamal Koshy
@ 2014-06-07 5:36 ` Kalle Valo
2014-06-07 6:11 ` Sven Schnelle
0 siblings, 1 reply; 39+ messages in thread
From: Kalle Valo @ 2014-06-07 5:36 UTC (permalink / raw)
To: Kamal Koshy; +Cc: ath10k
Kamal Koshy <kamal.koshy@gmail.com> writes:
> Attaching the result of dd if=/dev/mtd4 > ~/mtd4
Thanks, I'll take a look at that later. But before that, do you know
what's the mac address of the QCA9880 device with the proprietary
driver? (_not_ with ath10k) That would help searching for the
calibration data.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-07 5:36 ` Kalle Valo
@ 2014-06-07 6:11 ` Sven Schnelle
2014-06-08 11:52 ` Matti Laakso
2014-06-09 5:07 ` Michal Kazior
0 siblings, 2 replies; 39+ messages in thread
From: Sven Schnelle @ 2014-06-07 6:11 UTC (permalink / raw)
To: ath10k
Hi Kalle,
Am 07.06.2014 07:36, schrieb Kalle Valo:
> Kamal Koshy <kamal.koshy@gmail.com> writes:
>
>> Attaching the result of dd if=/dev/mtd4 > ~/mtd4
> Thanks, I'll take a look at that later. But before that, do you know
> what's the mac address of the QCA9880 device with the proprietary
> driver? (_not_ with ath10k) That would help searching for the
> calibration data.
>
To me it looks like ath9k calibration data starts at 0x1000, and ath10k
calibration data
starts at 0x5000 in that mtd image. That's the same as on my board.
Sven
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-07 6:11 ` Sven Schnelle
@ 2014-06-08 11:52 ` Matti Laakso
2014-06-09 8:28 ` Kalle Valo
2014-06-09 5:07 ` Michal Kazior
1 sibling, 1 reply; 39+ messages in thread
From: Matti Laakso @ 2014-06-08 11:52 UTC (permalink / raw)
To: ath10k
> ------------------------------------------------------------------------
> Hi Kalle,
>
> Am 07.06.2014 07:36, schrieb Kalle Valo:
> >/ Kamal Koshy <kamal.koshy at gmail.com <http://lists.infradead.org/mailman/listinfo/ath10k>> writes:
> />/
> />>/ Attaching the result of dd if=/dev/mtd4 > ~/mtd4
> />/ Thanks, I'll take a look at that later. But before that, do you know
> />/ what's the mac address of the QCA9880 device with the proprietary
> />/ driver? (_not_ with ath10k) That would help searching for the
> />/ calibration data.
> />/
> /To me it looks like ath9k calibration data starts at 0x1000, and ath10k
> calibration data
> starts at 0x5000 in that mtd image. That's the same as on my board.
>
> Sven
>
Yeah, that's definitely the case.
I think we need something like this for ath10k:
https://github.com/kvalo/ath/blob/master/include/linux/ath9k_platform.h
which we can then populate in the mach-file.
Matti
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-08 11:52 ` Matti Laakso
@ 2014-06-09 8:28 ` Kalle Valo
2014-06-09 14:39 ` Kamal Koshy
0 siblings, 1 reply; 39+ messages in thread
From: Kalle Valo @ 2014-06-09 8:28 UTC (permalink / raw)
To: Matti Laakso; +Cc: ath10k
Matti Laakso <malaakso@elisanet.fi> writes:
>> ------------------------------------------------------------------------
>> Hi Kalle,
>>
>> Am 07.06.2014 07:36, schrieb Kalle Valo:
>> >/ Kamal Koshy <kamal.koshy at gmail.com <http://lists.infradead.org/mailman/listinfo/ath10k>> writes:
>> />/
>> />>/ Attaching the result of dd if=/dev/mtd4 > ~/mtd4
>> />/ Thanks, I'll take a look at that later. But before that, do you know
>> />/ what's the mac address of the QCA9880 device with the proprietary
>> />/ driver? (_not_ with ath10k) That would help searching for the
>> />/ calibration data.
>> />/
>> /To me it looks like ath9k calibration data starts at 0x1000, and ath10k
>> calibration data
>> starts at 0x5000 in that mtd image. That's the same as on my board.
>>
>> Sven
>>
>
> Yeah, that's definitely the case.
>
> I think we need something like this for ath10k:
>
> https://github.com/kvalo/ath/blob/master/include/linux/ath9k_platform.h
>
> which we can then populate in the mach-file.
Yeah, we need that. But before that an ugly workaround is to do what
Michal suggests (copy the content to board.bin and skip otp.bin
execution in ath10k).
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-09 8:28 ` Kalle Valo
@ 2014-06-09 14:39 ` Kamal Koshy
0 siblings, 0 replies; 39+ messages in thread
From: Kamal Koshy @ 2014-06-09 14:39 UTC (permalink / raw)
To: ath10k
Michal, Kalle
I tried with the board file extracted from 0x5800-0x5843 (MD5 sum
0a0a9104555f857285b82b7f62b98440). This does not make a difference.
However, did not skip the OTP file, since I did not know how to do it. I
can try skipping the OTP file, if I can get the procedure.
Kamal
On 06/09/2014 01:28 AM, Kalle Valo wrote:
> Matti Laakso <malaakso@elisanet.fi> writes:
>
>>> ------------------------------------------------------------------------
>>> Hi Kalle,
>>>
>>> Am 07.06.2014 07:36, schrieb Kalle Valo:
>>>> / Kamal Koshy <kamal.koshy at gmail.com <http://lists.infradead.org/mailman/listinfo/ath10k>> writes:
>>> />/
>>> />>/ Attaching the result of dd if=/dev/mtd4 > ~/mtd4
>>> />/ Thanks, I'll take a look at that later. But before that, do you know
>>> />/ what's the mac address of the QCA9880 device with the proprietary
>>> />/ driver? (_not_ with ath10k) That would help searching for the
>>> />/ calibration data.
>>> />/
>>> /To me it looks like ath9k calibration data starts at 0x1000, and ath10k
>>> calibration data
>>> starts at 0x5000 in that mtd image. That's the same as on my board.
>>>
>>> Sven
>>>
>> Yeah, that's definitely the case.
>>
>> I think we need something like this for ath10k:
>>
>> https://github.com/kvalo/ath/blob/master/include/linux/ath9k_platform.h
>>
>> which we can then populate in the mach-file.
> Yeah, we need that. But before that an ugly workaround is to do what
> Michal suggests (copy the content to board.bin and skip otp.bin
> execution in ath10k).
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-07 6:11 ` Sven Schnelle
2014-06-08 11:52 ` Matti Laakso
@ 2014-06-09 5:07 ` Michal Kazior
2014-06-09 20:01 ` Sven Schnelle
1 sibling, 1 reply; 39+ messages in thread
From: Michal Kazior @ 2014-06-09 5:07 UTC (permalink / raw)
To: Sven Schnelle; +Cc: ath10k
On 7 June 2014 08:11, Sven Schnelle <svens@stackframe.org> wrote:
> Hi Kalle,
>
> Am 07.06.2014 07:36, schrieb Kalle Valo:
>
>> Kamal Koshy <kamal.koshy@gmail.com> writes:
>>
>>> Attaching the result of dd if=/dev/mtd4 > ~/mtd4
>>
>> Thanks, I'll take a look at that later. But before that, do you know
>> what's the mac address of the QCA9880 device with the proprietary
>> driver? (_not_ with ath10k) That would help searching for the
>> calibration data.
>>
> To me it looks like ath9k calibration data starts at 0x1000, and ath10k
> calibration data
> starts at 0x5000 in that mtd image. That's the same as on my board.
The data looks very similar to board.bin (2116 bytes and familiar hex
patterns). Can anyone replacing using it as the
/lib/firmware/ath10k/QCA988X/hw2.0/board.bin?
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread
* Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
2014-06-09 5:07 ` Michal Kazior
@ 2014-06-09 20:01 ` Sven Schnelle
0 siblings, 0 replies; 39+ messages in thread
From: Sven Schnelle @ 2014-06-09 20:01 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
Am 09.06.2014 07:07, schrieb Michal Kazior:
> On 7 June 2014 08:11, Sven Schnelle <svens@stackframe.org> wrote:
>> Hi Kalle,
>>
>> Am 07.06.2014 07:36, schrieb Kalle Valo:
>>
>>> Kamal Koshy <kamal.koshy@gmail.com> writes:
>>>
>>>> Attaching the result of dd if=/dev/mtd4 > ~/mtd4
>>> Thanks, I'll take a look at that later. But before that, do you know
>>> what's the mac address of the QCA9880 device with the proprietary
>>> driver? (_not_ with ath10k) That would help searching for the
>>> calibration data.
>>>
>> To me it looks like ath9k calibration data starts at 0x1000, and ath10k
>> calibration data
>> starts at 0x5000 in that mtd image. That's the same as on my board.
> The data looks very similar to board.bin (2116 bytes and familiar hex
> patterns). Can anyone replacing using it as the
> /lib/firmware/ath10k/QCA988X/hw2.0/board.bin?
>
Doesn't make a difference. The flash layout is the same on my
engineering sample,
and i've extracted board.bin from the flash layout. Can anyone explain
how OTP
works? It looks to me like otp is only run if calibration data in flash
is invalid in the
proprietary driver.
Thanks
Sven
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 39+ messages in thread