ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "KAVITA MATHUR" <kavitam@cdot.in>
To: Manikanta Pubbisetty <mpubbise@qti.qualcomm.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: regulatory.db file for ath10k
Date: Wed, 13 Dec 2017 13:44:38 +0530	[thread overview]
Message-ID: <20171213081213.M75864@cdot.in> (raw)
In-Reply-To: <240c63ef1f9745acaa0e7585be6a46de@aphydexm01f.ap.qualcomm.com>

Thankyou so much for this information. 

I do not want to use regulatory.db. Can you please share your ath10k build
configuration? I may be missing something in configuration.

Thanks & Regards,
Kavita


On Wed, 13 Dec 2017 07:54:00 +0000, Manikanta Pubbisetty wrote
> Please CC linux wireless when posting queries on cfg/mac80211.
> 
> At least, I have not had any issues in interface bring up after the latest 
> regulatory.db change, I have tested it with vanilla ath.git and it worked even 
> without regulatory.db file. If you may want to refer, Johannes submitted a 
> patch[1] for converting db.txt to firmware file format.
> 
> [1] https://patchwork.kernel.org/patch/9992477/
> 
> mkp
> 
> >-----Original Message-----
> >From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
> >KAVITA MATHUR
> >Sent: Wednesday, December 13, 2017 12:02 PM
> >To: ath10k@lists.infradead.org
> >Subject: regulatory.db file for ath10k
> >
> >hi,
> >
> >wifi interface is not up with ath10k driver due to missing regulatory.db.I have
> >taken ath10k latest driver code from backports and ath10k git on 12 Dec.
> >
> >
> >
> >Loading modules backported from Linux version v3.18-239930-g135da6d
> >Backport generated by backports.git v4.14-rc2-1-35-g3d13478 ath10k_pci
> >0002:03:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
> >cfg80211: failed to load regulatory.db
> >ath10k_pci 0002:03:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff
> >sub 0000:0000 ath10k_pci 0002:03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs
> >0 testmode 0 ath10k_pci 0002:03:00.0: firmware ver 10.2.4.70.66 api 5 features
> >no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 c2dd2ad5 ath10k_pci
> >0002:03:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 ath10k_pci
> >0002:03:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto
> >1
> >
> >wifi
> >root@CDOT:/# IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready device
> >wlan0 entered promiscuous mode device wlan0 left promiscuous mode
> >br-lan: port 2(wlan0) entered disabled state
> >
> >How to generate regulatory.db file or is it available to use it directly? Please
> >help me to fix it.
> >
> >
> >
> >
> >
> >
> >
> >
> >Thanks & Regards,
> >कविता माथुर Kavita Mathur
> >वरिष्ठ अनुसंधान अभियंता  Senior Research Engineer
> >सी-डॉट                      C-DOT
> >इलैक्ट्रॉनिक्स सिटी फेज़ I         Electronics City Phase I
> >होसूर रोड, बेंगलूरु               Hosur Road, Bengaluru – 560100
> >फोन  Ph 080-28529896
> >Disclaimer:
> >----------
> >This email and any files transmitted with it
> >
> >
> >_______________________________________________
> >ath10k mailing list
> >ath10k@lists.infradead.org
> >http://lists.infradead.org/mailman/listinfo/ath10k


Thanks & Regards,
कविता माथुर Kavita Mathur 
वरिष्ठ अनुसंधान अभियंता  Senior Research Engineer 
सी-डॉट                      C-DOT
इलैक्ट्रॉनिक्स सिटी फेज़ I         Electronics City Phase I
होसूर रोड, बेंगलूरु               Hosur Road, Bengaluru – 560100
फोन  Ph 080-28529896
Disclaimer:
----------
This email and any files transmitted with it


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2017-12-13  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  6:32 regulatory.db file for ath10k KAVITA MATHUR
2017-12-13  7:54 ` Manikanta Pubbisetty
2017-12-13  8:14   ` KAVITA MATHUR [this message]
2017-12-14  7:11     ` Manikanta Pubbisetty
2017-12-14 12:52     ` 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=20171213081213.M75864@cdot.in \
    --to=kavitam@cdot.in \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpubbise@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox