Re: [PATCH v1 05/12] website: docs: install: flashrom: add support for BSD.

[Adrien 'neox' Bourmault]

Le mardi 11 juin 2024 à 20:52 +0200, Denis 'GNUtoo' Carikli a écrit :
> From: Leah Rowe <leah@libreboot.org>
> 
> Signed-off-by: Leah Rowe <leah@libreboot.org>
> Signed-off-by: Leah Rowe <info@minifree.org>
> GNUtoo: fixed section underline, rebased, commit message, split patch.
> Acked-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
> ---
>  website/pages/docs/install/install.md | 24 +++++++++++++++++++-----
>  1 file changed, 19 insertions(+), 5 deletions(-)
> 
> diff --git a/website/pages/docs/install/install.md
> b/website/pages/docs/install/install.md
> index 4c75670..3e4d1ca 100644
> --- a/website/pages/docs/install/install.md
> +++ b/website/pages/docs/install/install.md
> @@ -5,11 +5,6 @@ x-unreviewed: true
>  
>  This section relates to installing GNU Boot on supported targets.
>  
> -NOTE: if running `flashrom -p internal` for software based flashing, and you
> -get an error related to `/dev/mem` access, you should reboot with
> -`iomem=relaxed` kernel parameter before running flashrom, or use a kernel
> that
> -has `CONFIG_STRICT_DEVMEM` not enabled.
> -
>  GNU Boot flashing can be risky business. Please ensure that you have external
>  flashing equipment, in case anything goes wrong. The general rule of thumb
> with
>  firmware is this: if it's non-free, replace it, but if you're already running
> @@ -21,6 +16,25 @@ If you're already running libre firmware on your board, you
> should decide for
>  sure whether you wish to risk it. See changelogs on
>  the [release announcements via the news page](/news/) and decide for
> yourself.
>  
> +FLASH ERRORS (and workarounds)
> +==============================
> +
> +Right out of the gate, some users may experience errors with flashrom when
> +using the internal programmer. They are:
> +
> +/dev/mem access error
> +---------------------
> +
> +NOTE: if running `flashrom -p internal` for software based flashing, and you
> +get an error related to `/dev/mem` access, you should reboot with
> +`iomem=relaxed` kernel parameter before running flashrom, or use a kernel
> that
> +has `CONFIG_STRICT_DEVMEM` not enabled.
> +
> +On NetBSD and OpenBSD systems, the equivalent to `iomem=relaxed` in this case
> +is `kernel.securelevel=-1`; see [NetBSD securelevel
> +manual](https://wiki.netbsd.org/tutorials/kernel_secure_levels/)
> +and [OpenBSD securelevel manual](https://man.openbsd.org/securelevel).
> +
>  About ROM image file names
>  ==========================
>  

Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>

signature.asc
Description: This is a digitally signed message part