linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	hhasselm@web.de
Subject: [PATCH #upstream] libata: Fujitsu AMILO Pa 2510 can't do 64bit DMA either
Date: Fri, 18 Sep 2009 08:43:54 +0900	[thread overview]
Message-ID: <4AB2C9BA.5040103@kernel.org> (raw)

This is the third SB600 system which can't do 64bit DMA.  Add it to
blacklist.

Signed-off-by: Tejun Heo <tj@kernel.org>
Reported-by: Holger Hasselmann <hhasselm@web.de>
Cc: Shane Huang <Shane.Huang@amd.com>
---
This is bad because we can't backport this to -stable and broken 64bit
DMA makes these systems unusable for kernels released without the
following blacklisting.  I think we should disable 64bit DMA for
SB600s in -stable.  Any objections?  Shane?

 drivers/ata/ahci.c |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index d4cd9c2..173a150 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -2688,6 +2688,20 @@ static bool ahci_sb600_32bit_only(struct pci_dev *pdev)
 				DMI_MATCH(DMI_BOARD_NAME, "GA-MA69VM-S2"),
 			},
 		},
+		/*
+		 * This laptop can't do 64bit DMA either.  The latest
+		 * BIOS as of this writing (1.10c) doesn't fix the
+		 * problem either.
+		 *
+		 * http://thread.gmane.org/gmane.linux.ide/42716
+		 */
+		{
+			.ident = "Fujitsu AMILO Pa 2510",
+			.matches = {
+				DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"),
+				DMI_MATCH(DMI_PRODUCT_NAME, "AMILO Pa 2510"),
+			},
+		},
 		{ }
 	};
 	const struct dmi_system_id *match;

                 reply	other threads:[~2009-09-17 23:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AB2C9BA.5040103@kernel.org \
    --to=tj@kernel.org \
    --cc=hhasselm@web.de \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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).