From: Tejun Heo <htejun@gmail.com>
To: Felipe Sere <dodofxp@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ata_piix problem with MacBook Pro and 2.6.26
Date: Tue, 29 Jul 2008 11:14:39 +0900 [thread overview]
Message-ID: <488E7D0F.4040204@gmail.com> (raw)
In-Reply-To: <da38d7b90807281154p6cd45e0pf0acd83cd583d06a@mail.gmail.com>
Felipe Sere wrote:
> 00:1f.2 IDE interface [0101]: Intel Corporation 82801HBM/HEM
> ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
The apple workaround is not kicking in probably because your machine has
different subsystem id which doesn't show in lspci -nn output. Can you
please post "lspci -nnv" result?
--
tejun
next prev parent reply other threads:[~2008-07-29 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <da38d7b90807240227q165cb5elad937973a58bf88f@mail.gmail.com>
[not found] ` <488D757B.6000002@gmail.com>
[not found] ` <da38d7b90807280101y44ef5624of99f7038967405a6@mail.gmail.com>
2008-07-28 18:54 ` ata_piix problem with MacBook Pro and 2.6.26 Felipe Sere
2008-07-29 2:14 ` Tejun Heo [this message]
2008-07-29 5:55 ` Felipe Sere
2008-07-29 6:06 ` [PATCH #upstream-fixes] ata_piix: subsys 106b:00a3 is apple ich8m too Tejun Heo
2008-07-31 5:50 ` Jeff Garzik
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=488E7D0F.4040204@gmail.com \
--to=htejun@gmail.com \
--cc=dodofxp@gmail.com \
--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).