From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>,
Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcm43xx: Add firmware version to ethtool output
Date: Sun, 4 Mar 2007 20:02:39 +0100 [thread overview]
Message-ID: <200703042002.39581.mb@bu3sch.de> (raw)
In-Reply-To: <45eb1612.l8xsd6TwZVsRseAH%Larry.Finger@lwfinger.net>
On Sunday 04 March 2007 19:55, Larry Finger wrote:
> As the removal of ethtool capability from bcm43xx has been NACKed,
> some useful functionality should be added.
I cannot follow this logics, sorry. ;)
> This patch changes it
> so that the firmware version is output.
I don't see how this is useful.
I really want to avoid having more ethtool stuff, as it will
only create compatibility issues for the future.
This doesn't give information that's not available elsewhere.
> #include "bcm43xx.h"
> +#include "bcm43xx_main.h"
> #include "bcm43xx_ethtool.h"
>
> #include <linux/netdevice.h>
> @@ -42,6 +43,8 @@ static void bcm43xx_get_drvinfo(struct n
> strncpy(info->driver, KBUILD_MODNAME, sizeof(info->driver));
> strncpy(info->version, utsname()->release, sizeof(info->version));
> strncpy(info->bus_info, pci_name(bcm->pci_dev), ETHTOOL_BUSINFO_LEN);
> + snprintf(info->fw_version, sizeof(info->fw_version), "0x%x",
> + bcm43xx_shm_read16(bcm, BCM43xx_SHM_SHARED, BCM43xx_UCODE_REVISION));
This will crash when the device is not up.
--
Greetings Michael.
next prev parent reply other threads:[~2007-03-04 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 18:55 [PATCH] bcm43xx: Add firmware version to ethtool output Larry Finger
2007-03-04 19:02 ` Michael Buesch [this message]
2007-03-16 17:14 ` John W. Linville
2007-03-16 18:13 ` Larry Finger
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=200703042002.39581.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.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 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.