further cleanup
and i've generally cleaned up the documentation Signed-off-by: Leah Rowe <info@minifree.org> Signed-off-by: Leah Rowe <leah@libreboot.org>master
parent
abd00dc26f
commit
663467d8bf
|
@ -9,9 +9,8 @@ WARNING: eCryptfs file name limits
|
||||||
Do not run the build system on a eCryptfs file system, because it has
|
Do not run the build system on a eCryptfs file system, because it has
|
||||||
very short file name limits and Canoeboot's build system deals with very
|
very short file name limits and Canoeboot's build system deals with very
|
||||||
long file names. We commonly get reports from this by Linux Mint users
|
long file names. We commonly get reports from this by Linux Mint users
|
||||||
who encrypt their home directory with cryptfs; use a serious distro like
|
who encrypt their home directory with eCryptfs; regular LUKS encryption will
|
||||||
Debian or Arch please. And use a decent file system; ZFS or perhaps LUKS
|
do nicely.
|
||||||
with btrfs will do nicely.
|
|
||||||
|
|
||||||
Introduction
|
Introduction
|
||||||
============
|
============
|
||||||
|
|
|
@ -9,9 +9,8 @@ WARNING: eCryptfs file name limits
|
||||||
Do not run the build system on a eCryptfs file system, because it has
|
Do not run the build system on a eCryptfs file system, because it has
|
||||||
very short file name limits and Canoeboot's build system deals with very
|
very short file name limits and Canoeboot's build system deals with very
|
||||||
long file names. We commonly get reports from this by Linux Mint users
|
long file names. We commonly get reports from this by Linux Mint users
|
||||||
who encrypt their home directory with cryptfs; use a serious distro like
|
who encrypt their home directory with eCryptfs; regular LUKS encryption will
|
||||||
Debian or Arch please. And use a decent file system; ZFS or perhaps LUKS
|
do nicely.
|
||||||
with btrfs will do nicely.
|
|
||||||
|
|
||||||
Introduction
|
Introduction
|
||||||
============
|
============
|
||||||
|
|
|
@ -27,12 +27,12 @@ motherboard while they still have the original BIOS present.
|
||||||
| **Flash chip** | SOIC-8 512KiB |
|
| **Flash chip** | SOIC-8 512KiB |
|
||||||
|
|
||||||
```
|
```
|
||||||
W+: Works without blobs;
|
W+: Works without vendor firmware;
|
||||||
N: Doesn't work;
|
N: Doesn't work;
|
||||||
W*: Works with blobs;
|
W*: Works with vendor firmware;
|
||||||
U: Untested;
|
U: Untested;
|
||||||
P+: Partially works;
|
P+: Partially works;
|
||||||
P*: Partially works with blobs
|
P*: Partially works with vendor firmware
|
||||||
```
|
```
|
||||||
|
|
||||||
| ***Features*** | | Notes |
|
| ***Features*** | | Notes |
|
||||||
|
|
|
@ -29,12 +29,12 @@ Dell OptiPlex 780
|
||||||
|
|
||||||
|
|
||||||
```
|
```
|
||||||
W+: Works without blobs;
|
W+: Works without vendor firmware;
|
||||||
N: Doesn't work;
|
N: Doesn't work;
|
||||||
W*: Works with blobs;
|
W*: Works with vendor firmware;
|
||||||
U: Untested;
|
U: Untested;
|
||||||
P+: Partially works;
|
P+: Partially works;
|
||||||
P*: Partially works with blobs
|
P*: Partially works with vendor firmware
|
||||||
?: UNKNOWN AT THIS TIME
|
?: UNKNOWN AT THIS TIME
|
||||||
```
|
```
|
||||||
|
|
||||||
|
@ -75,7 +75,7 @@ lack `_truncate` in the file name.
|
||||||
100% FREE
|
100% FREE
|
||||||
=========
|
=========
|
||||||
|
|
||||||
This mainboard does not rely on any binary blobs in the flash. It is using
|
This mainboard is entirely free software in the main boot flash. It is using
|
||||||
the Intel X4X / ICH10 platform, same as on the already supported
|
the Intel X4X / ICH10 platform, same as on the already supported
|
||||||
Gigabyte GA-G41M-ES2L mainboard.
|
Gigabyte GA-G41M-ES2L mainboard.
|
||||||
|
|
||||||
|
|
|
@ -24,12 +24,12 @@ GA-G41M-ES2L
|
||||||
| **Flash chip** | 2x8Mbit |
|
| **Flash chip** | 2x8Mbit |
|
||||||
|
|
||||||
```
|
```
|
||||||
W+: Works without blobs;
|
W+: Works without vendor firmware;
|
||||||
N: Doesn't work;
|
N: Doesn't work;
|
||||||
W*: Works with blobs;
|
W*: Works with vendor firmware;
|
||||||
U: Untested;
|
U: Untested;
|
||||||
P+: Partially works;
|
P+: Partially works;
|
||||||
P*: Partially works with blobs
|
P*: Partially works with vendor firmware
|
||||||
```
|
```
|
||||||
|
|
||||||
| ***Features*** | |
|
| ***Features*** | |
|
||||||
|
|
|
@ -9,7 +9,8 @@ a relic from Libreboot, upon which Canoeboot is based, and provided for
|
||||||
historical purposes (Libreboot also uses nvmutil these days).**
|
historical purposes (Libreboot also uses nvmutil these days).**
|
||||||
|
|
||||||
**If all you want to do is change the MAC address, you might use `nvmutil`
|
**If all you want to do is change the MAC address, you might use `nvmutil`
|
||||||
instead. See: [nvmutil documentation](../install/nvmutil.md).**
|
instead. See: [nvmutil documentation](../install/nvmutil.md), or use
|
||||||
|
the [inject script](ivy_has_common.md).**
|
||||||
|
|
||||||
The documentation below is *still valid*, if you actually want to use ich9utils.
|
The documentation below is *still valid*, if you actually want to use ich9utils.
|
||||||
You can find it in older Libreboot releases, up to Libreboot 20230625. The only
|
You can find it in older Libreboot releases, up to Libreboot 20230625. The only
|
||||||
|
|
|
@ -28,12 +28,12 @@ x-toc-enable: true
|
||||||
| **Flash chip** | SOIC-8/SOIC-16 4MiB/8MiB (Upgradable to 16MiB) |
|
| **Flash chip** | SOIC-8/SOIC-16 4MiB/8MiB (Upgradable to 16MiB) |
|
||||||
|
|
||||||
```
|
```
|
||||||
W+: Works without blobs;
|
W+: Works without vendor firmware;
|
||||||
N: Doesn't work;
|
N: Doesn't work;
|
||||||
W*: Works with blobs;
|
W*: Works with vendor firmware;
|
||||||
U: Untested;
|
U: Untested;
|
||||||
P+: Partially works;
|
P+: Partially works;
|
||||||
P*: Partially works with blobs
|
P*: Partially works with vendor firmware
|
||||||
```
|
```
|
||||||
|
|
||||||
| ***Features*** | |
|
| ***Features*** | |
|
||||||
|
|
|
@ -27,12 +27,12 @@ x-toc-enable: true
|
||||||
| **Flash chip** | SOIC-8/SOIC-16/WSON-8 4MiB/8MiB (Upgradable
|
| **Flash chip** | SOIC-8/SOIC-16/WSON-8 4MiB/8MiB (Upgradable
|
||||||
to 16MiB) |
|
to 16MiB) |
|
||||||
```
|
```
|
||||||
W+: Works without blobs;
|
W+: Works without vendor firmware;
|
||||||
N: Doesn't work;
|
N: Doesn't work;
|
||||||
W*: Works with blobs;
|
W*: Works with vendor firmware;
|
||||||
U: Untested;
|
U: Untested;
|
||||||
P+: Partially works;
|
P+: Partially works;
|
||||||
P*: Partially works with blobs
|
P*: Partially works with vendor firmware
|
||||||
```
|
```
|
||||||
|
|
||||||
| ***Features*** | |
|
| ***Features*** | |
|
||||||
|
|
|
@ -27,12 +27,12 @@ x-toc-enable: true
|
||||||
| **Flash chip** | SOIC-8/SOIC-16/WSON-8 4MiB/8MiB (Upgradable
|
| **Flash chip** | SOIC-8/SOIC-16/WSON-8 4MiB/8MiB (Upgradable
|
||||||
to 16MiB) |
|
to 16MiB) |
|
||||||
```
|
```
|
||||||
W+: Works without blobs;
|
W+: Works without vendor firmware;
|
||||||
N: Doesn't work;
|
N: Doesn't work;
|
||||||
W*: Works with blobs;
|
W*: Works with vendor firmware;
|
||||||
U: Untested;
|
U: Untested;
|
||||||
P+: Partially works;
|
P+: Partially works;
|
||||||
P*: Partially works with blobs
|
P*: Partially works with vendor firmware
|
||||||
```
|
```
|
||||||
|
|
||||||
| ***Features*** | |
|
| ***Features*** | |
|
||||||
|
|
|
@ -572,7 +572,7 @@ these changes relative to the old one:
|
||||||
* 192e23b7 vbe: implement function 09h (get/set palette data)
|
* 192e23b7 vbe: implement function 09h (get/set palette data)
|
||||||
* 3722c21d vgasrc: round up save/restore size
|
* 3722c21d vgasrc: round up save/restore size
|
||||||
* 5d87ff25 vbe: Add VBE 2.0+ OemData field to struct vbe_info
|
* 5d87ff25 vbe: Add VBE 2.0+ OemData field to struct vbe_info
|
||||||
* 163fd9f0 fix smbios blob length overflow
|
* 163fd9f0 fix smbios data length overflow
|
||||||
* 82faf1d5 Add LBA 64bit support for reads beyond 2TB.
|
* 82faf1d5 Add LBA 64bit support for reads beyond 2TB.
|
||||||
* 3f082f38 Add AHCI Power ON + ICC_ACTIVE into port setup code
|
* 3f082f38 Add AHCI Power ON + ICC_ACTIVE into port setup code
|
||||||
* 3ae88886 esp-scsi: terminate DMA transfer when ESP data transfer completes
|
* 3ae88886 esp-scsi: terminate DMA transfer when ESP data transfer completes
|
||||||
|
|
Loading…
Reference in New Issue