All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Linux Wireless List <linux-wireless@vger.kernel.org>,
	Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Fri, 06 Jun 2014 09:05:22 -0700	[thread overview]
Message-ID: <5391E6C2.7030602@candelatech.com> (raw)
In-Reply-To: <87oay6mthk.fsf@kamboji.qca.qualcomm.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Michal Kazior <michal.kazior@tieto.com>,
	Linux Wireless List <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Fri, 06 Jun 2014 09:05:22 -0700	[thread overview]
Message-ID: <5391E6C2.7030602@candelatech.com> (raw)
In-Reply-To: <87oay6mthk.fsf@kamboji.qca.qualcomm.com>

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


  reply	other threads:[~2014-06-06 16:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 18:35 compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2 Andy Lutomirski
2014-05-29  7:48 ` Michal Kazior
2014-05-29  7:48   ` Michal Kazior
2014-05-29 17:52   ` Andy Lutomirski
2014-05-29 17:52     ` Andy Lutomirski
2014-06-05 10:26     ` Kalle Valo
2014-06-05 10:26       ` Kalle Valo
2014-06-05 16:04       ` Andy Lutomirski
2014-06-05 16:04         ` Andy Lutomirski
2014-06-05 16:08       ` Ben Greear
2014-06-05 16:08         ` Ben Greear
2014-06-05 16:23         ` Andy Lutomirski
2014-06-05 16:23           ` Andy Lutomirski
2014-06-06  6:39         ` Kalle Valo
2014-06-06  6:39           ` Kalle Valo
2014-06-06 16:05           ` Ben Greear [this message]
2014-06-06 16:05             ` Ben Greear
2014-06-06  8:59       ` Matti Laakso
2014-06-06  9:09         ` Kalle Valo
2014-06-06 23:31           ` Kamal Koshy
2014-06-07  5:36             ` Kalle Valo
2014-06-07  6:11               ` Sven Schnelle
2014-06-08 11:52                 ` Matti Laakso
2014-06-09  8:28                   ` Kalle Valo
2014-06-09 14:39                     ` Kamal Koshy
2014-06-09  5:07                 ` Michal Kazior
2014-06-09 20:01                   ` Sven Schnelle
2014-06-05 11:15   ` Sven Schnelle
2014-06-05 11:36     ` Kalle Valo
2014-06-05 11:49       ` Sven Schnelle
2014-06-05 12:20         ` Michal Kazior
2014-06-07 20:37           ` Sven Schnelle
2014-06-07 20:41             ` Sven Schnelle
2014-06-08  5:59               ` Kamal Koshy
2014-06-09  5:40             ` Michal Kazior
2014-06-12 12:57             ` Michal Kazior
2014-06-12 19:37               ` Sven Schnelle
2014-06-13 11:12                 ` Michal Kazior
2014-06-14 16:51                   ` 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=5391E6C2.7030602@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=michal.kazior@tieto.com \
    /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.