From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: alan@lxorguk.ukuu.org.uk, linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_cmd64x: Correct the speed ranges
Date: Fri, 27 Jul 2007 01:16:19 +0400 [thread overview]
Message-ID: <46A90F23.8010907@ru.mvista.com> (raw)
In-Reply-To: <200707262101.l6QL1Iqk029149@harpo.it.uu.se>
Mikael Pettersson wrote:
> This fix inspired me to finally try to convert my Sun Ultra5
> (sparc64) with a CMD646 [1095:0646 rev 03] to libata.
> With pata_cmd64x the machine has so far survived a usual
> boot/mrproper/reconfig/make/install/reboot kernel update
> cycle without any issues, and performance seems to be the
> same as with the old IDE driver.
> /Mikael
>
> scsi0 : pata_cmd64x
> scsi1 : pata_cmd64x
> ata1: PATA max MWDMA2 cmd 0x000001fe02c00000 ctl 0x000001fe02c0000a bmdma 0x000001fe02c00020 irq 14
> ata2: PATA max MWDMA2 cmd 0x000001fe02c00010 ctl 0x000001fe02c0001a bmdma 0x000001fe02c00028 irq 14
> ata1.00: ATA-4: ST320420A, 3.21, max UDMA/66
> ata1.00: 39851760 sectors, multi 0: LBA
> pata_cmd64x: active 3 recovery 1 setup 1.
> ata1.00: configured for MWDMA2
> ata2.00: ATAPI: CRD-8483B, 1.00, max UDMA/33
> pata_cmd64x: active 3 recovery 1 setup 1.
> ata2.00: configured for MWDMA2
[...]
Note that the olde driver has MWDMA fixed, and the new one has it still
borken, yet MWDMA2 is the mode you're using.
MBR, Sergei
next prev parent reply other threads:[~2007-07-26 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 21:01 [PATCH] pata_cmd64x: Correct the speed ranges Mikael Pettersson
2007-07-26 21:16 ` Sergei Shtylyov [this message]
2007-07-26 22:06 ` Jeff Garzik
2007-07-27 12:29 ` Sergei Shtylyov
2007-07-27 12:40 ` Jeff Garzik
2007-07-27 12:44 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2007-07-26 17:43 Alan Cox
2007-07-26 17:52 ` Sergei Shtylyov
2007-08-01 14:01 ` Jeff Garzik
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=46A90F23.8010907@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).