linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>,
	Michael Buesch <mb@bu3sch.de>,
	Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcm43xx: remove ethtool
Date: Sat, 03 Mar 2007 22:58:39 -0500	[thread overview]
Message-ID: <45EA43EF.1080009@garzik.org> (raw)
In-Reply-To: <45EA3D21.3080203@lwfinger.net>

Larry Finger wrote:
> Jeff Garzik wrote:
>> Larry Finger wrote:
>>> Ethtool is useless for bcm43xx - remove it.
>>>
>>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> How is GDRVINFO useless?  Where does mac80211 provide equivalent
>> information?
> 
> I cannot speak for mac80211, but the current implementation for SoftMAC only implements the GDRVINFO
> call. From it, you get that the driver is bcm43xx (big surprise), the kernel version (easier gotten
> by a uname -r), and the bus info. None of the operational parameters can be changed or interrogated.
> 
> Is this enough to keep the ethtool interface? Because of the EOL for SoftMAC, this code will never
> be enhanced or extended. Does some userland code need this info?

It's a highly standardized interface that provides information that's 
either impossible or highly difficult to obtain elsewhere.

If you are a userland process querying a network interface, that's the 
only way to know which driver is attached, or the only way to build an 
association between a PCI device and a network interface.

So NAK this change.  All network drivers should implement GDRVINFO, even 
if they are not strictly ethernet drivers.

	Jeff




  reply	other threads:[~2007-03-04  3:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04  1:00 [PATCH] bcm43xx: remove ethtool Larry Finger
2007-03-04  2:44 ` Jeff Garzik
2007-03-04  3:29   ` Larry Finger
2007-03-04  3:58     ` Jeff Garzik [this message]
2007-03-04  5:04       ` Michael Wu
2007-03-04  5:10       ` Pavel Roskin
2007-03-04 12:59       ` Michael Buesch

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=45EA43EF.1080009@garzik.org \
    --to=jeff@garzik.org \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).