linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Timur Tabi <timur@freescale.com>
Cc: linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
	Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: "ahci: drop intx manipulation on msi enable" breaks ULI M1575
Date: Wed, 08 Apr 2009 14:13:25 -0700	[thread overview]
Message-ID: <49DD1375.8030400@kernel.org> (raw)
In-Reply-To: <49DD11D1.7060105@freescale.com>

Timur Tabi wrote:
> Tejun Heo wrote:
> 
>> Running "lspci -nnvvvxxx" before loading the driver should be enough.
> 
> That might be difficult.  My root file system is on my SATA drive.
> It'll be a while before I can build an NFS rootfs.
> 

Yeah, right.  The following patch should do the trick then.

diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 788bba2..b3f4df7 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -2606,6 +2606,12 @@ static int ahci_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
 	if (!printed_version++)
 		dev_printk(KERN_DEBUG, &pdev->dev, "version " DRV_VERSION "\n");
 
+	{
+		u16 cmd;
+		pci_read_config_word(pdev, PCI_COMMAND, &cmd);
+		printk("XXX PCI_COMMAND=0x%x\n", cmd);
+	}
+
 	/* The AHCI driver can only drive the SATA ports, the PATA driver
 	   can drive them all so if both drivers are selected make sure
 	   AHCI stays out of the way */


-- 
tejun

  reply	other threads:[~2009-04-08 21:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49DB6914.1030107@freescale.com>
     [not found] ` <49DBE858.9040004@kernel.org>
2009-04-08  0:36   ` "ahci: drop intx manipulation on msi enable" breaks ULI M1575 Timur Tabi
2009-04-08  0:52     ` Michael Ellerman
2009-04-08  1:19       ` Timur Tabi
2009-04-08  2:09     ` Michael Ellerman
2009-04-08  6:12       ` Jeff Garzik
2009-04-08 11:40       ` Timur Tabi
2009-04-08 21:04         ` Tejun Heo
2009-04-08 21:06           ` Timur Tabi
2009-04-08 21:13             ` Tejun Heo [this message]
2009-04-08 21:17               ` Timur Tabi
2009-04-08 21:31                 ` Tejun Heo
2009-04-08 22:15                   ` Timur Tabi
2009-04-08 23:53                     ` Michael Ellerman
2009-04-09  4:23                       ` Kumar Gala
2009-04-09  4:38                         ` Michael Ellerman
2009-04-09  5:18                           ` Kumar Gala
2009-04-09  5:32                           ` Jeff Garzik
2009-04-09 15:19                             ` Timur Tabi
2009-04-13 11:34                             ` Michael Ellerman
2009-04-16 21:27                             ` Timur Tabi

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=49DD1375.8030400@kernel.org \
    --to=tj@kernel.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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 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).