From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id 527B57803D0 for ; Wed, 1 Nov 2023 09:31:10 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=CvBdSdcdEZDuJPWzbuw98L0IMqk32fWLGohUC75vmCk=; c=relaxed/simple; d=groups.io; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Transfer-Encoding; s=20140610; t=1698831068; v=1; b=mCRfag9sYf/WP9UQHwwlMMmehA8eaM2+ZR69kYtDo0qpD4oSqolcza3CpKAMLdegOGtsfRHU aDvF1/OrJbyqESAo45UCau2nkL2ychW/JzTRPacR/Y5JioR1gPhKvGI8L1CZ2ccMWz4yG3Q91OQ 93wjLm77KbRxiugmcC2WsaAI= X-Received: by 127.0.0.2 with SMTP id zV4wYY7687511xQ26D4xU3Wc; Wed, 01 Nov 2023 02:31:08 -0700 X-Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.88]) by mx.groups.io with SMTP id smtpd.web10.3239.1698831067944616513 for ; Wed, 01 Nov 2023 02:31:08 -0700 X-IronPort-AV: E=McAfee;i="6600,9927,10880"; a="419582573" X-IronPort-AV: E=Sophos;i="6.03,267,1694761200"; d="scan'208";a="419582573" X-Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Nov 2023 02:31:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10880"; a="1092293734" X-IronPort-AV: E=Sophos;i="6.03,267,1694761200"; d="scan'208";a="1092293734" X-Received: from ray-dev.ccr.corp.intel.com ([10.239.158.139]) by fmsmga005.fm.intel.com with ESMTP; 01 Nov 2023 02:31:04 -0700 From: "Ni, Ray" To: devel@edk2.groups.io Cc: Chasel Chiu , Nate DeSimone , Duggapu Chinni B , Ray Han Lim Ng , Star Zeng , Ted Kuo , Ashraf Ali S , Susovan Mohapatra Subject: [edk2-devel] [PATCH] IntelFsp2Pkg/PatchFv: Fix syntax issue in markdown manual Date: Wed, 1 Nov 2023 17:30:26 +0800 Message-Id: <20231101093026.296-1-ray.ni@intel.com> MIME-Version: 1.0 Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,ray.ni@intel.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: ErSktSKNnq3ZxrFbM4paf6hkx7686176AA= Content-Transfer-Encoding: quoted-printable X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=mCRfag9s; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=intel.com (policy=none); spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io According to the markdown language syntax, headings should be after number signs (#). The number of number signs correspond to the heading level. But current PatchFvUserManual.md doesn't insert a space between the number signs and the heading title, resulting the markdown file is not rendered well in markdown viewers. The patch doesn't change any content but only adds spaces to ensure the headings are correctly recognized. Signed-off-by: Ray Ni Cc: Chasel Chiu Cc: Nate DeSimone Cc: Duggapu Chinni B Cc: Ray Han Lim Ng Cc: Star Zeng Cc: Ted Kuo Cc: Ashraf Ali S Cc: Susovan Mohapatra --- .../Tools/UserManuals/PatchFvUserManual.md | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md b/IntelFsp= 2Pkg/Tools/UserManuals/PatchFvUserManual.md index f28eedf625..205ad57773 100644 --- a/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md +++ b/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md @@ -1,9 +1,9 @@ -#Name=0D +# Name=0D **_PatchFv.py_** - The python script that patches the firmware volumes (**= FV**)=0D with in the flash device (**FD**) file post FSP build.=0D From version 0.60, script is capable of patching flash device (**FD**) dir= ectly.=0D =0D -#Synopsis=0D +# Synopsis=0D =0D ```=0D PatchFv FvBuildDir [FvFileBaseNames:]FdFileBaseNameToPatch ["Offset, Value= "]+=0D @@ -18,32 +18,32 @@ PatchFv FdFileDir FdFileName ["Offset, Value"]+ | ["Offset, Value, $Command, @Comment"]+=0D ```=0D =0D -#Description=0D +# Description=0D The **_PatchFv.py_** tool allows the developer to fix up FD images to foll= ow the=0D Intel FSP Architecture specification. It also makes the FD image relocata= ble.=0D The tool is written in Python and uses Python 2.7 or later to run.=0D Consider using the tool in a build script.=0D =0D -#FvBuildDir (Argument 1)=0D +# FvBuildDir (Argument 1)=0D This is the first argument that **_PatchFv.py_** requires. It is the buil= d=0D directory for all firmware volumes created during the FSP build. The path = must=0D be either an absolute path or a relevant path, relevant to the top level o= f the=0D FSP tree.=0D =0D -####Example usage:=0D +#### Example usage:=0D ```=0D Build\YouPlatformFspPkg\%BD_TARGET%_%VS_VERSION%%VS_X86%\FV=0D ```=0D =0D The example used contains Windows batch script %VARIABLES%.=0D =0D -#FvFileBaseNames (Argument 2: Optional Part 1)=0D +# FvFileBaseNames (Argument 2: Optional Part 1)=0D The firmware volume file base names (**_FvFileBaseNames_**) are the indepe= ndent=0D -Fv?s that are to be patched within the FD. (0 or more in the form=0D -**FVFILEBASENAME:**) The colon **:** is used for delimiting the single=0D +FVs that are to be patched within the FD. (0 or more in the form=0D +**FvFileBaseNames:**) The colon **:** is used for delimiting the single=0D argument and must be appended to the end of each (**_FvFileBaseNames_**).= =0D =0D -####Example usage:=0D +#### Example usage:=0D ```=0D STAGE1:STAGE2:MANIFEST:YOURPLATFORM=0D ```=0D @@ -55,14 +55,14 @@ In the example **STAGE1** is **STAGE1.Fv** in **YOURPLA= TFORM.fd**. Firmware device file name to patch (**_FdFileNameToPatch_**) is the base n= ame of=0D the FD file that is to be patched. (1 only, in the form **YOURPLATFORM**)= =0D =0D -####Example usage:=0D +#### Example usage:=0D ```=0D STAGE1:STAGE2:MANIFEST:YOURPLATFORM=0D ```=0D =0D In the example **YOURPLATFORM** is from **_YOURPLATFORM.fd_**=0D =0D -#"Offset, Value[, Command][, Comment]" (Argument 3)=0D +# "Offset, Value[, Command][, Comment]" (Argument 3)=0D The **_Offset_** can be a positive or negative number and represents where= the=0D **_Value_** to be patched is located within the FD. The **_Value_** is wha= t=0D will be written at the given **_Offset_** in the FD. Constants may be used= for=0D @@ -79,10 +79,10 @@ The entire argument includes the quote marks like in th= e example argument below: 0xFFFFFFC0, SomeCore:__EntryPoint - [0x000000F0],@SomeCore Entry=0D ```=0D =0D -###Constants:=0D +### Constants:=0D Hexadecimal (use **0x** as prefix) | Decimal=0D =0D -####Examples:=0D +#### Examples:=0D =0D | **Positive Hex** | **Negative Hex** | **Positive Decimal** | **Negative = Decimal** |=0D | ---------------: | ---------------: | -------------------: | -----------= --------: |=0D @@ -93,7 +93,7 @@ ModuleName:FunctionName | ModuleName:GlobalVariableName ModuleGuid:Offset=0D ```=0D =0D -###Operators:=0D +### Operators:=0D =0D ```=0D =0D @@ -113,7 +113,7 @@ From version 0.60 tool allows to pass flash device file= path as Argument 1 and flash device name as Argument 2 and rules for passing offset & value are s= ame=0D as explained in the previous sections.=0D =0D -####Example usage:=0D +#### Example usage:=0D Argument 1=0D ```=0D YouPlatformFspBinPkg\=0D @@ -123,21 +123,21 @@ Argument 2 Fsp_Rebased_T=0D ```=0D =0D -###Special Commands:=0D +### Special Commands:=0D Special commands must use the **$** symbol as a prefix to the command itse= lf.=0D There is only one command available at this time.=0D =0D ```=0D -$COPY ? Copy a binary block from source to destination.=0D +$COPY Copy a binary block from source to destination.=0D ```=0D =0D -####Example:=0D +#### Example:=0D =0D ```=0D 0x94, [PlatformInit:__gPcd_BinPatch_FvRecOffset] + 0x94, [0x98], $COPY, @S= ync up 2nd FSP Header=0D ```=0D =0D -###Comments:=0D +### Comments:=0D Comments are allowed in the **Offset, Value [, Comment]** argument. Commen= ts=0D must use the **@** symbol as a prefix. The comment will output to the buil= d=0D window upon successful completion of patching along with the offset and va= lue data.=0D --=20 2.39.1.windows.1 -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#110471): https://edk2.groups.io/g/devel/message/110471 Mute This Topic: https://groups.io/mt/102315223/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-