fix errant reference on the 780 page

Signed-off-by: Leah Rowe <info@minifree.org>
master
Leah Rowe 2024-11-02 06:48:15 +00:00
parent 92e977ebfd
commit 0c53ec500c
1 changed files with 11 additions and 11 deletions

View File

@ -3,7 +3,7 @@ title: Dell OptiPlex 780 MT/USFF
x-toc-enable: true
...
Libreboot is compatible with the Dell OptiPlex 780, of variants: MT and USFF.
Canoeboot is compatible with the Dell OptiPlex 780, of variants: MT and USFF.
SFF and DT may be supported in a future revision. These instructions are
identical both the MT and USFF variants.
@ -55,8 +55,8 @@ P*: Partially works with blobs
Introduction
============
**Unavailable in Libreboot 20240612 or earlier. You must [compile from
source](../build/), or use a version newer than Libreboot 20240612.**
**Unavailable in Canoeboot 20240612 or earlier. You must [compile from
source](../build/), or use a version newer than Canoeboot 20240612.**
Official information about the computer can be found here:
<https://www.dell.com/support/manuals/en-uk/optiplex-7010-plus-small-ff/opti_7010_sff_plus_om/specifications-of-optiplex-small-form-factor-plus-7010?guid=guid-7c9f07ce-626e-44ca-be3a-a1fb036413f9&lang=en-us>
@ -71,7 +71,7 @@ The build target, when building from source, is thus:
./mk -b coreboot dell780usff_truncate_8mb
./mk -b coreboot dell780usff_8mb
The `_truncate` image is needed if you're flashing Libreboot internally from
The `_truncate` image is needed if you're flashing Canoeboot internally from
the original Dell firmware. Otherwise, you only need the regular images that
lack `_truncate` in the file name.
@ -108,7 +108,7 @@ Flash a ROM image (software)
**Always make sure to dump a copy of the current flash first. ALSO: [make
sure /dev/mem protection is disabled](devmem.md) for the flashing to work!**
If you're already running Libreboot, and you don't have flash protection
If you're already running Canoeboot, and you don't have flash protection
turned on, [internal flashing](../install/) is possible.
If you have factory firmware (Dell), you can short the service jumper. It's a
@ -128,7 +128,7 @@ are 6MB in size, but they must be padded to 8MB. Normally a blank part of flash
should ideally be all 0xFF, but here we do:
dd if=/dev/zero of=2mb.bin bs=2M count=1
cat libreboot6mb.rom 2mb.bin > libreboot.rom
cat canoeboot6mb.rom 2mb.bin > canoeboot.rom
If you're not using the truncate images, you can ignore the above steps.
@ -136,17 +136,17 @@ The Flash Descriptor can be thought of more like a *partition table* for the
flash, at least in our use-case scenario. The `_truncate` images configure
the flash such that only the first 6MB is used, with the BIOS region ending
at that limit; the upper 2MB is specified as the platform data region, in
Libreboot's configuration. To flash it, do this:
Canoeboot's configuration. To flash it, do this:
./flashprog -p internal --ifd -i fd -w libreboot.rom
./flashprog -p internal --ifd -i gbe -w libreboot.rom
./flashprog -p internal --ifd -i bios -w libreboot.rom
./flashprog -p internal --ifd -i fd -w canoeboot.rom
./flashprog -p internal --ifd -i gbe -w canoeboot.rom
./flashprog -p internal --ifd -i bios -w canoeboot.rom
It's very important to do this in the *exact* order as above, because
the `--ifd` option references the *flashed* IFD, not the one in your image,
so you must flash the IFD first.
If you already have Libreboot running, and you don't have flash protection
If you already have Canoeboot running, and you don't have flash protection
enabled, you can omit `--ifd -i REGION` from the flashprog command, and flash
the full image; the one without `_truncate` in the file name uses all of the
flash, with the BIOS region ending at the 8MB limit, so the BIOS region is