Problems in regulatory.bin.5
This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand. I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template. -- Eric S. Raymond Problems with regulatory.bin.5: .SS markup in name section seriously confuses parsing, and sections don't follow standard naming conventions. --- regulatory.bin.5-unpatched 2012-07-02 01:57:14.437776710 -0400 +++ regulatory.bin.52012-07-02 01:59:11.117774528 -0400 @@ -2,12 +2,7 @@ .SH NAME regulatory.bin \- The Linux wireless regulatory database -.ad l -.in +8 -.ti -8 - -.SS -.SH Description +.SH DESCRIPTION .B regulatory.bin is the file used by the Linux wireless subsystem to keep its regulatory database information. It is read by @@ -22,7 +17,7 @@ .B regulatory.bin file should be updated upon regulatory changes or corrections. -.SH Upkeeping +.SH UPKEEP The regulatory database is maintained by the community as such you are encouraged to send any corrections or updates to the linux-wireless mailing list:
Re: Atheros AR9462 - 5Ghz not working
mgre...@cinci.rr.com wrote: > > mgre...@cinci.rr.com wrote: > > > > Sedat Dilek wrote: > > > On Tue, May 22, 2018 at 7:21 PM, wrote: > > > > I've run out of ideas and am hoping someone here can help. > > > > > > > > All I want to do is connect a client to my 5Ghz network. > > > > > > > > My client: > > > > OS is Debian stable "Stretch" with sysvinit instead of systemd > > > > Atheros AR9462 (World roaming 0x64 regdomain in EEPROM) > > > > "iw reg set US" > > > > "iw list" shows both 2.4Ghz and 5Ghz bands available. > > > > "iw wlp3s0 survey dump" shows received traffic on 5Ghz bands. > > > > > > > > There are oodles of 5Ghz AP's within range, but scans (including > > > > passive scans) reveal only 2.4Ghz networks. My only guess was that it > > > > won't transmit due to regulatory requirements, but I cannot make it > > > > work. > > > > > > > > What I've tried: > > > > Running with and without CRDA > > > > Running latest mainline kernel > > > > Hacking around on the ath9k driver and nl80211 to remove all > > > > regulatory enforcement. > > > > > > > > Nothing works and I'm pulling my hair out. Any help would be greatly > > > > appreciated. > > > > > > Hi, > > > > > > I try to give some initial help. > > > > > > The linux-wireless driver is supported by ath9k driver see [1] and [2]. > > > > > > Unfortunately, you have not sent any log-files at least your dmesg-log. > > > No output of the above userspace commands or userspace-tools versions. > > > No information to VendorID/ProductID (PCI, USB, whatever). > > > It's not clear to me if this is a kernelspace (ath9k-driver) or > > > userspace (CRDA/regulatory) problem. > > > How should someone help you effectively? > > > > > > The linux-wireless wiki has somne informations on how to debug > > > Atheros/Qualcomm ath9k-driver, see [3]. > > > > > > As a debianist I say try Linux v4.16 Debian packages from > > > stretch-backports (and maybe a higher version of wireless-regdb). > > > > > > Try to ask questions the smart way [4] :-). > > > > > > Hope this helps. > > > > > > Regards, > > > - Sedat - > > > > > > [1] https://wireless.wiki.kernel.org/en/users/drivers/ath9k > > > [2] https://wireless.wiki.kernel.org/en/users/drivers/ath9k/devices > > > [3] https://wireless.wiki.kernel.org/en/users/drivers/ath9k/debug > > > [4] http://www.catb.org/esr/faqs/smart-questions.html > > > > > > I have also built the latest wireless-regdb and crda, but it made no > > difference. > > > > Did any of the information I posted point towards a cause? Also, I'll gladly send one of these adapters to someone with ath9k experience if they suspect they can make it work. Just message me. :)
[PATCH] NFC: fdp: Fix unused variable warnings
Fix unused variable warnings reported on next-20180612.
Fixes: 7579d009c4a1 ("NFC: fdp: Remove __func__ from dev_dbg()")
Signed-off-by: Amit Pundir
---
drivers/nfc/fdp/fdp.c | 13 -
1 file changed, 13 deletions(-)
diff --git a/drivers/nfc/fdp/fdp.c b/drivers/nfc/fdp/fdp.c
index 36d1091d288a..6b5aba8c8937 100644
--- a/drivers/nfc/fdp/fdp.c
+++ b/drivers/nfc/fdp/fdp.c
@@ -247,7 +247,6 @@ static int fdp_nci_open(struct nci_dev *ndev)
{
int r;
struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
r = info->phy_ops->enable(info->phy);
@@ -256,16 +255,12 @@ static int fdp_nci_open(struct nci_dev *ndev)
static int fdp_nci_close(struct nci_dev *ndev)
{
- struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
-
return 0;
}
static int fdp_nci_send(struct nci_dev *ndev, struct sk_buff *skb)
{
struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
if (atomic_dec_and_test(>data_pkt_counter))
info->data_pkt_counter_cb(ndev);
@@ -275,9 +270,6 @@ static int fdp_nci_send(struct nci_dev *ndev, struct
sk_buff *skb)
int fdp_nci_recv_frame(struct nci_dev *ndev, struct sk_buff *skb)
{
- struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
-
return nci_recv_frame(ndev, skb);
}
EXPORT_SYMBOL(fdp_nci_recv_frame);
@@ -599,7 +591,6 @@ static int fdp_nci_core_reset_ntf_packet(struct nci_dev
*ndev,
struct sk_buff *skb)
{
struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
info->setup_reset_ntf = 1;
wake_up(>setup_wq);
@@ -611,7 +602,6 @@ static int fdp_nci_prop_patch_ntf_packet(struct nci_dev
*ndev,
struct sk_buff *skb)
{
struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
info->setup_patch_ntf = 1;
info->setup_patch_status = skb->data[0];
@@ -785,9 +775,6 @@ EXPORT_SYMBOL(fdp_nci_probe);
void fdp_nci_remove(struct nci_dev *ndev)
{
- struct fdp_nci_info *info = nci_get_drvdata(ndev);
- struct device *dev = >phy->i2c_dev->dev;
-
nci_unregister_device(ndev);
nci_free_device(ndev);
}
--
2.7.4
