From: Tejun <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata_piix: fix MAP VALUE interpretation for for ICH6/7
Date: Fri, 27 Jan 2006 16:35:21 +0900 [thread overview]
Message-ID: <43D9CD39.7000209@gmail.com> (raw)
In-Reply-To: <43D98C23.4040004@pobox.com>
Jeff Garzik wrote:
> Tejun Heo wrote:
>
>> Unlike their older siblings, ICH6 and 7 use different scheme for MAP
>> VALUE. This patch makes ata_piix interpret MV properly on ICH6/7.
>>
>> Pre-ICH6/7
>>
>> The value of these bits indicate the address range the SATA port
>> responds to, and whether or not the SATA and IDE functions are
>> combined.
>>
>> 000 = Non-combined. P0 is primary master. P1 is secondary master.
>> 001 = Non-combined. P0 is secondary master. P1 is primary master.
>> 100 = Combined. P0 is primary master. P1 is primary slave. P-ATA is
>> 2:0 Map Value secondary.
>> 101 = Combined. P0 is primary slave. P1 is primary master. P-ATA is
>> secondary.
>> 110 = Combined. P-ATA is primary. P0 is secondary master. P1 is
>> secondary slave.
>> 111 = Combined. P-ATA is primary. P0 is secondary slave. P1 is
>> secondary master.
>>
>> ICH6/7
>>
>> Map Value - R/W. Map Value (MV): The value in the bits below indicate
>> the address range the SATA ports responds to, and whether or not the
>> PATA and SATA functions are combined. When in combined mode, the AHCI
>> memory space is not available and AHCI may not be used.
>>
>> 00 = Non-combined. P0 is primary master, P2 is the primary slave. P1
>> is secondary master, P3 is the 1:0 secondary slave (desktop
>> only). P0 is primary master, P2 is the primary slave (mobile
>> only).
>> 01 = Combined. IDE is primary. P1 is secondary master, P3 is the
>> secondary slave. (desktop only)
>> 10 = Combined. P0 is primary master. P2 is primary slave. IDE is
>> secondary
>> 11 = Reserved
>>
>> Signed-off-by: Tejun Heo <htejun@gmail.com>
>
>
> applied to upstream-2.6.17. patch looks OK, but only testing on
> ICH5+6+7 will really convince me. Documentation has often been confused
> before, and the only data I've received from you is "it works for me."
> So, proceeding with caution :)
>
I'll follow up with test results next week.
--
tejun
next prev parent reply other threads:[~2006-01-27 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 8:17 [PATCH] ata_piix: fix MAP VALUE interpretation for for ICH6/7 Tejun Heo
2005-12-19 5:38 ` Jeff Garzik
2005-12-19 5:42 ` Tejun Heo
2006-01-23 12:25 ` Tejun Heo
2006-01-27 2:57 ` Jeff Garzik
2006-01-27 7:35 ` Tejun [this message]
2006-02-01 5:13 ` Tejun Heo
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=43D9CD39.7000209@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.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).