€•°DŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ1/translations/zh_CN/driver-api/pldmfw/file-format”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ1/translations/zh_TW/driver-api/pldmfw/file-format”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ1/translations/it_IT/driver-api/pldmfw/file-format”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ1/translations/ja_JP/driver-api/pldmfw/file-format”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ1/translations/ko_KR/driver-api/pldmfw/file-format”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ1/translations/sp_SP/driver-api/pldmfw/file-format”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ%SPDX-License-Identifier: GPL-2.0-only”h]”hŒ%SPDX-License-Identifier: GPL-2.0-only”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h¡hhhžhhŸŒK/var/lib/git/docbuild/linux/Documentation/driver-api/pldmfw/file-format.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ"PLDM Firmware file format overview”h]”hŒ"PLDM Firmware file format overview”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ paragraph”“”)”}”(hXA PLDM firmware package is a binary file which contains a header that describes the contents of the firmware package. This includes an initial package header, one or more firmware records, and one or more components describing the actual flash contents to program.”h]”hXA PLDM firmware package is a binary file which contains a header that describes the contents of the firmware package. This includes an initial package header, one or more firmware records, and one or more components describing the actual flash contents to program.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒ6This diagram provides an overview of the file format::”h]”hŒ5This diagram provides an overview of the file format:”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K hh¶hžhubhŒ literal_block”“”)”}”(hXN overall file layout +----------------------+ | | | Package Header | | | +----------------------+ | | | Device Records | | | +----------------------+ | | | Component Info | | | +----------------------+ | | | Package Header CRC | | | +----------------------+ | | | Component Image 1 | | | +----------------------+ | | | Component Image 2 | | | +----------------------+ | | | ... | | | +----------------------+ | | | Component Image N | | | +----------------------+”h]”hXN overall file layout +----------------------+ | | | Package Header | | | +----------------------+ | | | Device Records | | | +----------------------+ | | | Component Info | | | +----------------------+ | | | Package Header CRC | | | +----------------------+ | | | Component Image 1 | | | +----------------------+ | | | Component Image 2 | | | +----------------------+ | | | ... | | | +----------------------+ | | | Component Image N | | | +----------------------+”…””}”hhésbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hçhŸh³h Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒPackage Header”h]”hŒPackage Header”…””}”(hhúhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh÷hžhhŸh³h K2ubhÊ)”}”(hXThe package header begins with the UUID of the PLDM file format, and contains information about the version of the format that the file uses. It also includes the total header size, a release date, the size of the component bitmap, and an overall package version.”h]”hXThe package header begins with the UUID of the PLDM file format, and contains information about the version of the format that the file uses. It also includes the total header size, a release date, the size of the component bitmap, and an overall package version.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K4hh÷hžhubhÊ)”}”(hŒBThe following diagram provides an overview of the package header::”h]”hŒAThe following diagram provides an overview of the package header:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K9hh÷hžhubhè)”}”(hX€ header layout +-------------------------+ | PLDM UUID | +-------------------------+ | Format Revision | +-------------------------+ | Header Size | +-------------------------+ | Release Date | +-------------------------+ | Component Bitmap Length | +-------------------------+ | Package Version Info | +-------------------------+”h]”hX€ header layout +-------------------------+ | PLDM UUID | +-------------------------+ | Format Revision | +-------------------------+ | Header Size | +-------------------------+ | Release Date | +-------------------------+ | Component Bitmap Length | +-------------------------+ | Package Version Info | +-------------------------+”…””}”hj$sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hçhŸh³h K;hh÷hžhubeh}”(h]”Œpackage-header”ah ]”h"]”Œpackage header”ah$]”h&]”uh1h´hh¶hžhhŸh³h K2ubhµ)”}”(hhh]”(hº)”}”(hŒDevice Records”h]”hŒDevice Records”…””}”(hj=hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj:hžhhŸh³h KKubhÊ)”}”(hXUThe device firmware records area starts with a count indicating the total number of records in the file, followed by each record. A single device record describes what device matches this record. All valid PLDM firmware files must contain at least one record, but optionally may contain more than one record if they support multiple devices.”h]”hXUThe device firmware records area starts with a count indicating the total number of records in the file, followed by each record. A single device record describes what device matches this record. All valid PLDM firmware files must contain at least one record, but optionally may contain more than one record if they support multiple devices.”…””}”(hjKhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KMhj:hžhubhÊ)”}”(hX«Each record will identify the device it supports via TLVs that describe the device, such as the PCI device and vendor information. It will also indicate which set of components that are used by this device. It is possible that only subset of provided components will be used by a given record. A record may also optionally contain device-specific package data that will be used by the device firmware during the update process.”h]”hX«Each record will identify the device it supports via TLVs that describe the device, such as the PCI device and vendor information. It will also indicate which set of components that are used by this device. It is possible that only subset of provided components will be used by a given record. A record may also optionally contain device-specific package data that will be used by the device firmware during the update process.”…””}”(hjYhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KShj:hžhubhÊ)”}”(hŒFThe following diagram provides an overview of the device record area::”h]”hŒEThe following diagram provides an overview of the device record area:”…””}”(hjghžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KZhj:hžhubhè)”}”(hXŠ area layout +---------------+ | | | Record Count | | | +---------------+ | | | Record 1 | | | +---------------+ | | | Record 2 | | | +---------------+ | | | ... | | | +---------------+ | | | Record N | | | +---------------+ record layout +-----------------------+ | Record Length | +-----------------------+ | Descriptor Count | +-----------------------+ | Option Flags | +-----------------------+ | Version Settings | +-----------------------+ | Package Data Length | +-----------------------+ | Applicable Components | +-----------------------+ | Version String | +-----------------------+ | Descriptor TLVs | +-----------------------+ | Package Data | +-----------------------+”h]”hXŠ area layout +---------------+ | | | Record Count | | | +---------------+ | | | Record 1 | | | +---------------+ | | | Record 2 | | | +---------------+ | | | ... | | | +---------------+ | | | Record N | | | +---------------+ record layout +-----------------------+ | Record Length | +-----------------------+ | Descriptor Count | +-----------------------+ | Option Flags | +-----------------------+ | Version Settings | +-----------------------+ | Package Data Length | +-----------------------+ | Applicable Components | +-----------------------+ | Version String | +-----------------------+ | Descriptor TLVs | +-----------------------+ | Package Data | +-----------------------+”…””}”hjusbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hçhŸh³h K\hj:hžhubeh}”(h]”Œdevice-records”ah ]”h"]”Œdevice records”ah$]”h&]”uh1h´hh¶hžhhŸh³h KKubhµ)”}”(hhh]”(hº)”}”(hŒComponent Info”h]”hŒComponent Info”…””}”(hjŽhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj‹hžhhŸh³h K‰ubhÊ)”}”(hX3The component information area begins with a count of the number of components. Following this count is a description for each component. The component information points to the location in the file where the component data is stored, and includes version data used to identify the version of the component.”h]”hX3The component information area begins with a count of the number of components. Following this count is a description for each component. The component information points to the location in the file where the component data is stored, and includes version data used to identify the version of the component.”…””}”(hjœhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K‹hj‹hžhubhÊ)”}”(hŒBThe following diagram provides an overview of the component area::”h]”hŒAThe following diagram provides an overview of the component area:”…””}”(hjªhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K‘hj‹hžhubhè)”}”(hXÊ area layout +-----------------+ | | | Component Count | | | +-----------------+ | | | Component 1 | | | +-----------------+ | | | Component 2 | | | +-----------------+ | | | ... | | | +-----------------+ | | | Component N | | | +-----------------+ component layout +------------------------+ | Classification | +------------------------+ | Component Identifier | +------------------------+ | Comparison Stamp | +------------------------+ | Component Options | +------------------------+ | Activation Method | +------------------------+ | Location Offset | +------------------------+ | Component Size | +------------------------+ | Component Version Info | +------------------------+ | Package Data | +------------------------+”h]”hXÊ area layout +-----------------+ | | | Component Count | | | +-----------------+ | | | Component 1 | | | +-----------------+ | | | Component 2 | | | +-----------------+ | | | ... | | | +-----------------+ | | | Component N | | | +-----------------+ component layout +------------------------+ | Classification | +------------------------+ | Component Identifier | +------------------------+ | Comparison Stamp | +------------------------+ | Component Options | +------------------------+ | Activation Method | +------------------------+ | Location Offset | +------------------------+ | Component Size | +------------------------+ | Component Version Info | +------------------------+ | Package Data | +------------------------+”…””}”hj¸sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1hçhŸh³h K“hj‹hžhubeh}”(h]”Œcomponent-info”ah ]”h"]”Œcomponent info”ah$]”h&]”uh1h´hh¶hžhhŸh³h K‰ubhµ)”}”(hhh]”(hº)”}”(hŒPackage Header CRC”h]”hŒPackage Header CRC”…””}”(hjÑhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÎhžhhŸh³h KÁubhÊ)”}”(hŒxFollowing the component information is a short 4-byte CRC calculated over the contents of all of the header information.”h]”hŒxFollowing the component information is a short 4-byte CRC calculated over the contents of all of the header information.”…””}”(hjßhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÃhjÎhžhubeh}”(h]”Œpackage-header-crc”ah ]”h"]”Œpackage header crc”ah$]”h&]”uh1h´hh¶hžhhŸh³h KÁubhµ)”}”(hhh]”(hº)”}”(hŒComponent Images”h]”hŒComponent Images”…””}”(hjøhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjõhžhhŸh³h KÇubhÊ)”}”(hŒÜThe component images follow the package header information in the PLDM firmware file. Each of these is simply a binary chunk with its start and size defined by the matching component structure in the component info area.”h]”hŒÜThe component images follow the package header information in the PLDM firmware file. Each of these is simply a binary chunk with its start and size defined by the matching component structure in the component info area.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KÉhjõhžhubeh}”(h]”Œcomponent-images”ah ]”h"]”Œcomponent images”ah$]”h&]”uh1h´hh¶hžhhŸh³h KÇubeh}”(h]”Œ"pldm-firmware-file-format-overview”ah ]”h"]”Œ"pldm firmware file format overview”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jGŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j!jj7j4jˆj…jËjÈjòjïjjuŒ nametypes”}”(j!‰j7‰jˆ‰jˉjò‰j‰uh}”(jh¶j4h÷j…j:jÈj‹jïjÎjjõuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.