document dell latitude thermal safety paranoia

Signed-off-by: Leah Rowe <info@minifree.org>

site/docs/build/index.md

@@ -25,6 +25,14 @@ canoeboot from the available source code.
 The following document describes how `cbmk` works, and how you can make changes
 to it: [canoeboot maintenance manual](../maintain/)
 
+Environmental variables
+=======================
+
+Please read about environmental variables in [the build
+instructions](../maintain/), before running lbmk. You should set
+your variables accordingly, though you do not technically need to; some
+of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
+
 Sources
 =======
 

site/docs/build/index.uk.md

@@ -17,6 +17,14 @@ images (containing payloads) in `bin/`. This design is more efficient, and
 permits many configurations without needless duplication of work. More info
 is available in the [cbmk maintenance manual](../maintain/)**
 
+Environmental variables
+=======================
+
+Please read about environmental variables in [the build
+instructions](../maintain/), before running cbmk. You should set
+your variables accordingly, though you do not technically need to; some
+of them may be useful, e.g. `CBMK_THREADS` (sets the number of build threads).
+
 Introduction
 ============
 

site/docs/hardware/e6400.md

@@ -3,6 +3,12 @@ title: Dell Latitude E6400
 x-toc-enable: true
 ...
 
+**Thermal safety**: this machine shuts down very quickly, when the machine
+exceeds 80c CPU temperature, which is far more conservative than on most
+laptops (non-Dell ones), so you should make sure that your thermals are
+excellent. More info available [here](dell_thermal.md). This is a known bug,
+but otherwise the machine will be mostly stable.
+
 <div class="specs">
 <center>
 <img tabindex=1 alt="Dell Latitude E6400" class="p" src="https://av.canoeboot.org/e6400/e6400-seabios.jpg" /><span class="f"><img src="https://av.canoeboot.org/e6400/e6400-seabios.jpg" /></span> <img tabindex=1 alt="Dell Latitude E6400 XFR" class="p" style="max-width:24em" src="https://av.canoeboot.org/e6400/e6400xfr-seabios.jpg" /><span class="f"><img src="https://av.canoeboot.org/e6400/e6400xfr-seabios.jpg" /></span>

site/docs/maintain/index.md

@@ -60,6 +60,40 @@ build system itself, to make your own private modifications or even release
 your own coreboot distro (based upon Canoeboot - and you have this freedom
 with Libreboot too). Many choices are available!
 
+Environmental variables
+=======================
+
+LBMK\_THREADS
+-------------
+
+For example:
+
+       export LBMK_THREADS=2
+
+This would build on two threads, when running cbmk. It defaults to 1.
+
+Previous revisions of cbmk used `nproc` by default, but this was set to 1
+instead, because nproc is not available on every operating system.
+
+LBMK\_STATUS
+------------
+
+By default, the user is asked to confirm when building for a given mainboard,
+if that mainboard is not marked *stable* in `target.cfg`. To disable such
+dialogs, do this:
+
+       export LBMK_STATUS=n
+
+LBMK\_RELEASE
+-------------
+
+If set to `y`, it signals to `script/build/roms` that a release is being built,
+and it will honour `release="n"` in target.cfg files. You could also set this
+yourself, when doing regular builds, if you wanted to test how `./build roms`
+behaves running it in release mode. Do this if you want to:
+
+       export LBMK_RELEASE=y
+
 Best practises for learning cbmk
 ================================