Alan Cox wrote: >> * after successfully executing _GTF taskfiles, IDENTIFY page is >> reloaded > > Interesting question we should sort out: What is our identify page as > supplied to the user meant to be ? > > The old IDE one started off as the "identify data at boot" (which is > useful) and mutated through a million "kind of boot but mangled" and "not > boot" versions of the identify data, all of which are useless to > userspace. > > Having the "boot" data (for some definition of boot) is important in > order to know things like the BIOS view of the disk geometry and HPA (eg > for partitioning), having the current data is useless as its already > available via SG_IO. AFAIK, IDENTIFY using SG_IO is the way to obtain ID data. HDIO_GET_IDENTITY is only added for backward compatibility and as a sideway to obtain ATAPI IDENTIFY page while IDENTIFY_PACKET_DEVICE via SG_IO is broken. libata tries pretty hard to keep the cached IDENTIFY page up-to-date and I'm pretty sure it stays in sync with the drive most of the time. I think HDIO_GET_IDENTITY's meaning is something like "give me IDENTIFY page of the device as seen by the driver" and doesn't really matter as long as it can be used to get general idea about the device. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
