linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Paul Blazejowski <paulb@blazebox.homeip.net>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: Linux v2.6.16-rc6
Date: Thu, 16 Mar 2006 16:58:04 -0500	[thread overview]
Message-ID: <4419DF6C.7000103@tmr.com> (raw)
In-Reply-To: <1142205571.10354.1.camel@blaze.homeip.net>

Paul Blazejowski wrote:
> On Sun, 2006-03-12 at 17:54 -0500, Jeff Garzik wrote:
>> Paul Blazejowski wrote:
>>> sata_nv 0000:00:07.0: version 0.8
>> sata_nv
>>
>>> ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC400 irq 21
>>> ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC408 irq 21
>> host max udma6
>>
>>> ata3: dev 0 ATA-6, max UDMA/100, 390721968 sectors: LBA48
>>> ata3: dev 0 configured for UDMA/100
>> dev max udma5, configured for max speed
>>
>>> ata4: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
>>> ata4: dev 0 configured for UDMA/133
>> dev max udma6, configured for max speed
>>
>> Everything is correct.
>>
>> 	Jeff
>>
>>
>>
> 
> Jeff, thank you for confirming that everything looks correct. Next time
> i will be buying matching drives at the same time :-).

Since they are the same drive modulo firmware, you might contemplate 
upgrading all to the same level. NOTE: that's just a comment, not a 
recommendation.
-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

      reply	other threads:[~2006-03-16 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-12 18:45 Linux v2.6.16-rc6 Paul Blazejowski
2006-03-12 21:46 ` Lee Revell
2006-03-12 22:21   ` Paul Blazejowski
2006-03-12 22:57     ` Jeff Garzik
2006-03-13 20:17     ` Jan Engelhardt
2006-03-12 22:54 ` Jeff Garzik
2006-03-12 23:19   ` Paul Blazejowski
2006-03-16 21:58     ` Bill Davidsen [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=4419DF6C.7000103@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulb@blazebox.homeip.net \
    /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).