Date: Thu, 24 Jan 2002 20:54:28 +0100 (CET) From: Søren Schmidt <sos@freebsd.dk> To: Dmitry Morozovsky <marck@rinet.ru> Cc: scotty@klement.dstorm.net, Dmitry Valdov <dv@dv.ru>, Bill Moran <wmoran@potentialtech.com>, stable@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA driver feature request Message-ID: <200201241954.g0OJsTq94418@freebsd.dk> In-Reply-To: <20020124224757.O60455-100000@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Dmitry Morozovsky wrote: > > ad0: 19458MB <ST320420A> [39535/16/63] at ata0-master UDMA66 > > ad1: 76319MB <WDC WD800BB-40BSA0> [155061/16/63] at ata0-slave UDMA66 > > ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable > > ad2: 76319MB <WDC WD800BB-40BSA0> [155061/16/63] at ata1-master UDMA33 > > ad3: 2503MB <FUJITSU MPA3026ATU> [5086/16/63] at ata1-slave UDMA33 > > > > They are the exact same drives using the exact same cable. My controller > > only supports UDMA66, not 100... but the reason that the 2nd controller > > seems to print out "non-ATA66 compiant cable" appears to simply be that > > ad3 is only ATA33 capable. > > > > Just thought I'd pipe up, since the subject came up :) > > Hmm, can ever ATA controller clock out both master device at 66MHz and > slave at 33MHz? I suppose the effect is *not* unexpected. Yes, the way I've done the mode programming it is possible to have the two device run at different speeds (our competition cant do that). > However, the warning message would be slightly reworded like "non-ATA66 > compliant cable or second device" Good point, I'll get something done about this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201241954.g0OJsTq94418>