libreboot / lbwww (public) (License: Unspecified) (since 2023-04-11) (hash sha1)
libreboot website (markdown files). https://libreboot.org/
List of commits:
Subject Hash Author Date (UTC)
docs/build: notes about release status e647adc841e00fcf891b1b46808f05d4e8d4beb9 Leah Rowe 2024-05-01 05:07:51
document dell latitude thermal safety paranoia 67770346e26c52f20c3a5d450c540f2b249e2975 Leah Rowe 2024-05-01 04:53:28
update docs/maintain/ based on lbmk changes dc7d5cef900fbe3c58c55ed4966ab1c25e91d552 Leah Rowe 2024-05-01 04:40:30
remove redundant/finished tasks from todo b716e3feddb118365a99909c2abe851ca6536fff Leah Rowe 2024-04-27 00:47:10
hp8560w: wlan doesn't work 128d9e6094255a439f88703e0e49adae2b43302b Riku Viitanen 2024-04-16 23:12:15
post-release correction e0400031b95252f7ae44d99ac9cde12ba157df93 Leah Rowe 2024-04-16 13:29:09
change 820 links 20e2f572fb88d78e8979ba86bfdfd29eea226b98 Leah Rowe 2024-04-15 20:19:02
further note about qubes on 9020 b47f09e497525dca2317d1652f9a73fb8ca94664 Leah Rowe 2024-04-11 11:09:54
9020: note about iommu enablement for gfxcards 14f649771fb422d6f9c3f0bc051d4698a400f5e1 Leah Rowe 2024-04-11 11:05:04
context 240bfc950eda66a63b94d2a6080d466c284b3e48 Leah Rowe 2024-03-27 02:10:03
fix oversight caused by search and replace 2080975e953415019899668ffc7cf8c45fe75bd1 Leah Rowe 2024-03-22 11:20:23
note about w540 compatibility b1f3b1b4a6f6dca00dbcb11ac523c3b8420f383c Leah Rowe 2024-03-22 06:35:37
fix wrong info (9020 doesn't have SOIC-16) 0f56d4ce9116a4bf81a99dfc0e35819d753d6710 Leah Rowe 2024-03-14 12:06:02
docs/install/spi: note about wson8 probes 51c06dcae2594be1c80f7086f7d22677e527d47c Leah Rowe 2024-03-06 22:37:55
tasks: ideas about testing 5e1ca595cd8e8c7501ef8538001327ac76814522 Riku Viitanen 2024-03-01 20:16:13
fix the x60/t60 flashing instructions 01c11b27d97d581f6e62b7059c986dec65254182 Leah Rowe 2024-02-27 18:17:49
oversight ef8c2a7e59449f41bbf88b5cb57c22b0a8fbf756 Leah Rowe 2024-02-25 20:52:36
more context ad4e593dbfa759ab91da4ed71dcfbbb815b3d407 Leah Rowe 2024-02-25 20:31:39
remove unnecessary information 0a9bf4aa84eba77a728d42b6f6fbc3b7e3c4dd9b Leah Rowe 2024-02-25 20:27:57
correction d4886e608d6de0898b53543413985e751dcc9ea2 Leah Rowe 2024-02-25 19:42:08
Commit e647adc841e00fcf891b1b46808f05d4e8d4beb9 - docs/build: notes about release status
Signed-off-by: Leah Rowe <info@minifree.org>
Author: Leah Rowe
Author date (UTC): 2024-05-01 05:07
Committer name: Leah Rowe
Committer date (UTC): 2024-05-01 05:07
Parent(s): 67770346e26c52f20c3a5d450c540f2b249e2975
Signer:
Signing key:
Signing status: N
Tree: 1fcbebedb53074e636a9a5f01de4febdb4fc4d08
File Lines added Lines deleted
site/docs/build/index.md 33 0
site/docs/build/index.uk.md 41 0
File site/docs/build/index.md changed (mode: 100644) (index 2309237..c638d15)
... ... libreboot from the available source code.
25 25 The following document describes how `lbmk` works, and how you can make changes The following document describes how `lbmk` works, and how you can make changes
26 26 to it: [libreboot maintenance manual](../maintain/) to it: [libreboot maintenance manual](../maintain/)
27 27
28 Release status
29 ==============
30
31 Information about status will be reported during builds; if a board is
32 marked as stable, the build proceeds without further input. If the board is
33 marked anything other, a warning appears asking if you wish to proceed; to
34 disable these warnings, do this before building (not recommended):
35
36 export LBMK_STATUS=n
37
38 In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`.
39 The "unstable" marking means that the board boots mostly/entirely reliably
40 annd should be safe to use, but may have a few issues, but nothing which would,
41 for example, cause safety issues e.g. thermal, data reliability etc.
42
43 The `broken` setting means that a given board will likely brick if flashed.
44 The `untested` setting means untested.
45
46 Release status is always set with regards to the current lbmk revision, on
47 the theory that the current revision is being used to generate a full release.
48 The setting is decided on a board-by-board basis, taking its various quirks
49 and idiosynrasies into account.
50
51 Multi-threaded builds
52 =====================
53
54 Libreboot's build system defaults to a single build thread, but you can change
55 it by doing e.g.
56
57 export LBMK_THREADS=4
58
59 This would make lbmk run on 4 threads.
60
28 61 Environmental variables Environmental variables
29 62 ======================= =======================
30 63
File site/docs/build/index.uk.md changed (mode: 100644) (index 72f97cc..69826da)
... ... libreboot з доступного джерельного коду.
35 35 Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни
36 36 до нього: [керівництво обслуговування libreboot](../maintain/) до нього: [керівництво обслуговування libreboot](../maintain/)
37 37
38 Release status
39 ==============
40
41 Information about status will be reported during builds; if a board is
42 marked as stable, the build proceeds without further input. If the board is
43 marked anything other, a warning appears asking if you wish to proceed; to
44 disable these warnings, do this before building (not recommended):
45
46 export LBMK_STATUS=n
47
48 In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`.
49 The "unstable" marking means that the board boots mostly/entirely reliably
50 annd should be safe to use, but may have a few issues, but nothing which would,
51 for example, cause safety issues e.g. thermal, data reliability etc.
52
53 The `broken` setting means that a given board will likely brick if flashed.
54 The `untested` setting means untested.
55
56 Release status is always set with regards to the current lbmk revision, on
57 the theory that the current revision is being used to generate a full release.
58 The setting is decided on a board-by-board basis, taking its various quirks
59 and idiosynrasies into account.
60
61 Multi-threaded builds
62 =====================
63
64 Libreboot's build system defaults to a single build thread, but you can change
65 it by doing e.g.
66
67 export LBMK_THREADS=4
68
69 This would make lbmk run on 4 threads.
70
71 Environmental variables
72 =======================
73
74 Please read about environmental variables in [the build
75 instructions](../maintain/), before running lbmk. You should set
76 your variables accordingly, though you do not technically need to; some
77 of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
78
38 79 Environmental variables Environmental variables
39 80 ======================= =======================
40 81
Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/libreboot/lbwww

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/libreboot/lbwww

Clone this repository using git:
git clone git://git.rocketgit.com/user/libreboot/lbwww

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main