All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graham Gower <graham.gower@gmail.com>
To: netdev@vger.kernel.org, Stephen Hemminger <shemminger@vyatta.com>
Subject: [PATCH v2] skge: Add DMA mask quirk for Marvell 88E8001 on ASUS P5NSLI motherboard.
Date: Mon, 08 Oct 2012 16:03:44 +1030	[thread overview]
Message-ID: <507265B8.5070406@gmail.com> (raw)
In-Reply-To: <50711961.1010101@gmail.com>


Marvell 88E8001 on an ASUS P5NSLI motherboard is unable to send/receive
packets on a system with >4gb ram unless a 32bit DMA mask is used.

This issue has been around for years and a fix was sent 3.5 years ago, but
there was some debate as to whether it should instead be fixed as a PCI quirk.
http://www.spinics.net/lists/netdev/msg88670.html

However, 18 months later a similar workaround was introduced for another
chipset exhibiting the same problem.
http://www.spinics.net/lists/netdev/msg142287.html

Signed-off-by: Graham Gower <graham.gower@gmail.com>

--- a/drivers/net/ethernet/marvell/skge.c
+++ b/drivers/net/ethernet/marvell/skge.c
@@ -4143,6 +4143,13 @@
  			DMI_MATCH(DMI_BOARD_NAME, "nForce"),
  		},
  	},
+	{
+		.ident = "ASUS P5NSLI",
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."),
+			DMI_MATCH(DMI_BOARD_NAME, "P5NSLI")
+		},
+	},
  	{}
  };
  

  parent reply	other threads:[~2012-10-08  5:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07  5:55 skge: Add DMA mask quirk for Marvell 88E8001 on ASUS P5NSLI motherboard Graham Gower
2012-10-07  9:32 ` Jan Ceuleers
2012-10-08  5:33   ` Graham Gower
2012-10-08  5:33 ` Graham Gower [this message]
2012-10-08  5:36   ` [PATCH v2] " David Miller
2012-10-08  5:54     ` [PATCH v3] " Graham Gower
2012-10-08  6:11       ` David Miller
2012-10-08  6:15         ` Graham Gower
2012-10-08  6:21           ` David Miller
2012-10-08 16:16 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2012-10-08 16:54 [PATCH] " Jan Ceuleers
2012-10-08 18:34 ` [PATCH v2] " Jan Ceuleers
2012-10-08 18:49   ` David Miller

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=507265B8.5070406@gmail.com \
    --to=graham.gower@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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.