Subject: Re: ATA133 devices only run at ATA100?, was: Re: Install success with CL6000E
To: Jonathan A. Kollasch <jakllsch@kollasch.net>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: port-i386
Date: 12/05/2005 22:39:22
On Sat, Dec 03, 2005 at 01:19:02PM -0600, Jonathan A. Kollasch wrote:
> On Sat, Dec 03, 2005 at 06:17:27PM +0000, Alan Post wrote:
> > attached.  I'm not sure why it's using Ultra/100 mode on the drive
> > rather than Ultra/133.  Perhaps I misread the docs of either the board
> > or the HD (a Samsung SP2514N).
> 
> I've had this same problem with an Adaptec ASH-1233 cmdide(4) and both a
> Maxtor 6Y160P0 and Maxtor 6L200P0; both ends claim 133, yet only go 100.
> 
> cmdide0 at pci0 dev 15 function 0
> cmdide0: Silicon Image 0680 (rev. 0x02)
> cmdide0: bus-master DMA support present
> cmdide0: primary channel configured to native-PCI mode
> cmdide0: using irq 10 for native-PCI interrupt
> atabus1 at cmdide0 channel 0
> cmdide0: secondary channel configured to native-PCI mode
> atabus2 at cmdide0 channel 1
> 
> wd0 at atabus1 drive 0: <Maxtor 6Y160P0>
> wd0: drive supports 16-sector PIO transfers, LBA48 addressing
> wd0: 152 GB, 317632 cyl, 16 head, 63 sec, 512 bytes/sect x 320173056 sectors
> wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
> wd0(cmdide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)

Specifically for the 680, there is code in the driver to limit the bus
to Ultra/100 in some case. I don't know why (I didn't write this part of
code) but it could be related to a local clock speed or multiplier.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--