| … | |
… | |
| 481 | the leading GUID, which it can always decode). In such cases, it will |
481 | the leading GUID, which it can always decode). In such cases, it will |
| 482 | convert the device into this type with a hexdump of the element data. |
482 | convert the device into this type with a hexdump of the element data. |
| 483 | |
483 | |
| 484 | =item C<null> |
484 | =item C<null> |
| 485 | |
485 | |
| 486 | This is another special type - sometimes, a device all zero-filled, which |
486 | This is another special type - sometimes, a device is all zero-filled, |
| 487 | is not valid. This can mark the absence of a device or something PBCDEDIT |
487 | which is not valid. This can mark the absence of a device or something |
| 488 | does not understand, so it decodes it into this special "all zero" type |
488 | PBCDEDIT does not understand, so it decodes it into this special "all |
| 489 | called C<null>. |
489 | zero" type called C<null>. |
| 490 | |
490 | |
| 491 | It's most commonly found in devices that can use an optional parent |
491 | It's most commonly found in devices that can use an optional parent |
| 492 | device, when no parent device is used. |
492 | device, when no parent device is used. |
| 493 | |
493 | |
| 494 | =item C<boot> |
494 | =item C<boot> |
