Custom Query (1347 matches)
Results (16 - 18 of 1347)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1337 | fixed | Add OWC Mercury Elite Pro Quad USB ids (0x1e91:0xa4a7) | ||
Description |
Index: drivedb.h =================================================================== --- drivedb.h (revision 5059) +++ drivedb.h (working copy) @@ -5788,6 +5788,13 @@ "", "-d sat" }, + // 0x1e91 (?) + { "USB: OWC Mercury Elite Pro Quad; ", + "0x1e91:0xa4a7", + "", // 0x0100 + "", + "-d sat" + }, // Innostor { "USB: ; Innostor IS611", // USB3->SATA+PATA "0x1f75:0x0611", // SMART access via PATA does not work |
|||
#189 | fixed | Whitelist non-MA07 firmware for Dell Seagate Barracuda ES.2 drives | ||
Description |
We recently received a support call because a customer noted that one of the drives installed in a machine was reporting potential problems with a version of firmware. After doing some digging on the Dell site, it appears that only the MA07 firmware is affected. The attached patch whitelists all non-MA07 firmware so the message doesn't appear with unaffected drives. |
|||
#916 | duplicate | Adding --json command line option | ||
Description |
I would like to prepare a patch to implement '--json' cmd option, as mentioned in ticket #766. I'm new to this project and would appreciate your help.
Do you have insights about how the data structure should look like, considering hierarchy, data order, and which containers to use? When looking at the first chunks of output for SATA I was wondering how to represent the data, so it would be easy to traverse and print. The general idea is to have a container to represent each section, for example: struct smart_data {
}; Is there a certain format you prefer it to be represented?
Many thanks! |