linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "0602@eq.cz" <0602@eq.cz>
To: Tejun <htejun@gmail.com>
Cc: Jean-Fran?ois Stenuit <jfs@keytradebank.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: regarding ata_piix initialization trouble
Date: Thu, 23 Feb 2006 11:41:17 +0100	[thread overview]
Message-ID: <43FD914D.1020300@eq.cz> (raw)
In-Reply-To: <43FD6794.8020902@gmail.com>

Tejun wrote:
> Hello, Jean & 0602.
> 
> I was digging ICH docs to reimplement ata_piix initialization and found 
> out that 6300ESB lists high bits (the present bits) of PCS register as 
> reserved. But they indiciate that the bits might change anytime just as 
> in other docs. I think something went wrong with those bits in that 
> particular chipset and Intel decided to ignore the bits.
> 
> I'm wondering whether your problems are related to this. Can you guys 
> please run 'lspci -n' on your machines which had the piix initialization 
> trouble and report the result here?
> 
> Thanks a lot.
> 

Hi,

here is the result:
00:00.0 Class 0600: 8086:3592 (rev 0c)
00:00.1 Class ff00: 8086:3593 (rev 0c)
00:02.0 Class 0604: 8086:3595 (rev 0c)
00:03.0 Class 0604: 8086:3596 (rev 0c)
00:1c.0 Class 0604: 8086:25ae (rev 02)
00:1e.0 Class 0604: 8086:244e (rev 0a)
00:1f.0 Class 0601: 8086:25a1 (rev 02)
00:1f.2 Class 0101: 8086:25a3 (rev 02)
00:1f.3 Class 0c05: 8086:25a4 (rev 02)
02:00.0 Class 0200: 11ab:4361 (rev 17)
03:07.0 Class 0100: 11ab:6081 (rev 07)
04:02.0 Class 0300: 1002:4752 (rev 27)
04:03.0 Class 0200: 8086:1076 (rev 05)

Regards,

r.

      parent reply	other threads:[~2006-02-23 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  7:43 regarding ata_piix initialization trouble Tejun
2006-02-23  9:57 ` Jeff Garzik
2006-02-23 11:52   ` Tejun Heo
2006-02-23 10:41 ` 0602 [this message]

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=43FD914D.1020300@eq.cz \
    --to=0602@eq.cz \
    --cc=htejun@gmail.com \
    --cc=jfs@keytradebank.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).