On Fri, Aug 15, 2008 at 01:06:21PM +0100, Philip Paeps wrote: > On 2008-08-15 13:47:04 (+0200), Bernd Walter <[EMAIL PROTECTED]> wrote: > > On Fri, Aug 15, 2008 at 10:55:11AM +0000, Philip Paeps wrote: > > > This can be used to disable the 80pin cable check on systems which forget > > > to set the bit -- such as certain laptops and Soekris boards. > > > > Are those bits per device? > > That is what it looks like, yes. The cable is detected by checking whether a > certain pin is grounded. From how I read the standard, the pin should be > grounded in the connector, so I can imagine a very strange cable which has 80 > pins up to the first device and 40 to the second.
I thought the cable type is read by the controller. But if it is read by the device then it sounds possible. Hadn't thought about a broken cable yet. Well - in fact I never cared much about this problem at all. > > ad4: DMA limited to UDMA33, device found non-ATA66 cable > > ad4: 117246MB <Maxtor 6Y120L0 YAR41BW0> at ata2-master UDMA33 > > ad5: 156334MB <Maxtor 6Y160P0 YAR41BW0> at ata2-slave UDMA133 > > Which is strange, since both drives are on the same cable... > > I agree that this is very strange. I haven't read the ATA standard in any > kind of detail though... > > Does this commit fix it though? A update to a more recent current failed for other reasons. But I can test your change alone. -- B.Walter <[EMAIL PROTECTED]> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"