<?xml version="1.0"?>
<vpd>

  <record name="VNDR">
    <rdesc>The VNDR record</rdesc>

    <keyword name="RT">
      <kwdesc>The Record Type keyword</kwdesc>
      <kwformat>ascii</kwformat>
      <kwlen>4</kwlen>
      <kwdata>VNDR</kwdata>
    </keyword>

    <keyword name="VD">
      <kwdesc>Record Version</kwdesc>
      <kwformat>ascii</kwformat>
      <kwlen>2</kwlen>
      <kwdata>01</kwdata>
    </keyword>

    <keyword name="IN">
      <kwdesc>Vendor Specific Data</kwdesc>
      <kwformat>hex</kwformat>
      <kwlen>128</kwlen>
      <kwdata>00</kwdata>
    </keyword>

  </record>

</vpd>

<?xml version="1.0"?>
<vpd>

  <record name="VNDR">
    <rdesc>The VNDR record</rdesc>

    <keyword name="RT">
      <kwdesc>The Record Type keyword</kwdesc>
      <kwformat>ascii</kwformat>
      <kwlen>4</kwlen>
      <kwdata>VNDR</kwdata>
    </keyword>

    <keyword name="VD">
      <kwdesc>Record Version</kwdesc>
      <kwformat>ascii</kwformat>
      <kwlen>2</kwlen>
      <kwdata>02</kwdata>
    </keyword>

    <keyword name="IN">
      <kwdesc>Vendor Specific Data</kwdesc>
      <kwformat>hex</kwformat>
      <kwlen>128</kwlen>
      <kwdata>00</kwdata>
    </keyword>

    <keyword name="NV">
      <kwdesc>NVLINK Configuration Data</kwdesc>
      <kwformat>hex</kwformat>
      <kwlen>255</kwlen>
      <kwdata>00</kwdata>
    </keyword>

  </record>

</vpd>

Add NV keyword to VNDR Record
Add NV keyword to VNDR Record

Hostboot has the need to add nvlink configuration
data to support multiple nvlink on a system planar.
NV keyword was created and include in VNDR  record
to meet this requirement.

bug:  NA
branch:  master

Signed-off-by: Michael Y. Lim <3e670869924a171a7c113042bfa1ee4a88d80a7c@us.ibm.com>
