From: Jeff Garzik <jgarzik@pobox.com>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pata_atiixp: override cable detection on MSI E350DM-E33
Date: Fri, 17 Aug 2012 13:27:53 -0400 [thread overview]
Message-ID: <502E7F19.50306@pobox.com> (raw)
In-Reply-To: <1345191075-30425-1-git-send-email-arnd@arndnet.de>
On 08/17/2012 04:11 AM, Arnd Hannemann wrote:
> The mainboard MSI E350DM-E33 is advertised with 6 SATA ports.
> As it turns out, two of them seem to be driven by on-board
> SATA<->PATA converters. If a disk drive is connected to one
> of them kernel uses UDMA/33 mode due to cable detection:
>
> [ 34.550823] scsi4 : pata_atiixp
> [ 34.555517] scsi5 : pata_atiixp
> [ 34.555942] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf100 irq 14
> [ 34.555948] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf108 irq 15
> ...
> [ 35.040799] ata5.00: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133
> [ 35.040806] ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> [ 35.040817] ata5.00: limited to UDMA/33 due to 40-wire cable
> [ 35.049166] ata5.00: configured for UDMA/33
> [ 35.049402] scsi 4:0:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5
>
> This patch forces "short cable" mode on this board, as it seems clear that
> the on-board SATA<->PATA "cable" is short.
> With this patch the disk is configured for UDMA/100:
>
> [ 5.976756] ata5.00: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133
> [ 5.996434] ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> [ 6.024787] ata5.00: configured for UDMA/100
>
> Testing revealed no transfer issues.
>
> Signed-off-by: Arnd Hannemann <arnd@arndnet.de>
applied
prev parent reply other threads:[~2012-08-17 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 8:11 [PATCH] pata_atiixp: override cable detection on MSI E350DM-E33 Arnd Hannemann
2012-08-17 17:27 ` Jeff Garzik [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=502E7F19.50306@pobox.com \
--to=jgarzik@pobox.com \
--cc=arnd@arndnet.de \
--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;
as well as URLs for NNTP newsgroup(s).