On Wed, 2010-04-21 at 10:13 -0400, Mark Lord wrote: > On 21/04/10 10:04 AM, James Bottomley wrote: > .. > > But this isn't a userspace problem. By the time we present the device > > to userspace, we already know what it is ... so you can go by device > > type and only use ATA_12 for disk devices. > .. > > And most tools / programs can indeed do that. > > But hdparm's mission is to ignore what the kernel thinks, > and speak directly to the drive whenever possible. This is a bit dangerous where USB is concerned. We certainly don't have all the heuristics necessary in the kernel, but whenever anything goes wrong, we do tend to hear about it pretty quickly. > Because hdparm is an important part of how we verify > that the kernel is correct (or not). So I very much > prefer that it continue to work out the details as much > as it can without asking a possibly buggy kernel for help. > > :) > > That said.. what would you recommend as a way for a userspace > program to figure out whether to use ATA_12 or ATA_16 to talk > to a given arbitrary device name ? To be honest, no. For USB, All USB is SCSI or RBC command based. You don't have any idea whether it's a real SCSI device or an ATA device behind a SAT ... the only reason you assume it's ATA is because USB gadget builders tend to be cheapskates. > I guess the info is in sysfs somewhere. Only for direct interconnects. For USB most bets are off. James -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
