All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 1/2] ath9k_htc: Dump base eeprom header for UB91/94/95
Date: Fri, 29 Apr 2011 11:06:20 +0200	[thread overview]
Message-ID: <201104291106.21170.chunkeey@googlemail.com> (raw)
In-Reply-To: <19898.4633.920683.992470@gargle.gargle.HOWL>

On Friday 29 April 2011 03:19:21 Sujith wrote:
> Christian Lamparter wrote:
> > On Thursday 28 April 2011 10:58:33 Sujith wrote:
> > > From: Sujith Manoharan <Sujith.Manoharan@atheros.com>
> > > 
> > > Debugfs file location: <debugfs_mnt>/ieee80211/phy#/ath9k_htc/base_eeprom
> > > 
> > If you just want to dump the eeprom, then why not with a userspace utility?
> > It's pretty easy to write such a thing with libusb, furthermore it's more
> > versatile and portable so the *BSD-folks are not left out!
> 
> We do have an eeprom dump tool for PCI cards, but hardly any one uses
> that. 
Oh, I used ath_info for ath5k a lot. Especially to get around regdom restrictions.
Sure, your tool won't be able to do that, but never the less.

> It's much more convenient to use debugging features that are present
> in the driver itself. On an embedded board, it makes things a little bit easier.
Do you really think that everyone will be happy to recompile their stripped & heavily 
customised embedded kernels/or compat-wireless just to enable DEBUG and
waste precious resources? Even with a PC, this is not necessarily straightforward,
especially if the user has never done it before.

Regards,
	Chr

WARNING: multiple messages have this Message-ID (diff)
From: Christian Lamparter <chunkeey@googlemail.com>
To: Sujith <m.sujith@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ath9k-devel@lists.ath9k.org
Subject: Re: [PATCH 1/2] ath9k_htc: Dump base eeprom header for UB91/94/95
Date: Fri, 29 Apr 2011 11:06:20 +0200	[thread overview]
Message-ID: <201104291106.21170.chunkeey@googlemail.com> (raw)
In-Reply-To: <19898.4633.920683.992470@gargle.gargle.HOWL>

On Friday 29 April 2011 03:19:21 Sujith wrote:
> Christian Lamparter wrote:
> > On Thursday 28 April 2011 10:58:33 Sujith wrote:
> > > From: Sujith Manoharan <Sujith.Manoharan@atheros.com>
> > > 
> > > Debugfs file location: <debugfs_mnt>/ieee80211/phy#/ath9k_htc/base_eeprom
> > > 
> > If you just want to dump the eeprom, then why not with a userspace utility?
> > It's pretty easy to write such a thing with libusb, furthermore it's more
> > versatile and portable so the *BSD-folks are not left out!
> 
> We do have an eeprom dump tool for PCI cards, but hardly any one uses
> that. 
Oh, I used ath_info for ath5k a lot. Especially to get around regdom restrictions.
Sure, your tool won't be able to do that, but never the less.

> It's much more convenient to use debugging features that are present
> in the driver itself. On an embedded board, it makes things a little bit easier.
Do you really think that everyone will be happy to recompile their stripped & heavily 
customised embedded kernels/or compat-wireless just to enable DEBUG and
waste precious resources? Even with a PC, this is not necessarily straightforward,
especially if the user has never done it before.

Regards,
	Chr

  parent reply	other threads:[~2011-04-29  9:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  8:58 [ath9k-devel] [PATCH 1/2] ath9k_htc: Dump base eeprom header for UB91/94/95 Sujith
2011-04-28  8:58 ` Sujith
2011-04-28 23:16 ` [ath9k-devel] " Christian Lamparter
2011-04-28 23:16   ` Christian Lamparter
2011-04-29  0:10   ` [ath9k-devel] " Adrian Chadd
2011-04-29  0:10     ` Adrian Chadd
2011-04-29  1:19   ` [ath9k-devel] " Sujith
2011-04-29  1:19     ` Sujith
2011-04-29  4:58     ` [ath9k-devel] " Adrian Chadd
2011-04-29  4:58       ` Adrian Chadd
2011-04-29  9:06     ` Christian Lamparter [this message]
2011-04-29  9:06       ` Christian Lamparter
2011-04-29  9:54       ` [ath9k-devel] " Sujith
2011-04-29  9:54         ` Sujith
2011-05-03  2:31         ` [ath9k-devel] " Luis R. Rodriguez
2011-05-03  2:31           ` Luis R. Rodriguez
2011-05-03  2:59           ` Sujith

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=201104291106.21170.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --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.