libreboot / lbwww (public) (License: Unspecified) (since 2023-04-11) (hash sha1)
libreboot website (markdown files). https://libreboot.org/
Clone URLs: https://rocketgit.com/user/libreboot/lbwww ssh://rocketgit@ssh.rocketgit.com/user/libreboot/lbwww git://git.rocketgit.com/user/libreboot/lbwww
25.04 master
List of commits:
Subject Hash Author Date (UTC)
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
oversight e2ce9110fbec611f0138a72a634f5bb1927ec1d5 Leah Rowe 2024-02-25 19:20:49
Libreboot 20240225 a12f3efde70dc6f3fc4eebf966c3d32de1a3067f Leah Rowe 2024-02-25 19:14:34
Commit dc7d5cef900fbe3c58c55ed4966ab1c25e91d552 - update docs/maintain/ based on lbmk changes
Signed-off-by: Leah Rowe <info@minifree.org>
Author: Leah Rowe
Author date (UTC): 2024-05-01 04:40
Committer name: Leah Rowe
Committer date (UTC): 2024-05-01 04:40
Parent(s): b716e3feddb118365a99909c2abe851ca6536fff
Signer:
Signing key:
Signing status: N
Tree: 2e1adabb100132227e5d62411077f83fd416f4e1
File Lines added Lines deleted
site/docs/build/index.md 8 0
site/docs/build/index.uk.md 8 0
site/docs/maintain/index.md 63 19
File site/docs/build/index.md changed (mode: 100644) (index d2ea655..2309237)
... ... 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 Environmental variables
29 =======================
30
31 Please read about environmental variables in [the build
32 instructions](../maintain/), before running lbmk. You should set
33 your variables accordingly, though you do not technically need to; some
34 of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
35
28 36 Sources Sources
29 37 ======= =======
30 38
File site/docs/build/index.uk.md changed (mode: 100644) (index ab56c08..72f97cc)
... ... libreboot з доступного джерельного коду.
35 35 Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни
36 36 до нього: [керівництво обслуговування libreboot](../maintain/) до нього: [керівництво обслуговування libreboot](../maintain/)
37 37
38 Environmental variables
39 =======================
40
41 Please read about environmental variables in [the build
42 instructions](../maintain/), before running lbmk. You should set
43 your variables accordingly, though you do not technically need to; some
44 of them may be useful, e.g. `LBMK_THREADS` (sets the number of build threads).
45
38 46 Git Git
39 47 === ===
40 48
File site/docs/maintain/index.md changed (mode: 100644) (index 5cd09ff..82ac95e)
... ... the [freedom status page](../../freedom-status.md).
85 85 Before *configuration* info, you will first be shown a brief overview of every Before *configuration* info, you will first be shown a brief overview of every
86 86 project that Libreboot imports, such as coreboot. project that Libreboot imports, such as coreboot.
87 87
88 Environmental variables
89 =======================
90
91 LBMK\_THREADS
92 -------------
93
94 For example:
95
96 export LBMK_THREADS=2
97
98 This would build on two threads, when running lbmk. It defaults to 1.
99
100 Previous revisions of lbmk used `nproc` by default, but this was set to 1
101 instead, because nproc is not available on every operating system.
102
103 LBMK\_STATUS
104 ------------
105
106 By default, the user is asked to confirm when building for a given mainboard,
107 if that mainboard is not marked *stable* in `target.cfg`. To disable such
108 dialogs, do this:
109
110 export LBMK_STATUS=n
111
112 LBMK\_RELEASE
113 -------------
114
115 If set to `y`, it signals to `script/build/roms` that a release is being built,
116 and it will honour `release="n"` in target.cfg files. You could also set this
117 yourself, when doing regular builds, if you wanted to test how `./build roms`
118 behaves running it in release mode. Do this if you want to:
119
120 export LBMK_RELEASE=y
121
122 This has a similar effect compared to `LBMK_STATUS="y"` but you probably don't
123 need to use this option yourself.
124
88 125 Projects/files downloaded/generated by lbmk Projects/files downloaded/generated by lbmk
89 126 =========================================== ===========================================
90 127
 
