From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"Robin H. Johnson" <robbat2@gentoo.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/2 #upstream] ahci: honor PORTS_IMPL on ICH8s
Date: Sat, 11 Nov 2006 11:37:37 +0900 [thread overview]
Message-ID: <45553771.4030201@gmail.com> (raw)
In-Reply-To: <20061109060840.GZ13677@htj.dyndns.org>
Tejun Heo wrote:
> Some ICH8s use non-linear port mapping. ahci driver didn't use to
> honor PORTS_IMPL and this made ports after hole nonfunctional. This
> patch makes ahci mark those ports as dummy and properly initialize all
> the implemented ports after the dummies.
>
> As it's unknown whether other AHCIs implement PORTS_IMPL register
> properly, new board id board_ahci_pi is added and selectively applied
> to ICH8s. All other AHCIs continue to use linear mapping regardless
> of PORTS_IMPL value.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Robin H. Johnson <robbat2@gentoo.org>
> ---
>
> Two changes.
>
> * AHCI_FLAG_HONOR_PI was changed to 1<<25. 1<<23 is not for LLD
> specific flags.
>
> * VPRINTK() fixed as Robin H. Johnson pointed out.
Jeff, I think this should go into #upstream-fixes too. It's not as dumb
as adding a PCI ID but it's adding support for a highly popular hardware
and "wait for 2.6.20 for ICH8 support" just sucks.
Thanks.
--
tejun
next prev parent reply other threads:[~2006-11-11 2:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 3:17 [PATCH 1/2 #upstream] ahci: preserve PORTS_IMPL over host resets Tejun Heo
2006-11-02 3:20 ` [PATCH 2/2 #upstream] ahci: honor PORTS_IMPL on ICH8s Tejun Heo
2006-11-06 1:05 ` Robin H. Johnson
2006-11-07 9:54 ` Tejun Heo
2006-11-09 6:08 ` Tejun Heo
2006-11-11 2:37 ` Tejun Heo [this message]
2006-11-14 18:45 ` Jeff Garzik
2006-11-07 9:46 ` [PATCH 1/2 #upstream] ahci: preserve PORTS_IMPL over host resets 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=45553771.4030201@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=robbat2@gentoo.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).