MVD Services: Difference between revisions
| Line 589: | Line 589: | ||
|- | |- | ||
| 0x00010005 | | 0x00010005 | ||
| Unknown. A certain MVD state field must not be set to 0x8170 in order to use this. | | Unknown. A certain MVD state field must not be set to 0x8170 in order to use this. Some sort of 2-byte format it seems. | ||
|- | |- | ||
| 0x00010006 | | 0x00010006 | ||
| Unknown, see 0x00010005 for the usage requirement. | | Unknown, see 0x00010005 for the usage requirement. Some sort of 2-byte format it seems. | ||
|- | |- | ||
| 0x00010007 | | 0x00010007 | ||
| Unknown, see 0x00010005 for the usage requirement. | | Unknown, see 0x00010005 for the usage requirement. Some sort of 2-byte format it seems. | ||
|- | |- | ||
| 0x00010008 | | 0x00010008 | ||
| A certain MVD-module state field must not be set to 0x8170 in order to use this. Whether this can actually be used is determined by another MVD-module state field. | | A certain MVD-module state field must not be set to 0x8170 in order to use this. Whether this can actually be used is determined by another MVD-module state field. Some non-2-byte format it seems. | ||
|- | |- | ||
| 0x00010009 | | 0x00010009 | ||
| Unknown, see 0x00010008 for the usage requirements. | | Unknown, see 0x00010008 for the usage requirements. Some non-2-byte format it seems. | ||
|- | |- | ||
| 0x0001000A | | 0x0001000A | ||
| Unknown, see 0x00010008 for the usage requirements. | | Unknown, see 0x00010008 for the usage requirements. Some non-2-byte format it seems. | ||
|- | |- | ||
| 0x0001000B | | 0x0001000B | ||
| Unknown, see 0x00010008 for the usage requirements. | | Unknown, see 0x00010008 for the usage requirements. Some non-2-byte format it seems. | ||
|- | |- | ||
| 0x00020001 | | 0x00020001 | ||