... ... This file can contain several configuration lines, each being a string, such
530 567 as: as:
531 568
532 569 * `tree="default"` (example entry) * `tree="default"` (example entry)
533 * `romtype="normal"` (example entry)
534 570 * `rev="ad983eeec76ecdb2aff4fb47baeee95ade012225"` (example entry) * `rev="ad983eeec76ecdb2aff4fb47baeee95ade012225"` (example entry)
535 * `arch="x86_64"` (example entry)
571 * `xarch="i386-elf"` (example entry)
536 572 * `payload_grub="y"` (example entry) * `payload_grub="y"` (example entry)
537 573 * `payload_grub_withseabios="y"` (example entry) * `payload_grub_withseabios="y"` (example entry)
538 574 * `payload_seabios="y"` (example entry) * `payload_seabios="y"` (example entry)
 
... ... as:
542 578 * `payload_seabios_grubonly="y"` (example entry) * `payload_seabios_grubonly="y"` (example entry)
543 579 * `grub_scan_disk="ata"` * `grub_scan_disk="ata"`
544 580 * `uboot_config=default` (specify which U-Boot tree to use) * `uboot_config=default` (specify which U-Boot tree to use)
545 * `vendorfiles="n"`
546 * `microcode_required="y"`
581 * `release="n"` (example entry)
582 * `status=stable`
547 583
548 584 The `tree` value refers to `config/coreboot/TREE`; in other words, a given The `tree` value refers to `config/coreboot/TREE`; in other words, a given
549 585 target could specify a name other than its own as the tree; it would then target could specify a name other than its own as the tree; it would then
550 586 re-use code from that tree, rather than providing its own. re-use code from that tree, rather than providing its own.
551 587
552 The `romtype` entry is used during the building of ROM images, to define
553 special steps; for example, d8d16sas` would tell lbmk that a fake PIKE2008
554 ROM must be inserted into CBFS (prevents hanging on SeaBIOS).
555
556 588 The `rev` entry defines which coreboot revision to use, from the The `rev` entry defines which coreboot revision to use, from the
557 589 coreboot Git repository. *At present, lbmk only supports use of the official coreboot Git repository. *At present, lbmk only supports use of the official
558 590 repository from the upstream coreboot project*. repository from the upstream coreboot project*.
559 591
560 The `arch` entry specifies which CPU architecture is to be used: currently
561 recognized entries are `x86_32`, `x86_64`, `ARMv7` and `AArch64`. *Setting it
562 to a non-native arch means that necessary crossgcc-arch will be compiled and be
563 available when building roms, but not necessarily built or discovered when
564 individual scripts are called manually.*
592 The `xarch` entry specifies which CPU architecture is to be used: currently
593 recognized entries are `i386-elf`, `arm-eabi` and `aarch64-elf`. This is the
594 target architecture for building GCC/toolchain from coreboot crossgcc,
595 hence `xarch`.
565 596
566 597 The `payload_grub` entry specifies whether or not GRUB is to be included in The `payload_grub` entry specifies whether or not GRUB is to be included in
567 598 ROM images. ROM images.
 
... ... on a ThinkPad X60 with the optical drive may cause GRUB to hang, so on that
600 631 machine it is advisable to set this option to `ahci` (becuse the default HDD machine it is advisable to set this option to `ahci` (becuse the default HDD
601 632 slot is AHCI). slot is AHCI).
602 633
603 The `vendorfiles` entry doesn't affect anything in code, except that
604 the `noblobs` string will be appended to ROM image file names, on releases;
605 ditto `nomicrocode` but in that case, the behaviour is: if no microcode to
606 begin with, only `nomicrocode` images will be named, otherwise ROM images with
607 and without microcode updates will be provided in releases (CPU microcode
608 updates).
634 The `release` variable can be set to n, which makes the `script/update/release`
635 script skip that target, when creating release images. For example, a given
636 board may not be stable and you don't want images for it to be included in the
637 release.
638
639 The `status` variable can be set to whatever you want, but anything other
640 than `stable` will make `script/build/roms` ask for y/n confirmation if
641 not building images using `script/update/release`.
642
643 Recommended strings for `status` could be: `stable`, `unstable`, `broken`
644 or `untested`. Alternatively, you might state `wip`. You can set whatever
645 string you want here.
646
647 ### config/coreboot/BOARDNAME/warn.txt
648
649 Additionally: the `warn.txt` file can be included alongside target.cfg, to
650 provide warning of any potential issues or quirks. For example, raminit may
651 only be reliable with certain modules. This is printed on the user's terminal
652 when building that target.
609 653
610 654 ### config/coreboot/BOARDNAME/config/ ### config/coreboot/BOARDNAME/config/
611 655
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