From: Tejun Heo <htejun@gmail.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: AHCI driver preferring nr_ports over port map
Date: Sat, 02 Feb 2008 17:16:59 +0900 [thread overview]
Message-ID: <47A426FB.4090105@gmail.com> (raw)
In-Reply-To: <47A344DF.76E4.0078.0@novell.com>
Jan Beulich wrote:
> Jeff,
>
> while I realize that Intel's documentation may not be consistent with
> anything more generic (which I don't know where to look for), this
> current behavior seems to contradict what Intel documents for ESB2:
>
> "23.3.1.4 PI – Ports Implemented Register (D31:F2)
> Address Offset: ABAR + 0Ch–0Fh Attribute: R/WO, RO
> Default Value: 00000000h Size: 32 bits
>
> This register indicates which ports are exposed to the Intel®
> 631xESB/632xESB I/O Controller Hub. It is loaded by platform BIOS. It
> indicates which ports that the device supports are available for
> software to use. For ports that are not available, software must not
> read or write to registers within that port."
nr_ports is preferred over port_map when they disagree which shouldn't
happen in the first place. On some earlier ahcis, PI was cleared to
zero and lower nr_port number of ports should be used. The reason why
nr_ports is preferred over PI comes from similar place. Hardware/BIOSen
are more likely to get PI wrong than nr_ports, so...
Do you have any real case where the above behavior causes problem?
--
tejun
next prev parent reply other threads:[~2008-02-02 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 15:12 AHCI driver preferring nr_ports over port map Jan Beulich
2008-02-02 8:16 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-04 13:10 Jan Beulich
2008-02-04 13:16 ` Tejun Heo
2008-02-04 13:24 Jan Beulich
2008-02-04 13:38 ` Tejun Heo
2008-02-05 7:47 ` Jan Beulich
2008-02-05 12:21 ` Tejun Heo
2008-02-05 12:40 ` Jan Beulich
2008-02-05 13:17 ` Tejun Heo
2008-02-05 14:51 ` Jan Beulich
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=47A426FB.4090105@gmail.com \
--to=htejun@gmail.com \
--cc=jbeulich@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.