From: Peter Wu <lekensteyn@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: [PATCH] r8169: fix invalid register dump
Date: Sat, 17 Aug 2013 00:35:58 +0200 [thread overview]
Message-ID: <8673892.63sYyivWik@al> (raw)
In-Reply-To: <20130814224736.GA5193@electric-eye.fr.zoreil.com>
On Thursday 15 August 2013 00:47:36 Francois Romieu wrote:
> Spartan implementation:
>
> u32 __iomem *ioaddr = tp->mmio_addr;
> u32 *dw = p;
> int i;
>
> ...
>
> for (i = regs->len; i > 0; i -= 4)
> memcpy_fromio(dw++, ioaddr++, min(i, 4));
I like this one, simple and readable. I was worried about endianness
issues, but that does not apply here as the source and destination
are presumably in byte order.
I have tested this patch with a modified ethtool[1].
[1]: http://www.spinics.net/lists/netdev/msg246364.html
--
From: Peter Wu <lekensteyn@gmail.com>
For some reason, my PCIe RTL8111E onboard NIC on a GA-Z68X-UD3H-B3
motherboard reads as FFs when reading from MMIO with a block size
larger than 7. Therefore change to reading blocks of four bytes.
Signed-off-by: Peter Wu <lekensteyn@gmail.com>
---
drivers/net/ethernet/realtek/r8169.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/realtek/r8169.c
b/drivers/net/ethernet/realtek/r8169.c
index b5eb419..2943916 100644
--- a/drivers/net/ethernet/realtek/r8169.c
+++ b/drivers/net/ethernet/realtek/r8169.c
@@ -1897,12 +1897,16 @@ static void rtl8169_get_regs(struct net_device *dev,
struct ethtool_regs *regs,
void *p)
{
struct rtl8169_private *tp = netdev_priv(dev);
+ u32 __iomem *data = tp->mmio_addr;
+ u32 *dw = p;
+ int i;
if (regs->len > R8169_REGS_SIZE)
regs->len = R8169_REGS_SIZE;
rtl_lock_work(tp);
- memcpy_fromio(p, tp->mmio_addr, regs->len);
+ for (i = regs->len; i > 0; i -= 4)
+ memcpy_fromio(dw++, data++, min(4, i));
rtl_unlock_work(tp);
}
--
1.8.3.4
next prev parent reply other threads:[~2013-08-16 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 20:37 [PATCH] r8169: fix invalid register dump Peter Wu
2013-08-13 22:20 ` Francois Romieu
2013-08-14 13:12 ` Peter Wu
2013-08-14 19:58 ` Francois Romieu
2013-08-14 21:31 ` Peter Wu
2013-08-14 22:47 ` Francois Romieu
2013-08-16 22:35 ` Peter Wu [this message]
2013-08-15 20:33 ` Ben Hutchings
2013-08-16 22:58 ` Peter Wu
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=8673892.63sYyivWik@al \
--to=lekensteyn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.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.