Alan Cox wrote: >> What the function answers is not actually cable type but "according to >> the current configuration, using this cable type won't violate BIOS >> configuration" kind of answer. How the caller is to use that is the >> caller's responsibility. > > How does the caller make use of it ? The only way I can think of to use > it is that if either drive says UDMA > 33 then we know its 80 wire. > Otherwise we can't really prove anything. And if neither drive says > 80 > wire we have to go on what other info we have, which for NVidia appears > to be "guess 40". > > I'm not sure therefore we gain anything ? I was trying to discern between the following three. 1. UDMA mode isn't configured at all. Either BIOS forgot it, isn't there or some other entity cleared it before the driver is loaded. I can't tell you anything. If you have another source for cable detection, use it instead. 2. UDMA mode is configured but equal to or under UDMA33. Dunno whether it's cable or device limit but anyways you better limit it to UDMA33 too. 3. UDMA mode is configured and above UDMA33. Do whatever you wanna do. Return values are ATA_CBL_PATA_UNK, ATA_CBL_PATA_UDMA33 and ATA_CBL_PATA_UDMA66 respectively. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
