On Fri, Sep 25, 2009 at 09:53:35AM -0700, Luis R. Rodriguez wrote: > On Fri, Sep 25, 2009 at 9:47 AM, Kalle Valo <kalle.valo@xxxxxx> wrote: > > But we want to export two strings to user space (at least for now), is > > it really worth the effort to add ethtool support for such a minor > > feature? Also I have understood that ethtool is implemented only for > > ethernet drivers, I don't feel comfortable that we use ethernet driver > > interfaces with 802.11 device drivers. They are so much different that > > there isn't that much common functionality. That's why I prefer > > nl80211 over ethtool. > > > > What do people think? > > So for Wake-on-Wireless I ran into the same, ethtool just did not > offer the same wake up events needed for wireless. I could have > technically used ethtool and expanded it to support wireless but it > just seemed dirty. > > I agree that using ethtool seems overkill compared to the patches you posted. I think you either overestimate the amount of trouble for implementing (minimal) ethtool support or you underestimate the amount of functionality available through that interface. That, or you just don't like using something named "eth"tool for wireless -- but hey, let's be honest about the frames we send/receive to/from the kernel... :-) The ethtool interface provides functionality for viewing and modifying eeprom contents, dumping registers, trigger self-tests, basic driver info, getting and setting message reporting levels, external card identification (hey, _could_ be useful!), and some other bits like checksum offload that might(?) be useful in the future. I understand regarding the WoW vs. WoL issue but probably the answer is just to add a new method for WoW...? I'll post a patch series based on what Kalle sent but using ethtool instead of nl80211... John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
