From: Pavel Roskin <proski@gnu.org>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Michael Buesch <mb@bu3sch.de>, Zhu Yi <yi.zhu@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: mac80211 ethtool support
Date: Wed, 12 Dec 2007 19:31:28 -0500 [thread overview]
Message-ID: <1197505888.13188.9.camel@dv> (raw)
In-Reply-To: <1ba2fa240712121523h59d919f8k42fe54b992618432@mail.gmail.com>
On Thu, 2007-12-13 at 01:23 +0200, Tomas Winkler wrote:
> > NACK. Which virtual interface should get this? wmaster sounds like the
> > "obvious" candidate but we want to get rid of it ASAP. And the others
> > ones are pretty wrong because you can, technically, have a wiphy without
> > any virtual interfaces on it.
> >
> Just a thought. What if all virtual interfaces will quasi implements
> it. It doesn't matter if all the interfaces answers the same.
I think The True Linux Way (c) would be to have EEPROM support for
devices (those that live in /sys/device) without tying it to network
interfaces or cfg80211.
See __ATTR in include/linux/device.h, although I'm not sure if
attributes are suitable for EEPROM as is.
Maybe EEPROM should even be a separate class of devices connected to
other devices.
Of course, the topic would be better suited for LKML.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-12-13 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 8:17 mac80211 ethtool support Zhu Yi
2007-12-11 12:50 ` Michael Buesch
2007-12-12 1:13 ` Zhu Yi
2007-12-12 10:48 ` Michael Buesch
2007-12-12 17:45 ` Johannes Berg
2007-12-12 23:23 ` Tomas Winkler
2007-12-13 0:27 ` John W. Linville
2007-12-13 11:38 ` Johannes Berg
2007-12-13 13:43 ` Tomas Winkler
2007-12-13 17:34 ` Johannes Berg
2007-12-13 0:31 ` 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=1197505888.13188.9.camel@dv \
--to=proski@gnu.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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).