From: "zhao, forrest" <forrest.zhao@intel.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Albert Lee <albertcc@tw.ibm.com>, Jens Axboe <axboe@suse.de>,
Edward Falk <efalk@google.com>,
Carlos Pardo <Carlos.Pardo@siliconimage.com>,
Raymond Liu <Raymond.Liu@siliconimage.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [ANNOUNCE] libata EH/NCQ/hotplug/PM git tree
Date: Wed, 10 May 2006 13:36:36 +0800 [thread overview]
Message-ID: <1147239396.7273.13.camel@forrest26.sh.intel.com> (raw)
In-Reply-To: <44617782.7000302@gmail.com>
On Wed, 2006-05-10 at 14:17 +0900, Tejun Heo wrote:
> Does your ICH7 report 1 for the SMP bit (bit 17 of the CAP register)?
> Cool. How come mine doesn't? :/ Can you tell me the exact name of the
> product?
Yes, PMP bit is set. let me post the dmesg output here:
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports ? Gbps 0x3f impl SATA
mode
ahci 0000:00:1f.2: flags: 64bit stag led pmp
ata1: SATA max UDMA/133 cmd 0xFFFFC20000002100 ctl 0x0 bmdma 0x0 irq 201
ata2: SATA max UDMA/133 cmd 0xFFFFC20000002180 ctl 0x0 bmdma 0x0 irq 201
ata3: SATA max UDMA/133 cmd 0xFFFFC20000002200 ctl 0x0 bmdma 0x0 irq 201
ata4: SATA max UDMA/133 cmd 0xFFFFC20000002280 ctl 0x0 bmdma 0x0 irq 201
ata5: SATA max UDMA/133 cmd 0xFFFFC20000002300 ctl 0x0 bmdma 0x0 irq 201
ata6: SATA max UDMA/133 cmd 0xFFFFC20000002380 ctl 0x0 bmdma 0x0 irq 201
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
88:007f
ata1: dev 0 ATA-6, max UDMA/133, 234441648 sectors: LBA48 NCQ (depth
0/32)
ata1: dev 0 configured for UDMA/133
The platform name is bensley, and the chipset is ESB2 instead of ICH7
(sorry for my mistake in last mail), the output of lspci is:
00:1f.2 Class 0106: Intel Corporation Enterprise Southbridge SATA
cc=AHCI (rev 08)
> Zhao, I think I've ironed out all the problems you've reported with the
> previous revision of hotplug. If you've got some time, can you please
> check whether those problems are really gone?
>
Yes, I'm preparing for the next round of test for your updated patches.
Thanks,
Forrest
next prev parent reply other threads:[~2006-05-10 5:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 1:44 [ANNOUNCE] libata EH/NCQ/hotplug/PM git tree Tejun Heo
2006-05-10 4:51 ` zhao, forrest
2006-05-10 5:17 ` Tejun Heo
2006-05-10 5:36 ` zhao, forrest [this message]
2006-05-10 6:29 ` Raz Ben-Jehuda(caro)
2006-05-10 6:33 ` Tejun Heo
2006-05-10 13:37 ` Shem Multinymous
2006-05-10 16:44 ` Shem Multinymous
2006-05-11 3:09 ` zhao, forrest
2006-05-11 7:07 ` Tejun Heo
2006-05-13 1:30 ` Jeff Garzik
2006-05-13 1:36 ` Tejun Heo
2006-05-13 3:37 ` Jeff Garzik
2006-05-13 3:59 ` Tejun Heo
2006-05-13 4:09 ` Jeff Garzik
2006-05-13 4:19 ` Tejun Heo
2006-05-13 10:02 ` Stefan Smietanowski
2006-05-13 10:20 ` 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=1147239396.7273.13.camel@forrest26.sh.intel.com \
--to=forrest.zhao@intel.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=Raymond.Liu@siliconimage.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=axboe@suse.de \
--cc=efalk@google.com \
--cc=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).