summaryrefslogtreecommitdiffstats
path: root/docs/src/install/index.texi
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2016-03-10 23:20:52 (EST)
committer Francis Rowe <info@gluglug.org.uk>2016-03-10 23:25:57 (EST)
commit464076335d6ca5e6f801f863e95dc3847616a595 (patch)
tree0cb308ea155de7d0a65bba2de23cfbee92ebed60 /docs/src/install/index.texi
parent2d68bc1581647ca27ce8350a295de03cb7ff23d8 (diff)
downloadlibreboot-464076335d6ca5e6f801f863e95dc3847616a595.zip
libreboot-464076335d6ca5e6f801f863e95dc3847616a595.tar.gz
libreboot-464076335d6ca5e6f801f863e95dc3847616a595.tar.bz2
Remove ThinkPad R500 support (wasn't ready for production use yet anyway)
R500 support in its current state should not be merged in the master branch. This will likely not make it into the immediate upcoming release. This patch will be reverted in a separate experimental branch, for the time being.
Diffstat (limited to 'docs/src/install/index.texi')
-rw-r--r--docs/src/install/index.texi8
1 files changed, 2 insertions, 6 deletions
diff --git a/docs/src/install/index.texi b/docs/src/install/index.texi
index ddcaa5e..0ed27b4 100644
--- a/docs/src/install/index.texi
+++ b/docs/src/install/index.texi
@@ -75,8 +75,6 @@ This section relates to installing libreboot on supported targets.
@item
@uref{r400_external.html,ThinkPad R400 (needed if running the proprietary firmware, or to unbrick)}
@item
-@uref{r500_external.html,ThinkPad R500 (needed if running the proprietary firmware, or to unbrick)}
-@item
@uref{t400_external.html,ThinkPad T400 (needed if running the proprietary firmware, or to unbrick)}
@item
@uref{t500_external.html,ThinkPad T500 (needed if running the proprietary firmware, or to unbrick)}
@@ -146,7 +144,7 @@ If you are currently running the proprietary firmware (not libreboot or coreboot
X60/T60 users running the proprietary firmware should refer to @ref{#flashrom_lenovobios,#flashrom_lenovobios}. MacBook2,1 users running Apple EFI should refer to @ref{#flashrom_macbook21,#flashrom_macbook21}
-X200 users, refer to @uref{x200_external.html,x200_external.html}, R400 users refer to @uref{r400_external.html,r400_external.html}, R500 users refer to @uref{r500_external.html,r500_external.html}, T400 users refer to @uref{t400_external.html,t400_external.html}, T500 users refer to @uref{t500_external.html,t500_external.html}
+X200 users, refer to @uref{x200_external.html,x200_external.html}, R400 users refer to @uref{r400_external.html,r400_external.html}, T400 users refer to @uref{t400_external.html,t400_external.html}, T500 users refer to @uref{t500_external.html,t500_external.html}
@node ASUS KFSN4-DRE?
@section ASUS KFSN4-DRE?
@@ -188,7 +186,7 @@ Do check the HCL entry: @uref{../hcl/kcma-d8.html,../hcl/kcma-d8.html}
@anchor{#are-you-currently-running-libreboot-or-coreboot}
X60/T60 users should be fine with this guide. If you write-protected the flash chip, please refer to @uref{x60_unbrick.html,x60_unbrick.html}, @uref{x60tablet_unbrick.html,x60tablet_unbrick.html} or @uref{t60_unbrick.html,t60_unbrick.html}. @emph{This probably does not apply to you. Most people do not write-protect the flash chip, so you probably didn't either.}
-Similarly, it is possible to write-protect the flash chip in coreboot or libreboot on GM45 laptops (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).
+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, 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).
If you did not write-protect the flash chip, or it came to you without any write-protection (@strong{@emph{libreboot does not write-protect the flash chip by default, so this probably applies to you}}), read on!
@@ -199,8 +197,6 @@ If you did not write-protect the flash chip, or it came to you without any write
It is important that you change the default MAC address, before flashing. It will be printed on a sticker at the bottom of the laptop, or it will be printed on a sticker next to or underneath the RAM. Alternatively, and assuming that your current firmware has the correct MAC address in it, you can get it from your OS.
-@strong{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 @uref{../hcl/r500.html#nogbe,../hcl/r500.html#nogbe}.}
-
@node Flash chip size
@section Flash chip size
@anchor{#flash-chip-size}