On Wed, 31.03.10 18:58, Lennart Poettering (lennart@xxxxxxxxxxxxxx) wrote: > > As I said above, I don't think it's ata_id that is the problem - I think > > it's udisks-probe-ata-smart, via libatasmart, that is responsible for > > submitting the SET FEATURES command: Actually, libatasmart does not even call SET_FEATURES. We only issue four types of commands: IDENTIFY_DEVICE IDENTIFY_PACKET_DEVICE SMART CHECK_POWER_MODE the sources don't know about any other commands: http://git.0pointer.de/?p=libatasmart.git;a=blob;f=atasmart.c;h=a4b60c0eedf8e4f1ebafd932b7070c030459ef16;hb=HEAD#l128 So the SET_FEATURES must come from somewhere else... Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 -- 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
