From: "John W. Linville" <linville@tuxdriver.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: jgarzik@pobox.com, Jon_Wetzel@Dell.com
Subject: [patch 2.6.13 4/16] b44: support ETHTOOL_GPERMADDR
Date: Mon, 12 Sep 2005 10:48:55 -0400 [thread overview]
Message-ID: <09122005104855.31965@bilbo.tuxdriver.com> (raw)
In-Reply-To: <09122005104855.31900@bilbo.tuxdriver.com>
Add support for ETHTOOL_GPERMADDR to b44.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
drivers/net/b44.c | 2 ++
1 files changed, 2 insertions(+)
diff --git a/drivers/net/b44.c b/drivers/net/b44.c
--- a/drivers/net/b44.c
+++ b/drivers/net/b44.c
@@ -1676,6 +1676,7 @@ static struct ethtool_ops b44_ethtool_op
.set_pauseparam = b44_set_pauseparam,
.get_msglevel = b44_get_msglevel,
.set_msglevel = b44_set_msglevel,
+ .get_perm_addr = ethtool_op_get_perm_addr,
};
static int b44_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd)
@@ -1718,6 +1719,7 @@ static int __devinit b44_get_invariants(
bp->dev->dev_addr[3] = eeprom[80];
bp->dev->dev_addr[4] = eeprom[83];
bp->dev->dev_addr[5] = eeprom[82];
+ memcpy(bp->dev->perm_addr, bp->dev->dev_addr, bp->dev->addr_len);
bp->phy_addr = eeprom[90] & 0x1f;
next prev parent reply other threads:[~2005-09-12 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 14:48 [patch 2.6.13 0/16] implement ETHTOOL_GPERMADDR support for a number of drivers John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 1/16] 3c59x: support ETHTOOL_GPERMADDR John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 2/16] 8139cp: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 3/16] 8139too: " John W. Linville
2005-09-12 14:48 ` John W. Linville [this message]
2005-09-12 14:48 ` [patch 2.6.13 5/16] bnx2: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 6/16] e1000: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 7/16] e100: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 8/16] forcedeth: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 9/16] ixgb: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 10/16] ne2k-pci: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 11/16] pcnet32: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 12/16] r8169: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 13/16] skge: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 14/16] sundance: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 15/16] tg3: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 16/16] via-rhine: " John W. Linville
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=09122005104855.31965@bilbo.tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Jon_Wetzel@Dell.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).