From: Albert Lee <albertcc@tw.ibm.com>
To: Jonathan Benson <airbatica@verizon.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata machine check on Alpha
Date: Fri, 07 Apr 2006 14:18:13 +0800 [thread overview]
Message-ID: <44360425.3080402@tw.ibm.com> (raw)
In-Reply-To: <CF6023AC-C62F-4BA8-A1DA-5CF6100B9608@verizon.net>
Jonathan Benson wrote:
>
>>Could you please give a try to the attached patch and post the content
> of word 62?
>>If word 62 + SiI 3611 looks good, we can turn on the DMADIR
> automatically. Thanks!
>
> Per Albert's request, I've tested his patch to check the status of word
> 62 with the SiI 3611 bridge chip. I used kernel version 2.6.17- rc1, as
> 2.6.16 reported fuzz when I applied the patch. 2.6.17-rc1 reported an
> offset, but applied without any errors. I've tested with the
> ATAPI_ENABLE_DMADIR workaround enabled, and disabled. Debugging is
> disabled. Looks like word 62 returns 0 as its value, dmesg with the
> relevant parts attached below.
>
> If you need any more information, let me know and I'll be happy to
> provide it.
>
> Jonathan Benson
>
> (snip)
>
> ata2: dev 0 ATA-7, max UDMA/133, 240121728 sectors: LBA
> ata2(0): applying bridge limits
> ata2: dev 0 configured for UDMA/100
> scsi1 : sata_sil
> ata3: SATA link up 1.5 Gbps (SStatus 113)
> ata3: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003
> 88:007f
> ata3: dev 0 ATA-7, max UDMA/133, 240121728 sectors: LBA
> ata3(0): applying bridge limits
> ata3: dev 0 configured for UDMA/100
> scsi2 : sata_sil
> ata4: SATA link up 1.5 Gbps (SStatus 113)
> ata4: dev 0 cfg 49:0b00 82:0210 83:1000 84:0000 85:0000 86:0000 87:0000
> 88:0007
> ata4: dev 0 word 62 [0]
> ata4: dev 0 ATAPI, max UDMA/33
> ata4: dev 0 word 62 [0]
> ata4: dev 0 configured for UDMA/33
Word 62 is also zero on my JMicron 20330 bridge.
Since JMicron doesn't need the DMA DIR bit, it looks consistent
(maybe by coincidence) with the ATA-7 spec.
For SiI 3611, it was made before the ATA-7 spec is finalized. So, it is
reasonable that SiI 3611 doesn't implement word 62 and we have to
manually enable the DMA DIR support as work around unless SiImage provides
other solution to identify the SiI 3611 bridge.
Thanks for the test result. :)
--
albert
next prev parent reply other threads:[~2006-04-07 6:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 2:01 libata machine check on Alpha Jonathan Benson
2006-04-07 6:18 ` Albert Lee [this message]
2006-04-07 6:39 ` [PATCH/RFC] libata: turn on the ATAPI DMA DIR support per word 62 Albert Lee
2006-04-07 6:47 ` Jeff Garzik
2006-04-07 10:21 ` Albert Lee
2006-04-07 10:46 ` [PATCH/RFC] libata: turn on the ATAPI DMADIR support per word 62 (revised) Albert Lee
2006-04-07 17:54 ` Jeff Garzik
2006-04-18 4:34 ` Albert Lee
2006-04-20 22:51 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-04-05 0:14 libata machine check on Alpha Jonathan Benson
2006-04-04 17:12 Carlos Pardo
2006-04-06 2:04 ` Albert Lee
2006-04-06 2:17 ` Jeff Garzik
2006-04-06 2:31 ` Tejun Heo
2006-04-06 6:38 ` Albert Lee
2006-04-06 6:44 ` Doug Maxey
2006-04-06 7:14 ` Albert Lee
2006-04-03 18:56 Jonathan Blake Benson
2006-04-04 1:43 ` Tejun Heo
2006-04-04 2:12 ` Albert Lee
2006-04-04 2:15 ` Tejun Heo
2006-04-04 2:49 ` Albert Lee
2006-04-04 3:05 ` Tejun Heo
2006-04-04 8:24 ` Jeff Garzik
2006-04-05 15:48 ` Jonathan Blake Benson
2006-04-06 9:17 ` Albert Lee
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=44360425.3080402@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=airbatica@verizon.net \
--cc=albertl@mail.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).