From: Tejun Heo <tj@kernel.org>
To: Timur Tabi <timur@freescale.com>
Cc: michael@ellerman.id.au, 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:31:47 -0700 [thread overview]
Message-ID: <49DD17C3.7040607@kernel.org> (raw)
In-Reply-To: <49DD1465.6070001@freescale.com>
Timur Tabi wrote:
> Tejun Heo wrote:
>
>> Yeah, right. The following patch should do the trick then.
>
> Thanks, I appreciate it. I get this output:
>
> XXX PCI_COMMAND=0x407
^
Yeah, that's INTX disable. Strange that the controller has the bit
set on boot. I'm curious where this is from, the controller reset,
firmware or the PCI init (in decreasing likelihood). Hmmm... for now,
I think it would be best to revert the original change. Jeff, can you
please do that?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-04-08 21:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 14:54 "ahci: drop intx manipulation on msi enable" breaks ULI M1575 Timur Tabi
2009-04-07 23:57 ` Tejun Heo
2009-04-08 0:36 ` 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
2009-04-08 21:17 ` Timur Tabi
2009-04-08 21:31 ` Tejun Heo [this message]
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=49DD17C3.7040607@kernel.org \
--to=tj@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--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).