From d1bb5d6fcc75f07ca6a58b5536906980aff9d253 Mon Sep 17 00:00:00 2001
From: Francis Rowe <info@gluglug.org.uk>
Date: Sat, 18 Jul 2015 19:31:16 -0400
Subject: New board: ThinkPad R500 (experimental)

The ich9deblob and ich9gen utilities were modified, so that they
support reading and/or writing descriptor images where the GbE
region is not defined. These utilities were also re-factored
and tidied up a bit.

A quick was noticed during the course of this work, in that
Compenent 1 Density was being set to 8MiB constantly, even
on systems with 4MiB flash chips. Component 2 Density was
set statically to 2MiB. ich9gen now sets both to 4MiB or 8MiB,
depending on whether building the descriptor for a 4MiB or
8MiB ROM image.

There are still some ACPI bugs (see docs/hcl/r500.html), which
will have to be fixed upstream. TODO: get hw reg dumps from
a factory R500, and compare with the X200 or T400 dumps.
---
(limited to 'docs/install/index.html')

diff --git a/docs/install/index.html b/docs/install/index.html
index 56d5048..b0df387 100644
--- a/docs/install/index.html
+++ b/docs/install/index.html
@@ -45,6 +45,7 @@
 				<li><a href="t60_unbrick.html">ThinkPad T60: Recovery guide</a></li>
 				<li><a href="x200_external.html">ThinkPad X200/X200S/X200T (needed if running the proprietary firmware, or to unbrick)</a></li>
 				<li><a href="r400_external.html">ThinkPad R400 (needed if running the proprietary firmware, or to unbrick)</a></li>
+				<li><a href="r500_external.html">ThinkPad R500 (needed if running the proprietary firmware, or to unbrick)</a></li>
 				<li><a href="t400_external.html">ThinkPad T400 (needed if running the proprietary firmware, or to unbrick)</a></li>
 				<li><a href="t500_external.html">ThinkPad T500 (needed if running the proprietary firmware, or to unbrick)</a></li>
 			</ul>
@@ -142,6 +143,7 @@
 				<p>
 					X200 users, refer to <a href="x200_external.html">x200_external.html</a>,
 					R400 users refer to <a href="r400_external.html">r400_external.html</a>,
+					R500 users refer to <a href="r500_external.html">r500_external.html</a>,
 					T400 users refer to <a href="t400_external.html">t400_external.html</a>,
 					T500 users refer to <a href="t500_external.html">t500_external.html</a>
 				</p>
@@ -194,7 +196,7 @@
 				</p>
 				<p>
 					Similarly, it is possible to write-protect the flash chip in coreboot or libreboot on GM45 laptops
-					(X200/R400/T400/T500). If you did this, then you will need to use the links above for flashing, 
+					(X200/R400/R500/T400/T500). If you did this, then you will need to use the links above for flashing, 
 					treating your laptop as though it currently has the proprietary firmware (because write-protected SPI flash
 					requires external re-flashing, as is also the case when running the proprietary firmware).
 				</p>
@@ -222,7 +224,15 @@
 					and assuming that your current firmware has the correct MAC address in it, you can get it from your OS.
 				</p>
 
-			<h2>Flash chip size on GM45 (X200/R400/T400/T500)</h2>
+				<p>
+					<b>
+						R500 users: your laptop lacks a GbE region, because it has a different NIC. You do not need to change the MAC
+						address on this laptop; it will already be correct. You can simply flash the available ROM images for the R500, as-is.
+						See <a href="../hcl/r500.html#nogbe">../hcl/r500.html#nogbe</a>.
+					</b>
+				</p>
+
+			<h2>Flash chip size</h2>
 
 				<p>
 					Use this to find out:<br/>
--
cgit v0.9.1