From a8843dee58d15de6860b682975ee01ee61893670 Mon Sep 17 00:00:00 2001
From: Paul Menzel
Date: Mon, 5 Jun 2017 12:33:23 +0200
Subject: Use more secure HTTPS URLs for coreboot sites
The coreboot sites support HTTPS, and requests over HTTP with SSL are
also redirected. So use the more secure URLs, which also saves a
request most of the times, as nothing needs to be redirected.
Run the command below to replace all occurences.
```
$ git grep -l -E 'http://(www.|review.|)coreboot.org'
| xargs sed -i 's,http://\(.*\)coreboot.org,https://\1coreboot.org,g'
```
Change-Id: If53f8b66f1ac72fb1a38fa392b26eade9963c369
Signed-off-by: Paul Menzel
Reviewed-on: https://review.coreboot.org/20034
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi
---
Documentation/Intel/Board/board.html | 10 ++---
Documentation/Intel/SoC/soc.html | 82 ++++++++++++++++++------------------
Documentation/Intel/development.html | 8 ++--
3 files changed, 50 insertions(+), 50 deletions(-)
(limited to 'Documentation/Intel')
diff --git a/Documentation/Intel/Board/board.html b/Documentation/Intel/Board/board.html
index 1b2d323091..489d802709 100644
--- a/Documentation/Intel/Board/board.html
+++ b/Documentation/Intel/Board/board.html
@@ -161,20 +161,20 @@
- 0x34:
- Just after entering
- raminit
+ raminit
- 0x36:
- Just before displaying the
- UPD parameters
+ UPD parameters
for FSP MemoryInit
- - 0x92: POST_FSP_MEMORY_INIT
+
- 0x92: POST_FSP_MEMORY_INIT
- Just before calling FSP
- MemoryInit
+ MemoryInit
- 0x37:
- Just after returning from FSP
- MemoryInit
+ MemoryInit
diff --git a/Documentation/Intel/SoC/soc.html b/Documentation/Intel/SoC/soc.html
index 8f1d75ce64..6f6d6308ab 100644
--- a/Documentation/Intel/SoC/soc.html
+++ b/Documentation/Intel/SoC/soc.html
@@ -108,11 +108,11 @@ mv build/coreboot.rom.new build/coreboot.rom
When the reset vector is successfully invoked, port 0x80 will output the following value:
@@ -154,15 +154,15 @@ mv build/coreboot.rom.new build/coreboot.rom
Add the necessary .h files to define the necessary values and structures
When successful port 0x80 will output the following values:
- - 0x01: POST_RESET_VECTOR_CORRECT
+
- 0x01: POST_RESET_VECTOR_CORRECT
- Bootblock successfully executed the
- reset vector
+ reset vector
and entered the 16-bit code at
- _start
+ _start
- - 0x10: POST_ENTER_PROTECTED_MODE
+
- 0x10: POST_ENTER_PROTECTED_MODE
- Bootblock executing in
- 32-bit mode
+ 32-bit mode
- 0x10 - Verstage/romstage reached 32-bit mode
@@ -173,26 +173,26 @@ mv build/coreboot.rom.new build/coreboot.rom
Build Note: The following files are included into the default bootblock image:
@@ -231,19 +231,19 @@ Use the following steps to locate the FSP binary:
Edit the src/soc/<Vendor>/<Chip Family>/Kconfig file
- Add "select USE_GENERIC_FSP_CAR_INC" to enable the use of
- src/drivers/intel/fsp1_1/cache_as_ram.inc
+ src/drivers/intel/fsp1_1/cache_as_ram.inc
- Add "select SOC_INTEL_COMMON" to enable the use of the files from src/soc/intel/common
specifically building
- util.c
+ util.c
Debug the result until port 0x80 outputs
- - 0x90: POST_FSP_TEMP_RAM_INIT
+
- 0x90: POST_FSP_TEMP_RAM_INIT
- Just before calling
- TempRamInit
+ TempRamInit
- Alternating 0xba and 0x01 - The FSP image was not found
@@ -257,9 +257,9 @@ Use the following steps to locate the FSP binary:
Debug the result until port 0x80 outputs
- - 0x90: POST_FSP_TEMP_RAM_INIT
+
- 0x90: POST_FSP_TEMP_RAM_INIT
- Just before calling
- TempRamInit
+ TempRamInit
- Alternating 0xbb and 0x02 - TempRamInit executed, no CPU microcode update found
@@ -287,12 +287,12 @@ Use the following steps to debug the call to TempRamInit:
Debug the result until port 0x80 outputs
- - 0x90: POST_FSP_TEMP_RAM_INIT
+
- 0x90: POST_FSP_TEMP_RAM_INIT
- Just before calling
- TempRamInit
+ TempRamInit
- 0x2A - Just before calling
- cache_as_ram_main
+ cache_as_ram_main
which is the start of the verstage code which may be part of romstage
@@ -349,14 +349,14 @@ Use the following steps to debug the call to TempRamInit:
- 0x32:
- Just after entering
- romstage_common
+ romstage_common
- 0x33 - Just after calling
- soc_pre_ram_init
+ soc_pre_ram_init
- 0x34:
- Just after entering
- raminit
+ raminit
@@ -410,7 +410,7 @@ Use the following steps to debug the call to TempRamInit:
execution during ramstage. This file is processed by the util/sconfig utility
to generate build/mainboard/<Vendor>/<Board>/static.c. The various
state routines in
- src/lib/hardwaremain.c
+ src/lib/hardwaremain.c
call dev_* routines which use the tables in static.c to locate operation tables
associated with the various chips and devices. After location the operation
tables, the state routines call one or more functions depending upon the
@@ -540,7 +540,7 @@ Use the following steps to debug the call to TempRamInit:
BS_DEV_RESOURCES state of ramstage. The northcluster driver will typically
specify the DRAM resources while the other drivers will typically specify
the IO resources. These resources are hung off the device_t data structure by
- src/device/device_util.c/new_resource.
+ src/device/device_util.c/new_resource.
During the BS_WRITE_TABLES state, coreboot collects these resources and
@@ -552,7 +552,7 @@ Use the following steps to debug the call to TempRamInit:
-
Implement a read_resources routine which calls macros defined in
- src/include/device/device.h
+ src/include/device/device.h
like:
- ram_resource
@@ -661,7 +661,7 @@ Use the following steps to debug the call to TempRamInit:
The EDK2 data structure is defined in
MdeModulePkg/Include/IndustryStandard/Acpi61.h
The coreboot data structure is defined in
- src/arch/x86/include/arch/acpi.h
+ src/arch/x86/include/arch/acpi.h
diff --git a/Documentation/Intel/development.html b/Documentation/Intel/development.html
index a2ba2781e0..24b2fa9261 100644
--- a/Documentation/Intel/development.html
+++ b/Documentation/Intel/development.html
@@ -170,7 +170,7 @@
after_raminit.S
FindFSP: POST code 0x90
- (POST_FSP_TEMP_RAM_INIT)
+ (POST_FSP_TEMP_RAM_INIT)
is displayed
Enable: POST code
0x2A
@@ -303,7 +303,7 @@
| TempRamInit |
FSP TempRamInit |
FSP binary found: POST code 0x90
- (POST_FSP_TEMP_RAM_INIT)
+ (POST_FSP_TEMP_RAM_INIT)
is displayed
TempRamInit successful: POST code
0x2A
@@ -332,7 +332,7 @@
|
TempRamExit |
- src/drivers/intel/fsp1_1/after_raminit.S |
+ src/drivers/intel/fsp1_1/after_raminit.S |
Post code 0x91
(POST_FSP_TEMP_RAM_EXIT)
is displayed before calling TempRamExit by
@@ -354,7 +354,7 @@
| FspNotify |
The code which calls FspNotify is located in
- src/drivers/intel/fsp1_1/fsp_util.c.
+ src/drivers/intel/fsp1_1/fsp_util.c.
The fsp_notify_boot_state_callback routine is called three times as specified
by the BOOT_STATE_INIT_ENTRY macros below the routine.
|
--
cgit v1.2.3