From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 1/2] ath9k_htc: Dump base eeprom header for UB91/94/95
Date: Mon, 2 May 2011 19:31:58 -0700 [thread overview]
Message-ID: <20110503023158.GA11667@tux> (raw)
In-Reply-To: <19898.35529.55613.593784@gargle.gargle.HOWL>
On Fri, Apr 29, 2011 at 02:54:17AM -0700, Sujith wrote:
> Christian Lamparter wrote:
> > 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.
>
> Yeah, this was the reasoning that I used to write a tool to dump eeprom
> data for PCI cards (using libpciaccess), and it is languishing internally. :)
>
> I agree that there are benefits to having a userspace tool,
> maybe Luis' ath-utils tree can be used. But until then, it would be useful
> to have these in the driver.
Why didn't we ever open your tool up?
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Sujith <m.sujith@gmail.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [ath9k-devel] [PATCH 1/2] ath9k_htc: Dump base eeprom header for UB91/94/95
Date: Mon, 2 May 2011 19:31:58 -0700 [thread overview]
Message-ID: <20110503023158.GA11667@tux> (raw)
In-Reply-To: <19898.35529.55613.593784@gargle.gargle.HOWL>
On Fri, Apr 29, 2011 at 02:54:17AM -0700, Sujith wrote:
> Christian Lamparter wrote:
> > 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.
>
> Yeah, this was the reasoning that I used to write a tool to dump eeprom
> data for PCI cards (using libpciaccess), and it is languishing internally. :)
>
> I agree that there are benefits to having a userspace tool,
> maybe Luis' ath-utils tree can be used. But until then, it would be useful
> to have these in the driver.
Why didn't we ever open your tool up?
Luis
next prev parent reply other threads:[~2011-05-03 2:31 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 ` [ath9k-devel] " Christian Lamparter
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 ` Luis R. Rodriguez [this message]
2011-05-03 2:31 ` [ath9k-devel] " 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=20110503023158.GA11667@tux \
--to=lrodriguez@atheros.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.