From: Patrick McHardy <kaber@trash.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: RFC: mac80211: add ethtool support
Date: Wed, 25 Nov 2009 17:47:17 +0100 [thread overview]
Message-ID: <4B0D5F95.9000308@trash.net> (raw)
In-Reply-To: <20091125164313.GE7800@tuxdriver.com>
John W. Linville wrote:
> On Wed, Nov 25, 2009 at 05:42:53PM +0100, Patrick McHardy wrote:
>> Johannes Berg wrote:
>>> On Wed, 2009-11-25 at 17:34 +0100, Patrick McHardy wrote:
>>>> Johannes Berg wrote:
>>>>> On Wed, 2009-11-25 at 17:18 +0100, Patrick McHardy wrote:
>>>>>> mac80211: add ethtool support
>>>>>>
>>>>>> Add ethtool support and add a drvname field to struct ieee80211_ops, which is
>>>>>> used for ethtool driver information. This is useful with multiple different
>>>>>> wireless cards to find out which device is using which driver.
>>>>>>
>>>>> I thought we _had_ ethtool support via cfg80211?!
>>>> Mhh good point :) For some reason it didn't show any information, but
>>>> that might have been a mistake on my part. I'll give it another shot :)
>>> It probably won't show the driver name because we haven't pushed that
>>> through in any way?
>> Its actually showing:
>>
>> # ethtool -i wlan0
>> Cannot get driver information: Operation not supported
>>
>> which shouldn't happen, since the callback is defined. I'll
>> have a closer look at this.
>
> What kernel are you using?
OK, that was a mistake on my part, I added the patch on net-next,
but the above test was done on net-2.6. Everything is working fine,
sorry for the confusion :)
prev parent reply other threads:[~2009-11-25 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:18 RFC: mac80211: add ethtool support Patrick McHardy
2009-11-25 16:31 ` Johannes Berg
2009-11-25 16:34 ` Patrick McHardy
2009-11-25 16:36 ` Johannes Berg
2009-11-25 16:42 ` Patrick McHardy
2009-11-25 16:43 ` John W. Linville
2009-11-25 16:47 ` Patrick McHardy [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=4B0D5F95.9000308@trash.net \
--to=kaber@trash.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).