Documentation: Use file paths to flashing firmware tutorial

In preperation for CB:62424, replace HTTP links pointing to the flashing
firmware tutorial with file paths to the Markdown files.

Change-Id: I6a271a912348cbe002bc9cced9922ed743e1133c
Signed-off-by: Felix Singer <felixsinger@posteo.net>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/62452
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Thomas Heijligen <src@posteo.de>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-by: Michael Niewöhner <foss@mniewoehner.de>

Documentation/mainboard/asus/p5q.md

@@ -130,5 +130,5 @@ You can also control the CPU fan with similar rules:
     echo 2000 >/sys/class/hwmon/hwmon2/pwm1_tolerance
 
 [ASUS P5Q]: https://www.asus.com/Motherboards/P5Q
-[this guide]: https://doc.coreboot.org/flash_tutorial/int_flashrom.html
+[this guide]: ../../flash_tutorial/int_flashrom.md
 [kernel docs]: https://www.kernel.org/doc/Documentation/hwmon/w83627ehf.rst

Documentation/mainboard/lenovo/ivb_internal_flashing.md

@@ -353,9 +353,12 @@ Verify that it worked:
 
 Bingo!
 
-Now you can [flash internally](/flash_tutorial/int_flashrom.md).
-Remember to flash only the `bios` region (use `--ifd -i bios -N`
-flashrom arguments). `fd` and `me` are still locked.
+Now you can [flash internally]. Remember to flash only the `bios` region
+(use `--ifd -i bios -N` flashrom arguments). `fd` and `me` are still
+locked.
 
 Note that you should have an external SPI programmer as a backup method.
 It will help you recover if you flash non-working ROM by mistake.
+
+
+[flash internally]: ../../flash_tutorial/int_flashrom.md

Documentation/mainboard/msi/ms7707/ms7707.md

@@ -74,7 +74,7 @@ seconds. Setting the jumper alone is not enough (the Fintek is VBAT backed).
 Put all back in place and restart the board. It might need 1-2 AC power cycles
 to reinitialize (running at full fan speed - don't panic).
 * External flashing has been tested with RPi2 without main power connected.
-3.3V provided by RPi2. Read more about flashing methods [here](https://doc.coreboot.org/flash_tutorial/index.html).
+3.3V provided by RPi2. Read more about [flashing methods].
 * In case of going back to proprietary BIOS create/save CMOS settings as early
 as possible (do not leave BIOS on first start without saving settings).
 The BIOS might corrupt nvram (not cmos!) and leave the system in a dead state
@@ -110,3 +110,4 @@ needed (internally re-routed already).
 [Winbond 25Q32BV datasheet]: https://www.winbond.com/resource-files/w25q32bv_revi_100413_wo_automotive.pdf
 [Fintek F71808A datasheet]: https://www.alldatasheet.com/datasheet-pdf/pdf/459069/FINTEK/F71808A.html
 [flashlayout]: flashlayout.svg
+[flashing methods]: ../../../flash_tutorial/index.md

Documentation/mainboard/supermicro/x9sae.md

@@ -41,10 +41,9 @@ first, otherwise ME may write something back and break the firmware you write.
 The following command may be used to flash coreboot. (To do so, linux kernel
 could be started with `iomem=relaxed` or unload the `lpc_ich` kernel module)
 
-Now you can [flash internally](/flash_tutorial/int_flashrom.md). It is
-recommended to flash only the `bios` region (use `--ifd -i bios -N` flashrom
-arguments), in order to minimize the chances of messing something up in the
-beginning.
+Now you can [flash internally]. It is recommended to flash only the `bios`
+region (use `--ifd -i bios -N` flashrom arguments), in order to minimize the
+chances of messing something up in the beginning.
 
 The flash chip is a SOIC-8 SPI flash, and may be socketed, so it's also easy
 to do in-system programming, or remove and flash externally if it is socketed.
@@ -106,3 +105,4 @@ seems that it shall not appear on X9SAE even if it is defined.
 [X9SAE-V]:  https://www.supermicro.com/products/motherboard/xeon/c216/x9sae-v.cfm
 [W25Q128FVSG]: https://static.chipdip.ru/lib/093/DOC001093213.pdf
 [flashrom]: https://flashrom.org/Flashrom
+[flash internally]: ../../flash_tutorial/int_flashrom.md