From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, jeff@garzik.org
Subject: Re: [patch] libata: use correct map_db values for ICH8
Date: Fri, 20 Oct 2006 09:26:22 -0700 [thread overview]
Message-ID: <20061020092622.f564da61.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <453891AD.70704@gmail.com>
On Fri, 20 Oct 2006 18:06:53 +0900
Tejun Heo <htejun@gmail.com> wrote:
> Hello, Kristen.
>
> Kristen Carlson Accardi wrote:
> > Use valid values for ICH8 map_db. With the old values, when the
> > controller was in Native mode, and SCC was 1 (drives configured for
> > IDE), any drive plugged into a slave port was not recognized. For
> > Combined Mode (and SCC is still 1), 2 is a value value for MAP.map_value,
> > and needs to be recognized.
> >
> > Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
>
> Do you guys have doc update related to this? The doc and spec update
> still indicate that MAP value is reserved to 00b. Anyways, if you say
> that's right...
>
> Acked-by: Tejun Heo <htejun@gmail.com>
>
> --
> tejun
As far as I know, this has always been documented.
The datasheet is located here:
http://developer.intel.com/design/chipsets/datashts/313056.htm
Indicates that 10b is valid for combined mode. Make sure you are looking
at device 31 function 2 - for 31 function 5 it is hardwired to 00b, but
for function 2, it can be 00 or 10. This was not very clear, so it's
easy to understand how this could have been misunderstood. See
section 11.1.33 in the notes, or do a search on "combined mode" through
the doc, and you'll see that MV can be 10b when SCC is 01 on device 31
function 2.
next prev parent reply other threads:[~2006-10-20 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 20:27 Kristen Carlson Accardi
2006-10-20 9:06 ` Tejun Heo
2006-10-20 16:26 ` Kristen Carlson Accardi [this message]
2006-10-20 16:35 ` 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=20061020092622.f564da61.kristen.c.accardi@intel.com \
--to=kristen.c.accardi@intel.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®