All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Enabling debug on Ath9k
Date: Thu, 02 Apr 2009 12:24:56 -0400	[thread overview]
Message-ID: <1238689496.1675.11.camel@mj> (raw)
In-Reply-To: <7439b3d10904020557x39f5051bu5f8d6d889d8cbba4@mail.gmail.com>

On Thu, 2009-04-02 at 14:57 +0200, Giorgio Mazzucchelli wrote:
> As far as I have learn, the first step to read the card's EEPROM is to
> enabling debug, correct me if I'm wrong.

EEPROM is read by ath9k regardless of whether debugging is enabled or
not.

> Here they are the steps that I have follow:
> 
> in config.mk
> added  CONFIG_ATH9K_DEBUG=y 
> then make && make install in compat wireless' directory
> 
> problem: where I can find this configuration menu? make menuconfig in
> which directory?
> Device Drivers  --->
>   [*] Network device support  --->
>         Wireless LAN  --->
>           <M>   Atheros 802.11n wireless cards support
>           [*]     Atheros ath9k debugging

Sorry, I haven't touched compat-wireless for a long time.

> The issue is that I can't see any 'debug' parameter for ath9k module,
> take a look:
> 
> modinfo ath9k
> filename:       /lib/modules/2.6.28-9-generic/updates/drivers/net/wireless/ath9k/ath9k.ko
> license:        Dual BSD/GPL
> description:    Support for Atheros 802.11n wireless LAN cards.
> author:         Atheros Communications
> srcversion:     0E00038F566194A06BE4261
> alias:          pci:v0000168Cd0000002Bsv*sd*bc*sc*i*
> alias:          pci:v0000168Cd0000002Asv*sd*bc*sc*i*
> alias:          pci:v0000168Cd00000029sv*sd*bc*sc*i*
> alias:          pci:v0000168Cd00000027sv*sd*bc*sc*i*
> alias:          pci:v0000168Cd00000024sv*sd*bc*sc*i*
> alias:          pci:v0000168Cd00000023sv*sd*bc*sc*i*
> depends:        led-class,mac80211,cfg80211
> vermagic:       2.6.28-9-generic SMP mod_unload modversions 586 
> parm:           nohwcrypt:Disable hardware encryption (int)
> parm:           btcoex_enable:Enable Bluetooth coexistence support
> (bool)

It means that CONFIG_ATH9K_DEBUG wasn't enabled.  If I enable it, I see
3 parameters:

parm:           debug:uint
parm:           nohwcrypt:Disable hardware encryption (int)
parm:           btcoex_enable:Enable Bluetooth coexistence support (bool)

> Then, 
> modprobe ath9k debug=0xo... should return me the regulatory info write
> in the EEPROM

It would load the module.  If you need any specific information, you can
just add a printk() statement in the place where the code is read.

> and 
> modprobe cfg80211 ieee80211_regdom=(the country code that I want)
> should let me set the country code

That should work.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2009-04-02 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 12:57 [ath9k-devel] Enabling debug on Ath9k Giorgio Mazzucchelli
2009-04-02 16:24 ` Pavel Roskin [this message]

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=1238689496.1675.11.camel@mj \
    --to=proski@gnu.org \
    --cc=ath9k-devel@lists.ath9k.org \
    /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.