updates

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

site.cfg

@@ -1,5 +1,5 @@
-TITLE="-T Libreboot"
+TITLE="Libreboot"
 DOMAIN="https://libreboot.org/"
 BLOGDIR="news/" # leave as empty string if you want the blog to be the homepage
-CSS="--css /global.css"
+CSS="/global.css"
 LAZY="y"

site/contact.de.md

@@ -3,7 +3,19 @@ title: Kontakt
 x-toc-enable: true
 ...
 
-**TODO: mailing lists, mastodon server and peertube account.**
+Buy Libreboot pre-installed
+==========
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+If you're installing Libreboot yourself, support for that is also available.
+Contact information (IRC, mailing list etc) is below:
 
 User support
 ============
@@ -11,10 +23,18 @@ User support
 IRC oder Reddit werden bevorzugt, sofern Du eine Support Anfrage hast (IRC empfohlen).
 Für Informationen bzgl. IRC and Reddit siehe unten.
 
+Mailing list
+============
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
 Entwicklungs Diskussion
 ======================
 
-Eine Mailing Liste ist für die Zukunft in Planung. Bis dahin, siehe unter
+Siehe unter
 [der Git Seite](git.md) für Informationen wie Du dich an der Entwicklung beteiligen kannst.
 
 Hier finden sich ebenso Anleitungen zum Senden von Patches (via Pull-Requests).

site/contact.it.md

@@ -0,0 +1,98 @@
+---
+title: Contatti
+x-toc-enable: true
+...
+
+Buy Libreboot pre-installed
+==========
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+If you're installing Libreboot yourself, support for that is also available.
+Contact information (IRC, mailing list etc) is below:
+
+Supporto utenti
+===============
+
+IRC o Reddit sono consigliati, sebbene preferiamo che usi il canale IRC
+per avere o per offrire supporto tecnico. Continua a leggere per avere
+ulteriori informazioni.
+
+Mailing list
+============
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
+Discussione sullo sviluppo
+==========================
+
+Per ora dai un occhiata sulla
+[pagina Git](git.md) per avere maggiori informazioni su come puoi
+assistere con lo sviluppo.
+
+Su quella stessa pagina puoi trovare informazioni su come inviare
+correzioni (patches) tramite pull requests.
+
+Canale IRC
+==========
+
+IRC e' il modo principale per contattare chi collabora con il progetto libreboot.
+Il canale ufficiale e' `#libreboot` su Libera IRC.
+
+Webchat:
+<https://web.libera.chat/#libreboot>
+
+Libera e' una tra le piu' grandi reti IRC usate per i progetti di software libero.
+Maggiori informazioni le trovi qui: <https://libera.chat/>
+
+Puoi usare il client IRC che preferisci (come weechat or irssi) usando le seguenti informazioni:
+
+* Server: `irc.libera.chat`
+* Canale: `#libreboot`
+* Porta (TLS): `6697`
+* Porta (non-TLS): `6667`
+
+Ti suggeriamo di usare la porta `6697` e ablitare la cifratura TLS...
+
+Inoltre ti suggeriamo di abilitare l'autenticazione SASL. Le pagine web
+di Libera spiegano come:
+
+* Guida per WeeChat: <https://libera.chat/guides/weechat>
+* Guida per Irssi: <https://libera.chat/guides/irssi>
+* Guida per HexChat: <https://libera.chat/guides/hexchat>
+
+Comunque dovresti sempre controllare la documentazione del tuo client IRC preferito.
+
+Reti sociali online
+===================
+
+Libreboot esiste ufficialmente in molte piattaforme.
+
+Mastodon
+--------
+
+Il fondatore e sviluppatore principale, Leah Rowe, e' su Mastodon:
+
+* <https://mas.to/@libreleah>
+
+Posta elettronica
+-----------------
+
+Leah puo' essere contattata anche via email a questo indirizzo:
+[leah@libreboot.org](mailto:leah@libreboot.org)
+
+Reddit
+------
+
+Usato principalmente come canale di supporto e per annunciare notizie:
+<https://www.reddit.com/r/libreboot/>
+

site/contact.md

@@ -3,7 +3,19 @@ title: Contact
 x-toc-enable: true
 ...
 
-**TODO: mailing lists, mastodon server and peertube account.**
+Buy Libreboot pre-installed
+==========
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+If you're installing Libreboot yourself, support for that is also available.
+Contact information (IRC, mailing list etc) is below:
 
 User support
 ============
@@ -11,10 +23,18 @@ User support
 IRC or Reddit are recommended, if you wish to ask for support (IRC recommended).
 See below for information about IRC and Reddit.
 
+Mailing list
+============
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
 Development discussion
 ======================
 
-Mailing lists are planned for the future. For now, see notes
+See notes
 on [the Git page](git.md) for information about how to assist with development.
 
 Instructions are also on that page for sending patches (via pull requests).

site/contact.uk.md

@@ -3,7 +3,19 @@ title: Зв'язок
 x-toc-enable: true
 ...
 
-**TODO: списки розсилки, сервер mastodon та обліковий запис peertube.**
+Buy Libreboot pre-installed
+==========
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+If you're installing Libreboot yourself, support for that is also available.
+Contact information (IRC, mailing list etc) is below:
 
 Підтримка користувачів
 ============
@@ -11,10 +23,18 @@ x-toc-enable: true
 IRC або Reddit рекомендовані, якщо ви бажаєте попросити про допомогу (найкраще IRC).
 Дивіться інформацію нижче щодо IRC та Reddit.
 
+Mailing list
+============
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
 Обговорення розробки
 ======================
 
-Списки розсилки плануються на майбутнє. Зараз, подивіться нотатки
+Зараз, подивіться нотатки
 на [сторінці Git](git.md) для інформації щодо допомоги з розробкою.
 
 На цій сторінці також знаходяться інструкції по відправці патчів (через pull request'и).

site/contrib.md

@@ -196,33 +196,13 @@ systems.
 Joshua Gay
 ----------
 
-Joshua is former FSF staff.
+Joshua was in a position during 2014-2016 to help promote Libreboot in the
+media, in his capacity working for the employer he worked for at the time;
+I credit him specifically. Joshua was one of Libreboot's earliest supporters.
 
-Joshua helped with the early founding of the Libreboot project, in his capacity
-(at that time) as the FSF's licensing and compliance manager. It was his job to
-review products sent into to the FSF for review; the FSF has a certification
-program called *Respects Your Freedom* (RYF) where the FSF will promote your
-company's products if it comes with all Free Software.
-
-I, Leah Rowe, was initially just selling ThinkPad X60 laptops with regular
-coreboot on them, and this included CPU microcode updates. At the time, I didn't
-think much of that. Joshua contacted me, in his capacity at the FSF, and asked
-if I would be interested in the FSF's RYF program; I was very surprised that the
-FSF would take me seriously, and I said yes. This is what started the early
-work on Libreboot. Joshua showed me all the problems my products had, and from
-that, the solution was clear:
-
-Joshua used his media connections at the FSF to heavily promote my work, and
-on December 13th, 2013, the Libreboot project was born (but not called that).
-Joshua made sure that everyone knew what I was doing!
-
-A few months later, the name *Libreboot* was coined, and the domain name
-*libreboot.org* was registered. At that point, the Libreboot project (in early
-2014) was officially born. Once again, Joshua provided every bit of help he
-could, heavily promoting the project and he even wrote this article on the FSF
-website, announcing it:
-
-<https://web.archive.org/web/20171222063358/https://www.fsf.org/blogs/licensing/replace-your-proprietary-bios-with-libreboot>
+He made sure everyone knew what I was doing, and he taught me a *lot* about
+licensing; many of Libreboot's practises today are still based on his lessons,
+such as the pitfalls of GPL compliance and how to really audit everything.
 
 Klemens Nanni
 -------------
@@ -233,55 +213,28 @@ libreboot, and several tweaks to the build system.
 Lisa Marie Maginnis
 -------------------
 
-Lisa is a former sysadmin at the Free Software Foundation. In the early days of
-the project, she provided Leah with a lot of technical advice. She initially
-created Libreboot IRC channel, when Leah did not know how to
-use IRC, and also handed +F founder status to Leah for the channel. As an FSF
-sysadmin, it was Lisa's job to maintain a lot of the infrastructure used by
-Libreboot; at the time, mailing lists on the Savannah website were used by
-the Libreboot project. When Paul Kocialkowski was a member of the project in
-2016, she helped him get help from the FSF; he was the leader of the Replicant
-project at the time, which had funding from the FSF, and the FSF authorized him
-to use some of that funding for his work on Libreboot, thanks to Lisa's
-encouragement while she worked at the FSF.
+Lisa was one of Libreboot's early contributors to Libreboot. She personally
+helped me set up a lot of the early infrastructure, including things like IRC,
+mailing list and so on. She provided a lot of technical guidance, while working
+in a sysadmin job for a certain free software organisation; she was both a
+mentor and a friend.
 
-Lisa also stepped in when Leah Rowe missed her LibrePlanet 2016 talk. Leah was
-scheduled to do a talk about Libreboot, but didn't show up in time. Lisa, along
-with Patrick McDermott (former Libreboot developer, who was present at that
-conference) did the talk in Leah's place. The talk was never recorded, but the
-Free Software Foundation has these photos of that talk on their LibrePlanet
-website (the woman with the blue hair is Lisa, and the long-haired dude with the
-moustache is Patrick):
+She got me in touch with a lot of people, and at one point was instrumental in
+helping Paul Kocialkowski secure funding to work on the Veyron Speedy boards
+in Libreboot, e.g. ASUS Chromebook C201PA - at the time, this was using
+Google's own Depthcharge payload, which you can find in 2016 Libreboot
+releases.
 
-<http://web.archive.org/web/20170319043913/https://media.libreplanet.org/u/libreplanet/m/session-02-c-mws-png-libreplanet-2016-sessions/>
+Lorenzo Aloe
+------------
 
-<http://web.archive.org/web/20170319043915/https://media.libreplanet.org/u/libreplanet/m/session-02-c-wide-png-libreplanet-2016-sessions/>
+Provided hardware testing for the [Dell OptiPlex 9020](docs/hardware/dell9020.md),
+also provided testing for proxmox with GPU passthrough on Dell Precision T1650,
+confirming near-native performance; with this, you can boot operating systems
+virtually natively, performance-wise, on a Libreboot system in cases where
+that OS is not natively supported.
 
-Fun fact: Patrick is also the lead developer of ProteanOS, an FSF-endorsed
-embedded OS project: <http://proteanos.com/> (uses BusyBox and Linux-libre)
-
-Leah Rowe ran *2* LibrePlanet workshops; one in 2015 and another in 2016, while
-visiting Boston, MA, USA on both occasions to attend these conferences. These
-workshops were for Libreboot installations. People came to both workshops, to
-have Libreboot installed onto their computers. As FSF sysadmin, at that time,
-Lisa provided all of the infrastructure and equipment used at those workshops.
-Without her help, those workshops would have not been possible.
-
-When the ASUS KGPE-D16 mainboard (high-end server board) was ported to Libreboot,
-Leah, working with Timothy Pearson (the one who ported it), shared patches back
-and forth with Lisa around mid 2016, mostly raminit patches, to get the board
-running at the FSF offices. This work ultimately lead to a most wonderful
-achievement:
-
-The FSF and GNU websites now run on
-Librebooted ASUS KGPE-D16 based servers, on a fully free GNU+Linux distro. This
-means that the FSF now has full software freedom for their hosting infrastructure.
-
-The FSF also provides access to this infrastructure for many other projects
-(besides GNU projects).
-
-Lisa was a strong supporter of Libreboot in the very early days of the project,
-and her contributions were invaluable. I, Leah Rowe, owe her a debt of gratitude.
+All round good guy, an honest and loyal fan.
 
 Marcus Moeller
 --------------
@@ -305,10 +258,6 @@ relating to the [Intel Management Engine](../faq.md#intelme), in addition
 to making several improvements to the build system in libreboot. **Former
 libreboot project maintainer.**
 
-In 2016, Leah Rowe ran a Libreboot installation workshop at the FSF's
-LibrePlanet conference. Working alongside Leah, Patrick helped run the workshop
-and assisted with installing Libreboot onto people's machines.
-
 Paul Kocialkowski
 -----------------
 
@@ -337,6 +286,8 @@ Helped write the [FAQ section about DMA](../faq.md#hddssd-firmware), and provide
 general advice in the early days of the project. Peter was a coreboot developer
 in those days, and a major developer in the *libusb* project (which flashrom
 makes heavy use of).
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024.
 
 Peter also wrote the *bucts* utility used to set Backup Control (BUC) Top Swap
 (TS) bit on i945 laptops such as ThinkPad X60/T60, which is useful for a

site/contrib.uk.md

@@ -1,454 +0,0 @@
----
-title: Учасники проекту
-x-toc-enable: true
-...
-
-У цьому списку не обов'язково вказується, хто зараз працює над проектом,
-але в ньому вказано людей, які зробили значний внесок у проект.
-
-Якщо ми забули вас тут згадати, повідомте нам, і ми вас додамо. (або якщо
-ви не хочете, щоб вас згадували, повідомте нас, і ми видалимо ваш
-запис)
-
-Інформацію про те, хто працює над libreboot і як працює проект, можна
-знайти на цій сторінці: [who.md](who.md)
-
-Ви можете дізнатися історію проекту libreboot, просто прочитавши цю сторінку.
-Тут докладно розповідається про всі основні внески в проект і
-загалом про те, як створювався проект (і хто допоміг його створити).
-
-Лія Роу
----------
-
-**Засновник проекту Libreboot, а зараз провідний розробник** Лія
-працює над усіма аспектами libreboot, такими як:
-
-* Загальне керівництво. Лія обробляє всі зовнішні внески до libreboot,
-  переглядає пул реквести, має справу із звітами про помилки, делегує завдання, коли це необхідно
-  або бажано. Лія контролює серверну інфраструктуру libreboot.org, розміщену
-  в її лабораторії.
-* Лія має останнє слово щодо всіх рішень, беручи внесок через обговорення з
-  представниками громадськості, переважно на IRC. Лія контролює випуски libreboot
-  і загалом підтримує проект. Без Лії не було би Libreboot!
-* Система збірки (lbmk, скорочення від libreboot Make). Це автоматизована
-  система збирання, яка лежить в серці libreboot; він завантажує, патчить, налаштовує
-  та компілює відповідні компоненти, такі як coreboot, GRUB, і генерує образи ROM
-  libreboot, які ви можете знайти в архівах випусків.
-* Апстрім робота над coreboot, коли необхідно (та іншими проектами, які libreboot
-  використовує). Це також означає роботу з людьми поза межами проекту libreboot,
-  щоб об'єднати виправлення (між іншим) в апстрім проектах,
-  які libreboot використовує
-* Надання підтримки користувачів на IRC
-
-Калеб Ла Гранж
----------------
-
-**Вторинний розробник, номер два для Лії.** Калеб - розробник libreboot на повний робочий день
-з вузьким фокусом. Калеб зосереджується на кількох напрямках розвитку:
-
-* Система побудови. Калеб відповідає за вдосконалення та виправлення системи побудови libreboot Make.
-Зокрема, управління бінарними блобами, автоматизація та відтворюваність. 
-* Апаратна модифікація. Калеб має пристрасть до переробки апаратного забезпечення; паяння,
-розпаювання, та тестування libreboot на отриманому обладнанні.
-* Перенесення плати. Все, що підтримується в Coreboot, можна перенести на libreboot, Калеб
-перевірить і перенесе будь-яку плату, до якої зможе потрапити. Крім того, будь-хто може
-зв'язатись з Калебом, щоб створити образи libreboot для тестування на своїй платі.
-* Документація. Калеб активно веде документацію щодо зазначених вище сфер
-інтересу. Додатково, Калеб відповідає за посібники з розбирання з власними
-малюнками та діаграмами для кількох плат.
-* Підтримка користувачів. Калеб активний в irc і готовий допомогти будь-якому користувачеві, який зацікавлений в
-використанні libreboot або потребує допомоги.
-* Цілі проекту. Калеб співпрацює з Лією над визначенням цілей проекту.
-Лія має останнє слово в кожному рішенні.
-
-Зовнішні проекти
-================
-
-Проект Coreboot
-----------------
-
-Без coreboot проект libreboot був би просто неможливий.
-
-Людей і компаній, які працюють над coreboot, багато, і вони роблять
-проект libreboot таким, яким він є. Проект libreboot активно використовує coreboot
-для ініціалізації обладнання.
-
-GRUB
---------
-
-GRUB - це завантажувач, який використовується libreboot. Само собою зрозуміло, що
-розробники GRUB стимулюють libreboot своєю роботою.
-
-SeaBIOS
--------
-
-Прошивка libreboot надає SeaBIOS як опцію корисного навантаження. SeaBIOS забезпечує
-застарілу реалізацію BIOS x86.
-
-U-Boot
-------
-
-Libreboot використовує U-Boot як корисне навантаження coreboot на ноутбуках
-ARM Chromebook з підтримкою coreboot.
-
-Внески в алфавітному порядку
-============================
-
-Алісса Розенцвейг
------------------
-
-Переключила веб-сайт на використання розмітки замість рукописного HTML та користувацького
-PHP. **Колишній супроводжувач проекту libreboot (системний адміністратор libreboot.org).**
-
-Алісса написала оригінальний генератор статичних сайтів (скрипти `sh`, що перетворюють
-markdown в html, через pandoc) для libreboot.org. Цей генератор статичних сайтів
-був значно змінений і відгалужений Лією Роу у формальний проект:
-
-<https://untitled.vimuser.org/> (untitled - це робота Лії, а не Алісси, але вона базується на
-оригінальній роботі Аліси над генератором статичних сайтів, який раніше використовував Libreboot;
-веб-сайт Libreboot тепер створено за допомогою Untitled)
-
-Альпер Небі Ясак
-----------------
-
-Надав інтеграцію системи збірки та документацію для використання
-U-Boot в якості корисного навантаження, та початкові порти Libreboot деяких ARM Chromebook
-виходячи з того.
-
-Альпер також займається розробкою на U-Boot, напр. продовжив майже завершений
-порт плати `gru-kevin` і об'єднав його з апстрімом.
-
-Артур Хейманс
---------------
-
-Об'єднав патч із coreboot у libreboot, дозволяючи режимам живлення C3 та C4
-правильно працювати на ноутбуках GM45. Це була давня проблема до внеску
-Артура. Артур також виправив розмір відеопам'яті на i945 на системах
-GM45, що дозволило максимально розподілити VRAM для вбудованих графічних процесорів
-у цих системах, ще одна давня проблема в libreboot.
-
-Артур також працював над системою збірки Libreboot, коли він був учасником
-проекту. Він досі працює над coreboot, і Libreboot отримує велику
-користь від його роботи. Його внесок у проект coreboot і Libreboot
-неоціненний.
-
-Володимир Сербіненко
--------------------
-
-Перенес багато thinkpad, які підтримуються в libreboot, на coreboot, а
-також зробив багато виправлень у coreboot, які принесли користь проекту libreboot.
-
-Володимир написав багато вихідного коду ініціалізації відео, який використовується різними
-платформами Intel у Libreboot, під час прошивки (зараз переписаний
-іншими в Ada, для libgfxinit в coreboot, але спочатку він був написаний на
-C і включений безпосередньо в coreboot; libgfxinit є субмодуль третьої сторони).
-
-Демієн Замміт
--------------
-
-Підтримує порт coreboot Gigabyte GA-G41M-ES2L, інтегрований у
-libreboot. Також працює над іншим апаратним забезпеченням на користь
-проекту libreboot.
-
-Демієн не працював безпосередньо над самим Libreboot, але він багато працював з
-Лією Роу, інтегруючи патчі та нові порти плати в Libreboot на основі
-попередньої роботи Демієна над coreboot.
-
-Денис Каріклі
--------------
-
-На основі роботи, виконаної Пітером Стюджем, Володимиром Сербіненко та іншими
-в проекті coreboot, вдалось налагодити нативну ініціалізацію графіки для роботи
-на ThinkPad X60, що дозволяє підтримувати її в libreboot. Денис дав
-багато порад і допоміг створити проект libreboot.
-
-Денис був наставником Лії Роу в ранні дні, коли вона заснувала проект
-Libreboot. Багато прийнятих рішень, особливо щодо системи збірки
-Libreboot (lbmk), були натхненні розмовами з Денисом.
-
-Денис навчив Лію про регістри, які використовуються графічним процесором Intel для керування підсвічуванням.
-В ранні дні, ноутбуки ThinkPad X60 та T60 в Libreboot не мали працюючого
-контроля підсвічуванням, тому яскравість завжди була 100%. За допомогою Дениса,
-Лія змогла налаштувати керування підсвічуванням шляхом зворотньої розробки
-правильних значень для запису в ці регістри. На основі цього в coreboot
-було написано просте виправлення; однак виправлення перезаписувало безпосередньо регістр
-і не працювало з елементами керування яскравістю на основі ACPI. Інші в coreboot
-пізніше вдосконалили його, змусивши елементи керування підсвічуванням на основі ACPI працювати належним чином, на основі цієї
-попередньої роботи.
-
-Джерун Квінт
-------------
-
-Додав кілька виправлень до документації libreboot, пов'язаної зі
-встановленням Arch з повним дисковим шифруванням у системах libreboot.
-
-Джошуа Гей
-----------
-
-Джошуа колишній співробітник FSF.
-
-Джошуа допоміг із раннім заснуванням проекту Libreboot, будучи
-(на той час) менеджером з ліцензування та відповідності FSF. Його роботою було
-переглядати продукти, надіслані до FSF для перевірки; FSF має програму
-сертифікації, під назвою *Поважає Вашу Свободу* (Respects Your Freedom), за якою FSF рекламуватиме
-продукти вашої компанії, якщо вони постачаються з усім вільним програмним
-забезпеченням.
-
-Я, Лія Роу, спочатку просто продавала ноутбуки ThinkPad X60 із звичайним
-coreboot, і це включало оновлення мікрокоду ЦП. У той час
-я не дуже про це думала. Джошуа зв'язався зі мною, в своїх повноваженнях FSF, і спитав,
-чи зацікавить мене програма RYF FSF; Я була дуже здивована, що FSF
-сприйме мене серйозно, і я сказала так. Саме з цього почалася рання робота
-над Libreboot. Джошуа показав мені всі проблеми з моїми продуктами, і з
-цього, рішення було очевидним:
-
-Необхідно, щоб існував проект із повністю вільною версією coreboot без будь-яких
-бінарних блобів. У той час (і це актуально й сьогодні) coreboot не був
-повністю вільним програмним забезпеченням і за замовчуванням постачався з двійковими блобами. Зокрема,
-оновлення мікрокоду ЦП включено за замовчуванням на всіх машинах x86. Працюючи
-з Джошуа, я створила повністю вільну версію coreboot.
-Спочатку він не називався Libreboot, і робота була призначена виключно для моєї
-компанії (на той час вона називалася Gluglug), яку просувала FSF.
-
-Джошуа використовував свої медійні зв'язки в FSF, щоб активно рекламувати мою роботу, і
-13 грудня 2013 року народився проект Libreboot (але не названий так).
-Джошуа переконався, щоб всі знали, що я роблю!
-
-Через кілька місяців було створено назву *Libreboot* і зареєстровано доменне ім'я
-*libreboot.org*. У цей момент офіційно народився проект Libreboot (на початку
-2014 року). Знову Джошуа надав всю можливу допомогу,
-активно просуваючи проект, і навіть написав цю статтю на веб-сайті FSF
-оголосивши про це:
-
-<https://web.archive.org/web/20171222063358/https://www.fsf.org/blogs/licensing/replace-your-proprietary-bios-with-libreboot>
-
-Ендрю Роббінс
---------------
-
-Працював над великими частинами старої системи збірки Libreboot і пов'язаною документацією.
-Ендрю приєднався до проекту Libreboot як штатний розробник у червні 2017,
-до моменту свого відходу в березні 2021 року.
-
-Я, Лія Роу, дуже вдячна Ендрю Роббінсу за його численні внески
-протягом багатьох років.
-
-Клеменс Нанні
--------------
-
-Внесено багато виправлень і покращень у конфігурацію GRUB, яка використовується в
-libreboot, а також кілька змін у системі збірки.
-
-Ліза Марі Магінніс
--------------------
-
-Ліза - колишній системний адміністратор Free Software Foundation. На перших днях
-проекту вона давала Лії багато технічних порад. Спочатку вона створила
-IRC-канал Libreboot, коли Лія не знала, як користуватися
-IRC, а також передала +F статус засновника для каналу. Як системний
-адміністратор FSF, роботою Лізи було підтримувати велику частину інфраструктури,
-яку використовує Libreboot; на той час списки розсилки на веб-сайті Savannah
-використовувалися проектом Libreboot. Коли Пол Коціалковскі був
-учасником проекту в 2016 році, вона допомогла йому отримати допомогу від FSF; на той час він був
-керівником проекту Replicant, який фінансував FSF, і FSF дозволив
-йому використати частину цього фінансування для його роботи над Libreboot, завдяки Лізи
-підтримці, коли вона працювала у FSF.
-
-Ліза також втрутилася, коли Лія Роу пропустила виступ на LibrePlanet 2016. Лія мала
-виступити з доповіддю про Libreboot, але не з'явилася вчасно. Ліза разом
-із Патріком Макдермоттом (колишнім розробником Libreboot, який був присутній
-на тій конференції) виступили замість Лії. Розмова ніколи не була записана, але
-Фонд вільного програмного забезпечення має ці фотографії цієї розмови на веб-сайті LibrePlanet
-(жінка з блакитним волоссям - Ліза, а довговолосий хлопець із вусами -
-Патрік):
-
-<http://web.archive.org/web/20170319043913/https://media.libreplanet.org/u/libreplanet/m/session-02-c-mws-png-libreplanet-2016-sessions/>
-
-<http://web.archive.org/web/20170319043915/https://media.libreplanet.org/u/libreplanet/m/session-02-c-wide-png-libreplanet-2016-sessions/>
-
-Цікавий факт: Патрік також є провідним розробником ProteanOS, проекту вбудованої
-ОС, схваленого FSF: <http://proteanos.com/> (використовує BusyBox і Linux-libre)
-
-Лія Роу провела *2* семінари LibrePlanet; один у 2015 році та інший у 2016 році,
-відвідуючи Бостон, Массачусетс, США в обох випадках для участі в цих конференціях. Ці
-семінари стосувалися встановлення Libreboot. Люди приходили на обидва семінари, щоб
-встановити Libreboot на свої комп'ютери. Як системний адміністратор FSF, на той час,
-Ліза забезпечила всю інфраструктуру та обладнання, яке використовувалося на цих семінарах.
-Без її допомоги ці майстер-класи були б неможливими.
-
-Коли материнська плата ASUS KGPE-D16 (серверна плата високого класу) була перенесена на Libreboot,
-Лія, працюючи з Тімоті Пірсоном (той, хто її переніс),
-приблизно в середині 2016 року поділилася з Лізою виправленнями, в основному виправленнями raminit, щоб отримати плату, яка працює в офісах FSF. Ця робота
-зрештою призвела до чудового досягнення:
-
-Веб-сайти FSF і GNU тепер працюють на, з встановленим Libreboot,
-заснованих на ASUS KGPE-D16 серверах, на повністю вільному GNU+Linux дистрибутиві. Це
-означає, що FSF тепер має повну свободу програмного забезпечення для своєї
-інфраструктури хостингу.
-
-FSF також надає доступ до цієї інфраструктури для багатьох інших проектів
-(крім проектів GNU).
-
-Ліза була сильною прихильницею Libreboot на перших днях проекту,
-і її внесок був неоціненним. Я, Лія Роу, у боргу перед нею.
-
-Маркус Мьоллер
---------------
-
-Зробив логотип libreboot.
-
-Nicholas Chin
--------------
-
-[Ported Dell Latitude E6400 to Libreboot](news/e6400.md).
-
-Патрік "П. Дж." Макдермотт
----------------------------
-
-Патрік також провів багато досліджень і написав розділ поширених запитань libreboot,
-пов'язаний із [Intel Management Engine](../faq.md#intelme), а також зробив кілька покращень у
-системі збірки libreboot. **Колишній супроводжувач проекту
-libreboot.**
-
-У 2016 році Лія Роу провела семінар зі встановлення Libreboot на конференції FSF
-LibrePlanet. Працюючи разом з Лією, Патрік допомагав вести семінар
-та допомагав установлювати Libreboot на комп'ютери людей.
-
-Пітер Стюдж
------------
-
-Допоміг написати [розділ поширених запитань про DMA](../faq.md#hddssd-firmware), та надав
-загальні поради на перших днях проекту. У той час Пітер був розробником coreboot
-і головним розробником проекту *libusb* (який flashrom
-активно використовує).
-
-Пітер також написав утиліту *bucts*, яка використовується для встановлення біта Top Swap
-(TS) для керування резервним копіюванням (BUC) на ноутбуках i945, таких як ThinkPad X60/T60, яка є корисною для
-обхідного шляху для прошивки Libreboot без використання зовнішнього обладнання; на цій машині,
-з Lenovo BIOS, можна перепрошити все, крім головного завантажувального
-блоку, але платформи Intel мають 2 завантажувальні блоки, і ви вказуєте, який із них
-використовувати, встановленням біта TS. Потім ви завантажуєтеся лише з одним прошитим завантажувальним блоком
-(завантажувальним блоком проекту coreboot на цій машині), а потім скидаєте
-bucts перед повторною прошивкою ROM, щоб прошити основний завантажувальний блок. Libreboot
-розміщує копію його роботи, оскільки його веб-сайт, на якому розміщено bucts,
-більше не відповідає.
-
-Пол Коціалковський
------------------
-
-Переніс ноутбуки Chromebook на основі ARM (Rockchip RK3288 SoC) до
-libreboot. Також один із головних розробників [Replicant](http://www.replicant.us/).
-
-Пол Менцель
------------
-
-Дослідив та виправив помилку в coreboot на ThinkPad X60/T60, яку виявляло
-ядро Linux 3.12 і новіших версій, через яку прискорення 3D не
-працювало, а відео загалом ставало нестабільним. Проблема полягала в тому, що
-coreboot під час ініціалізації відеочіпсета Intel, відображав *GTT Stolen Memory* в
-не тому місці, оскільки код базувався на коді ядра, а в ядрі Linux
-була така сама помилка. Коли Linux це виправив, він виявив ту саму помилку в coreboot.
-
-Пол працював над цим із Libreboot,
-періодично надсилаючи патчі для тестування, доки помилку не було виправлено
-в coreboot, а потім допоміг ій інтегрувати виправлення в libreboot.
-
-Riku Viitanen
--------------
-
-Added support for HP Elite 8200 SFF desktop PC to Libreboot. You can read
-about this in the hardware page:
-
-[HP Elite 8200 SFF](docs/hardware/hp8200sff.md)
-
-Стів Шентон
--------------
-
-Стів виконав першу роботу зі зворотньої розробки Intel Flash Descriptor, який використовується
-на машинах ICH9M, таких як ThinkPad X200. Він створив структуру C, що визначає (використовуючи
-бітові поля в C) цю область дескриптора. За допомогою деяких хитрих трюків він зміг
-виявити існування біта в дескрипторі для *вимкнення* Intel ME
-(management engine) на цих платформах.
-
-Його початкове підтвердження концепції визначило лише дескриптор, і зробило би це:
-
-* Читання дескриптора за замовчуванням і регіонів GbE з ROM Lenovo X200 (прошивка
-  за замовчуванням, не coreboot)
-* Вимкнення ME, встановивши 2 біти в дескрипторі
-* Вимкнення регіона ME
-* Переміщення дескриптора+GbE (загалом 12КБ) поруч
-* Виділення решти флеш-пам'яті для регіону BIOS
-* На основі цього створено 12КБ регіон дескриптор+область GBE для вставки
-  в образ ROM coreboot.
-
-У перші дні, до того, як Libreboot підтримував платформи GM45+ICH9M, такі як
-ThinkPad X200/T400, ви могли використовувати ці машини, але щоб уникнути
-Intel ME, вам доводилося виконувати прошивку без області дескриптора. У ті часи це працювало нормально,
-тому що ME обробляв лише TPM та AMT на цих машинах, і система
-працювала нормально, але Intel Flash Descriptor також обробляє область Intel GbE NVM
-у флеш-пам'яті, яка використовується для інтерфейсу Intel Gigabit Ethernet.
-
-Отже, ви або мали Intel ME, або не підтримували ethernet. Стів зрозумів, як
-вимкнути Intel ME за допомогою 2 бітів перемикання в дескрипторі, а також як видалити область
-Intel ME з флеш-пам'яті.
-
-Ґрунтуючись на його дослідженні, я, Лія Роу, працюючи разом зі Стівом, також виконала зворотню розробку
-області Intel GbE NVM (енергонезалежна пам'ять) у
-завантажувальній флеш-пам'яті. Цей регіон визначає параметри конфігурації для вбудованої мережевої карти Intel
-GbE, якщо присутня.
-
-На основі цього я змогла взяти початкове підтвердження концепції та написати
-утиліту `ich9gen`, яка генерує Intel Flash Descriptor та регіон GbE NVM,
-з нуля, без визначення регіону Intel ME. Саме цей інструмент,
-інструмент `ich9gen`, використовує Libreboot для надання образів ROM для GM45+ICH9M
-платформ (таких як ThinkPad X200/T400/T500/W500), із повнофункціональним
-дескриптором та функціональним Gigabit Ethernet, але *без* необхідності мікропрограми Intel
-Management Engine (ME), що робить ці машини *вільними* (ME
-повністю вимкнено, коли ви використовуєте образ дескриптора+gbe, створене `ich9gen`).
-
-З *моїм* інструментом `ich9gen` (інструмент Стіва називався `ich9deblob`), вам більше
-не потрібен був дамп оригінальної мікропрограми Lenovo BIOS! Я не могла би написати цей інструмент
-без первинного підтвердження концепції Стіва. Я працювала з ним
-протягом багатьох місяців. Вся GM45+ICH9M підтримка (X200, T400 і так далі) в
-Libreboot стала можливою завдяки його роботі у 2014 році.
-
-Тімоті Пірсон
----------------
-
-Перенес плату ASUS KGPE-D16 до coreboot для компанії Raptor
-Engineering, генеральним директором якої є Тімоті.
-Тімоті підтримує цей код у coreboot, допомогаючи проекту,
-з його інтеграцією з libreboot. Контактні
-дані цієї людини є на сайті raptor.
-
-**Підтримку D16 було припинено 19 листопада 2022 року. Ви все ще можете використовувати
-старіші версії Libreboot, і старіші випуски.**
-
-Swift Geek
-----------
-
-Додав патч для ich9gen для створення дескрипторів розміром 16MiB.
-
-Після цього Swift Geek повільно почав долучатися, поки не став розробником на повний
-робочий день. Внески Swift Geek насправді ніколи не були у формі *коду*,
-але те, що йому не вистачало в коді, він компенсував чудовою підтримкою як для користувачів,
-так і для інших розробників, допомагаючи іншим дізнатися більше про технології на
-низькому рівні.
-
-Коли Swift Geek був учасником проекту, його роль здебільшого полягала в
-наданні підтримки користувачам (на каналі IRC) і проведенні досліджень. Swift Geek знає
-багато про апаратне забезпечення. Swift Geek також зробив деяку апстрім розробку GRUB.
-
-Swift Geek неодноразово надавав технічні поради Лії Роу
-та допоміг їй покращити її навички паяння, а також навчив її
-деяким навичкам ремонту, до того моменту, коли вона тепер може виправляти більшість несправностей
-на материнських платах ThinkPad (під час перегляду схем та бордв'ю).
-
-Swiftgeek залишив проект у березні 2021 року. Я, Лія Роу, бажаю його всього найкращого в його
-починаннях і дуже вдячна за його численні внески протягом багатьох
-років.
-
-vitali64
---------
-
-Додав підтримку cstate 3 на macbook21, що забезпечує тривалий термін служби батареї
-та нижчу температуру процесора під час простою. vitali64 на irc

site/docs/build/index.md

@@ -25,6 +25,45 @@ libreboot from the available source code.
 The following document describes how `lbmk` works, and how you can make changes
 to it: [libreboot maintenance manual](../maintain/)
 
+Release status
+==============
+
+Information about status will be reported during builds; if a board is
+marked as stable, the build proceeds without further input. If the board is
+marked anything other, a warning appears asking if you wish to proceed; to
+disable these warnings, do this before building (not recommended):
+
+	export LBMK_STATUS=n
+
+In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`.
+The "unstable" marking means that the board boots mostly/entirely reliably
+annd should be safe to use, but may have a few issues, but nothing which would,
+for example, cause safety issues e.g. thermal, data reliability etc.
+
+The `broken` setting means that a given board will likely brick if flashed.
+The `untested` setting means untested.
+
+Release status is always set with regards to the current lbmk revision, on
+the theory that the current revision is being used to generate a full release.
+
+Multi-threaded builds
+=====================
+
+Libreboot's build system defaults to a single build thread, but you can change
+it by doing e.g.
+
+	export LBMK_THREADS=4
+
+This would make lbmk run on 4 threads.
+
+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
 =======
 
@@ -93,6 +132,13 @@ Actual development/testing is always done using lbmk directly, and this
 includes when building from source. Here are some instructions to get you
 started:
 
+Zero..st, check time/date
+-------------------------
+
+Make sure date/hwclock report the correct time and date on your system,
+because parts of the build process download from HTTPS servers and wrong
+time or date can cause connections to be dropped during negotiation.
+
 First, install build dependencies
 ---------------------------------
 
@@ -174,118 +220,3 @@ example want to modify a config, e.g.:
 
 Or perhaps add a new board! The maintenance manual will teach you how the
 Libreboot build system (lbmk) works!
-
-Post-compilation steps
-======================
-
-So you compiled your Libreboot image? Congratulations!
-
-Before you flash, please make sure that you *dumped* two copies of the original
-firmware just in case (verifying the hashes of each dump, to ensure that they
-match), using the `-r` option in flashrom.
-
-There are some additional considerations:
-
-Regarding binary blobs
-----------------------
-
-Firstly, you should read the Libreboot *Binary Blob Reduction Policy*:
-<https://libreboot.org/news/policy.html>
-
-A lot of mainboards in Libreboot will boot entirely with free software,
-but there are certain newer mainboards supported in Libreboot
-that need binary blobs added to them, mostly for minor initialisation tasks.
-
-They are *automatically* inserted during the build process, but then deleted
-during the *release* process; images built directly from lbmk can be flashed
-without further modification, but release images need to have these files
-re-inserted (e.g. KBC1126 EC firmware on HP EliteBooks). Please read this page
-for context:
-<https://libreboot.org/docs/install/ivy_has_common.html>
-
-The scripts under directory `script/update/vendor/` are the ones that do this.
-Specifically, `script/vendor/download`. The benefit of this is that you
-do not need to extract anything from the original vendor image (e.g. Lenovo
-UEFI image).
-
-To know if this was performed on your board, you can read the Freedom Status
-page which documents which files are used (if any), on which boards:
-<https://libreboot.org/freedom-status.html>
-
-There are specific files that you must know about, so they will be covered
-next:
-
-### Regarding CPU microcode
-
-Libreboot release archives provide ROMs with or without CPU microcode updates,
-but the newest revisions of lbmk (from `lbmk.git`) *only* build ROM images that
-contain microcode updates, by default. Libreboot's build system contains a script
-that will generate release archives, and this is used to provide Libreboot
-releases; this script is what provides the images with microcode removed,
-alongside the default ones generated by lbmk during the build.
-
-Please read:
-<https://libreboot.org/freedom-status.html#cpu-microcode>
-
-The linked page has info, and includes instructions about how to manually remove
-them, if you wish to do so. Removal of CPU microcode updates (on Intel/AMD
-processors) will result in unpredictable security/stability issues, so beware.
-
-Further context is provided in the Libreboot *Binary Blob Reduction Policy*:
-<https://libreboot.org/news/policy.html>
-
-We *recommend* that you do not delete these updates, but you have the freedom
-to choose. Additionally: we have only tested certain mainboards under this
-configuration. To know which ones they are, do this in `lbmk.git`:
-
-	cd config/coreboot/
-	git grep microcode_required
-
-Example entry:
-
-	e6400_4mb/target.cfg:microcode_required="n"
-
-If it says `="n"`, that means it has been tested. That *does not* mean it will
-be stable, it's just that we're reasonably sure it will at least *boot* most
-of the time, but you should expect random instability e.g. kernel panics.
-
-If a given mainboard *excludes* `microcode_required` in `target.cfg`, or if
-it says `microcode_required="y"`, then the release ROMs will only contain
-microcode updates. Manual removal (as above) is still possible, but it has
-not been tested and is not recommended.
-
-NOTE: ARM-based chromebooks (that Libreboot supports) don't use microcode at
-all. This section is only revelant for x86 (Intel/AMD).
-
-### Regarding Nvidia GPU ROM (Dell Latitude E6400)
-
-Dell Latitude E6400 comes in two variants: Nvidia graphics, or Intel graphics.
-More information is available on the page:
-<https://libreboot.org/docs/hardware/e6400.html>
-
-The intel graphics model can boot with coreboot's native video initialisation,
-which is free software. The *Nvidia* model (comes with Nvidia GPU) requires
-proprietary code called a *VGA Option ROM* to initialise the video display in
-early boot.
-
-Libreboot automatically fetches this during the build process, inserting it into
-the very same ROM image that can be flashed on either model, but the VGA ROM
-will only be *executed* if you actually have the Nvidia *GPU* on your board.
-
-**ALSO: Libreboot 20230625 did not support Nvidia models at all (only Intel).
-In releases, only Libreboot 20231021 and newer will support it.**
-
-Pre-built ROM images from release archives since 20231021 will *not* contain
-this file by default, but it will be present if you compiled directly from lbmk.
-To remove it, do this:
-
-	./cbutils/default/cbfstool libreboot.rom remove -n pci10de,06eb.rom
-
-The cbfstool binary was compiled when your image (target `e6400_4mb`) was
-compiled, which can alter the file system within your coreboot image.
-
-Obviously, removing this VGA ROM will mean that the ROM image will only work
-correctly on Intel GPU variants of E6400, but you probably knew that already!
-
-(If you're using a release archive instead, you can re-insert the VGA ROM by
-following [these instructions](../install/ivy_has_common.md))

site/docs/build/index.uk.md

@@ -35,6 +35,55 @@ libreboot з доступного джерельного коду.
 Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни
 до нього: [керівництво обслуговування libreboot](../maintain/)
 
+Release status
+==============
+
+Information about status will be reported during builds; if a board is
+marked as stable, the build proceeds without further input. If the board is
+marked anything other, a warning appears asking if you wish to proceed; to
+disable these warnings, do this before building (not recommended):
+
+	export LBMK_STATUS=n
+
+In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`.
+The "unstable" marking means that the board boots mostly/entirely reliably
+annd should be safe to use, but may have a few issues, but nothing which would,
+for example, cause safety issues e.g. thermal, data reliability etc.
+
+The `broken` setting means that a given board will likely brick if flashed.
+The `untested` setting means untested.
+
+Release status is always set with regards to the current lbmk revision, on
+the theory that the current revision is being used to generate a full release.
+The setting is decided on a board-by-board basis, taking its various quirks
+and idiosynrasies into account.
+
+Multi-threaded builds
+=====================
+
+Libreboot's build system defaults to a single build thread, but you can change
+it by doing e.g.
+
+	export LBMK_THREADS=4
+
+This would make lbmk run on 4 threads.
+
+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).
+
+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).
+
 Git
 ===
 
@@ -61,6 +110,13 @@ Python
 Python2 не використовується lbmk або будь-чим, що завантажується в якості модулів. Ви
 маєте переконатись, що команда `python` виконує python 3 на вашій системі.
 
+Zero..st, check time/date
+-------------------------
+
+Make sure date/hwclock report the correct time and date on your system,
+because parts of the build process download from HTTPS servers and wrong
+time or date can cause connections to be dropped during negotiation.
+
 Побудова з джерельного коду
 ============================
 

site/docs/hardware/d510mo.md

@@ -4,7 +4,7 @@ title: Intel D510MO and D410PT desktop boards
 
 <div class="specs">
 <center>
-![Intel D510MO]()
+Intel D510MO
 </center>
 
 | ***Specifications***       |                                                |

site/docs/hardware/dell9020.md

@@ -0,0 +1,231 @@
+---
+title: Dell OptiPlex 9020 SFF/MT (and 7020), and XE2 MT/SFF
+x-toc-enable: true
+...
+
+**NOTE: Dell XE2 MT/SFF are also known to work, using the 9020 images. Same
+motherboards as the 9020 and 7020.**
+
+**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
+OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+
+<div class="specs">
+<center>
+<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020sff.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff.jpg" /></span>
+<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020sff_ports.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_ports.jpg" /></span>
+<br/>
+<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020sff_inside.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_inside.jpg" /></span>
+<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020mt.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020mt.jpg" /></span>
+<br/>
+<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020mt_ports.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020mt_ports.jpg" /></span>
+<img tabindex=1 alt="Dell OptiPlex 9020" class="p" src="https://av.libreboot.org/9020/9020mt_inside.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020mt_inside.jpg" /></span>
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | Dell                                           |
+| **Name**                   | OptiPlex 9020 SFF/MT                                |
+| **Variants**               | OptiPlex 9020 SFF/MT                                |
+| **Chipset**                | Intel Q87 Express                                     |
+| **CPU**                    | Intel Haswell                               |
+| **Graphics**               | Intel HD Graphics |
+| **Memory**                 | DDR3 DIMMs (max 32GB, 4x8GB)    |
+| **Architecture**           | x86_64                                         |
+| **Original boot firmware** | Dell UEFI firmware                             |
+| **Intel ME/AMD PSP**       | Present. Can be disabled with me_cleaner.      |
+| **Flash chip**             | 2x SOIC-8, 12MiB (8+4) (96Mbit)           |
+
+
+```
+W+: Works without blobs; 
+N: Doesn't work; 
+W*: Works with blobs; 
+U: Untested; 
+P+: Partially works; 
+P*: Partially works with blobs
+?: UNKNOWN AT THIS TIME
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | ?  |
+| **Display (if Intel GPU)**                        | W+ |
+| **Display (discrete CPU, SeaBIOS payload only)**  | W* |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+
+| ***Payloads supported***   |           |
+|----------------------------|-----------|
+| **GRUB (libgfxinit only)** | Works     |
+| **SeaBIOS**                | Works     |
+| **SeaBIOS with GRUB**      | Works     |
+</div>
+Introduction
+============
+
+**Unavailable in Libreboot 20240126 or earlier. You must [compile from
+source](../build/), or use a version newer than Libreboot 20240126**
+
+Official information about the laptop can be found here:
+<https://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/optiplex-9020-micro-technical-spec-sheet.pdf>
+
+Buy Libreboot preinstalled
+======================
+
+You can buy this machine professionally serviced, with Libreboot preinstalled
+and your choice of Linux/BSD system. Many upgrades are also available. See:
+
+<https://minifree.org/product/libreboot-9020/>
+
+Sales are conducted to provide funding for the Libreboot project. Leah Rowe
+who runs Minifree, is also Libreboot's founder and lead developer.
+
+Patch
+=====
+
+Mate Kukri is the author of the original coreboot port. Thanks go to Kukri.
+Kukri's patch is here:
+
+<https://review.coreboot.org/c/coreboot/+/55232/31>
+
+This patch, at this revision (patchset 31), is what Libreboot uses for this
+port.
+
+QUBES: how to get it working
+-------------------
+
+Qubes requires IOMMU to be turned on. Please now read the next section.
+Qubes *WILL* work, if you configure Libreboot as directed below, but otherwise
+it will fail by default. This is because Libreboot *disables the IOMMU by
+default*, on this board.
+
+Graphics cards and IOMMU
+--------------
+
+IOMMU is buggy for some reason (we don't know why yet), when you plug in
+a graphics card. The graphics card simply won't work. On some of them,
+you can use the console but as soon as you start xorg, it will just b0rk.
+
+Current Libreboot revisions *disable IOMMU by default*, on this board. The
+coreboot code for initialising IOMMU was modified by the Libreboot project, to
+make it a toggle. IOMMU works fine if you use only Intel graphics.
+
+The way coreboot works is this: if vt-d is present on the CPU, it enables an
+IOMMU, and only if vt-d is present. This is still the behaviour in Libreboot,
+but Libreboot adds an additional check: if `iommu` is not set in nvram, it
+defaults to on, but if it's set to disabled, then IOMMU is not initialised.
+
+On all other Haswell boards, LIbreboot enables IOMMU by default. To enable
+it on the 9020, do this on your ROM:
+
+	nvramtool -C libreboot.rom -w iommu=Enable
+
+Then flash the ROM image. You can find nvram
+under `src/coreboot/default/util/nvramtool`. Do this in lbmk if you don't
+already havse `src/coreboot/default/`:
+
+	./update trees -f coreboot default
+
+Then do this:
+
+	make -C src/coreboot/default/util/nvramtool
+
+The binary `nvramtool` will then live in that directory. More information
+available in [Libreboot build instructions](../build/). Information about
+dumping/flashing the ROM can be found
+in [Libreboot flashing instructions](../install/)
+and [Libreboot external flashing instructions](../install/spi.md).
+
+NOTE: If IOMMU is enabled, you can still use a graphics card, but you must
+pass this on the Linux cmdline paramaters: `iommu=off`
+
+NOTE2: Libreboot uses a *static option table* on all boards that have nvram,
+which is why you must use the `-C` option on your ROM, to change the static
+table that is baked into it.
+
+On current lbmk master, graphics cards *do* work. The option to hide PEG
+devices from MRC was disabled. Now when you insert a graphics card, the
+onboard Intel GPU is disabled and the graphics card is used instead.
+
+Here is an example of the type of errors we got when testing graphics cards
+with IOMMU enabled:
+
+<https://av.vimuser.org/error.jpg>
+
+We believe the native MRC replacement may work better on graphics card with
+IOMMU turned on. This will be enabled in a future Libreboot release, if not
+already supported.
+
+7020 compatibility
+------------------
+
+7020/9020 MT each have the same motherboard. Flash the 9020 ROM from Libreboot
+on your 7020, and it will work.
+
+Ditto 7020/9020 SFF, it's the same motherboard. However, Libreboot provides
+separate targets for MT and SFF.
+
+Build ROM image from source
+---------------------------
+
+For the MT variant (7020 MT and 9020 SFF):
+
+	./build roms dell9020mt_12mb
+
+For the SFF variant (7020 MT and 7020 SFF):
+
+	./build roms dell9020sff_12mb
+
+It is important that you choose the right one. The MT variant is the full
+MTX tower.
+
+Installation
+============
+
+Insert binary files
+-------------------
+
+If you're using a release ROM, please ensure that you've inserted extra firmware
+required refer to the [guide](../install/ivy_has_common.md) for that. (failure
+to adhere to this advice will result in a bricked machine)
+
+Libreboot's build system automatically downloads and processes these files if
+you build Libreboot from source, but the same logic that it uses must be re-run
+if you're using a release image.
+
+Set MAC address
+---------------
+
+This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
+region. As such, release/build ROMs will contain the same MAC address. To
+change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
+
+Flash a ROM image (software)
+-----------------
+
+If you're already running Libreboot, and you don't have flash protection
+turned on, [internal flashing](../install/) is possible.
+
+Flash a ROM image (hardware)
+-----------------
+
+**REMOVE all power sources and connectors from the machine, before doing this.
+This is to prevent short circuiting and power surges while flashing.**
+
+For general information, please refer to [25xx NOR flash
+instructions](../install/spi.md) - that page refers to use of socketed flash.
+
+There are two SOIC-8 chips. You can split up your 12MB ROM image
+like so:
+
+	dd if=libreboot.rom of=4mb.rom bs=1M skip=8
+	dd if=libreboot.rom of=8mb.rom bs=1M count=8
+
+The side cover comes off easily, and you can find the flash ICs next to the RAM.
+
+Here's the SOIC8 ICs being flashed:
+
+<img tabindex=1 alt="SOIC8 flash IC on 9020 SFF" style="max-width:35%" src="https://av.libreboot.org/9020/9020sff_flash1.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_flash1.jpg" /></span>
+<img tabindex=1 alt="SOIC8 flash IC on 9020 SFF" style="max-width:35%" src="https://av.libreboot.org/9020/9020sff_flash2.jpg" /><span class="f"><img src="https://av.libreboot.org/9020/9020sff_flash2.jpg" /></span>
+
+Enjoy!

site/docs/hardware/dell_thermal.md

@@ -0,0 +1,52 @@
+---
+title: Dell Latitude thermal throttling
+x-toc-enable: true
+...
+
+On some Dell Latitude laptops, you may encounter random shutdowns on
+heavy load. We believe this is because the SMSC EC is overly conservative
+by default; it is in charge of handling thermals and fan control on this
+machine. Our theory is that coreboot needs to write certain EC commands
+to allow higher temperatures; please read:
+
+<https://codeberg.org/libreboot/lbmk/issues/202>
+
+Basically, what you need to do is:
+
+* Use high quality thermal paste (don't use the same dried up paste that the
+  laptop came with, if you bought it on ebay for example). Arctic MX-6 is good.
+* Check that the fan works reliably
+
+Also: the `intel_pstate` driver can be used to artifically cap CPU speed. See:
+
+<https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html>
+
+When you use this machine, it is recommended that you cap the CPU speed once
+you've booted into Linux. Set it to something like 50% at first. Then run a
+stress test, for example:
+
+	stress -c x
+
+Where `x` is the number of CPU cores, e.g. 2. Monitor the temperatures using
+something like `xsensors`, making sure the CPU doesn't exceed 80c temperature.
+
+You can also monitor CPU speeds in Linux like so:
+
+	watch -n .2 grep MHz /proc/cpuinfo
+
+This will let you know what speed you're at. You can use this to determine
+whether the `intel_pstate` driver is working. How to cap speed to 50 percent, as
+in the above example:
+
+	echo 50 > /sys/devices/system/cpu/cpufreq/intel_pstate/max_perf_pct
+
+Gradually increase the CPU speed (up to 100 on `max_perf_pct`), waiting a few
+minutes each time. You should ensure that your machine does not exceed 80C.
+
+Dell's thermal safety is far too protective by default, on some of these, and
+we don't yet know how to properly configure it. Running a CPU below 80c in
+temperature and never higher than that, is a good idea anyway, for the
+long term life of your CPU.
+
+Regardless, thermal shutdown is extremely reliable on this machine, but Dell
+makes it shut down *earlier*, before it can even start to CPU throttle.

site/docs/hardware/e5520.md

@@ -0,0 +1,84 @@
+---
+title: Dell Latitude E5520
+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>
+Dell Latitude E5520
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | Dell                                           |
+| **Name**                   | Latitude E5520                                 |
+| **Variants**               | E5520 with Intel GPU supported                 |
+| **Released**               | 2012                                           |
+| **Chipset**                | Intel Sandy Bridge                             |
+| **CPU**                    | Intel Core i3, i5 or i7                        |
+| **Graphics**               | Intel HD 4000 and unsupported Nvidia NVS 5200M |
+| **Display**                | 1366x768/1600x900 TFT                          |
+| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                  |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC MEC5055 with proprietary firmware         |
+| **Original boot firmware** | Dell UEFI                                      |
+| **Intel ME/AMD PSP**       | Present, neutered                              |
+| **Flash chip**             | 2xSOIC-8, 6MiB (4MiB and 2MiB in combination) |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | W+ |
+| **Display (if Intel GPU)**                        | W+ |
+| **Display (if Nvidia GPU)**                       | U  |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | P+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Libreboot 20231021 and releases newer than this have ROMs available for
+Dell Latitude E5520.**
+
+ROM images for Dell Latitude E5520 are available for flashing in the Libreboot
+releases *after* 20230625, or you can compile a ROM image for installation via
+lbmk, see: [build instructions](../build/)
+
+Only the Intel GPU variants are supported, currently. All models with Intel GPU
+are assumed to work.
+
+Unlike the E6400, this one does require a neutered Intel ME image to run. This
+means running it through `me_cleaner` before flashing; the Libreboot build
+system does this automatically, during build, or you can insert a neutered
+ROM image using the vendor scripts, see guide:
+
+[Insert vendor files](../install/ivy_has_common.md)
+
+As with the E6400, this one is flashable in software, from Dell UEFI firmware
+to Libreboot. Please refer to the installation instructions.
+
+**To install Libreboot, see: [E5520 installation
+instructions](../install/e6430.md)**

site/docs/hardware/e5530.md

@@ -0,0 +1,86 @@
+---
+title: Dell Latitude E5530
+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>
+Dell Latitude E5530
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | Dell                                           |
+| **Name**                   | Latitude E5530                                 |
+| **Variants**               | E5530 with Intel GPU supported                 |
+| **Released**               | 2012                                           |
+| **Chipset**                | Intel Ivy Bridge                               |
+| **CPU**                    | Intel Core i3, i5 or i7                        |
+| **Graphics**               | Intel HD 4000 and unsupported Nvidia NVS 5200M |
+| **Display**                | 1366x768/1600x900 TFT                          |
+| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                  |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC MEC5055 with proprietary firmware         |
+| **Original boot firmware** | Dell UEFI                                      |
+| **Intel ME/AMD PSP**       | Present, neutered                              |
+| **Flash chip**             | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | W+ |
+| **Display (if Intel GPU)**                        | W+ |
+| **Display (if Nvidia GPU)**                       | U  |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | P+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Libreboot 20231021 and releases newer than this have ROMs available for
+Dell Latitude E5530.**
+
+ROM images for Dell Latitude E5530 are available for flashing in the Libreboot
+releases *after* 20230625, or you can compile a ROM image for installation via
+lbmk, see: [build instructions](../build/)
+
+Only the Intel GPU variants are supported, currently. All models with Intel GPU
+are assumed to work.
+
+Unlike the E6400, this one does require a neutered Intel ME image to run. This
+means running it through `me_cleaner` before flashing; the Libreboot build
+system does this automatically, during build, or you can insert a neutered
+ROM image using the vendor scripts, see guide:
+
+[Insert vendor files](../install/ivy_has_common.md)
+
+As with the E6400, this one is flashable in software, from Dell UEFI firmware
+to Libreboot. Please refer to the installation instructions.
+
+**To install Libreboot, see: [E5530 installation
+instructions](../install/e6430.md)**
+
+Of note: this machine features a Broadnic nic, for ethernet.

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.libreboot.org/e6400/e6400-seabios.jpg" /><span class="f"><img src="https://av.libreboot.org/e6400/e6400-seabios.jpg" /></span> <img tabindex=1 alt="Dell Latitude E6400 XFR" class="p" style="max-width:24em" src="https://av.libreboot.org/e6400/e6400xfr-seabios.jpg" /><span class="f"><img src="https://av.libreboot.org/e6400/e6400xfr-seabios.jpg" /></span>

site/docs/hardware/e6420.md

@@ -0,0 +1,84 @@
+---
+title: Dell Latitude E6420
+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>
+Dell Latitude E6420
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | Dell                                           |
+| **Name**                   | Latitude E6420                                 |
+| **Variants**               | E6420 with Intel GPU supported                 |
+| **Released**               | 2012                                           |
+| **Chipset**                | Intel Sandy Bridge                             |
+| **CPU**                    | Intel Core i3, i5 or i7                        |
+| **Graphics**               | Intel HD 4000 and unsupported Nvidia NVS 5200M |
+| **Display**                | 1366x768/1600x900 TFT                          |
+| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                  |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC MEC5055 with proprietary firmware         |
+| **Original boot firmware** | Dell UEFI                                      |
+| **Intel ME/AMD PSP**       | Present, neutered                              |
+| **Flash chip**             | 2xSOIC-8, 6MiB (4MiB and 2MiB in combination) |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | W+ |
+| **Display (if Intel GPU)**                        | W+ |
+| **Display (if Nvidia GPU)**                       | U  |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | P+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Libreboot 20231021 and releases newer than this have ROMs available for
+Dell Latitude E6420.**
+
+ROM images for Dell Latitude E6420 are available for flashing in the Libreboot
+releases *after* 20230625, or you can compile a ROM image for installation via
+lbmk, see: [build instructions](../build/)
+
+Only the Intel GPU variants are supported, currently. All models with Intel GPU
+are assumed to work.
+
+Unlike the E6400, this one does require a neutered Intel ME image to run. This
+means running it through `me_cleaner` before flashing; the Libreboot build
+system does this automatically, during build, or you can insert a neutered
+ROM image using the vendor scripts, see guide:
+
+[Insert vendor files](../install/ivy_has_common.md)
+
+As with the E6400, this one is flashable in software, from Dell UEFI firmware
+to Libreboot. Please refer to the installation instructions.
+
+**To install Libreboot, see: [E6420 installation
+instructions](../install/e6430.md)**

site/docs/hardware/e6430.md

@@ -3,6 +3,12 @@ title: Dell Latitude E6430
 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 the machine will otherwise be mostly stable.
+
 <div class="specs">
 <center>
 Dell Latitude E6430
@@ -15,23 +21,23 @@ Dell Latitude E6430
 | **Variants**               | E6430 with Intel GPU supported                 |
 | **Released**               | 2012                                           |
 | **Chipset**                | Intel Ivy Bridge                               |
-| **CPU**                    | Intel Core i3, i5 or i7         .              |
-| **Graphics**               | Intel HD 4000 and unsupported NVidia NVS 5200M | 
+| **CPU**                    | Intel Core i3, i5 or i7                        |
+| **Graphics**               | Intel HD 4000 and unsupported Nvidia NVS 5200M |
 | **Display**                | 1366x768/1600x900 TFT                          |
-| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                   |
+| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                  |
 | **Architecture**           | x86_64                                         |
 | **EC**                     | SMSC MEC5055 with proprietary firmware         |
 | **Original boot firmware** | Dell UEFI                                      |
-| **Intel ME/AMD PSP**       | Present. Can be completely disabled.           |
+| **Intel ME/AMD PSP**       | Present, neutered                              |
 | **Flash chip**             | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
 
 
 ```
-W+: Works without blobs; 
-N: Doesn't work; 
-W*: Works with blobs; 
-U: Untested; 
-P+: Partially works; 
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
 P*: Partially works with blobs
 ```
 
@@ -43,13 +49,13 @@ P*: Partially works with blobs
 | **Audio**                                         | W+ |
 | **RAM Init**                                      | W+ |
 | **External output**                               | W+ |
-| **Display brightness**                            | P+ | 
+| **Display brightness**                            | P+ |
 
 | ***Payloads supported***  |           |
 |---------------------------|-----------|
-| **GRUB**                  | FAIL     |
+| **GRUB**                  | Works     |
 | **SeaBIOS**               | Works     |
-| **SeaBIOS with GRUB**     | Works    |
+| **SeaBIOS with GRUB**     | Works     |
 </div>
 Introduction
 ============

site/docs/hardware/e6520.md

@@ -0,0 +1,84 @@
+---
+title: Dell Latitude E6520
+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 the machine will otherwise be mostly stable.
+
+<div class="specs">
+<center>
+Dell Latitude E6520
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | Dell                                           |
+| **Name**                   | Latitude E6520                                 |
+| **Variants**               | E6520 with Intel GPU supported                 |
+| **Released**               | 2012                                           |
+| **Chipset**                | Intel Sandy Bridge                             |
+| **CPU**                    | Intel Core i3, i5 or i7                        |
+| **Graphics**               | Intel HD 4000 and unsupported Nvidia NVS 5200M |
+| **Display**                | 1366x768/1600x900 TFT                          |
+| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                  |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC MEC5055 with proprietary firmware         |
+| **Original boot firmware** | Dell UEFI                                      |
+| **Intel ME/AMD PSP**       | Present, neutered                              |
+| **Flash chip**             | 2xSOIC-8, 6MiB (4MiB and 2MiB in combination) |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | W+ |
+| **Display (if Intel GPU)**                        | W+ |
+| **Display (if Nvidia GPU)**                       | U  |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | P+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Libreboot 20231021 and releases newer than this have ROMs available for
+Dell Latitude E6520.**
+
+ROM images for Dell Latitude E6520 are available for flashing in the Libreboot
+releases *after* 20230625, or you can compile a ROM image for installation via
+lbmk, see: [build instructions](../build/)
+
+Only the Intel GPU variants are supported, currently. All models with Intel GPU
+are assumed to work.
+
+Unlike the E6400, this one does require a neutered Intel ME image to run. This
+means running it through `me_cleaner` before flashing; the Libreboot build
+system does this automatically, during build, or you can insert a neutered
+ROM image using the vendor scripts, see guide:
+
+[Insert vendor files](../install/ivy_has_common.md)
+
+As with the E6400, this one is flashable in software, from Dell UEFI firmware
+to Libreboot. Please refer to the installation instructions.
+
+**To install Libreboot, see: [E6520 installation
+instructions](../install/e6430.md)**

site/docs/hardware/e6530.md

@@ -0,0 +1,84 @@
+---
+title: Dell Latitude E6530
+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 the machine will otherwise be mostly stable.
+
+<div class="specs">
+<center>
+Dell Latitude E6530
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | Dell                                           |
+| **Name**                   | Latitude E6530                                 |
+| **Variants**               | E6530 with Intel GPU supported                 |
+| **Released**               | 2012                                           |
+| **Chipset**                | Intel Ivy Bridge                               |
+| **CPU**                    | Intel Core i3, i5 or i7                        |
+| **Graphics**               | Intel HD 4000 and unsupported Nvidia NVS 5200M |
+| **Display**                | 1366x768/1600x900 TFT                          |
+| **Memory**                 | 4 or 8GB (Upgradable to 16GB)                  |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC MEC5055 with proprietary firmware         |
+| **Original boot firmware** | Dell UEFI                                      |
+| **Intel ME/AMD PSP**       | Present, neutered                              |
+| **Flash chip**             | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | W+ |
+| **Display (if Intel GPU)**                        | W+ |
+| **Display (if Nvidia GPU)**                       | U  |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | P+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Libreboot 20231021 and releases newer than this have ROMs available for
+Dell Latitude E6530.**
+
+ROM images for Dell Latitude E6530 are available for flashing in the Libreboot
+releases *after* 20230625, or you can compile a ROM image for installation via
+lbmk, see: [build instructions](../build/)
+
+Only the Intel GPU variants are supported, currently. All models with Intel GPU
+are assumed to work.
+
+Unlike the E6400, this one does require a neutered Intel ME image to run. This
+means running it through `me_cleaner` before flashing; the Libreboot build
+system does this automatically, during build, or you can insert a neutered
+ROM image using the vendor scripts, see guide:
+
+[Insert vendor files](../install/ivy_has_common.md)
+
+As with the E6400, this one is flashable in software, from Dell UEFI firmware
+to Libreboot. Please refer to the installation instructions.
+
+**To install Libreboot, see: [E6530 installation
+instructions](../install/e6430.md)**

site/docs/hardware/ga-g41m-es2l.md

@@ -4,7 +4,7 @@ title: Gigabyte GA-G41M-ES2L desktop board
 
 <div class="specs">
 <center>
-![GA-G41M-ES2L]()
+GA-G41M-ES2L
 </center>
 
 | ***Specifications***       |                                                |

site/docs/hardware/hp2560p.md

@@ -35,6 +35,14 @@ OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 </div>
 
 
+BROKEN WIFI
+===========
+
+Wifi is broken in current revisions. This is because hardware `rfkill` is set,
+and pressing the button combo to enable wifi doesn't work; we believe that the
+EC is sending rfkill. We do not yet know how to enable it, at least as of
+Libreboot 202405xx.
+
 Introduction
 ============
 

site/docs/hardware/hp2570p.md

@@ -7,6 +7,10 @@ x-toc-enable: true
 OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 
 <div class="specs">
+<center>
+HP EliteBook 2570p
+</center>
+
 | ***Specifications***      |                                   |
 |---------------------------|-----------------------------------|
 | **Manufacturer**          | HP                                |

site/docs/hardware/hp8200sff.md

@@ -138,13 +138,16 @@ between the pins until you can see the normal BIOS boot screen.
 
 ![](https://av.libreboot.org/hp8200sff/fdo\_screwdriver.jpg)
 
-Boot into an OS supported by flashrom. On Linux, make sure you add the
+Boot into an OS supported by flashprog. On Linux, make sure you add the
 kernel parameter **iomem=relaxed** which disables memory protections that
 prevent BIOS flashing.
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 Now, run this command:
 
-	flashrom -p internal -c MX25L6406E/MX25L6408E
+	flashprog -p internal -c MX25L6406E/MX25L6408E
 
 The output should contain the text "The Flash Descriptor Override
 Pin-Strap is set". If it doesn't, start again from the beginning.
@@ -170,18 +173,21 @@ We'll refer to it as `libreboot4.rom`. We need to pad it to 8 MiB:
 Flash the Libreboot image with a tweaked layout:
 
 	ifdtool libreboot4.rom -f layout
-	flashrom -p internal -c MX25L6406E/MX25L6408E -w libreboot4.rom -l layout -i fd -i gbe -i bios -i me
+	flashprog -p internal -c MX25L6406E/MX25L6408E -w libreboot4.rom -l layout -i fd -i gbe -i bios -i me
 
 Power off the computer. Make sure to power off, rebooting is not enough!
 
 Power on the computer.
-Now we can flash the full 8 MiB image. Boot to an OS with flashrom
+Now we can flash the full 8 MiB image. Boot to an OS with flashprog
 again. On linux, remember the **iomem=relaxed** kernel parameter.
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 Pick a Libreboot image of your choice from `bin/hp8200sff_8mb`
 or from a release archive. We'll refer to it as `libreboot8.rom`.
 
-	flashrom -p internal -c MX25L6406E/MX25L6408E -w libreboot8.rom
+	flashprog -p internal -c MX25L6406E/MX25L6408E -w libreboot8.rom
 
 Power cycle the computer again.
 

site/docs/hardware/hp820g2.md

@@ -0,0 +1,330 @@
+---
+title: HP EliteBook 820 G2
+x-toc-enable: true
+...
+
+**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
+OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+
+<div class="specs">
+<center>
+<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2.jpg" /></span>
+<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_lid.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_lid.jpg" /></span>
+<br/>
+<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_ports1.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_ports1.jpg" /></span>
+<img tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_ports2.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_ports2.jpg" /></span>
+<br/>
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | HP                                             |
+| **Name**                   | EliteBook 820 G2                               |
+| **Variants**               | EliteBook 820 G2                               |
+| **Released**               | 2014                                           |
+| **Chipset**                | 5th gen (Broadwell, SoC)                       |
+| **CPU**                    | Intel i5-5200U, i5-5300U, i7-5500U, i7-5600U   |
+| **Graphics**               | Intel HD 5500 graphics (libre initialisation)  |
+| **Display**                | 14" 1366x768 or 1920x1080 TFT                  |
+| **Memory**                 | Two slots, max 16GB/slot (32GB), DDR3/SODIMM   |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC MEC1324 in main boot flash                |
+| **Original boot firmware** | HP UEFI firmware                               |
+| **Intel ME/AMD PSP**       | Present. Can be disabled with me_cleaner.      |
+| **Flash chip**             | SOIC-8 16MiB 128Mbit, 12MiB usable by coreboot |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | N  |
+| **Display (if Intel GPU)**                        | W+ |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | W+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+
+Full hardware specifications can be found on HP's own website:
+
+<https://support.hp.com/gb-en/document/c04543492>
+
+Introduction
+============
+
+**Unavailable in Libreboot 20231106 or earlier. You must [compile from
+source](../build/), or use a release newer than 20231106.**
+
+This is a beastly 12.5" Broadwell machine from HP, the main benefit of which is
+greater power efficiency (compared to Ivybridge and Haswell platforms), while
+offering similar CPU performance but much higher graphics performance.
+
+Variants exist with either Intel Core i5-5200U, i5-5300U, i7-5500U or
+i7-5600U and it comes with a plethora of ports; 3x USB 3.0, DisplayPort (which
+can do 4K 60Hz), a VGA port, can be expanded to 32GB RAM, has *3* slots which
+can take SSDs (PCIe, M2 and regular SATA), also has a side dock connector (for
+a docking station). The screen is eDP type and can be upgraded to 1920x1080.
+
+This is a nice portable machine, with very reasonable performance. Most people
+should be very satisfied with it, in daily use. It is widely available in
+online market places. This page will tell you how to flash it!
+
+All variants of this mainboard will come with Intel HD 5500 graphics, which has
+completely free software initialisation in coreboot, provided by *libgfxinit*.
+
+Build ROM image from source
+---------------------------
+
+First, install the build dependencies and initialise git, using the
+instructions in [building from source](../build/). Unless you're using a
+release after Libreboot 20231106, you *must* use the latest `lbmk.git`.
+
+The build target, when building from source, is thus:
+
+	./build roms hp820g2_12mb
+
+NOTE: The actual flash is 16MB, but you must flash only the first 12MB of it.
+The ROM images provided by Libreboot are 12MB.
+
+There is a separate 2MB *system* flash that you must *erase*, prior to
+installing Libreboot. This, along with Libreboot's modified IFD, bypasses
+the security (HP Sure Start) that the vendor put there, allowing you to
+use coreboot-based firmware such as Libreboot.
+
+Installation
+============
+
+Insert binary files
+-------------------
+
+If you're using a release ROM, please ensure that you've inserted extra firmware
+required refer to the [guide](../install/ivy_has_common.md) for that. (**failure
+to adhere to this advice will result in a bricked machine**)
+
+If you're *building* from source (using lbmk), the steps takes above are done
+for you automatically, inserting all of the required files. The above link is
+only relevant for *release* images, which lack some of these files.
+
+Set MAC address
+---------------
+
+This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
+region. As such, release/build ROMs will contain the same MAC address. To
+change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
+
+Update an existing Libreboot installation
+-----------------
+
+<img class="l" tabindex=1 alt="HP EliteBook 820 G2" class="p" src="https://av.libreboot.org/hp820g2/hp820g2_backlit.jpg" /><span class="f"><img src="https://av.libreboot.org/hp820g2/hp820g2_backlit.jpg" /></span>
+
+NOTE: This section only applies if you haven't enabled write protection. You
+can otherwise use the external flashing instructions (see below) for both the
+initial installation and updates, but for updates you don't need to re-erase
+the private flash, if it was already erased.
+
+If you're already running Libreboot, and you don't have flash protection
+turned on, [internal flashing](../install/) is possible, but please note:
+
+You must *only* flash the first 12MB, and nothing in the final 4MB of the flash.
+This is because the EC firmware is in flash, and we don't touch that during
+initial installation or during updates.
+
+Update it like so:
+
+Create a dummy 16MB ROM like so:
+
+```
+dd if=/dev/zero of=new.bin bs=16M count=1
+```
+
+Then insert your 12MB Libreboot ROM image into the dummy file:
+
+```
+dd if=libreboot.rom of=new.bin bs=12M count=1 conv=notrunc
+```
+
+The `libreboot.rom` file is the 12MB image from Libreboot. The `new.bin`
+file is the Libreboot ROM, padded to 16MB. You will not flash the entire 16MB
+file, but flashprog detects a 16MB flash IC. This just makes flashrom not
+complain about mismatching ROM/chip size.
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
+You should flash each region individually:
+
+```
+flashprog -p internal --ifd -i gbe -w new.bin --noverify-all
+flashprog -p internal --ifd -i bios -w new.bin --noverify-all
+flashprog -p internal --ifd -i me -w new.bin --noverify-all
+flashprog -p internal --ifd -i ifd -w new.bin --noverify-all
+```
+
+NOTE: The `--ifd` option uses the regions defined in the *flashed* IFD, so
+they must match the ROM. You can otherwise dump a layout file and use that,
+using the instructions below (using `-l layout.txt` instead of `--ifd`).
+
+NOTE: If you already did an installation before, and you don't want to
+[change the MAC address](../install/nvmutil.html) stored in the gbe region,
+you can skip the gbe/ifd/me regions as above, and flash just the BIOS region.
+
+NOTE: Use of `--ifd` requires flashrom 1.2 or higher. If you have an older
+version, or you don't have `--ifd`, you could instead do:
+
+```
+ifdtool -f layout.txt libreboot.rom
+```
+
+Then, instead of `--ifd` you would use `-l layout.txt`.
+
+ALSO: The `--ifd` option makes flashrom flash regions based on what's in
+the *current* flashed IFD.
+
+Flashing Libreboot first time (hardware)
+========================================
+
+**PLEASE ENSURE that you dump a copy of both flash ICs (system flash and
+private flash). Take two dumps of each, and make sure each has two good hashes.
+This is because there are certain files that, while you may not need for a
+regular Libreboot installation, may be useful for recovery purposes. You have
+been warned!**
+
+This section is relevant to you if you're still running the original HP
+firmware. You must [flash externally](../install/spi.md).
+
+Take stock of these further notes, because there are extra steps that you
+must take.
+
+HP Sure Start
+-------------
+
+There is a 16MB flash and a 2MB flash. Read this page for info:
+<https://doc.coreboot.org/mainboard/hp/hp_sure_start.html>
+
+The page makes it seem more complicated than necessary, from a user's point
+of view. What you really need to do is just erase the 2MB flash IC, and flash
+only the first 12MB of the 16MB flash IC. A photo is shown below. Consult
+the [SPI flashing guide](../install/spi.md) and act as if you were flashing,
+but leave out `-w libreboot.rom` (don't write an image), and instead
+use the `--erase` option, with your clip connected to the private flash (2MB
+flash IC).
+
+You might want to dump the private flash first, just in case (use `-r priv.rom`
+or whatever filename you want to dump to, and take two dumps, ensuring that
+the hashes match). The private (2MB) flash is inaccessible from your OS. The
+system stores hashes of the IFD, GbE and a copy of IFD/GbE in private flash,
+restoring them if they were modified, but erasing the private flash disables
+this security mechanism.
+
+Here is a photo of the board, with the flashes:
+
+![HP 820 G2 flash](https://av.libreboot.org/hp820g2/hp820g2_flash.jpg)
+
+HP bootblock
+------------
+
+See: <https://doc.coreboot.org/mainboard/hp/elitebook_820_g2.html?highlight=elitebook>
+
+In this page it talks about HP's own bootblock and EC firmware. These are in
+the final 4MB of the flash. You must *not* modify these, because you will brick
+your machine unless the IFD is modified;
+
+This is why Libreboot provides 12MB images. The IFD in Libreboot is modified, as
+per this coreboot documentation, to make the BIOS region *end* at the last byte
+of the first 12MB in flash, bypassing HP's security entirely. In other words,
+you can run whatever you want (such as Libreboot) in the first 12MB of flash,
+so long as the upper 4MB is untouched and the private 2MB flash has been erased.
+
+With Libreboot's modified IFD, HP's own bootblock is never executed, but the
+EC firmware *is*, and must be left alone. You do not to insert it in your
+Libreboot ROM because it's already in flash, within that last 4MB.
+
+Flash a ROM image (hardware)
+-----------------
+
+**REMOVE all power sources like battery, charger and so on, before doing this.
+This is to prevent short circuiting and power surges while flashing.**
+
+For general information, please refer to [25xx NOR flash
+instructions](../install/spi.md).
+
+Remove the bottom cover via the latch, and the flashes are accessible.
+First, dump both flashes for backup, using the `-r` option (instead of `-w`)
+in flashrom. Two dumps of each flash, make sure both dumps match for each chip.
+
+We will assume that your system flash (16MB) dump is named `dump.bin`. This is
+the dump of your 16MB flash, containing HP's firmware, including the final
+bootblock and EC firmware.
+
+This gives you everything, including the final 4MB. Now insert your new ROM
+into a copy of `dump.bin`:
+
+```
+cp -R dump.bin new.bin
+dd if=libreboot.rom of=new.bin bs=12M count=1 conv=notrunc
+```
+
+Flash `new.bin` to system flash (16MB IC) using the `-w` option in flashrom,
+and erase the private (2MB) flash IC,
+using the `--erase` option (instead of `-w filename.rom`) in flashrom.
+
+In the above example, you replaced the first 12MB of the HP dump with that of
+your Libreboot image, but leaving the final 4MB intact which contains the EC
+firmware. Libreboot's custom IFD sets everything so that all regions, from
+IFD to GbE, ME and then BIOS region, exist within the first 12MB of flash.
+This makes the machine boot from the end of the 12MB section, containing the
+coreboot bootblock, instead of the HP bootblock (which is never executed but
+must remain intact).
+
+It's very important that you *erase* the 2MB flash. Be careful *not* to
+erase the system (16MB flash). This is yet another reason why you should keep
+a backup of both flash ICs, just in case (dumped using `-r` in flashrom).
+
+![](https://av.libreboot.org/hp820g2/hp820g2.jpg)
+
+![](https://av.libreboot.org/hp820g2/hp820g2_inside.jpg)
+
+And that's all. Refer to other documents on Libreboot's website for how
+to handle Linux/BSD systems and generally use your machine.
+
+TPM 2.0 potentially supported
+==============================
+
+The onboard TPM is an SLB 9660, which supports TPM 1.2 but it is known to be
+compatible with TPM 2.0 via firmware upgrade. Although not yet tested, we have
+some notes about that here:
+
+[../../tasks/#hp-820-g2-tpm](../../tasks/#hp-820-g2-tpm)
+
+Not yet used meaningfully by Libreboot itself, but the TPM can be used to
+implement things like measured boot.
+
+References
+==========
+
+See: <https://doc.coreboot.org/soc/intel/broadwell/blobs.html>
+
+Libreboot's build system automatically pulls down the MRC/refcode files, and
+modifies the refcode to enable the onboard Intel Gigabit Ethernet (GbE). You
+don't need to mess with this at all, when you build Libreboot yourself.
+
+You can see how this works, by looking at the patch which added 820 G2 support:
+<https://browse.libreboot.org/lbmk.git/commit/?id=401c0882aaec059eab62b5ce467d3efbc1472d1f>
+
+If you're using release builds, the MRC, refcode and (neutered) ME images are
+missing from flash, and must be re-inserted, using the instructions
+on [this page](../install/ivy_has_common.md).

site/docs/hardware/hp8300usdt.md

@@ -71,15 +71,18 @@ crystal (small metal cylinder) and the power cable for the optical drive.
 
 ![](https://av.libreboot.org/hp8300usdt/jumper_to_fdo.jpg)
 
-Boot into an OS of your choice (that has flashrom support). When using Linux,
+Boot into an OS of your choice (that has flashprog support). When using Linux,
 you need to supply the kernel parameter `iomem=relaxed`.
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 The BIOS should no longer impose any write-protections.
-You can now use `flashrom -p internal` freely.
+You can now use `flashprog -p internal` freely.
 
 Take a backup of the original BIOS:
 
-	flashrom -p internal -r oem_bios
+	flashprog -p internal -r oem_bios
 
 This is an Ivy Bridge board which means that a neutered ME image
 is required if you wish to flash the ME region. Libreboot's
@@ -95,7 +98,7 @@ platforms](../install/ivy_has_common.md)
 
 You can now flash libreboot:
 
-	flashrom -p internal -w libreboot.rom
+	flashprog -p internal -w libreboot.rom
 
 You can now move the jumper back to its original place.
 By default, Libreboot applies no write-protection, so

site/docs/hardware/hp8460p.md

@@ -0,0 +1,114 @@
+---
+title: HP EliteBook 8460p
+x-toc-enable: true
+...
+
+**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
+OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+
+<div class="specs">
+<center>
+<img tabindex=1 alt="HP EliteBook 8460p" class="p" src="https://av.libreboot.org/hp8460p/hp8460p.webp" /><span class="f"><img src="https://av.libreboot.org/hp8460p/hp8460p.webp" /></span>
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | HP                                             |
+| **Name**                   | EliteBook 8460p                                |
+| **Variants**               | EliteBook 8460p                                |
+| **Released**               | 2011                                           |
+| **Chipset**                | Intel QM67                                     |
+| **CPU**                    | Intel Sandy Bridge (socketed)                  |
+| **Graphics**               | Intel HD Graphics (supported in Libreboot) or
+                               AMD Radeon HD 6470M (unsupported in Libreboot) |
+| **Display**                | 14" 1366x768 or 1600x900 TFT                   |
+| **Memory**                 | Two slots, max 8GB/slot (16GB), DDR3/SODIMM    |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC KBC1126, proprietary (in main boot flash) |
+| **Original boot firmware** | HP UEFI firmware                               |
+| **Intel ME/AMD PSP**       | Present. Can be disabled with me_cleaner.      |
+| **Flash chip**             | SOIC-8 8MiB (64Mbit)                           |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | N  |
+| **Display (if Intel GPU)**                        | W+ |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | W+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Unavailable in Libreboot 20231106 or earlier. You must [compile from
+source](../build/), or use a release newer than 20231106.**
+
+This is a beastly 14" Sandy Bridge platform from HP.
+**NOTE: Until otherwise stated, only the Intel GPU variant is supported in
+Libreboot.**
+
+Build ROM image from source
+---------------------------
+
+The build target, when building from source, is thus:
+
+	./build roms hp8460pintel_8mb
+
+Installation
+============
+
+Insert binary files
+-------------------
+
+If you're using a release ROM, please ensure that you've inserted extra firmware
+required refer to the [guide](../install/ivy_has_common.md) for that. (failure
+to adhere to this advice will result in a bricked machine)
+
+Set MAC address
+---------------
+
+This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
+region. As such, release/build ROMs will contain the same MAC address. To
+change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
+
+Flash a ROM image (software)
+-----------------
+
+If you're already running Libreboot, and you don't have flash protection
+turned on, [internal flashing](../install/) is possible.
+
+Flash a ROM image (hardware)
+-----------------
+
+**REMOVE all power sources like battery, charger and so on, before doing this.
+This is to prevent short circuiting and power surges while flashing.**
+
+For general information, please refer to [25xx NOR flash
+instructions](../install/spi.md).
+
+At this present time, disassembly instructions are unavailable from the
+Libreboot project, but you can search for HP's own hardware maintenance manual
+or look at videos online showing disassembly.
+
+The flash chip is visible by removing the "bottom door" panel. But the
+frame makes it hard to put a clip on it, so it's recommended to follow the
+HP [service manual](https://h10032.www1.hp.com/ctg/Manual/c03015458.pdf)
+to remove the **bottom cover**, as it's called.
+

site/docs/hardware/hp8560w.md

@@ -0,0 +1,135 @@
+---
+title: HP EliteBook 8560w
+x-toc-enable: true
+...
+
+**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
+OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+
+<div class="specs">
+<center>
+<img tabindex=1 alt="HP EliteBook 8560w" class="p" src="https://av.libreboot.org/hp8560w/hp8560w.webp" /><span class="f"><img src="https://av.libreboot.org/hp8560w/hp8560w.webp" /></span>
+</center>
+
+| ***Specifications***       |                                                |
+|----------------------------|------------------------------------------------|
+| **Manufacturer**           | HP                                             |
+| **Name**                   | EliteBook 8560w                                |
+| **Variants**               | EliteBook 8560w                                |
+| **Released**               | 2011                                           |
+| **Chipset**                | Intel QM67                                     |
+| **CPU**                    | Intel Sandy Bridge (socketed)                  |
+| **Graphics**               | MXM-A (3.0), socketed                          |
+| **Display**                | 15.6" 1600x900 or 1920x1080 LCD                |
+| **Memory**                 | Two or four slots, max 8GB/slot
+                               (16GB or 32GB), DDR3/SODIMM                    |
+| **Architecture**           | x86_64                                         |
+| **EC**                     | SMSC KBC1126, proprietary (in main boot flash) |
+| **Original boot firmware** | HP UEFI firmware                               |
+| **Intel ME/AMD PSP**       | Present. Can be disabled with me_cleaner.      |
+| **Flash chip**             | SOIC-8 8MiB (64Mbit)                           |
+
+
+```
+W+: Works without blobs;
+N: Doesn't work;
+W*: Works with blobs;
+U: Untested;
+P+: Partially works;
+P*: Partially works with blobs
+```
+
+| ***Features***                                    |    |
+|---------------------------------------------------|----|
+| **Internal flashing with original boot firmware** | N  |
+| **Display**                                       | W* |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | W+ |
+
+| ***Payloads supported***  |           |
+|---------------------------|-----------|
+| **GRUB**                  | Works     |
+| **SeaBIOS**               | Works     |
+| **SeaBIOS with GRUB**     | Works     |
+</div>
+Introduction
+============
+
+**Unavailable in Libreboot 20240126 or earlier. You must [compile from
+source](../build/), or use a release newer than 20240126.**
+
+This is a beastly 15" Sandy Bridge mobile workstation from HP.
+
+**Wi-Fi does not work. It shows correctly in lspci, but stays hard blocked.**
+
+GPU
+---
+
+This laptop has upgradeable GPU: it has a socketed MXM-A 3.0 card. So far,
+only Quadro 1000M and 2000M (which shipped with the laptop originally) have
+been tested with Libreboot.
+
+These laptops shipped with eDP and LVDS panels. If you choose to upgrade the
+graphics card, make sure it is compatible with the panel you have. Use the
+following command to check:
+
+	xrandr
+
+Or if using Wayland:
+
+	wlr-randr
+
+If you have "LVDS-1 connected", your GPU upgrade needs to support LVDS.
+According to [this forum thread](https://forums.macrumors.com/threads/2011-imac-graphics-card-upgrade.1596614/),
+AMD's 1st gen GCN cards are the newest and most powerful to support LVDS.
+If you have an eDP panel, you should be able to use newer cards than that.
+
+As long as the card has an onboard VBIOS, Libreboot will execute it and
+everything *should* work. **However, this is currently untested.**
+
+Build ROM image from source
+---------------------------
+
+The build target, when building from source, is thus:
+
+	./build roms hp8560w_8mb
+
+Installation
+============
+
+Insert binary files
+-------------------
+
+If you're using a release ROM, please ensure that you've inserted extra firmware
+required refer to the [guide](../install/ivy_has_common.md) for that. (failure
+to adhere to this advice will result in a bricked machine)
+
+Set MAC address
+---------------
+
+This platform uses an Intel Flash Descriptor, and defines an Intel GbE NVM
+region. As such, release/build ROMs will contain the same MAC address. To
+change the MAC address, please read [nvmutil documentation](../install/nvmutil.md).
+
+Flash a ROM image (software)
+-----------------
+
+If you're already running Libreboot, and you don't have flash protection
+turned on, [internal flashing](../install/) is possible.
+
+Flash a ROM image (hardware)
+-----------------
+
+**REMOVE all power sources like battery, charger and so on, before doing this.
+This is to prevent short circuiting and power surges while flashing.**
+
+Remove the bottom cover. The SOIC-8 flash chip is next to the memory slot 2.
+You need to cut away a small piece of the clear plastic protection material
+to get to the chip.
+
+![](https://av.libreboot.org/hp8560w/hp8560w_chip.webp)
+
+For information about programming the chip, please refer to [25xx NOR flash
+instructions](../install/spi.md).

site/docs/hardware/hp9470m.md

@@ -89,5 +89,8 @@ to program Libreboot on it.
 
 Some part of the board might turn on when programming. If programming fails,
 you might have to attach the laptop to a charger. Make sure the laptop
-powers off before running flashrom. No LEDs should be lit.
+powers off before running flashprog. No LEDs should be lit.
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 

site/docs/hardware/imac52.md

@@ -4,7 +4,7 @@ title: Apple iMac 5,2
 
 <div class="specs">
 <center>
-![iMac5,2]()
+iMac5,2
 </center>
 
 | ***Specifications***       |                                                |

site/docs/hardware/index.md

@@ -3,38 +3,29 @@ title: Hardware compatibility list
 x-toc-enable: true
 ...
 
-**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
-OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+Introduction
+============
+
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 This sections relates to known hardware compatibility in libreboot.
 
 For installation instructions, refer to [../install/](../install/).
 
-NOTE: For T60/R60 thinkpads, make sure that it has an Intel GPU, not an ATI GPU
-because coreboot lacks native video initialization for the ATI GPUs on these
-machines.
-
-(for later machines like T500, T400, ATI GPU doesn't matter, because it also
-has an Intel GPU, and libreboot uses the Intel one)
-
-READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
-====================================================================
-
-**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
-ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
-the release ROMs of Libreboot are MISSING certain files, that you must insert
-yourself. FAILURE to adhere to this warning may result in you bricking your
-machine (rendering it unbootable), if you were to flash the release ROMs without
-modifying them in any way. For more information, please read:**
-
-**[Insert vendor files on Sandybridge/Ivybridge/Haswell](../install/ivy_has_common.md)**
-
-NOTE: This warning does not apply to ROMs that you compiled yourself, using
-lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
-in release ROMs. The link above says how to re-add them. When building ROM images
-yourself, from source, Libreboot's build system automatically handles it. See:
-[Libreboot build instructions](../build/)
-
 Supported hardware
 ==================
 
@@ -47,27 +38,44 @@ libreboot currently supports the following systems in this release:
 
 ### Desktops (AMD, Intel, x86)
 
+-   **[Dell OptiPlex 7020/9020 MT and SFF](dell9020.md) - Also [available to buy
+    with Libreboot preinstalled](https://minifree.org/product/libreboot-9020/)** - Dell OptiPlex XE2 MT/SFF also known to work
 -   [Acer G43T-AM3](acer_g43t-am3.md)
 -   [Apple iMac 5,2](imac52.md)
 -   [ASUS KCMA-D8 motherboard](kcma-d8.md)
--   [Dell Precision T1650](t1650.md) (**easy to flash without disassembly**)
+-   Dell OptiPlex 7010 **MT** (known to work, using the T1650 ROM, but more
+    research is needed)
+-   [Dell Precision T1650](t1650.md)
 -   [Gigabyte GA-G41M-ES2L motherboard](ga-g41m-es2l.md)
 -   [HP Elite 8200 SFF/MT](hp8200sff.md) (HP 6200 Pro Business probably works too)
-    (**easy to flash without disassembly**)
--   [HP Elite 8300 USDT](hp8300usdt.md) (**easy to flash without disassembly**)
+-   [HP Elite 8300 USDT](hp8300usdt.md)
 -   [Intel D510MO and D410PT motherboards](d510mo.md)
+-   [Intel D945GCLF](d945gclf.md)
 
 ### Laptops (Intel, x86)
 
--   [Apple MacBook1,1 and MacBook2,1](macbook21.md) (2,1 flashable without disassembly)
+-   **[Lenovo ThinkPad T440p](../install/t440p_external.md) - Also [available
+    to buy with Libreboot preinstalled](https://minifree.org/product/libreboot-t440p/)**
+-   **[Lenovo ThinkPad W541](../install/ivy_has_common.md) - Also [available to
+    buy with Libreboot preinstalled](https://minifree.org/product/libreboot-w541/)** - NOTE: W540 also compatible (same mainboard, so flash the same ROM)
+-   Lenovo ThinkPad X230 - *Also* available on Minifree: <https://minifree.org/product/libreboot-x230/>
+-   [Apple MacBook1,1 and MacBook2,1](macbook21.md)
 -   [Dell Latitude E6400, E6400 XFR and E6400 ATG, all with Nvidia or Intel
-    GPU](e6400.md) **(easy to flash, no disassembly, similar
-    hardware to X200/T400)**
--   [Dell Latitude E6430 (Intel GPU](e6430.md) **(easy to flash, no disassembly)**
--   [HP EliteBook 2170p](hp2170p.md) (**socketed flash IC**)
+    GPU](e6400.md)
+-   [Dell Latitude E6420 (Intel GPU](e6420.md)
+-   [Dell Latitude E6430 (Intel GPU](e6430.md)
+-   [Dell Latitude E5520 (Intel GPU](e5520.md)
+-   [Dell Latitude E5530 (Intel GPU](e5530.md)
+-   [Dell Latitude E6520 (Intel GPU](e6520.md)
+-   [Dell Latitude E6530 (Intel GPU](e6530.md)
+-   Dell Latitude E5420.
+-   [HP EliteBook 2170p](hp2170p.md)
 -   [HP EliteBook 2560p](hp2560p.md)
 -   [HP EliteBook 2570p](hp2570p.md)
+-   [HP EliteBook 820 G2](hp820g2.md)
+-   [HP EliteBook 8460p](hp8460p.md)
 -   [HP EliteBook 8470p](hp8470p.md)
+-   [HP EliteBook 8560w](hp8560w.md)
 -   [HP EliteBook Folio 9470m](hp9470m.md)
 -   [Lenovo ThinkPad R400](r400.md)
 -   [Lenovo ThinkPad R500](r500.md)
@@ -75,20 +83,18 @@ libreboot currently supports the following systems in this release:
 -   [Lenovo Thinkpad T420](../install/ivy_has_common.md) (no install docs yet)
 -   [Lenovo ThinkPad T420S](../install/ivy_has_common.md) (no install docs yet)
 -   [Lenovo ThinkPad T430](../install/ivy_has_common.md) (no install docs yet)
--   [Lenovo ThinkPad T440p](../install/t440p_external.md)
 -   [Lenovo ThinkPad T500](t500.md)
+-   [Lenovo ThinkPad T520 / W520](../install/ivy_has_common.md) (no install guide yet)
 -   [Lenovo ThinkPad T530 / W530](../install/ivy_has_common.md) (no install
--   Lenovo ThinkPad T60 (with Intel GPU) (**easy to flash without disassembly**)
+-   Lenovo ThinkPad T60 (with Intel GPU)
 -   [Lenovo ThinkPad W500](t500.md)
--   [Lenovo ThinkPad W541](../install/ivy_has_common.md) (no install docs yet)
 -   [Lenovo ThinkPad X200 / X200S / X200 Tablet](x200.md)
 -   [Lenovo Thinkpad X220](../install/ivy_has_common.md)
 -   [Lenovo Thinkpad X220t](../install/ivy_has_common.md)
--   Lenovo ThinkPad X230
 -   [Lenovo Thinkpad X230](../install/x230_external.md)
 -   [Lenovo Thinkpad X230t](../install/x230_external.md)
 -   Lenovo ThinkPad X301
--   Lenovo ThinkPad X60 / X60S / X60 Tablet (**easy to flash without disassembly**)
+-   Lenovo ThinkPad X60 / X60S / X60 Tablet
 
 ### Laptops (ARM, with U-Boot payload)
 
@@ -107,7 +113,6 @@ re-adding them at a later date. They were removed due to issues. List:
 -   [Hisense Chromebook C11 and more (veyron-jerry)](../install/chromebooks.md)
 -   [HP Chromebook 11 G1 (daisy-spring)](../install/chromebooks.md)
 -   [HP Chromebook 14 G3 (nyan-blaze)](../install/chromebooks.md)
--   [Intel D945GCLF](d945gclf.md) (removed from lbmk, TODO: re-add support)
 -   [Samsung Chromebook 2 11" (peach-pit)](../install/chromebooks.md)
 -   [Samsung Chromebook 2 13" (peach-pi)](../install/chromebooks.md)
 -   [Samsung Chromebook XE303 (daisy-snow)](../install/chromebooks.md)
@@ -161,9 +166,12 @@ libreboot, so we don't actually provide that, but if you still have
 Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
 will update both the BIOS and EC version. See:
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 NOTE: this can only be done when you are using Lenovo BIOS. How to
 update the EC firmware while running libreboot is unknown. libreboot
 only replaces the BIOS firmware, not EC.

site/docs/hardware/index.zh-cn.md

@@ -3,6 +3,22 @@ title: 兼容硬件列表
 x-toc-enable: true
 ...
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+Introduction
+============
+
 **[安装之前请先阅读这些指示](../../news/safety.md)，否则你的机器可能会变砖：[安全措施](../../news/safety.md)**
 
 这一部分说明了 libreboot 已知兼容的硬件。
@@ -34,24 +50,40 @@ x-toc-enable: true
 
 ### Desktops (AMD, Intel, x86)
 
+-   **Dell OptiPlex 7020/9020 MT and SFF (no guides yet) - [Available to buy
+    with Libreboot preinstalled](https://minifree.org/product/libreboot-9020/)**
 -   [Acer G43T-AM3](acer_g43t-am3.md)
 -   [Apple iMac 5,2](imac52.md)
 -   [ASUS KCMA-D8 主板](kcma-d8.md)
+-   Dell OptiPlex 7010 **MT** (known to work, using the T1650 ROM, but more
+    research is needed)
 -   [Dell Precision T1650](t1650.md)
 -   [Gigabyte GA-G41M-ES2L 主板](ga-g41m-es2l.md)
 -   [HP Elite 8200 SFF/MT](hp8200sff.md)（HP 6200 Pro Business 多半也能用）
 -   [HP Elite 8300 USDT](hp8300usdt.md)
 -   [Intel D510MO 及 D410PT 主板](d510mo.md)
+-   [Intel D945GCLF](d945gclf.md)（移出 lbmk，计划：重新加入支持）
 
 ### 笔记本（Intel，x86）
 
+-   **[Lenovo ThinkPad T440p](../install/t440p_external.md) - Also [available
+    to buy with Libreboot preinstalled](https://minifree.org/product/libreboot-t440p/)**
+-   **[Lenovo ThinkPad W541](../install/ivy_has_common.md) - Also [available to
+    buy with Libreboot preinstalled](https://minifree.org/product/libreboot-w541/)**
+-   Lenovo ThinkPad X230 - *Also* available on Minifree: <https://minifree.org/product/libreboot-x230/>
 -   [Apple MacBook1,1 及 MacBook2,1](macbook21.md)
--   [Dell Latitude E6400, E6400 XFR 及 E6400 ATG，皆支持 Nvidia 或 Intel GPU](e6400.md) **（刷入简单，无需拆解，硬件类似 X200/T400）**
--   [Dell Latitude E6430, Intel GPU](e6430.md) **（刷入简单，无需拆解）**
+-   [Dell Latitude E6400, E6400 XFR 及 E6400 ATG，皆支持 Nvidia 或 Intel GPU](e6400.md)
+-   Dell Latitude E6420 (Intel GPU) - no guide yet.
+-   [Dell Latitude E6430, Intel GPU](e6430.md)
+-   Dell Latitude E5530 (Intel GPU) - no guide yet.
+-   Dell Latitude E6520 (Intel GPU) - no guide yet.
 -   [HP EliteBook 2170p](hp2170p.md)
 -   [HP EliteBook 2560p](hp2560p.md)
 -   [HP EliteBook 2570p](hp2570p.md)
+-   [HP EliteBook 820 G2](hp820g2.md)
+-   [HP EliteBook 8460p](hp8460p.md)
 -   [HP EliteBook 8470p](hp8470p.md)
+-   [HP EliteBook 8560w](hp8560w.md)
 -   [HP EliteBook Folio 9470m](hp9470m.md)
 -   [Lenovo ThinkPad R400](r400.md)
 -   [Lenovo ThinkPad R500](r500.md)
@@ -59,16 +91,13 @@ x-toc-enable: true
 -   [Lenovo Thinkpad T420](../install/ivy_has_common.md)（暂无安装文档）
 -   [Lenovo ThinkPad T420S](../install/ivy_has_common.md)（暂无安装文档）
 -   [Lenovo ThinkPad T430](../install/ivy_has_common.md)（暂无安装文档）
--   [Lenovo ThinkPad T440p](../install/t440p_external.md)
 -   [Lenovo ThinkPad T500](t500.md)
 -   [Lenovo ThinkPad T530 / W530](../install/ivy_has_common.md)（暂无安装文档）
 -   Lenovo ThinkPad T60（Intel GPU 款）
 -   [Lenovo ThinkPad W500](t500.md)
--   [Lenovo ThinkPad W541](../install/ivy_has_common.md)（暂无安装文档）
 -   [Lenovo ThinkPad X200 / X200S / X200 Tablet](x200.md)
 -   [Lenovo Thinkpad X220](../install/ivy_has_common.md)
 -   [Lenovo Thinkpad X220t](../install/ivy_has_common.md)
--   Lenovo ThinkPad X230
 -   [Lenovo Thinkpad X230](../install/x230_external.md)
 -   [Lenovo Thinkpad X230t](../install/x230_external.md)
 -   Lenovo ThinkPad X301
@@ -93,7 +122,6 @@ x-toc-enable: true
 -   [ASUS Chromebit CS10 (veyron-mickey)](../install/chromebooks.md)
 -   [ASUS Chromebook Flip C100PA (veyron-minnie)](../install/chromebooks.md)
 -   [ASUS Chromebook C201PA (veyron-speedy)](../install/c201.md)
--   [Intel D945GCLF](d945gclf.md)（移出 lbmk，计划：重新加入支持）
 
 ### 关于已移除的主板
 
@@ -122,9 +150,12 @@ d945gclf：据上次报告，根本无法启动。D510MO 仍在 lbmk 中，但
 
 建议更新到最新 EC 固件版本。[EC 固件](../../faq.md#ec-embedded-controller-firmware) 与 libreboot 是独立的，所以我们实际上并不会提供这些固件，但如果你仍还有 Lenovo BIOS，那你可以直接运行 Lenovo BIOS 更新工具，它会同时更新 BIOS 和 EC 版本。见：
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 注意：只有在运行 Lenovo BIOS 的时候，你才能这样做。如何在运行 libreboot 的时候更新 EC 固件尚不清楚。libreboot 只会替换 BIOS 固件，而不会替换 EC。
 
 更新的 EC 固件有一些好处，例如电池管理更加好。

site/docs/hardware/kcma-d8.md

@@ -3,6 +3,8 @@ title: ASUS KCMA-D8 desktop/workstation board
 x-toc-enable: true
 ...
 
+TODO: this page is OLD. check that the info is still valid.
+
 Introduction
 ============
 
@@ -149,7 +151,7 @@ Current issues {#issues}
 
 -   Opteron 4100 series CPUs are currently incompatible
 -   LRDIMM memory modules are currently incompatible
-	(use UDIMMs please)
+	(use UDIMMs please) - NOTE: might actually work nowadays.
 -   Memory initialization is still problematic for some modules. We
     recommend avoiding Kingston and Super Talent modules for this reason.
 
@@ -157,11 +159,6 @@ The coreboot wiki has some information about RAM compatibility. The wiki is
 deprecated but the info on it is still correct for this board. Some other
 considerations:
 
--   Booting from USB mass storage devices is currently broken under GRUB.
-    Consequently, the textmode ROM with SeaBIOS is recommended otherwise
-    in order to install an operating system you will need a hard disk with
-    a pre-installed OS or will have to plug in another HDD or CD/DVD
-    reader in order to boot OS installation media.
 -   SeaBIOS lacked serial console support out-of-the-box in release 20160907
     and as such a workaround using SGABIOS is necessary. You can find
     instructions on how to do this on the

site/docs/hardware/kfsn4-dre.md

@@ -52,7 +52,10 @@ This is a server board using AMD hardware (Fam10h). It can also be used
 for building a high-powered workstation. Powered by libreboot.
 
 Flashing instructions can be found at
-[../install/\#flashrom](../install/)
+[../install/\#flashprog](../install/)
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 Form factor {#formfactor}
 ===========

site/docs/hardware/kgpe-d16.md

@@ -3,6 +3,8 @@ title: ASUS KGPE-D16 server/workstation board
 x-toc-enable: true
 ...
 
+TODO: OLD page. TODO: check that all the info is still valid.
+
 Introduction
 ============
 
@@ -17,7 +19,7 @@ recommend avoiding Kingston modules.*
 *For working configurations see <https://www.coreboot.org/Board:asus/kgpe-d16>.*
 
 Flashing instructions can be found at
-[../install/\#flashrom](../install/#flashrom) - note that external
+[../install/\#flashprog](../install/#flashprog) - note that external
 flashing is required, if the proprietary (ASUS) firmware is
 currently installed. If you already have libreboot, by default it is
 possible to re-flash using software running in Linux on the
@@ -79,6 +81,7 @@ Current issues {#issues}
 ==============
 
 -   LRDIMM memory modules are currently incompatible
+	(IT MAY WORK NOWADAYS, TODO TEST)
 -   SAS (via PIKE 2008 module) requires a vendor option ROM (and
     SeaBIOS) to boot from it (theoretically possible to replace, but you
     can put a kernel in CBFS or on SATA and boot from that, which

site/docs/hardware/macbook21.md

@@ -85,7 +85,7 @@ For the MacBook2,1:
     working)*
 * MA701LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
     working)*
-* MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 (untested)
+* MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 *(tested -
 * MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
     working)*
 * MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 *(tested - working)*
@@ -103,7 +103,10 @@ Internal flashing
 
 MacBook2,1 can always be flashed internally, even if running Apple firmware:
 
-	sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w your.rom
+	sudo flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w your.rom
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 The MacBook1,1 can't be flashed internally if running the Apple EFI firmware. 
 You must flash externally.

site/docs/hardware/r400.md

@@ -77,7 +77,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
 (contains notes, plus instructions)
 
 Flashing instructions can be found at
-[../install/\#flashrom](../install/#flashrom)
+[../install/\#flashprog](../install/#flashprog)
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 EC update {#ecupdate}
 =========
@@ -88,7 +91,7 @@ libreboot, so we don't actually provide that, but if you still have
 Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
 will update both the BIOS and EC version. See:
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 
 NOTE: this can only be done when you are using Lenovo BIOS. How to

site/docs/hardware/t1650.md

@@ -17,15 +17,15 @@ OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 | **Name**                   | Precision T1650                                |
 | **Variants**               | Precision T1650                                |
 | **Released**               | 2012                                           |
-| **Chipset**                | Intel QM77                                     |
+| **Chipset**                | Intel C216                                     |
 | **CPU**                    | Intel Ivy Bridge                               |
 | **Graphics**               | Discrete graphics, or Intel HD Graphics model
                                depending on CPU model                         | 
-| **Memory**                 | DDR3 DIMMs (max 32GB, 2x16GB), ECC memory supported    |
+| **Memory**                 | DDR3 DIMMs (max 32GB, 4x8GB), ECC memory supported    |
 | **Architecture**           | x86_64                                         |
-| **Original boot firmware** | Dell UEFI firmware                               |
+| **Original boot firmware** | Dell UEFI firmware                             |
 | **Intel ME/AMD PSP**       | Present. Can be disabled with me_cleaner.      |
-| **Flash chip**             | SOIC-16 16MiB (128Mbit)                        |
+| **Flash chip**             | SOIC-16 and/or SOIC-8 12MiB (96Mbit)           |
 
 
 ```

site/docs/hardware/t400.md

@@ -76,7 +76,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
 (contains notes, plus instructions)
 
 Flashing instructions can be found at
-[../install/\#flashrom](../install/#flashrom)
+[../install/\#flashprog](../install/#flashprog)
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 EC update {#ecupdate}
 =========
@@ -87,7 +90,7 @@ libreboot, so we don't actually provide that, but if you still have
 Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
 will update both the BIOS and EC version. See:
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 
 NOTE: this can only be done when you are using Lenovo BIOS. How to

site/docs/hardware/t500.md

@@ -78,7 +78,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
 (contains notes, plus instructions)
 
 Flashing instructions can be found at
-[../install/\#flashrom](../install/#flashrom)
+[../install/\#flashprog](../install/#flashprog)
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 EC update {#ecupdate}
 =========
@@ -89,7 +92,7 @@ libreboot, so we don't actually provide that, but if you still have
 Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
 will update both the BIOS and EC version. See:
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 
 NOTE: this can only be done when you are using Lenovo BIOS. How to

site/docs/hardware/x200.md

@@ -76,7 +76,10 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
 (contains notes, plus instructions)
 
 Flashing instructions can be found at
-[../install/\#flashrom](../install/#flashrom)
+[../install/\#flashprog](../install/#flashprog)
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 EC update {#ecupdate}
 =========
@@ -87,7 +90,7 @@ libreboot, so we don't actually provide that, but if you still have
 Lenovo BIOS then you can just run the Lenovo BIOS update utility, which
 will update both the BIOS and EC version. See:
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 -   [X200, X200s, X200si BIOS Update](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x200/downloads/ds015007)
 -   [X200t BIOS Update](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/thinkpad-x200-tablet/downloads/ds018814)

site/docs/hardware/x200.uk.md

@@ -69,7 +69,10 @@ X200S та X201S; знову ж таки, це неперевірено. *Шви
 (містить примітки та інструкції)
 
 Інструкції з перепрошивки можна знайти за адресою
-[../install/\#flashrom](../install/#flashrom)
+[../install/\#flashprog](../install/#flashprog)
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 Оновлення EC {#ecupdate}
 =========
@@ -80,7 +83,7 @@ libreboot, тому ми її фактично не надаємо, але як
 Lenovo BIOS, ви можете просто запустити утиліту оновлення BIOS Lenovo, яка
 оновить як BIOS, так і версію EC. Дивіться:
 
--   [../install/#flashrom](../install/#flashrom)
+-   [../install/#flashprog](../install/#flashprog)
 -   <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk>
 -   [Оновлення BIOS X200, X200s, X200i](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x200/downloads/ds015007)
 -   [Оновлення BIOS X200t](http://pcsupport.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/thinkpad-x200-tablet/downloads/ds018814)

site/docs/index.md

@@ -8,6 +8,19 @@ the [main news section](../news/).
 
 [Answers to Frequently Asked Questions about libreboot](../faq.md).
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
 Installing libreboot
 ====================
 

site/docs/index.uk.md

@@ -8,6 +8,19 @@ libreboot. Новини, включаючи оголошення про випу
 
 [Відповіді на поширені запитання про libreboot](../faq.md).
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
 Встановлення libreboot
 ====================
 

site/docs/index.zh-cn.md

@@ -6,6 +6,19 @@ libreboot 的最新更新，可以在 [libreboot.org](https://libreboot.org) 上
 
 [libreboot 常见问题解答](../faq.md).
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
 安装 libreboot
 ====================
 

site/docs/install/c201.md

@@ -22,6 +22,10 @@ A special fork of flashrom, maintained by Google, is required for flashing.
 More information about this is present in the generic [chromebook flashing
 instructions](chromebooks.md).
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom, but the chromium fork
+is another fork of flashrom, and you should use that on chromebooks.
+
 Depthcharge payload (obsolete)
 ------------------------------
 

site/docs/install/chromebooks.md

@@ -88,7 +88,7 @@ Chromebooks may have 1.8V as the supply voltage for the SPI NOR chip, be
 extra careful about that.
 
 On newer Chromebooks, there is a root-of-trust chip providing a
-[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_cr50.md)
+[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md)
 mechanism that lets you flash externally using a special USB debugging
 cable. However, most boards that Libreboot supports do not have this.
 
@@ -109,7 +109,7 @@ by the fact that it bridges electrical contacts, but finding and
 removing it might require you to disassemble most of the board.
 
 Newer boards have a root-of-trust chip enforcing write-protection. The
-[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_cr50.md)
+[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md)
 mechanism should be used to disable hardware write-protection. Opening
 the case and disconnecting the battery might also disable it.
 
@@ -151,7 +151,7 @@ first (like Intel ME firmware). This is not yet documented here.
 
 You can flash the ROM image both internally and externally. For the
 latter, see the [external flashing guide](spi.md) and the ChromiumOS
-[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_cr50.md)
+[Closed Case Debugging](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md)
 documentation if your board supports it.
 
 To flash the entire ROM image internally, run within ChromeOS:

site/docs/install/d510mo.md

@@ -12,7 +12,10 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 Flashing instructions {#clip}
 =====================

site/docs/install/d945gclf.md

@@ -2,10 +2,6 @@
 title: Intel D945GCLF flashing tutorial 
 ...
 
-NOTE: On newer Libreboot revisions, boot issues were reported so this board
-was temporarily removed. It will be re-added at a later date, after testing
-has been done.
-
 This guide is for those who want libreboot on their Intel D945GCLF
 motherboard while they still have the original BIOS present.
 

site/docs/install/e6400.md

@@ -68,7 +68,7 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
 
 We believe most/all are 4MB (32Mb) flash sizes, but larger ROM images are
 provided for people who wish to upgrade.
@@ -119,17 +119,15 @@ build target `e6400_4mb` - either build from source and it gets inserted
 automatically, or you can [insert it
 manually](ivy_has_common.md) on future release ROMs past Libreboot 20230625.
 
-An earlier experimental revision existed in the `e6400nvidia_wip` branch of
+An earlier experimental revision existed in an experimental branch of
 lbmk, as build target `e6400nvidia_4mb`, but it was decided that since SeaBIOS
 is the only payload anyway on this board, having just a single build target is
-more efficient if that can (and it does) support both variants.
+more efficient if that can (and it does) support both variants. It was therefore
+added to the master branch.
 
 Actual installation is the same as with regular E6400 (Intel GPU) variants.
 Refer to the [E6400 flashing instructions](../docs/install/e6400.md).
 
-The `e6400nvidia_wip` branch is obsolete, and it is merely referenced for
-historical purposes.
-
 Problems with Linux video drivers on Nvidia
 -------------------------------------------
 
@@ -160,29 +158,12 @@ codeberg](https://codeberg.org/libreboot/lbmk/issues/14#issuecomment-907758).
 How to flash internally (no diassembly)
 =======================================
 
-Warning for BSD users
----------------------
-
-**NOTE (15 October 2023): The util is now called `dell-flash-unlock`, but it
-was previously called `e6400-flash-unlock`. Links have been updated.**
-
-BSD *boots* and works properly on these machines, but take note:
-
-Nicholas's [dell-flash-unlock](https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/dell_flash_unlock.c)
-utility has been ported to OpenBSD, but *other* BSDs are assumed unsupported for
-now. The `flashrom` software is available on BSD systems. Libreboot's build
-system has *itself* not yet been ported to the BSDs, but you can use the
-flash unlock utility.
-
-NOTE: BSD is mentioned above, but the only BSD tested for `dell-flash-unlock`
-is OpenBSD, as of 15 October 2023.
-
 Flashing from Linux
 -------------------
 
 MAKE SURE you boot with this Linux kernel parameter: `iomem=relaxed` - this
-disables memory protections, permitting `/dev/mem` access needed by flashrom.
-The flash is memory mapped and flashrom accesses it via `/dev/mem`.
+disables memory protections, permitting `/dev/mem` access needed by flashprog.
+The flash is memory mapped and flashprog accesses it via `/dev/mem`.
 
 You can flash Libreboot directly from the vendor (Dell) BIOS, without taking
 the machine apart. It can be done entirely from Linux. It will probably also
@@ -218,18 +199,18 @@ Protected Range registers.
 
 When you flash it, you can use this command:
 
-	flashrom -p internal -w libreboot.rom
+	flashprog -p internal -w libreboot.rom
 
 Where `libreboot.rom` is your E6400 ROM. *Make sure* it's the right one.
-If flashrom complains about multiple flash chips detected, just pick one of
+If flashprog complains about multiple flash chips detected, just pick one of
 them (doesn't matter which one). On *most* Dell machines, the most correct
-would probably be this option in flashrom: `-c MX25L3205D/MX25L3208D`.
+would probably be this option in flashprog: `-c MX25L3205D/MX25L3208D`.
 
 So:
 
-	flashrom -p internal -w libreboot.rom -c MX25L3205D/MX25L3208D
+	flashprog -p internal -w libreboot.rom -c MX25L3205D/MX25L3208D
 
-When you see flashrom say `VERIFIED` at the end, that means the flash was
+When you see flashprog say `VERIFIED` at the end, that means the flash was
 successful. If you don't see that, or you're unsure, please [contact the
 Libreboot project via IRC](../../contact.md).
 
@@ -239,7 +220,7 @@ BACK UP THE FACTORY BIOS
 The `-w` option flashes `libreboot.rom`. You may consider *backing up* the
 original Dell BIOS first, using the -r option:
 
-	flashrom -p internal -r backup.rom -c MX25L3205D/MX25L3208D
+	flashprog -p internal -r backup.rom -c MX25L3205D/MX25L3208D
 
 Do this while in a flashable state, after the 2nd run of `dell-flash-unlock`.
 

site/docs/install/e6430.md

@@ -3,6 +3,9 @@ title: Flashing the Dell Latitude E6430
 x-toc-enable: true
 ...
 
+**NOTE:** This installation guide also pertains to E5520, E6420, E6520, E5530
+and E6530.
+
 Introduction
 ============
 
@@ -21,7 +24,7 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
 
 The internal flash size is 12MiB on this board; physically, an 8MiB and 4MiB
 chip (two chips) but this distinction only matters for external flashing.
@@ -38,12 +41,12 @@ Refer to [mac\_address.md](../hardware/mac_address.md).
 
 It is recommended that you run *nvmutil*. See:
 
-[nvmutil usage manual](nvmutil.md)
+[nvmutil usage manual](nvmutil.md) - E5530 users don't need to run this.
 
 The `nvmutil` software is specifically designed for changing MAC addresses,
 and it implements a few more safeguards (e.g. prevents multicast/all-zero
 MAC addresses) and features (MAC address randomisation, ability to correct or
-intententionally corrupt(disable) GbE sections if you wish, swap GbE parts,
+intentionally corrupt(disable) GbE sections if you wish, swap GbE parts,
 etc). - **it is also the only software available for this. Please do not
 use ich9gen on this board. This is an ivybridge board, not ICH9M.**
 
@@ -79,9 +82,10 @@ BSD *boots* and works properly on these machines, but take note:
 
 Nicholas's [dell-flash-unlock](https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/dell_flash_unlock.c)
 utility has been ported to OpenBSD, but *other* BSDs are assumed unsupported for
-now. The `flashrom` software is available on BSD systems. Libreboot's build
-system has *itself* not yet been ported to the BSDs, but you can use the
-flash unlock utility.
+now.
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 NOTE: BSD is mentioned above, but the only BSD tested for `dell-flash-unlock`
 is OpenBSD, as of 15 October 2023.
@@ -90,8 +94,8 @@ Flashing from Linux
 -------------------
 
 MAKE SURE you boot with this Linux kernel parameter: `iomem=relaxed` - this
-disables memory protections, permitting `/dev/mem` access needed by flashrom.
-The flash is memory mapped and flashrom accesses it via `/dev/mem`.
+disables memory protections, permitting `/dev/mem` access needed by flashprog.
+The flash is memory mapped and flashprog accesses it via `/dev/mem`.
 
 You can flash Libreboot directly from the vendor (Dell) BIOS, without taking
 the machine apart. It can be done entirely from Linux. It will probably also
@@ -114,27 +118,28 @@ is included in that program's directory, or you can read it online here:
 
 <https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/README.md>
 
-Literally just run that program, and do what it says. You run it once, and shut
-down, and when you do, the system brings itself back up automatically.  Then
-you run it and flash it unlocked. Then you run it again. The source code is
-intuitive enough that you can easily get the gist of it; it's writing some EC
-commands and changing some chipset config bits. The EC on this machine is
-hooked up to the `GPIO33` signal, sometimes called `HDA_DOCK_EN`, which sets
-the flash descriptor override thus disabling any flash protection by the IFD.
-It also bypasses the SMM BIOS lock protection by disabling SMIs, and Dell's
-BIOS doesn't set any other type of protection either such as writing to
-Protected Range registers.
+Literally just run that program, and do what it says. You run it once, shut
+down, and then power on the machine. Then run it again to confirm that the
+flash is unlocked. The source code is intuitive enough that you can easily get
+the gist of it; it's writing some EC commands and changing some chipset config
+bits. The EC on this machine is hooked up to the `HDA_SDO` signal, also known
+as the Flash Descriptor Override (FDO), which disables any flash protection by
+the IFD. When booted with the FDO set, the original Dell firmware disables all
+other BIOS write protections such as SMM BIOS lock bits.
+
+*Make sure* to make a backup of the original firmware before proceeding to
+flash; see the instructions below.
 
 When you flash it, you can use this command:
 
-	flashrom -p internal -w libreboot.rom
+	flashprog -p internal -w libreboot.rom
 
 Where `libreboot.rom` is your E6430 ROM. *Make sure* it's the right one.
-If flashrom complains about multiple flash chips detected, just pick one of
+If flashprog complains about multiple flash chips detected, just pick one of
 them (doesn't matter which one), with the `-C` flag as directed; just pick one,
 and if it doesn't work, try the next.
 
-When you see flashrom say `VERIFIED` at the end, that means the flash was
+When you see flashprog say `VERIFIED` at the end, that means the flash was
 successful. If you don't see that, or you're unsure, please [contact the
 Libreboot project via IRC](../../contact.md).
 
@@ -144,10 +149,10 @@ BACK UP THE FACTORY BIOS
 The `-w` option flashes `libreboot.rom`. You may consider *backing up* the
 original Dell BIOS first, using the -r option:
 
-	flashrom -p internal -r backup.rom
+	flashprog -p internal -r backup.rom
 
 AGAIN: make sure to use `-C` accordingly, if you need to pick a chip (where
-flashrom has detected multiple chip definitions). Just pick one, any of them
+flashprog has detected multiple chip definitions). Just pick one, any of them
 will probably work, if not try the next.
 
 Do this while in a flashable state, after the 2nd run of `dell-flash-unlock`.
@@ -163,11 +168,11 @@ How to flash externally
 
 Refer to [spi.md](spi.md) as a guide for external re-flashing.
 
-The SPI flash chip shares a voltage rail with the ICH9 southbridge, which is
-not isolated using a diode. As a result, powering the flash chip externally
-causes the ICH9 to partially power up and attempt to drive the SPI clock pin
-low, which can interfere with programmers such as the Raspberry Pi. See
-[RPi Drive Strength](spi.md#rpi-drive-strength) for a workaround.
+The SPI flash chip shares a voltage rail with the chipset, which is not
+isolated using a diode. As a result, powering the flash chip externally may
+cause the QM77 chipset to partially power up and drive the SPI pins, which can
+interfere with programmers such as the Raspberry Pi. See [RPi Drive
+Strength](spi.md#rpi-drive-strength) for a workaround.
 
 Have a look online for videos showing how to disassemble, if you wish to
 externally re-flash.

site/docs/install/ga-g41m-es2l.md

@@ -22,7 +22,7 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
 
 Flashing instructions {#clip}
 =====================
@@ -52,11 +52,11 @@ Linux. There are 2 flash chips (one is backup).
 
 Flash the first chip:
 
-	./flashrom -p internal:dualbiosindex=0 -w libreboot.rom
+	./flashprog -p internal:dualbiosindex=0 -w libreboot.rom
 
 Flash the second chip:
 
-	./flashrom -p internal:dualbiosindex=1 -w libreboot.rom
+	./flashprog -p internal:dualbiosindex=1 -w libreboot.rom
 
 NOTE: you can still boot the system with just the main flash chip
 connected, after desoldering the backup chip. This has been tested while
@@ -66,5 +66,5 @@ NOTE: If you don't flash both chips, the recovery program from the default
 factory BIOS will kick in and your board will be soft bricked. Make sure that
 you flash both chips!
 
-NOTE: You need the latest flashrom. Just get it on flashrom.org from
-their SVN or Git repos.
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.

site/docs/install/ich9utils.md

@@ -123,7 +123,7 @@ accomplish the same result of locking or unlocking a descriptor.**
 These files contain the descriptor+GbE region and are suitable for systems
 that have an Intel GbE NIC present. The flash regions (as defined by the
 Intel Flash Descriptor) are set *read-write* which means that you can also
-re-flash using `flashrom -p internal` in your operating system running on
+re-flash using `flashprog -p internal` in your operating system running on
 that machine. This is the default setup used when libreboot's build system
 compiles ROM images.
 
@@ -181,7 +181,7 @@ a Broadcom NIC for ethernet. In descriptorless mode, ICH9M works very similarly
 to older ICH7 chipsets.
 
 Your libreboot.rom image is now ready to be flashed on the system. Refer
-back to [../install/\#flashrom](../install/#flashrom) for how to flash
+back to [../install/\#flashprog](../install/#flashprog) for how to flash
 it.
 
 Write-protecting the flash chip
@@ -289,7 +289,7 @@ This takes a `factory.rom` dump and disables the ME/TPM, but leaves the
 region intact. It also sets all regions read-write. Simply put, this means
 that you can use the original factory firmware but without the Intel ME enabled.
 
-The ME interferes with flash read/write in flashrom, and the default
+The ME interferes with flash read/write in flashprog, and the default
 descriptor locks some regions. The idea is that doing this will remove
 all of those restrictions.
 

site/docs/install/index.md

@@ -3,34 +3,76 @@ title: Installation instructions
 x-toc-enable: true
 ...
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+FLASH ERRORS (and workarounds)
+=======================
+
+**NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.**
+
 This section relates to installing libreboot on supported targets.
 
-NOTE: if running `flashrom -p internal` for software based flashing, and you
+Right out of the gate, some users may experience errors with flashprog when
+using the internal programmer. They are:
+
+/dev/mem access error
+---------------------
+
+NOTE: if running `flashprog -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
+`iomem=relaxed` kernel parameter before running flashprog, or use a kernel that
 has `CONFIG_STRICT_DEVMEM` not enabled.
 
-READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
+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).
+
+ERROR: Could not get I/O privileges
+------------------------------------
+
+Error message: `ERROR: Could not get I/O privileges (Function not implemented)`
+
+If you get this while running `flashprog -p internal -w filename.rom` (or any
+internal flash operation), note: flashprog heavily uses ioperm/iopl functions
+to operate the internal flasher, at least on x86 machines.
+
+See: <https://lwn.net/Articles/804143/>
+
+Yeah, just enable `CONFIG_X86_IOPL_IOPERM` in your Linux kernel. This is
+a *build-time* option, so you must re-compile your kernel, or find a build that
+has this option enabled (IOPL emulation). Many default kernel configurations
+now disable this option.
+
+Here's a handy-dandy guide for building a kernel from source:
+<https://www.cyberciti.biz/tips/compiling-linux-kernel-26.html>
+
+**BSD users:** On OpenBSD and NetBSD if you get similar errors, note that it
+should work here, but you need to boot with `kern.securelevel=-1`.
+See: [NetBSD securelevel manual](https://wiki.netbsd.org/tutorials/kernel_secure_levels/)
+and [OpenBSD securelevel manpage](https://man.openbsd.org/securelevel).
+
+Otherwise, if you get such errors, it may just be that you're not root. You
+must run flashprog as root, at least to use the internal flasher (using external
+USB flashing dongles doesn't normally require root).
+
+SAFETY WARNING!
 ====================================================================
 
-**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
-ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
-the release ROMs of Libreboot are MISSING certain files, that you must insert
-yourself. FAILURE to adhere to this warning may result in you bricking your
-machine (rendering it unbootable), if you were to flash the release ROMs without
-modifying them in any way. For more information, please read:**
-
-**[Insert vendor files on Sandybridge/Ivybridge/Haswell](ivy_has_common.md)**
-
-NOTE: This warning does not apply to ROMs that you compiled yourself, using
-lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
-in release ROMs. The link above says how to re-add them. When building ROM images
-yourself, from source, Libreboot's build system automatically handles it. See:
-[Libreboot build instructions](../build/)
-
-This isn't required on *all* Libreboot-supported boards, but if in doubt, follow
-these instructions anyway. If you run the vendor scripts on a board that doesn't
-need vendor files, nothing will happen.
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 PRECAUTIONS
 ===========
@@ -228,6 +270,18 @@ which means that the MAC address is irrelevant (either there will be an Intel
 PHY module that is now unusable, and you use an add-on card, or it doesn't use
 an Intel PHY module and the onboard NIC is usable).
 
+HP EliteBook 820 G2
+===================
+
+Please refer to the [820 G2 page](../hardware/hp820g2.md) for specific
+flashing instructions, both internal and external.
+
+HP EliteBook 8560w
+===================
+
+Please refer to the [8560w page](../hardware/hp8560w.md) for specific
+flashing instructions, both internal and external.
+
 Install via host CPU (internal flashing)
 ========================================
 
@@ -237,7 +291,7 @@ may be configured to restrict write privileges by the host CPU.
 
 In some situations, the host CPU can rewrite/erase/dump the boot flash.
 This is called *internal flashing*. This means that you will run software,
-namely `flashrom`, to read/erase/write the contents of the boot flash from a
+namely `flashprog`, to read/erase/write the contents of the boot flash from a
 running operating system on the target device.
 
 NOTE: please also read the sections further down this page. On some systems,
@@ -248,11 +302,11 @@ NOTE: in some cases, external flashing is possible but special steps are
 required. This depends on your mainboard. Again, please read this page
 carefully.
 
-Run flashrom on host CPU
+Run flashprog on host CPU
 ------------------------
 
 You can simply take any ROM image from the libreboot project, and flash it.
-Boot a Linux distribution on the target device, and install flashrom.
+Boot a Linux distribution on the target device, and install flashprog.
 
 In some cases, this is not possible or there are other considerations. Please
 read this section *carefully*.
@@ -261,7 +315,7 @@ read this section *carefully*.
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
 
 In the output will be information pertaining to your boot flash.
 
@@ -269,14 +323,14 @@ In the output will be information pertaining to your boot flash.
 
 How to read the current chip contents:
 
-	sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -r dump.bin
+	sudo flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -r dump.bin
 
 You should still make several dumps, even if you're flashing internally, to
 ensure that you get the same checksums. Check each dump using `sha1sum`
 
 How to erase and rewrite the chip contents:
 
-	sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w libreboot.rom
+	sudo flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w libreboot.rom
 
 If you are re-flashing a GM45+ICH9M laptop (e.g. ThinkPad X200/X200S/X200T,
 T400, T500, R400, W500 etc - but not R500), you should run the ich9gen utility
@@ -285,13 +339,13 @@ Please read the ich9utils documentation:
 [/docs/install/ich9utils.html](/docs/install/ich9utils.html)
 
 NOTE: `force_I_want_a_brick` is not scary. Do not be scared! This merely disables
-the safety checks in flashrom. Flashrom and coreboot change a lot, over the years,
+the safety checks in flashprog. Flashrom and coreboot change a lot, over the years,
 and sometimes it's necessary to use this option. If you're scared, then just
 follow the above instructions, but remove that option. So, just use `-p internal`.
 If that doesn't work, next try `-p internal:boardmismatch=force`. If that doesn't
 work, try `-p internal:boardmismatch=force,laptop=force_I_want_a_brick`. So long
 as you *ensure* you're using the correct ROM for your machine, it will be safe
-to run flashrom. These extra options just disable the safetyl checks in flashrom.
+to run flashprog. These extra options just disable the safetyl checks in flashprog.
 There is nothing to worry about.
 
 If successful, it will either say `VERIFIED` or it will say that the chip
@@ -306,14 +360,34 @@ the sections below:
 
 [You must flash it externally](spi.md)
 
-#### DELL Latitude E6400 laptop (easy to flash, similar to X200/T400)
+#### DELL Latitude E6400 laptop
 
 See: [Dell Latitude E6400 Libreboot Installation Guide](e6400.md)
 
-#### DELL Latitude E6430 laptop (easy to flash, no disassembly)
+#### DELL Latitude E6420 laptop
+
+See: [Dell Latitude E6420 Libreboot Installation Guide](e6430.md)
+
+#### DELL Latitude E6430 laptop
 
 See: [Dell Latitude E6430 Libreboot Installation Guide](e6430.md)
 
+#### DELL Latitude E6520 laptop
+
+See: [Dell Latitude E6520 Libreboot Installation Guide](e6420.md)
+
+#### DELL Latitude E6530 laptop
+
+See: [Dell Latitude E6530 Libreboot Installation Guide](e6430.md)
+
+#### DELL Latitude E5520 laptop
+
+See: [Dell Latitude E5520 Libreboot Installation Guide](e5520.md)
+
+#### DELL Latitude E5530 laptop
+
+See: [Dell Latitude E5530 Libreboot Installation Guide](e6430.md)
+
 #### ThinkPad X200/T400/T500/W500/R400/R500 vendor BIOS
 
 If you're running one of these, it cannot be flashed internally if you're still
@@ -328,6 +402,13 @@ Please also see notes about the built-in MAC address inside the boot flash, for
 the onboard NIC (ethernet one); not relevant on R500, which doesn't use an
 Intel NIC.
 
+TARGET: ThinkPad X201/X201S/X201 Tablet
+--------------------------------
+
+**SUPPORT WAS REMOVED, because fan controls fail when the ME is neutered on
+this platform. This only affects the arrandale machines, and does not affect
+newer Intel platforms.**
+
 #### Intel D510MO and D410PT running original Intel BIOS
 
 [You must flash it externally](spi.md)
@@ -376,6 +457,26 @@ example of the push pin as a proof of concept:
 
 #### ThinkPad X60/X60S/X60T/T60 with Lenovo BIOS {#flashrom_lenovobios}
 
+**WARNING: Libreboot 20231021 and likely older 2023 releases do not have the
+bootblock copied in release ROMs, so the bucts trick below will actually cause
+a brick. This is fixed in lbmk as of 25 October 2023 onward, but you should
+do this on 20231021 release ROMs before following the instructions below:**
+
+	dd if=libreboot.rom of=bootblock.bin bs=1 skip=$(($(stat -c %s libreboot.rom) - 0x10000)) count=64k
+
+And then do this:
+
+	dd if=bootblock.bin of=libreboot.rom bs=1 seek=$(($(stat -c %s libreboot.rom) - 0x20000)) count=64k conv=notrunc
+
+(This was fixed in Libreboot 20231101)
+
+**NOTE: the section below pertaining to 20160907 static binaries references
+flashrom. Libreboot recommends flashprog nowadays, but if you're using that
+utils archive, please note that it is from a time when Libreboot used
+flashrom. Use flashrom there as that's what included in those binaries.
+Libreboot does not currently document how to patch flashprog for sst/macronix
+on X60/T60, when going (in software) from lenovobios to libreboot.**
+
 **NOTE: This section partially relates to `utils` release archive in
 Libreboot 20160907, which contains static compiled binaries for things like
 bucts and flashrom. It will *still* work on modern distros, and thus is
@@ -408,12 +509,12 @@ Here are a list of targets:
   and you will run it at 115200 baud rate. agetty/fgetty in Linux can give
   you a serial console in your OS)
 
-Download and build flashrom, using the instructions
-on [the Git page](../../git.md), and download the `bucts` software using the
-notes on that very same page.
-
 You can replace Lenovo BIOS with libreboot, using flashrom running on the host
-CPU. However, there are some considerations.
+CPU. However, there are some considerations. NOTE: needs patching for SST
+and macronix chips, but libreboot doesn't yet do this for flashprog. You can
+use the old Libreboot 20160907 sources to get the modified flashrom instead,
+which contains this patch - and static binaries are provided, for convenience;
+they will still work, due to libs being statically linked.
 
 Firstly, make sure that the yellow CMOS battery is installed, and functioning
 correctly. You could check the voltage. The battery is a CR2032
@@ -438,7 +539,7 @@ program referenced below.
 The libreboot ROM images already have the upper 64KiB bootblock copied to the lower
 one, so you don't have to worry about copying it yourself.
 
-If you build flashrom using the libreboot build system, there will be three
+If you use the Libreboot 20160907 utils archive, there will be three
 binaries:
 
 * `flashrom`
@@ -458,7 +559,7 @@ Macronix chip. The Macronix chip will have "MX" written on the chip. You will
 use `flashrom_i945_sst` for the SST chip, and `flashrom_i945_mx` for the
 Macronix chip.
 
-Now run flashrom (for SST):
+Now run flashrom from the Libreboot 20160907 utils archive (for SST):
 
 	sudo ./flashrom_i945_sst -p internal -w coreboot.rom
 
@@ -495,7 +596,8 @@ Your flash chip is in an unknown state.
 If you see this, rejoice! It means that the flash was successful. Please do not
 panic. Shut down now, and wait a few seconds, then turn back on again.
 
-**WARNING: if flashrom complains about `/dev/mem` access, please
+**WARNING: if flashrom (from Libreboot 20160907 utils) complains
+about `/dev/mem` access, please
 run `sudo ./bucts 0`. If flashrom is complaining about `/dev/mem`, it means
 that you have `CONFIG_STRICT_DEVMEM` enabled in your kernel. Reboot with the
 following kernel parameter added in your bootloader: `iomem=relaxed` and try
@@ -512,17 +614,24 @@ volatile memory, powered by that CR2032 coin-cell battery.
 
 Assuming that everything went well:
 
-Flash the ROM for a second time. For this second flashing attempt, the upper
-64KiB bootblock is now read-write. Use the *unpatched* flashrom binary:
+Switch to flashprog now! (avoid flashrom)
+---------------------------------------
 
-	sudo ./flashrom -p internal -w libreboot.rom
+Flash the ROM for a second time. For this second flashing attempt, the upper
+64KiB bootblock is now read-write. Use the *unpatched* flashprog binary:
+
+	sudo ./flashprog -p internal -w libreboot.rom
+
+NOTE: At this point, we recommend use of flashprog instead of flashrom, for
+the reasons mentioned in the [Libreboot 20240225
+release](../../news/libreboot20240225.md).
 
 To reset bucts, do this:
 
 	sudo ./bucts 0
 
 ONLY set bucts back to 0 if you're sure that the upper 64KiB bootblock is
-flashed. It is flashed if flashrom said VERIFIED when running the above
+flashed. It is flashed if flashprog said VERIFIED when running the above
 command.
 
 If it said VERIFIED, shut down. If it didn't say VERIFIED, make sure bucts is
@@ -568,19 +677,24 @@ ASUS KFSN4-DRE
 
 The KFSN4-DRE has an LPC chip.  Most people have been flashing these
 internally, hot-swapping the chip out after boot, preserving the original chip,
-and using flashrom on a new chip as described above.
+and using flashprog on a new chip as described above.
 
 TODO: Document PLCC32 (LPC) flashing.
 The [FlexyICE](https://www.coreboot.org/FlexyICE) has been used to flash these
 chips, but it is hard to find now.  A custom flasher may be made such as
-[flashrom serprog stm32](https://github.com/wosk/stm32-vserprog-lpc) or
-[teensy flasher](https://www.flashrom.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher)
+[flashprog serprog stm32](https://github.com/wosk/stm32-vserprog-lpc) or
+[teensy flasher](https://www.flashprog.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher)
 
 TARGET: DELL Precision T1650 desktop
 ------------------------------------
 
 Refer to the [T1650 hardware page](../hardware/t1650.md).
 
+TARGET: DELL OptiPlex 7020/9020 SFF and MT desktops
+------------------------------------
+
+Refer to the [7020/9020 hardware page](../hardware/dell9020.md).
+
 TARGET: Apple Macbook2,1, Macbook1,1 and iMac5,2 (i945 platform)
 ----------------------------------------------------------------
 
@@ -604,6 +718,8 @@ Links to specific HP laptop pages:
 * [HP EliteBook 2170p](../hardware/hp2170p.md)
 * [HP EliteBook 2560p](../hardware/hp2560p.md)
 * [HP EliteBook 2570p](../hardware/hp2570p.md)
+* [HP EliteBook 820 G2](../hardware/hp820g2.md)
+* [HP EliteBook 8460p](../hardware/hp8460p.md)
 * [HP EliteBook 8470p](../hardware/hp8470p.md)
 * [HP EliteBook Folio 9470m](../hardware/hp9470m.md)
 
@@ -727,8 +843,8 @@ below.**
 On currently supported HP laptops AND desktops
 -------------------------------------
 
-**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
-OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 Refer to links about and the [hardware page](../hardware/) for installation
 instructions on each HP mainboard.
@@ -736,8 +852,8 @@ instructions on each HP mainboard.
 TARGET: ThinkPad X220/T420/T420s
 --------------------------------
 
-**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
-OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 Similar to X230 but there's only 1 flash. Intel ME image must be inserted
 if using release ROMs. See: [guide](ivy_has_common.md) (says ivy/haswell but
@@ -756,8 +872,8 @@ guide.**
 TARGET: Thinkpad X230/T430/T530/W530
 ---------------------
 
-**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
-OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 NOTE: no install docs for T430/T530/W530 yet, but check coreboot wiki.
 
@@ -774,8 +890,8 @@ Read [board documentation](/docs/install/x230_external.html) for disassembly.
 TARGET: Thinkpad X230t
 ---------------------
 
-**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
-OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
 make the rom image usable for external flashing.
@@ -790,8 +906,8 @@ guide.**
 TARGET: Thinkpad t440p/w541
 ---------------------
 
-**[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
-OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](../../news/safety.md).**
 
 Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
 make the rom image usable for external flashing.

site/docs/install/nvmutil.md

@@ -111,23 +111,26 @@ containing your NIC's configuration. This is the part that
 many people will struggle with, so we will dedicated an
 entire next section to it:
 
-Use flashrom
+Use flashprog
 ------------
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 If you wish to operate on the GbE section that's already
 flashed, you should *dump* the current full ROM image.
 If you already have a ROM image, you do not need to dump
 it, so you can skip this section.
 
-Download flashrom here:
+Download flashprog here:
 
-* <https://flashrom.org/>
+* <https://flashprog.org/>
 
-Using recent flashrom versions, you can extract this region. If
-your regions are unlocked, you can run flashrom on the target
+Using recent flashprog versions, you can extract this region. If
+your regions are unlocked, you can run flashprog on the target
 system, like so:
 
-	flashrom -p internal -r rom.bin
+	flashprog -p internal -r rom.bin
 
 If your system has two flash chips, the GbE region is usually
 stored on SPI1 (not SPI2). Otherwise, it may be that you have
@@ -145,7 +148,7 @@ from and writing to the chip. See:
 * <https://libreboot.org/docs/install/spi.html>
 
 If you're using an external programmer, the `-p internal`
-option should be changed accordingly. Read flashrom
+option should be changed accordingly. Read flashprog
 documentation, and make sure you have everything
 properly configured.
 
@@ -201,18 +204,18 @@ This will create the file `rom.bin.new`, which contains
 your modified GbE section with the NVM images inside; this
 includes your MAC address.
 
-Refer to flashrom documentation. You may flash the new ROM
+Refer to flashprog documentation. You may flash the new ROM
 like so, if running on the same system and the regions are
 read-write:
 
-	flashrom -p internal -w rom.bin.new
+	flashprog -p internal -w rom.bin.new
 
-Newer versions of flashrom support flashing just the specified
+Newer versions of flashprog support flashing just the specified
 region, like so:
 
-	flashrom -p internal --ifd -i gbe -w rom.bin.new
+	flashprog -p internal --ifd -i gbe -w rom.bin.new
 
-If you're running flashrom from host CPU on the target
+If you're running flashprog from host CPU on the target
 system, and it's dual flash, you can just flash the
 concatenated image, which you created earlier by running
 the `cat` program; dual-IC flash configurations appear to

site/docs/install/r400_external.md

@@ -64,7 +64,10 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
 
 MAC address {#macaddress}
 ===========

site/docs/install/spi.md

@@ -3,6 +3,25 @@ title: Read/write 25XX NOR flash via SPI protocol
 x-toc-enable: true
 ...
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+Introduction
+============
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
 OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 
@@ -14,7 +33,7 @@ which uses LPC flash in a PLCC32 socket, which you can simply hot-swap after
 booting the vendor firmware, and then flash internally. Simple!
 
 We will be using
-the [flashrom](https://flashrom.org/Flashrom) software which is written to
+the [flashprog](https://flashprog.org/Flashrom) software which is written to
 dump, erase and rewrite these flash chips.
 
 libreboot currently documents how to use these SPI programmers:
@@ -36,7 +55,7 @@ libreboot is running.
 
 *Internal* flashing means that the host CPU on your system can re-program the
 SPI flash, using an on-board SPI programmer (which all boards have). You do this
-from Linux, with flashrom.
+from Linux, with flashprog.
 
 *This* guide that you're reading now is for using an *external* programmer. It
 is called *external* because it's not the *internal* one on your mainboard.
@@ -67,9 +86,13 @@ You can download the serprog firmware here:\
 or here:\
 <https://notabug.org/libreboot/pico-serprog>
 
+You can also find the source code for these, under `src/` in Libreboot release
+archives (source code tarball), and/or under `src/` in `lbmk.git` if downloading
+using the build instructions below.
+
 Copy the file `rpi-pico-serprog.uf2` into your Pico. To build this firmware, you
 could build it yourself or you could also clone `lbmk.git` and [install build
-dependencies](..//build/#first-install-build-dependencies), then inside lbmk,
+dependencies](../build/#first-install-build-dependencies), then inside lbmk,
 do:
 
 	./build serprog rp2040 pico
@@ -85,6 +108,9 @@ pre-compiled in the next Libreboot release, after the 20230625 release.
 Disconnect the Pico and proceed to wire it to your
 [flash chip](/docs/install/spi.html#identify-which-flash-type-you-have).
 
+**NOTE: SCK and CLK mean the same thing. The diagram below says SCK, and other
+parts of this guide say CLK. It's the same thing!**
+
 ![Raspberry Pi Pico pinout, when using the firmware linked
 above](https://av.libreboot.org/rpi_pico/pinout_serprog.png)
 
@@ -104,7 +130,7 @@ will appear:
 Take note of the ttyACMx. Flashrom is now usable
 (substitute ttyACMx with what you observed earlier).
 
-	flashrom -p serprog:dev=/dev/ttyACMx,spispeed=16M
+	flashprog -p serprog:dev=/dev/ttyACMx,spispeed=16M
 
 spispeed=32M usually works, but since it's not much faster it's probably
 not worth it. The 12Mbps USB port is limiting the actual speed here.
@@ -205,8 +231,8 @@ SOIC16
 
 | Pin | Function |
 |-----|----------|
+|   1 | HOLD     |
 |   2 | VCC      |
-|   3 | HOLD     |
 |   7 | CS       |
 |   8 | MISO     |
 |   9 | WP       |
@@ -263,7 +289,7 @@ BeagleBone Black (BBB)
 ----------------------
 
 SSH into your BeagleBone Black. It is assumed that you are running Debian 9 on
-your BBB. You will run `flashrom` from your BBB.
+your BBB. You will run `flashprog` from your BBB.
 
 NOTE: This section is out of date, because it is written for Debian 9 (running
 on the BBB)
@@ -304,9 +330,9 @@ RemainAfterExit=yes
 WantedBy=multi-user.target
 ```
 
-Now test flashrom:
+Now test flashprog:
 
-	./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
+	./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
 
 It is important to use `spispeed=512` or a lower number such as 256 or 128,
 because otherwise the BBB will be quite unstable.
@@ -316,7 +342,7 @@ Example output:
 ```
 Calibrating delay loop... OK.
 No EEPROM/flash device found.
-Note: flashrom can never write if the flash chip isn't found automatically.
+Note: flashprog can never write if the flash chip isn't found automatically.
 ```
 
 This means that it's working (the clip isn't connected to any flash
@@ -335,7 +361,7 @@ TODO: document other SPI flashers
 Rasberry Pi (RPi)
 -----------------
 
-SSH into your Raspberry Pi. You will run `flashrom` from your Raspberry Pi.
+SSH into your Raspberry Pi. You will run `flashprog` from your Raspberry Pi.
 
 You must configure `spidev` on your Raspberry Pi. This is a special driver in
 the Linux kernel; technically, the driver name is `spi-bcm2835`.
@@ -443,7 +469,7 @@ Website:
 
 <https://librerpi.github.io/>
 
-Install flashrom
+Install flashprog
 ----------------
 
 If you're using a BBB or RPi, you will do this while SSH'd into those.
@@ -452,7 +478,7 @@ Flashrom is the software that you will use, for dumping, erasing and rewriting
 the contents of your NOR flash.
 
 In the libreboot build system, from the Git repository, you can download and
-install flashrom. Do this after downloading the
+install flashprog. Do this after downloading the
 [lbmk Git repository](https://codeberg.org/libreboot/lbmk):
 
 	cd lbmk
@@ -461,7 +487,7 @@ install flashrom. Do this after downloading the
 NOTE: debian, arch or void can be written instead of ubuntu2004. the debian
 script is also applicable to newer ubuntu versions
 
-	./update trees -b flashrom
+	./update trees -b flashprog
 
 If the `ubuntu2004` script complains about missing dependencies, just modify
 the dependencies config to remove those dependencies. The script is located
@@ -469,29 +495,29 @@ at `config/dependencies/ubuntu2004` and it is written for
 Ubuntu 20.04, but it should work fine in other Linux distributions that use
 the `apt-get` package manager.
 
-A `flashrom/` directory will be present, with a `flashrom` executable inside
+A `flashprog/` directory will be present, with a `flashprog` executable inside
 of it. If you got an error about missing package when running the dependencies
 command above, tweak `config/dependencies/ubuntu2004`. That
 script downloads and installs build dependencies in apt-get and it is intended
 for use on x86-64 systems running Ubuntu 20.04, but it should work in Raspbian
 on the Raspberry Pi.
 
-Alternatively, you may download flashrom directly from upstream
-at <https://flashrom.org/Flashrom>
+Alternatively, you may download flashprog directly from upstream
+at <https://flashprog.org/Flashrom>
 
 If you're flashing a Macronix flashchip on a ThinkPad X200, you will want to
-use a special patched version of flashrom, which you can download here:
+use a special patched version of flashprog, which you can download here:
 <https://vimuser.org/hackrom.tar.xz> - patched source code is available, and a
 binary is also available that you can simply run. Pass the `--workaround-mx`
-argument in flashrom. This mitigates stability issues.
+argument in flashprog. This mitigates stability issues.
 
-If you downloaded the flashrom source code directly, you can go into the
+If you downloaded the flashprog source code directly, you can go into the
 directory and simply type `make`. In the libreboot build system, build
 dependencies are documented in configuration files located
 at `config/dependencies/` which you can install
 using the `apt-get` software.
 
-How to use flashrom
+How to use flashprog
 ===================
 
 Read past these sections, further down this page, to learn about specific chip
@@ -506,11 +532,11 @@ current chip contents to a file.
 Run this command to see if 25xx flash is detected, with your RPi properly
 wired.
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
 
 For BBB, you must use a lower speed and a different device path:
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
 
 On BBB, never use a speed higher than `spispeed=512`. In some cases, you may
 even need to go as low as `spispeed=128`. The BBB is highly unstable and
@@ -528,11 +554,11 @@ or you can try flashing it with a new ROM.
 
 Dump it like so (RPi):
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
 
 For BBB, do this:
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
 
 It is advisable to take a *2nd* dump, e.g. `dump2.bin`, and then check sha1sum:
 
@@ -563,11 +589,11 @@ Writing
 
 Next, run this command (RPi):
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
 
 If using BBB:
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
 
 If using BBB, you may have to use a lower speed than 512. You may also have to
 re-flash several times before it works fully.
@@ -940,6 +966,9 @@ Your DIP8 IC has the same pinout as a SOIC8 IC.
 Replace WSON8 IC with SOIC8
 ---------------------------
 
+**NOTE: You can alternatively purchase WSON8 probes from a site like Aliexpress.
+They look similar to SOIC8 clips, and they work similarly.**
+
 You *can* connect a SOIC8 test clip, but you will struggle to get good
 connections and it will be extremely unreliable. DO NOT solder to the pads of
 the WSON8 directly; some people do this, but you shouldn't do it, because you

site/docs/install/spi.zh-cn.md

@@ -3,11 +3,27 @@ title: 通过 SPI 协议对 25XX NOR flash 进行读/写
 x-toc-enable: true
 ...
 
+Need help?
+==========
+
+Help is available on [Libreboot IRC](../../contact.md) and other channels.
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
+Introduction
+============
+
 **[安装之前请先阅读这些指示](../../news/safety.md)，否则你的机器可能会成砖：[安全措施](../../news/safety.md)**
 
 本指南将教你怎样使用各种工具，通过 SPI 协议对 25xx NOR flash 进行外部再编程。这是 coreboot 所支持的计算机中，最常见的 flash IC 类型。目前 libreboot 支持的每个系统，基本都使用这种类型的引导 flash；唯一的例外就是 ASUS KFSN4-DRE，它在 PLCC32 芯片座中使用了 LPC flash，你可以在供应商固件启动后，对其进行热切换，然后再内部刷入。十分简单！
 
-我们会用到 [flashrom](https://flashrom.org/Flashrom) 软件，这个软件可以读出、擦除及重写这些 flash 芯片。
+我们会用到 [flashprog](https://flashprog.org/Flashrom) 软件，这个软件可以读出、擦除及重写这些 flash 芯片。
 
 libreboot 目前记录了这些 SPI 编程器的使用方法：
 
@@ -20,7 +36,7 @@ libreboot 目前记录了这些 SPI 编程器的使用方法：
 
 大部分支持 libreboot 机器，都需要在第一次刷写的时候，借助这里的教程或是类似教程，对其进行外部再刷写。不过，目前支持的所有机器，你都可以在 libreboot 运行时，对其进行内部再刷写。
 
-*内部*刷写是指，主机上的 CPU 可以使用板载 SPI 编程器（每个主板都有）对 SPI flash 进行再编程。这可以在 Linux 上使用 flashrom 做到。
+*内部*刷写是指，主机上的 CPU 可以使用板载 SPI 编程器（每个主板都有）对 SPI flash 进行再编程。这可以在 Linux 上使用 flashprog 做到。
 
 你在读的*这个*教程，使用的是*外部*编程器。之所以叫*外部*，是因为用的不是主板上的*内部*编程器。
 
@@ -52,7 +68,7 @@ or here:\
 
 Copy the file `rpi-pico-serprog.uf2` into your Pico. To build this firmware, you
 could build it yourself or you could also clone `lbmk.git` and [install build
-dependencies](..//build/#first-install-build-dependencies), then inside lbmk,
+dependencies](../build/#first-install-build-dependencies), then inside lbmk,
 do:
 
 	./build serprog rp2040 pico
@@ -85,7 +101,7 @@ will appear:
 Take note of the ttyACMx. Flashrom is now usable
 (substitute ttyACMx with what you observed earlier).
 
-	flashrom -p serprog:dev=/dev/ttyACMx,spispeed=16M
+	flashprog -p serprog:dev=/dev/ttyACMx,spispeed=16M
 
 spispeed=32M usually works, but since it's not much faster it's probably
 not worth it. The 12Mbps USB port is limiting the actual speed here.
@@ -173,7 +189,7 @@ DIP8
 BeagleBone Black（BBB）
 ----------------------
 
-SSH 连接到你的 BeagleBone Black。假定你在 BBB 上用的是 Debian 9。你将在 BBB 上运行 `flashrom`。
+SSH 连接到你的 BeagleBone Black。假定你在 BBB 上用的是 Debian 9。你将在 BBB 上运行 `flashprog`。
 
 注意：该部分已过时，因为它是写给 BBB 上运行的 Debian 9 的。
 
@@ -212,9 +228,9 @@ RemainAfterExit=yes
 WantedBy=multi-user.target
 ```
 
-现在测试 flashrom：
+现在测试 flashprog：
 
-	./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
+	./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
 
 重要的一点是，要使用 `spispeed=512` 或者更低的速度，例如 256 或 128，否则 BBB 会十分不稳定。
 
@@ -223,7 +239,7 @@ WantedBy=multi-user.target
 ```
 Calibrating delay loop... OK.
 No EEPROM/flash device found.
-Note: flashrom can never write if the flash chip isn't found automatically.
+Note: flashprog can never write if the flash chip isn't found automatically.
 ```
 
 这表示正常工作了（夹子没连接任何 flash 芯片，所以出错是正常的）。
@@ -238,7 +254,7 @@ BBB 注意事项
 Rasberry Pi（RPi）
 -----------------
 
-SSH 连接到树莓派。你将在树莓派上运行 `flashrom`。
+SSH 连接到树莓派。你将在树莓派上运行 `flashprog`。
 
 你必须在树莓派上配置 `spidev`。这是 Linux 内核的一个特别驱动；它严谨的名字叫做 `spi-bcm2835`。
 
@@ -256,7 +272,7 @@ SSH 连接到树莓派。你将在树莓派上运行 `flashrom`。
 RPi 驱动强度（Drive Strength）
 ------------------
 
-RPi 的 flashrom 可能无法检测到一些系统的 SPI flash，即使你已经完美地连好了线并夹住了芯片。这可能是因为树莓派 GPIO 的驱动强度，它默认是 8mA。驱动强度本质上就是，在保持高电平最低电压的同时，引脚最高能输出的电流。对树莓派而言，这个电压是 3.0 V。
+RPi 的 flashprog 可能无法检测到一些系统的 SPI flash，即使你已经完美地连好了线并夹住了芯片。这可能是因为树莓派 GPIO 的驱动强度，它默认是 8mA。驱动强度本质上就是，在保持高电平最低电压的同时，引脚最高能输出的电流。对树莓派而言，这个电压是 3.0 V。
 
 类似地，也要满足一个最低电压，SPI flash 芯片才会把它当成高逻辑电平。这个值一般是 SPI flash 的 0.7*VCC，对 3.3V 的芯片而言也就是 2.31V。如果驱动强度太低了，那 flash 芯片的引脚处的电压可能会低于最低电压，导致它被视为发送了低逻辑电平，而不是高逻辑电平。
 
@@ -309,33 +325,33 @@ RPi 的自由固件
 
 <https://librerpi.github.io/>
 
-安装 flashrom
+安装 flashprog
 ----------------
 
 如果你在使用 BBB 或者 RPi，你需要在 SSH 进去之后再这么做。
 
 Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
 
-使用 Git 仓库中的 libreboot 构建系统，你可以下载并安装 flashrom。首先下载 [lbmk Git 仓库](https://codeberg.org/libreboot/lbmk)，然后执行：
+使用 Git 仓库中的 libreboot 构建系统，你可以下载并安装 flashprog。首先下载 [lbmk Git 仓库](https://codeberg.org/libreboot/lbmk)，然后执行：
 
 	cd lbmk
 	sudo ./build dependencies ubuntu2004
 
 注意：你可以输入 debian、arch 或 void 来替换 ubuntu。debian 脚本也可以用于新版 ubuntu。
 
-	./update trees -b flashrom
+	./update trees -b flashprog
 
 如果 `ubuntu2004` 报告了依赖缺失，编辑一下这个脚本，把缺失的依赖移除就行了。脚本位于 `config/dependencies/ubuntu2004`，它是写给 Ubuntu 20.04 的，但在其他使用 `apt-get` 包管理器的 Linux 发行版应该也能用。
 
-接下来，会出现一个 `flashrom/` 目录，其中有一个 `flashrom` 可执行文件。如果你在运行上面的依赖命令的时候，出现了缺失包的错误，则修改 `config/dependencies/ubuntu2004`。那个脚本会在 apt-get 中下载并安装构建依赖，它是为运行 Ubuntu 的 x86-64 系统写的，但在树莓派上的 Raspbian 应该能用。
+接下来，会出现一个 `flashprog/` 目录，其中有一个 `flashprog` 可执行文件。如果你在运行上面的依赖命令的时候，出现了缺失包的错误，则修改 `config/dependencies/ubuntu2004`。那个脚本会在 apt-get 中下载并安装构建依赖，它是为运行 Ubuntu 的 x86-64 系统写的，但在树莓派上的 Raspbian 应该能用。
 
-或者，你可以直接从上游下载 flashrom，位于：<https://flashrom.org/Flashrom>
+或者，你可以直接从上游下载 flashprog，位于：<https://flashprog.org/Flashrom>
 
-如果你是在 ThinkPad X200 上刷写 Macronix flash 芯片，则要使用一个 flashrom 的特别修改版，下载地址在这里：<https://vimuser.org/hackrom.tar.xz> —— 其中有修改版的源代码，也有可以直接运行的二进制文件。将 `--workaround-mx` 参数传给 flashrom。这会缓解稳定性问题。
+如果你是在 ThinkPad X200 上刷写 Macronix flash 芯片，则要使用一个 flashprog 的特别修改版，下载地址在这里：<https://vimuser.org/hackrom.tar.xz> —— 其中有修改版的源代码，也有可以直接运行的二进制文件。将 `--workaround-mx` 参数传给 flashprog。这会缓解稳定性问题。
 
-如果你直接下载了 flashrom 源代码，你可以进入目录并直接运行 `make`。在 libreboot 构建系统中，`config/dependencies/` 处的脚本写明了构建依赖，你可以直接使用 `apt-get` 软件安装。
+如果你直接下载了 flashprog 源代码，你可以进入目录并直接运行 `make`。在 libreboot 构建系统中，`config/dependencies/` 处的脚本写明了构建依赖，你可以直接使用 `apt-get` 软件安装。
 
-如何使用 flashrom
+如何使用 flashprog
 ===================
 
 请先阅读本页更下方的部分，了解特定的芯片类型及其接线方法。
@@ -347,11 +363,11 @@ Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
 
 树莓派正确接线后，运行这个命令来查看是否检测到 25xx flash：
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768
 
 对 BBB 而言，必须使用更慢的速度及不同的设备路径：
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512
 
 在 BBB 上，绝对不要使用高于 `spispeed=512` 的速度。有时候，你可能还要低到 `spispeed=128` 的速度。BBB 对 SPI 刷写而言非常不稳定、不可靠。在读取的时候，要多次读出，并检查它们的 checksum 是否一致，然后再刷。你可能需要多次刷写芯片！
 
@@ -361,11 +377,11 @@ Flashrom 是用来读出、擦除、重写 NOR flash 内容的软件。
 
 在 RPi 上，这样读出：
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r dump.bin
 
 BBB 的话，这样：
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r dump.bin
 
 建议读出*两次*，比如弄一个 `dump2.bin`，然后检查 sha1sum：
 
@@ -386,11 +402,11 @@ BBB 的话，这样：
 
 接下来，运行这个命令（RPi）：
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
 
 如果用的是 BBB：
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w /path/to/libreboot.rom
 
 用 BBB 的时候，可能得使用低于 512 的速度。你也许还得多次重复刷写，才能完全工作。
 
@@ -627,6 +643,9 @@ DIP8 IC 的引脚分配和 SOIC8 IC 一样。
 使用 SOIC8 替换 WSON8 IC
 ---------------------------
 
+**NOTE: You can alternatively purchase WSON8 probes from a site like Aliexpress.
+They look similar to SOIC8 clips, and they work similarly.**
+
 你*连是可以连* SOIC8 测试夹，但要连接效果好，需要费点功夫，而且这也十分不可靠。不要直接焊接 WSON8 的焊盘；有些人会这样做，但你不要这样做，因为你这样很容易就会损坏焊盘。
 
 WSON8 的引脚分配和 SOIC8 一样，但它是球状 QFN（四边扁平无引脚封装）。它没有合适的夹子，有时候称为 QFN8。

site/docs/install/spi_generic.md

@@ -3,6 +3,9 @@ title: Generic SPI Flashing Guide
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
 OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 
@@ -83,24 +86,24 @@ sudo ldto merge spicc spicc-spidev
 Using Flashrom
 ==============
 
-Most linux distros will provide flashrom in their default repositories.
-You can also download flashrom in binary form with [libreboot utils.](https://libreboot.org/download.html#https)
+Most linux distros will provide flashprog in their default repositories.
+You can also download flashprog in binary form with [libreboot utils.](https://libreboot.org/download.html#https)
 Here is an example using raspbian:
 
 ```
 sudo apt update
-sudo apt install flashrom
+sudo apt install flashprog
 ```
 
 Reading/writing from SPI works respectively as such:
 
 ```
-sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r /path/to/read.bin
-sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
+sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -r /path/to/read.bin
+sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=32768 -w /path/to/libreboot.rom
 ```
 
 Note that `spispeed` varies based on the board in question.
 A standard lower limit is *512.*
 For example, to read on a board with a lower SPI speed, you may try:
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r /path/to/read.bin
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r /path/to/read.bin

site/docs/install/t400_external.md

@@ -3,6 +3,9 @@ title: Flashing the ThinkPad T400 externally
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 Dell Latitude E6400
 ===================
 
@@ -77,7 +80,7 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
 
 MAC address {#macaddress}
 ===========

site/docs/install/t440p_external.md

@@ -3,6 +3,18 @@ title: ThinkPad T440p external flashing
 x-toc-enable: true
 ...
 
+Buy Libreboot preinstalled
+==========================
+
+This laptop is available to buy with Libreboot pre-installed:
+<https://minifree.org/product/libreboot-t440p/>
+
+Introduction
+============
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
 OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 
@@ -65,7 +77,7 @@ external flashing.
 	dd if=libreboot.rom of=bottom.rom bs=1M count=8
 
 Flash the top chip with top.rom, and tho bottom chip with bottom.rom.
-Don't worry about knowing which chip is which on a standard setup; flashrom will let you know if the 
+Don't worry about knowing which chip is which on a standard setup; flashprog will let you know if the 
 image size is incorrect for the chip you're flashing.
 
 

site/docs/install/t500_external.md

@@ -3,6 +3,9 @@ title: ThinkPad T500 external flashing
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **If you haven't bought a T500 yet: the [Dell Latitude
 E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
 it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
@@ -73,7 +76,7 @@ Flash chip size {#flashchips}
 
 Use this to find out:
 
-	flashrom -p internal
+	flashprog -p internal
 
 MAC address {#macaddress}
 ===========

site/docs/install/t60_unbrick.md

@@ -3,6 +3,9 @@ title: ThinkPad T60 Recovery guide
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 This section documents how to recover from a bad flash that prevents
 your ThinkPad T60 from booting.
 
@@ -160,16 +163,16 @@ which all draw a lot of current, more than your flasher can provide.
 
 Example command:
 
-	sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w libreboot.rom -V
+	sudo ./flashprog -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w libreboot.rom -V
 
-If flashrom complains about multiple flash chips detected, just pass the `-c`
+If flashprog complains about multiple flash chips detected, just pass the `-c`
 option as it suggests, and pick any of the chips it lists. `spispeed=4096` or
 lower (e.g. `spispeed=512`) is recommended on this board. The flashing becomes
 unstable, on this machine, when you use higher speeds.
 
 Reverse the steps to re-assemble your system, after you've flashed the chip.
 
-It should be `Verifying flash... VERIFIED` at the end. If flashrom
+It should be `Verifying flash... VERIFIED` at the end. If flashprog
 complains about multiple flash chip definitions detected, then choose
 one of them following the instructions in the output.
 

site/docs/install/x200_external.md

@@ -3,6 +3,9 @@ title: First-time ThinkPad X200 flashing
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **If you haven't bought an X200 yet: the [Dell Latitude
 E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
 it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
@@ -25,7 +28,7 @@ Flash chip size
 
 Run this command on x200 to find out flash chip model and its size:
 
-	flashrom -p internal
+	flashprog -p internal
 
 MAC address
 ===========
@@ -106,7 +109,7 @@ Look just above the 7 in TP37 (that's GPIO33):
 
 ![](https://av.libreboot.org/x200/gpio33_location.jpg)
 
-By default we would see this in lenovobios, when trying flashrom -p
+By default we would see this in lenovobios, when trying flashprog -p
 internal -w rom.rom:
 
 ```
@@ -147,7 +150,7 @@ that does the flashing; Lenovo BIOS then probably sees that and runs that, inste
 of setting PRx and going for normal boot. It is theoretically possible that we
 could discover how this works, by debugging the Lenovo BIOS update utility (in
 Windows), and then replicate what it is doing, with some tool for Linux,
-then load a flashrom binary into memory and the ROM to flash (for the BIOS
+then load a flashprog binary into memory and the ROM to flash (for the BIOS
 region). You would do this with GPIO33 grounded, and the payload program would
 actually flash the entire chip, with just a normal libreboot image.
 

site/docs/install/x200_external.uk.md

@@ -3,6 +3,9 @@ title: Прошивка ThinkPad X200 вперше
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **If you haven't bought an X200 yet: the [Dell Latitude
 E6400](../../news/e6400.md) is much easier to flash; no disassembly required,
 it can be flashed entirely in software from Dell BIOS to Libreboot. It is the
@@ -25,7 +28,7 @@ same hardware generation (GM45), with same CPUs, video processor, etc.**
 
 Виконайте цю команду на x200, щоб дізнатися модель флеш-чіпа та його розмір:
 
-    flashrom -p internal
+    flashprog -p internal
 
 MAC адреса
 ===========
@@ -106,7 +109,7 @@ sgsit дізнався про контакт під назвою GPIO33, яки
 
 ![](https://av.libreboot.org/x200/gpio33_location.jpg)
 
-Це замовчуванням ми побачимо це в lenovobios, під час спроби flashrom -p
+Це замовчуванням ми побачимо це в lenovobios, під час спроби flashprog -p
 internal -w rom.rom:
 
     FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
@@ -141,7 +144,7 @@ internal -w rom.rom:
 встановлення PRx і переходу до нормального завантаження. Теоретично можливо, що ми
 зможемо дізнатися, як це працює, налагодивши утиліту оновлення BIOS Lenovo (у
 Windows), а потім відтворивши її дії за допомогою якогось інструменту для Linux,
-а потім завантаживши двійковий файл flashrom в пам'ять та ROM для прошивки (для BIOS
+а потім завантаживши двійковий файл flashprog в пам'ять та ROM для прошивки (для BIOS
 регіона). Ви б зробили це з заземленням GPIO33, і програма корисного навантаження
 фактично прошиє весь чіп, лише звичайним образом libreboot.
 

site/docs/install/x230_external.md

@@ -3,6 +3,12 @@ title: ThinkPad X230/X230T external flashing
 x-toc-enable: true
 ...
 
+This machine is available to purchase with Libreboot pre-installed:
+<https://minifree.org/product/libreboot-x230/>
+
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 **[PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING](../../news/safety.md),
 OR YOU MIGHT BRICK YOUR MACHINE: [SAFETY PRECAUTIONS](../../news/safety.md)**
 
@@ -58,7 +64,7 @@ external flashing.
 	dd if=libreboot.rom of=bottom.rom bs=1M count=8
 
 Flash the top chip with top.rom, and tho bottom chip with bottom.rom.
-Don't worry about knowing which chip is which on a standard setup; flashrom will let you know if the 
+Don't worry about knowing which chip is which on a standard setup; flashprog will let you know if the 
 image size is incorrect for the chip you're flashing.
 
 

site/docs/linux/grub_cbfs.md

@@ -3,6 +3,9 @@ title: Modifying grub.cfg in CBFS
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 Before you follow this guide, it is advisable that you have the ability to
 flash externally, just in case something goes wrong.
 
@@ -27,7 +30,7 @@ a *soft brick* where your machine is effectively useless and, in that scenario,
 may or may not require external flashing equipment for restoring the machine to
 a known state.
 
-Compile flashrom and cbfstool
+Compile flashprog and cbfstool
 =============================
 
 libreboot does not currently distribute utilities pre-compiled. It only
@@ -75,34 +78,34 @@ The `cbfstool` utility is what you shall use. It is used to manipulate CBFS
 (coreboot file system) which is a file system contained within the coreboot
 ROM image; as a *coreboot distribution*, libreboot inherits this technology.
 
-You will also want to build `flashrom` which libreboot recommends for reading
+You will also want to build `flashprog` which libreboot recommends for reading
 from and/or writing to the boot flash. In the libreboot build system, you can
 build it by running this command:
 
-	./update trees -b flashrom
+	./update trees -b flashprog
 
-An executable will be available at `src/flashrom/flashrom` after you have done
+An executable will be available at `src/flashprog/flashprog` after you have done
 this.
 
 Dump the boot flash
 ===================
 
 If you wish to modify your *existing* libreboot ROM, which was installed on
-your computer, you can use `flashrom` to acquire it.
+your computer, you can use `flashprog` to acquire it.
 
 Simply run the following, after using libreboot's build system to compile
-flashrom:
+flashprog:
 
-	sudo ./src/flashrom/flashrom -p internal -r dump.bin
+	sudo ./src/flashprog/flashprog -p internal -r dump.bin
 
-If flashrom complains about multiple flash chip definitions, do what it says to
+If flashprog complains about multiple flash chip definitions, do what it says to
 rectify your command and run it again.
 
 You may want to use the following, instead of `-p internal`:
 `-p internal:laptop=force_I_want_a_brick,boardmismatch=force`
 
 Do not let the word *brick* fools you. This merely disables the safety checks
-in flashrom, which is sometimes necessary depending on what ROM was already
+in flashprog, which is sometimes necessary depending on what ROM was already
 flashed, versus the new ROM image.
 
 The `internal` option assumes that internal read/write is possible; this is
@@ -195,17 +198,17 @@ Flash the modified ROM image
 Your modified `dump.bin` or other modified libreboot ROM can then be re-flashed
 using:
 
-	sudo ./flashrom -p internal -w dump.bin
+	sudo ./flashprog -p internal -w dump.bin
 
 If a `-c` option is required, use it and specify a flash chip name. This is
-only useful when `flashrom` complains about multiple flash chips being
+only useful when `flashprog` complains about multiple flash chips being
 detected.
 
-If flashrom complains about wrong chip/board, make sure that your ROM is for
+If flashprog complains about wrong chip/board, make sure that your ROM is for
 the correct system. If you're sure, you can disable the safety checks by running
 this instead:
 
-	sudo ./flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w dump.bin
+	sudo ./flashprog -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w dump.bin
 
 If you need to use external flashing equipment, see the link above to the
 Raspberry Pi page.

site/docs/linux/index.md

@@ -46,14 +46,25 @@ Then still as root, do these commands:
 	export PATH="$PATH:/sbin"
 	update-grub
 
+NOTE: `update-grub` is very much Debian-centric. Not all distros will have it.
+On Arch-based distros for instance, you might do:
+
+	grub-mkconfig -o /boot/grub/grub.cfg
+
 Now your distro's GRUB menu should work, when your distro's GRUB bootloader is
 executed from Libreboot's SeaBIOS payload.
 
-Encrypted (LUKS/dm-crypt) installations
+Encrypted /boot via LUKS2 with argon2
 =======================================
 
 Full encryption for basic LUKS2 (with PBKDF or argon2 key derivation) is
-supported in libreboot. Legacy LUKS1 is also supported.
+supported in libreboot. Legacy LUKS1 is also supported. On *most* other
+systems, `/boot` must be unencrypted, but Libreboot supports use of the
+GRUB bootloader as a coreboot payload, directly in the boot flash.
+
+GRUB has code in it that can be used to unlock LUKS1 and LUKS2 dm-crypt,
+using the `cryptomount` command. With this, you can boot with *true* full
+disk encryption, by encrypting `/boot`.
 
 This is a boon for security, because it's harder
 to tamper with, and you could potentially write-protect plus maybe provide
@@ -92,6 +103,15 @@ At the time of the Libreboot 20231021 release, the GRUB upstream (on gnu.org)
 did not have these argon2 patches in its source tree, but Libreboot merges and
 maintains them out of tree.
 
+argon2id
+--------
+
+You should *specifically* use argon2id. Please ensure this, because some
+older LUKS2 setups defaulted to the weaker *argon2i*. This post by Matthew
+Garret contains information about that:
+
+<https://mjg59.dreamwidth.org/66429.html>
+
 NOTE: You should also read the instructions about about `GRUB_TERMINAL`.
 
 Rebooting system in case of freeze

site/docs/maintain/index.md

@@ -3,6 +3,9 @@ title: lbmk maintenance manual
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 In addition to this manual, you should also refer to [porting.md](porting.md)
 and [testing.md](testing.md).
 
@@ -82,6 +85,43 @@ the [freedom status page](../../freedom-status.md).
 Before *configuration* info, you will first be shown a brief overview of every
 project that Libreboot imports, such as coreboot.
 
+Environmental variables
+=======================
+
+LBMK\_THREADS
+-------------
+
+For example:
+
+	export LBMK_THREADS=2
+
+This would build on two threads, when running lbmk. It defaults to 1.
+
+Previous revisions of lbmk 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
+
+This has a similar effect compared to `LBMK_STATUS="y"` but you probably don't
+need to use this option yourself.
+
 Projects/files downloaded/generated by lbmk
 ===========================================
 
@@ -99,8 +139,8 @@ This directory is created when running any of the following commands, with the
 right arguments:
 
 	./build roms ARGUMENTS_HERE
-	./build serprog stm32
-	./build serprog rp2040
+	./build roms serprog stm32
+	./build roms serprog rp2040
 
 Simply speaking, `bin/` shall contain finished ROM images or firmware, that
 can then be installed (flashed) to the target device.
@@ -189,8 +229,9 @@ src/bios\_extract/
 Used by the vendor file handler scripts. The upstream that we use is here:
 <https://review.coreboot.org/bios_extract>
 
-Specifically: the pfs extract utility from this is used on Dell vendor updates,
-to extract SCH5545 EC (Environment Control) firmware.
+The `dell_inspiron_1100_unpacker.py` script is used here, to extract from Dell
+BIOS updates, to get at the VGA ROM for Nvidia GPU on certain models of Dell
+Latitude E6400.
 
 src/biosutilities/
 ---------------
@@ -198,9 +239,8 @@ src/biosutilities/
 Used by the vendor file handler scripts. The upstream that we use is here:
 <https://github.com/platomav/BIOSUtilities>
 
-The `dell_inspiron_1100_unpacker.py` script is used here, to extract from Dell
-BIOS updates, to get at the VGA ROM for Nvidia GPU on certain models of Dell
-Latitude E6400.
+Specifically: the pfs extract utility from this is used on Dell vendor updates,
+to extract SCH5545 EC (Environment Control) firmware.
 
 src/coreboot/
 ---------------
@@ -222,12 +262,12 @@ This may be less efficient on disk usage, but it simplifies the logic greatly.
 Coreboot also uses its own toolchain called *crossgcc*, and crossgcc is in fact
 compiled *per tree* in Libreboot.
 
-src/flashrom/
+src/flashprog/
 ---------------
 
-Please also visit: <https://flashrom.org/>
+Please also visit: <https://flashprog.org/>
 
-Although currently unused by any part of lbmk, we provide flashrom for the
+Although currently unused by any part of lbmk, we provide flashprog for the
 convenience of users, and this is copied to release archives. Flashrom is the
 program that you will use to read, erase and write the flash, containing
 coreboot firmware.
@@ -348,7 +388,7 @@ may not have much RAM.
 Where large files (or a large number of files) are handled by lbmk on a
 temporary basis, this `tmp/` directory is created and then used.
 
-vendor/
+vendorfiles/
 ---------------
 
 Used by the vendor file handler scripts, referenced in certain coreboot configs.
@@ -527,37 +567,34 @@ This file can contain several configuration lines, each being a string, such
 as:
 
 * `tree="default"` (example entry)
-* `romtype="normal"` (example entry)
 * `rev="ad983eeec76ecdb2aff4fb47baeee95ade012225"` (example entry)
-* `arch="x86_64"` (example entry)
+* `xarch="i386-elf"` (example entry)
 * `payload_grub="y"` (example entry)
 * `payload_grub_withseabios="y"` (example entry)
 * `payload_seabios="y"` (example entry)
 * `payload_memtest="y"` (example entry)
 * `payload_uboot="y"` (example entry)
 * `payload_seabios_withgrub="y"` (example entry)
+* `payload_seabios_grubonly="y"` (example entry)
 * `grub_scan_disk="ata"`
 * `uboot_config=default` (specify which U-Boot tree to use)
-* `vendorfiles="n"`
-* `microcode_required="y"`
+* `release="n"` (example entry)
+* `status=stable` (example entry)
+* `xtree="default"` (example entry)
+* `tree_depend="default"` (example entry)
 
 The `tree` value refers to `config/coreboot/TREE`; in other words, a given
 target could specify a name other than its own as the tree; it would then
 re-use code from that tree, rather than providing its own.
 
-The `romtype` entry is used during the building of ROM images, to define
-special steps; for example, d8d16sas` would tell lbmk that a fake PIKE2008
-ROM must be inserted into CBFS (prevents hanging on SeaBIOS).
-
 The `rev` entry defines which coreboot revision to use, from the
 coreboot Git repository. *At present, lbmk only supports use of the official
 repository from the upstream coreboot project*.
 
-The `arch` entry specifies which CPU architecture is to be used: currently
-recognized entries are `x86_32`, `x86_64`, `ARMv7` and `AArch64`. *Setting it
-to a non-native arch means that necessary crossgcc-arch will be compiled and be
-available when building roms, but not necessarily built or discovered when
-individual scripts are called manually.*
+The `xarch` entry specifies which CPU architecture is to be used: currently
+recognized entries are `i386-elf`, `arm-eabi` and `aarch64-elf`. This is the
+target architecture for building GCC/toolchain from coreboot crossgcc,
+hence `xarch`.
 
 The `payload_grub` entry specifies whether or not GRUB is to be included in
 ROM images.
@@ -571,6 +608,11 @@ in ROM images. This option is *automatically* enabled
 if `payload_grub_withseabios` and/or `payload_seabios_withgrub` are also turned
 on.
 
+The `payload_seabios_grubonly` option, if enabled, creates separate ROM
+images alongside regular `seabios_withgrub` ones, where the `grubonly` ones
+start SeaBIOS but disable the menu and only ever load GRUB from CBFS, which
+then provides the boot for your machine.
+
 The `payload_memtest` entry specifies whether or not MemTest86+ is to be
 included in ROM images; it will only be included in ROM images for *text mode*
 startup, on x86 machines.
@@ -591,12 +633,32 @@ on a ThinkPad X60 with the optical drive may cause GRUB to hang, so on that
 machine it is advisable to set this option to `ahci` (becuse the default HDD
 slot is AHCI).
 
-The `vendorfiles` entry doesn't affect anything in code, except that
-the `noblobs` string will be appended to ROM image file names, on releases;
-ditto `nomicrocode` but in that case, the behaviour is: if no microcode to
-begin with, only `nomicrocode` images will be named, otherwise ROM images with
-and without microcode updates will be provided in releases (CPU microcode
-updates).
+The `release` variable can be set to n, which makes the `script/update/release`
+script skip that target, when creating release images. For example, a given
+board may not be stable and you don't want images for it to be included in the
+release.
+
+The `status` variable can be set to whatever you want, but anything other
+than `stable` will make `script/build/roms` ask for y/n confirmation if
+not building images using `script/update/release`.
+
+Recommended strings for `status` could be: `stable`, `unstable`, `broken`
+or `untested`. Alternatively, you might state `wip`. You can set whatever
+string you want here.
+
+The `xtree` option specifies that a given tree with use a specific coreboot
+tree for compiling crossgcc. This can be used to skip building gcc if OK on
+a given board; two trees may use the same crossgcc as each other.
+
+The `tree_depend` option means that a given tree needs another tree, defined
+by this variable, to also be present.
+
+### config/coreboot/BOARDNAME/warn.txt
+
+Additionally: the `warn.txt` file can be included alongside target.cfg, to
+provide warning of any potential issues or quirks. For example, raminit may
+only be reliable with certain modules. This is printed on the user's terminal
+when building that target.
 
 ### config/coreboot/BOARDNAME/config/
 
@@ -1000,7 +1062,7 @@ Updated each time lbmk runs, based on either `git describe` or, on release
 archives, this file is static and never changes. It says the *time* of
 whichever Libreboot revision is currently in use (time of commit).
 
-At least, you will now learn about the *scripts* (exclusively written as
+At last, you will now learn about the *scripts* (exclusively written as
 posix shell scripts) that constitute the entire Libreboot build system, lbmk:
 
 Scripts in root directory of lbmk
@@ -1013,8 +1075,12 @@ This is the main script in lbmk, Libreboot's build system. It is what executes
 all other parts of the Libreboot build system. The rules are as follows:
 
 * Argument zero, representing the name of the symlink, will be used to
-  execute `script/LINKNAME/mode/option` - for example: `./build roms all`
+  execute `script/LINKNAME/COMMAND` - for example: `./build roms all`
   would execute `script/build/roms all` in `sh`.
+* In the above example, `LINKNAME` could also be `vendor`. In examples below,
+  symlinks are described pointing to `build` (the actual script). The script
+  works by checking argument zero, so it would look in a different directory
+  under `script/` matching `LINKNAME` - in this case, `script/vendor/`
 * `TMPDIR` is exclicitly set, providing a constant location where temporary
   files and directories can be made. `TMPDIR` is exported by the parent to
   all children; for example, `./build roms all` would export it
@@ -1036,7 +1102,13 @@ update
 ---------------
 
 Symbolic link, pointing to the `build` script. This is executed by the user, or
-by lbmk, referencing scripts under `script/update/*/`.
+by lbmk, referencing scripts under `script/update/`.
+
+vendor
+---------------
+
+Symbolic link, pointing to the `build` script. This is executed by the user, or
+by lbmk, referincing scripts under `script/vendor/`
 
 include/
 ===============
@@ -1045,27 +1117,6 @@ This directory contains *helper scripts*, to be included
 by main scripts using the `.` command (called the `source`
 command in `bash`, but we rely upon posix `sh` only).
 
-include/err.sh
----------------
-
-Generic error handling, used by all lbmk scripts.
-
-This also contains functions to verify the current libreboot version, and check
-whether Git is properly initialised on the host system. It also contains
-the `setvars` function, which provides a shorthand way of initialising many
-variables (combined with use of `eval`), which lbmk uses heavily.
-
-This function also contains `x_` and `xx_` which lbmk uses to execute commands
-and ensure that they cause an exit (with non-zero status) from lbmk, if they
-return an error state; the `xx_` function calls `fail()` which a script must
-provide, to perform some action before calling `err` which in turn prints an
-error message provided as argument. It is used similarly to the C
-function `err()` in BSD libc. The `x_` function simply calls `err`.
-
-This entire file is heavily inspired by `err.h` in BSD libc code. This file is
-heavily used by lbmk (it's used by every script), to provide clean error
-handling in `sh`.
-
 include/git.sh
 --------------
 
@@ -1095,7 +1146,7 @@ in the script at `script/vendor/download`, and it is used from there.
 include/option.sh
 ---------------
 
-Functions used by scripts under `script/update/vendor/`, for checking defconfig
+Functions used by scripts under `script/vendor/`, for checking defconfig
 files. These files are checked because the scripts need to know whether a given
 file is used; if it is, a path is then specified in defconfig, telling the vendor
 script either where it is, or where it should be downloaded to.
@@ -1106,11 +1157,22 @@ possible, and contains miscallaneous functions that don't belong anywhere else.
 The functions here are mostly those that deal with configuration files; scanning
 them to set variables and so on.
 
+This file also contains generic error handling, used by all lbmk scripts.
+
+This also contains functions to verify the current libreboot version, and check
+whether Git is properly initialised on the host system. It also contains
+the `setvars` function, which provides a shorthand way of initialising many
+variables (combined with use of `eval`), which lbmk uses heavily.
+
+This function also contains `x_()` which lbmk uses to execute commands
+and ensure that they cause an exit (with non-zero status) from lbmk, if they
+return an error state.
+
 script/
 =======
 
 *All* scripts under `script/` are executed only by the main `lbmk` script,
-conforming to the standard `buildpath/mode/option` e.g. `build/roms` - so,
+conforming to the standard `buildpath/option` e.g. `build/roms` - so,
 running `./build roms` would run `script/build/roms`.
 
 script/build/
@@ -1214,29 +1276,19 @@ When the ROM is finished compiling, it will appear under a directory in `bin/`
 This script is the beating heart of Libreboot. Break it, and you break
 Libreboot!
 
-### script/build/grub
-
-This builds the `grub.elf` file and keymap configuration files, placing these
-under `elf/grub/` for use by `script/build/roms`.
-
-Command: `./build grub`
-
-This builds the `grub-mkstandalone` utility under `src/grub/`, which is used
-by `script/build/roms` to insert GRUB payloads inside coreboot ROM
-images.
-
-### script/build/serprog
+Serprog images:
 
 Build firmware images for serprog-based SPI programmers, where they use an
 STM32 MCU. It also builds for RP2040-based programmers like Raspberry Pi Pico.
 
-Example command: `./build serprog stm32`
+Example command: `./build roms serprog stm32`
 
-Example command: `./build serprog rp2040`
+Example command: `./build roms serprog rp2040`
 
 The `list` argument is available:
 
-	./build serprog stm32 list
+	./build roms serprog stm32 list
+	./build roms serprog rp2040 list
 
 Without arguments, all targets would be compiled, but you can specify a short
 list of targets instead, based on the output of `list`.

site/docs/maintain/porting.md

@@ -2,6 +2,9 @@
 title: Porting guide for new mainboards
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 NOTE: This page is largely Intel-centric, at present. It should be revised to
 cover more vendors. [Patches welcome!](../../git.md)
 
@@ -93,7 +96,7 @@ Wrong CBFS and or ROM size
 
 Different boards have different flash chip setups.
 Generally, you have one or two flash chips with a combined size of 4-16MB.
-Thankfully, flashrom will let you know the size of the flash chip you're flashing.
+Thankfully, flashprog will let you know the size of the flash chip you're flashing.
 For example: when flashing an X230, you'll see that one chip is 8192, and the other is 4096.
 The total rom size should therefore be set as 12MB.
 

site/docs/maintain/porting.uk.md

@@ -2,6 +2,9 @@
 title: Керівництво перенесення
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 Це керівнитво передбачається для тих, хто має дуже низький рівень знань про прошивку
 загалом та coreboot окремо.
 Більшість плат в coreboot може бути доволі легко перенесена в libreboot.
@@ -90,7 +93,7 @@ libreboot як `плата.`
 
 Різні плати мають різні налаштування чіпів флеш-пам'яті.
 Загалом, ви маєте один або два флеш-пам'яті з сумарним розміром в 4-16Мбайт.
-На щастя, flashrom дасть вам знати розмір флеш-чіпа, який ви прошиваєте.
+На щастя, flashprog дасть вам знати розмір флеш-чіпа, який ви прошиваєте.
 Наприклад: коли прошиваєте X230, ви побачите, що один чіп 8192, та інший 4096.
 Сумарний розмір rom тоді має бути встановлено на 12Мбайт.
 

site/docs/misc/emulation.md

@@ -36,9 +36,25 @@ qemu-system-aarch64 -bios bin/qemu_arm64_12mb/uboot_payload_qemu_arm64_12mb_libg
 	-M virt,secure=on,virtualization=on,acpi=on -cpu cortex-a53 -m 768M -serial stdio -vga none -display none
 ```
 
-NOTE: After the 20230625 release, U-Boot support was removed from x86 Qemu; it's
-also problematic on ARM-based Qemu. Only x86 qemu, with other payloads, is to
-be considered reliable for now.
+That command (above) does a serial console. Alper Nebi Yasak added this patch to Libreboot:
+<https://browse.libreboot.org/lbmk.git/commit/?id=444f2899e69e9b84fd5428625aa04b00c1341804>
+
+This enables a graphical display in qemu, like so (only works in releases
+after Libreboot 20231021, but not including Libreboot 20231021, so you
+must [build lbmk from git](../build/)). Command:
+
+```
+qemu-system-aarch64 \
+    -machine virt,secure=on,virtualization=on \
+    -cpu cortex-a72 -m 1G \
+    -serial stdio -device VGA \
+    -device qemu-xhci \
+    -device usb-kbd -device usb-mouse \
+    -bios bin/qemu_arm64_12mb/*.rom
+```
+
+NOTE: After the 20230625 release, U-Boot support was removed from x86 Qemu.
+It works fine on the aaarch64 one.
 
 Use Cases
 =========

site/download.html

@@ -1,294 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" dir="ltr">
-<head>
-  <meta charset="utf-8">
-  <meta name="generator" content="pandoc">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
-
-<!-- anti-social media tags -->
-  <meta property="og:title" content="Libreboot – Downloads">
-  <meta property="og:type" content="article" />
-  <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
-  <meta property="og:url" content="https://libreboot.org/download.html">
-  <meta name="twitter:card" content="summary_large_image">
-  <meta property="og:description" content="Libreboot – Downloads">
-  <meta property="og:site_name" content="Libreboot – Downloads">
-  <meta name="twitter:image:alt" content="Libreboot – Downloads">
-
-  <title>Libreboot – Downloads</title>
-  <link rel="stylesheet" href="/global.css">
-<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
-</head>
-<body>
-<div class="page">
-<header>
-<div class="title">
-<p class="title-logo">
-<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
-</p>
-<h1 class="title">Downloads</h1>
-</div>
-<ul>
-<li><a href="/">Home</a></li>
-<li><a href="/faq.html">FAQ</a></li>
-<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li>
-<li><strong><a href="/download.html">Download</a></strong></li>
-<li><a href="/docs/install/">Install</a></li>
-<li><a href="/docs/">Docs</a></li>
-<li><a href="/news/">News</a></li>
-<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
-<li><a href="/git.html">Send patch</a></li>
-<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li>
-<li><a href="/contact.html">Contact</a></li>
-<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li>
-</ul>
-<hr/>
-</header>
-<nav id="TOC">
-<h1>Navigate this page:</h1>
-<ul>
-<li><a
-href="#read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
-THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</a>
-<ul>
-<li><a href="#gpg-signing-key">GPG signing key</a>
-<ul>
-<li><a href="#new-key">NEW KEY</a></li>
-<li><a href="#old-key">OLD KEY:</a></li>
-</ul></li>
-<li><a href="#git-repository">Git repository</a></li>
-<li><a href="#https">HTTPS mirrors</a></li>
-<li><a href="#rsync">RSYNC mirrors</a></li>
-<li><a href="#http">HTTP mirrors</a></li>
-<li><a href="#ftp">FTP mirrors</a></li>
-<li><a href="#statically-linked">Statically linked</a></li>
-</ul></li>
-</ul>
-</nav>
-<div class="pagetext">
-<p><a href="download.html">English</a> | <a
-href="download.uk.html">українська</a></p>
-<p><a href="./">Return to index</a></p>
-<p>New releases are announced in the <a href="news/">main news
-section</a>.</p>
-<p>If you’re more interested in libreboot development, go to the <a
-href="../git.html">libreboot development page</a>, which also includes
-links to the Git repositories. The page on <a
-href="docs/maintain/">/docs/maintain/</a> describes how Libreboot is put
-together, and how to maintain it. If you wish to build Libreboot from
-source, <a href="docs/build/">read this page</a>.</p>
-<h1
-id="read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
-THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</h1>
-<p><strong>On newer Intel platforms that require Intel ME and/or MRC
-firmware, such as ThinkPad X230 or T440p, and/or HP laptops that require
-KBC1126 EC firmware, the release ROMs of Libreboot are MISSING certain
-files, that you must insert yourself. FAILURE to adhere to this warning
-may result in you bricking your machine (rendering it unbootable), if
-you were to flash the release ROMs without modifying them in any way.
-For more information, please read:</strong></p>
-<p><strong><a href="docs/install/ivy_has_common.html">Insert vendor
-files on Sandybridge/Ivybridge/Haswell</a></strong></p>
-<p>NOTE: This warning does not apply to ROMs that you compiled yourself,
-using lbmk. It only applies to release ROMs, because ME/MRC/EC firmware
-is <em>deleted</em> in release ROMs. The link above says how to re-add
-them. When building ROM images yourself, from source, Libreboot’s build
-system automatically handles it. See: <a href="docs/build/">Libreboot
-build instructions</a></p>
-<p>This isn’t required on <em>all</em> Libreboot-supported boards, but
-if in doubt, follow these instructions anyway. If you run the vendor
-scripts on a board that doesn’t need blobs, nothing will happen.</p>
-<div class="h"><h2 id="gpg-signing-key">GPG signing key</h2><a aria-hidden="true" href="#gpg-signing-key">[link]</a></div>
-<p><strong>The latest release is Libreboot 20231021, under the
-<code>testing</code> directory.</strong></p>
-<div class="h"><h3 id="new-key">NEW KEY</h3><a aria-hidden="true" href="#new-key">[link]</a></div>
-<p>Full key fingerprint:
-<code>98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856</code></p>
-<p>This key is for Libreboot releases <em>after</em> the 20160907
-release.</p>
-<p>Download the key here: <a href="lbkey.asc">lbkey.asc</a></p>
-<p>Libreboot releases are signed using GPG.</p>
-<div class="h"><h3 id="old-key">OLD KEY:</h3><a aria-hidden="true" href="#old-key">[link]</a></div>
-<p>This key is for Libreboot 20160907, and releases older than
-20160907:</p>
-<p>Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8
-C5B2</p>
-<p>The GPG key can also be downloaded with this exported dump of the
-pubkey: <a href="lbkeyold.asc">lbkeyold.asc</a>.</p>
-<pre><code>sha512sum -c sha512sum.txt
-gpg --verify sha512sum.txt.sig</code></pre>
-<div class="h"><h2 id="git-repository">Git repository</h2><a aria-hidden="true" href="#git-repository">[link]</a></div>
-<p>Links to regular release archives are listed on this page.</p>
-<p>However, for the absolute most bleeding edge up-to-date version of
-Libreboot, there is a Git repository that you can download from. Go
-here:</p>
-<p><a href="git.html">How to download Libreboot from Git</a></p>
-<div class="h"><h2 id="https">HTTPS mirrors</h2><a aria-hidden="true" href="#https">[link]</a></div>
-<p><strong>The latest release is Libreboot 20231021, under the
-<code>testing</code> directory.</strong></p>
-<p>These mirrors are recommended, since they use TLS (https://)
-encryption.</p>
-<p>You can download Libreboot from these mirrors:</p>
-<ul>
-<li><a href="https://www.mirrorservice.org/sites/libreboot.org/release/"
-class="uri">https://www.mirrorservice.org/sites/libreboot.org/release/</a>
-(University of Kent, UK)</li>
-<li><a href="https://mirrors.mit.edu/libreboot/"
-class="uri">https://mirrors.mit.edu/libreboot/</a> (MIT university,
-USA)</li>
-<li><a href="https://mirror.math.princeton.edu/pub/libreboot/"
-class="uri">https://mirror.math.princeton.edu/pub/libreboot/</a>
-(Princeton university, USA)</li>
-<li><a href="https://mirror.shapovalov.tech/libreboot/"
-class="uri">https://mirror.shapovalov.tech/libreboot/</a>
-(shapovalov.tech, Ukraine)</li>
-<li><a href="https://mirror.koddos.net/libreboot/"
-class="uri">https://mirror.koddos.net/libreboot/</a> (koddos.net,
-Netherlands)</li>
-<li><a href="https://mirror-hk.koddos.net/libreboot/"
-class="uri">https://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
-Hong Kong)</li>
-<li><a href="https://mirror.cyberbits.eu/libreboot/"
-class="uri">https://mirror.cyberbits.eu/libreboot/</a> (cyberbits.eu,
-France)</li>
-<li><a href="https://mirror.mangohost.net/libreboot/"
-class="uri">https://mirror.mangohost.net/libreboot/</a> (mangohost.net,
-Moldova)</li>
-</ul>
-<div class="h"><h2 id="rsync">RSYNC mirrors</h2><a aria-hidden="true" href="#rsync">[link]</a></div>
-<p>The following rsync mirrors are available publicly:</p>
-<ul>
-<li><a href="rsync://rsync.mirrorservice.org/libreboot.org/release/"
-class="uri">rsync://rsync.mirrorservice.org/libreboot.org/release/</a>
-(University of Kent, UK)</li>
-<li><a href="rsync://mirror.math.princeton.edu/pub/libreboot/"
-class="uri">rsync://mirror.math.princeton.edu/pub/libreboot/</a>
-(Princeton university, USA)</li>
-<li><a href="rsync://rsync.shapovalov.tech/libreboot/"
-class="uri">rsync://rsync.shapovalov.tech/libreboot/</a>
-(shapovalov.tech, Ukraine)</li>
-<li><a href="rsync://ftp.linux.ro/libreboot/"
-class="uri">rsync://ftp.linux.ro/libreboot/</a> (linux.ro, Romania)</li>
-<li><a href="rsync://mirror.koddos.net/libreboot/"
-class="uri">rsync://mirror.koddos.net/libreboot/</a> (koddos.net,
-Netherlands)</li>
-<li><a href="rsync://mirror-hk.koddos.net/libreboot/"
-class="uri">rsync://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
-Hong Kong)</li>
-<li><a href="rsync://mirror.mangohost.net/libreboot/"
-class="uri">rsync://mirror.mangohost.net/libreboot/</a> (mangohost.net,
-Moldova)</li>
-</ul>
-<p>Are you running a mirror? Contact the libreboot project, and the link
-will be added to this page!</p>
-<p>You can make your rsync mirror available via your web server, and
-also configure your <em>own</em> mirror to be accessible via rsync.
-There are many resources online that show you how to set up an rsync
-server.</p>
-<p>How to create your own rsync mirror:</p>
-<p>Useful for mirroring Libreboot’s entire set of release archives. You
-can put an rsync command into crontab and pull the files into a
-directory on your web server.</p>
-<p>If you are going to mirror the entire set, it is recommended that you
-allocate at least 25GiB. Libreboot’s rsync is currently about 12GiB, so
-allocating 25GiB will afford you plenty of space for the future. At
-minimum, you should ensure that at least 15-20GiB of space is available,
-for your Libreboot mirror.</p>
-<p><em>It is highly recommended that you use the libreboot.org
-mirror</em>, if you wish to host an official mirror. Otherwise, if you
-simply want to create your own local mirror, you should use one of the
-other mirrors, which sync from libreboot.org.</p>
-<p>Before you create the mirror, make a directory on your web server.
-For example:</p>
-<pre><code>mkdir /var/www/html/libreboot/</code></pre>
-<p>Now you can run rsync, for instance:</p>
-<pre><code>rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
-<p>You might put this in an hourly crontab. For example:</p>
-<pre><code>crontab -e</code></pre>
-<p>Then in crontab, add this line and save/exit (hourly crontab):</p>
-<pre><code>0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
-<p><strong>It’s extremely important to have the final forward slash (/)
-at the end of each path, in the above rsync command. Otherwise, rsync
-will behave very strangely.</strong></p>
-<p><strong>NOTE: <code>rsync.libreboot.org</code> is not directly
-accessible by the public, except those whose IPs are whitelisted. For
-bandwidth reasons, the firewall running on libreboot.org blocks incoming
-rsync requests, except by specific IPs.</strong></p>
-<p><strong>If you wish to run an rsync mirror, sync from one of the
-third party mirrors above and set up your mirror. You can then contact
-Leah Rowe, to have your IP addresses whitelisted for rsync usage - if
-the IP addresses match DNS A/AAAA records for your rsync host, this can
-be used. A script runs in an hourly crontab on libreboot.org, that
-fetches the A/AAAA records of whitelisted rsync mirrors, automatically
-adding rules permitting them to get through the firewall.</strong></p>
-<p>If you wish to regularly keep your rsync mirror updated, you can add
-it to a crontab. This page tells you how to use crontab: <a
-href="https://man7.org/linux/man-pages/man5/crontab.5.html"
-class="uri">https://man7.org/linux/man-pages/man5/crontab.5.html</a></p>
-<div class="h"><h2 id="http">HTTP mirrors</h2><a aria-hidden="true" href="#http">[link]</a></div>
-<p><strong>The latest release is Libreboot 20231021, under the
-<code>testing</code> directory.</strong></p>
-<p>WARNING: these mirrors are non-HTTPS which means that they are
-unencrypted. Your traffic could be subject to interference by
-adversaries. Make especially sure to check the GPG signatures, assuming
-that you have the right key. Of course, you should do this anyway, even
-if using HTTPS.</p>
-<ul>
-<li><a href="http://mirror.linux.ro/libreboot/"
-class="uri">http://mirror.linux.ro/libreboot/</a> (linux.ro,
-Romania)</li>
-<li><a href="http://mirror.helium.in-berlin.de/libreboot/"
-class="uri">http://mirror.helium.in-berlin.de/libreboot/</a>
-(in-berlin.de, Germany)</li>
-</ul>
-<div class="h"><h2 id="ftp">FTP mirrors</h2><a aria-hidden="true" href="#ftp">[link]</a></div>
-<p><strong>The latest release is Libreboot 20231021, under the
-<code>testing</code> directory.</strong></p>
-<p>WARNING: FTP is also unencrypted, like HTTP. The same risks are
-present.</p>
-<ul>
-<li><a href="ftp://ftp.mirrorservice.org/sites/libreboot.org/release/"
-class="uri">ftp://ftp.mirrorservice.org/sites/libreboot.org/release/</a>
-(University of Kent, UK)</li>
-<li><a href="ftp://ftp.linux.ro/libreboot/"
-class="uri">ftp://ftp.linux.ro/libreboot/</a> (linux.ro, Romania)</li>
-</ul>
-<div class="h"><h2 id="statically-linked">Statically linked</h2><a aria-hidden="true" href="#statically-linked">[link]</a></div>
-<p>Libreboot includes statically linked executables in some releases,
-built from the available source code. Those executables have certain
-libraries built into them, so that the executables will work on many
-Linux distros.</p>
-<p>To comply with GPL v2, source ISOs are supplied by the Libreboot
-project. You can find these source ISOs in the <code>ccsource</code>
-directory on the <code>rsync</code> mirrors.</p>
-<p>Libreboot releases past version 20160907 do not distribute statically
-linked binaries. Instead, these releases are source-only, besides
-pre-compiled ROM images for which the regular Libreboot source code
-archives suffice. These newer releases instead automate the installation
-of build dependencies, with instructions in the documentation for
-building various utilities from source.</p>
-<p>These executables are utilities such as <code>flashrom</code>.</p>
-<div id="footer">
-<hr />
-<ul>
-<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li>
-<li><a href="/git.html">Edit this page</a></li>
-<li><a href="/who.html">Who develops Libreboot?</a></li>
-<li><a href="/license.html">License</a></li>
-<li><a href="/template-license.html">Template</a></li>
-<li><a href="/logo-license.html">Logo</a></li>
-<li><a href="/contrib.html">Authors</a></li>
-</ul>
-<hr />
-</div>
-<p>Markdown file for this page: <a
-href="https://libreboot.org/download.md"
-class="uri">https://libreboot.org/download.md</a></p>
-<p><a href="/sitemap.html">Site map</a></p>
-<p>This HTML page was generated by the <a
-href="https://untitled.vimuser.org/">untitled static site
-generator</a>.</p>
-</div>
-</div>
-</body>
-</html>

site/download.md

@@ -11,51 +11,61 @@ Git repositories. The page on [/docs/maintain/](docs/maintain/) describes how
 Libreboot is put together, and how to maintain it. If you wish to build
 Libreboot from source, [read this page](docs/build/).
 
-READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
-====================================================================
+Buy Libreboot pre-installed
+-----------------
 
-**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
-ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
-the release ROMs of Libreboot are MISSING certain files, that you must insert
-yourself. FAILURE to adhere to this warning may result in you bricking your
-machine (rendering it unbootable), if you were to flash the release ROMs without
-modifying them in any way. For more information, please read:**
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
 
-**[Insert vendor files on Sandybridge/Ivybridge/Haswell](docs/install/ivy_has_common.md)**
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
 
-NOTE: This warning does not apply to ROMs that you compiled yourself, using
-lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
-in release ROMs. The link above says how to re-add them. When building ROM images
-yourself, from source, Libreboot's build system automatically handles it. See:
-[Libreboot build instructions](docs/build/)
+Safety warning
+--------------
 
-This isn't required on *all* Libreboot-supported boards, but if in doubt, follow
-these instructions anyway. If you run the vendor scripts on a board that doesn't
-need blobs, nothing will happen.
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](news/safety.md).**
 
 GPG signing key
 ---------------
 
-**The latest release is Libreboot 20231021, under the `testing` directory.**
+**The latest release is Libreboot 20240504, under the `stable` directory.**
 
 ### NEW KEY
 
-Full key fingerprint: `98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856`
+Full key fingerprint: `8BB1 F7D2 8CF7 696D BF4F  7192 5C65 4067 D383 B1FF`
 
-This key is for Libreboot releases *after* the 20160907 release.
+This key is for Libreboot releases *after* the 20240126 release. It applies to
+all Libreboot releases from the year 2024, and it will expire (unless revoked
+early) on 26 December 2028.
 
 Download the key here: [lbkey.asc](lbkey.asc)
 
 Libreboot releases are signed using GPG.
 
-### OLD KEY:
+### OLD KEY
+
+Full key fingerprint: `98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856`
+
+This key is for Libreboot releases *after* the 20160907 release, and up
+to the Libreboot 20240126 release. This key *expired* during December 2023,
+so you should use the *newer* key (see above) for the releases after
+Libreboot 20240126.
+
+Download the key here: [lbkey.asc](lbkeyold.asc)
+
+Libreboot releases are signed using GPG.
+
+### OLD OLD KEY:
 
 This key is for Libreboot 20160907, and releases older than 20160907:
 
 Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD  C804 969A 9795 05E8 C5B2
 
 The GPG key can also be downloaded with this exported dump of the
-pubkey: [lbkeyold.asc](lbkeyold.asc).
+pubkey: [lbkeyold.asc](lbkeyoldold.asc).
 
 	sha512sum -c sha512sum.txt
 	gpg --verify sha512sum.txt.sig
@@ -73,22 +83,21 @@ there is a Git repository that you can download from. Go here:
 HTTPS mirrors {#https}
 -------------
 
-**The latest release is Libreboot 20231021, under the `testing` directory.**
+**The latest release is Libreboot 20240504, under the `stable` directory.**
 
 These mirrors are recommended, since they use TLS (https://) encryption.
 
 You can download Libreboot from these mirrors:
 
+* <https://mirror.math.princeton.edu/pub/libreboot/> (Princeton
+university, USA)
+* <https://mirror.shapovalov.website/libreboot/> (shapovalov.website, Ukraine)
 * <https://www.mirrorservice.org/sites/libreboot.org/release/> (University
 of Kent, UK)
 * <https://mirrors.mit.edu/libreboot/> (MIT university, USA)
-* <https://mirror.math.princeton.edu/pub/libreboot/> (Princeton
-university, USA)
-* <https://mirror.shapovalov.tech/libreboot/> (shapovalov.tech, Ukraine)
 * <https://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
 * <https://mirror-hk.koddos.net/libreboot/> (koddos.net, Hong Kong)
 * <https://mirror.cyberbits.eu/libreboot/> (cyberbits.eu, France)
-* <https://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
 
 RSYNC mirrors {#rsync}
 -------------
@@ -98,11 +107,10 @@ The following rsync mirrors are available publicly:
 * <rsync://rsync.mirrorservice.org/libreboot.org/release/> (University of Kent,
 UK)
 * <rsync://mirror.math.princeton.edu/pub/libreboot/> (Princeton university, USA)
-* <rsync://rsync.shapovalov.tech/libreboot/> (shapovalov.tech, Ukraine)
+* <rsync://rsync.shapovalov.website/libreboot/> (shapovalov.website, Ukraine)
 * <rsync://ftp.linux.ro/libreboot/> (linux.ro, Romania)
 * <rsync://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
 * <rsync://mirror-hk.koddos.net/libreboot/> (koddos.net, Hong Kong)
-* <rsync://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
 
 Are you running a mirror? Contact the libreboot project, and the link will be
 added to this page!
@@ -166,7 +174,7 @@ crontab. This page tells you how to use crontab:
 HTTP mirrors {#http}
 ------------
 
-**The latest release is Libreboot 20231021, under the `testing` directory.**
+**The latest release is Libreboot 20240504, under the `stable` directory.**
 
 WARNING: these mirrors are non-HTTPS which means that they are
 unencrypted. Your traffic could be subject to interference by
@@ -180,7 +188,7 @@ if using HTTPS.
 FTP mirrors {#ftp}
 -----------
 
-**The latest release is Libreboot 20231021, under the `testing` directory.**
+**The latest release is Libreboot 20240504, under the `stable` directory.**
 
 WARNING: FTP is also unencrypted, like HTTP. The same risks are present.
 
@@ -205,4 +213,4 @@ images for which the regular Libreboot source code archives suffice. These newer
 releases instead automate the installation of build dependencies, with instructions
 in the documentation for building various utilities from source.
 
-These executables are utilities such as `flashrom`.
+These executables are utilities such as `flashprog`.

site/download.md.date

@@ -1 +0,0 @@
-1697840199

site/download.uk.html

@@ -1,299 +0,0 @@
-<!DOCTYPE html>
-<html lang="uk" dir="ltr">
-<head>
-  <meta charset="utf-8">
-  <meta name="generator" content="pandoc">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
-
-<!-- anti-social media tags -->
-  <meta property="og:title" content="Libreboot – Завантаження">
-  <meta property="og:type" content="article" />
-  <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
-  <meta property="og:url" content="https://libreboot.org/download.uk.html">
-  <meta name="twitter:card" content="summary_large_image">
-  <meta property="og:description" content="Libreboot – Завантаження">
-  <meta property="og:site_name" content="Libreboot – Завантаження">
-  <meta name="twitter:image:alt" content="Libreboot – Завантаження">
-
-  <title>Libreboot – Завантаження</title>
-  <link rel="stylesheet" href="/global.css">
-<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
-</head>
-<body>
-<div class="page">
-<header>
-<div class="title">
-<p class="title-logo">
-<img loading="lazy" class="title-logo" alt="Логотип Libreboot" src="/favicon.ico" />
-</p>
-<h1 class="title">Завантаження</h1>
-</div>
-<ul>
-<li><a href="/index.uk.html">Домашня</a></li>
-<li><a href="/faq.html">FAQ</a></li>
-<li><strong><a href="/freedom-status.html">Статус свободи</a></strong></li>
-<li><strong><a href="/download.uk.html">Завантаження</a></strong></li>
-<li><a href="/docs/install/">Встановлення</a></li>
-<li><a href="/docs/index.uk.html">Документація</a></li>
-<li><a href="/news/">Новини</a></li>
-<li><a href="https://codeberg.org/libreboot/lbmk/issues">Помилки</a></li>
-<li><a href="/git.uk.html">Відправити виправлення</a></li>
-<li><strong><a href="https://www.patreon.com/libreleah">Пожертвувати</a></strong></li>
-<li><a href="/contact.uk.html">Зв'язок</a></li>
-<li><strong><a href="https://minifree.org/">Придбати передвстановленим</a></strong></li>
-</ul>
-<hr/>
-</header>
-<nav id="TOC">
-<h1>Навігація цією сторінкою:</h1>
-<ul>
-<li><a
-href="#read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
-THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</a>
-<ul>
-<li><a href="#код-підпису-gpg">Код підпису GPG</a>
-<ul>
-<li><a href="#новий-ключ">НОВИЙ КЛЮЧ</a></li>
-<li><a href="#старий-ключ">СТАРИЙ КЛЮЧ:</a></li>
-</ul></li>
-<li><a href="#репозиторій-git">Репозиторій Git</a></li>
-<li><a href="#https">Дзеркала HTTPS</a></li>
-<li><a href="#rsync">Дзеркала RSYNC</a></li>
-<li><a href="#http">Дзеркала HTTP</a></li>
-<li><a href="#ftp">Дзеркала FTP</a></li>
-<li><a href="#статично-звязані">Статично зв’язані</a></li>
-</ul></li>
-</ul>
-</nav>
-<div class="pagetext">
-<p><a href="download.html">English</a> | <a
-href="download.uk.html">українська</a></p>
-<p><a href="./">попередній індекс</a></p>
-<p>Нові випуски оголошуються в <a href="news/">основній секції
-новин</a>.</p>
-<p>Якщо ви більше зацікавлені в розробці libreboot, пройдіть на <a
-href="../git.html">сторінку розробки libreboot</a>, яка також включає
-посилання на репозиторії Git. Сторінка на <a
-href="docs/maintain/">/docs/maintain/</a> описує те, як Libreboot
-складається разом, і як підтримувати його. Якщо ви бажаєте зібрати
-Libreboot із джерельного кода, <a href="docs/build/">прочитайте цю
-сторінку</a>.</p>
-<h1
-id="read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ
-THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</h1>
-<p><strong>On newer Intel platforms that require Intel ME and/or MRC
-firmware, such as ThinkPad X230 or T440p, and/or HP laptops that require
-KBC1126 EC firmware, the release ROMs of Libreboot are MISSING certain
-files, that you must insert yourself. FAILURE to adhere to this warning
-may result in you bricking your machine (rendering it unbootable), if
-you were to flash the release ROMs without modifying them in any way.
-For more information, please read:</strong></p>
-<p><strong><a href="docs/install/ivy_has_common.html">Insert vendor
-files on Sandybridge/Ivybridge/Haswell</a></strong></p>
-<p>NOTE: This warning does not apply to ROMs that you compiled yourself,
-using lbmk. It only applies to release ROMs, because ME/MRC/EC firmware
-is <em>deleted</em> in release ROMs. The link above says how to re-add
-them. When building ROM images yourself, from source, Libreboot’s build
-system automatically handles it. See: <a href="docs/build/">Libreboot
-build instructions</a></p>
-<p>This isn’t required on <em>all</em> Libreboot-supported boards, but
-if in doubt, follow these instructions anyway. If you run the vendor
-scripts on a board that doesn’t need vendor files, nothing will
-happen.</p>
-<div class="h"><h2 id="код-підпису-gpg">Код підпису GPG</h2><a aria-hidden="true" href="#код-підпису-gpg">[link]</a></div>
-<p><strong>Останнім випуском є Libreboot 20231021, в директорії
-<code>testing</code>.</strong></p>
-<div class="h"><h3 id="новий-ключ">НОВИЙ КЛЮЧ</h3><a aria-hidden="true" href="#новий-ключ">[link]</a></div>
-<p>Повний відбиток ключа:
-<code>98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856</code></p>
-<p>Вищезазначений ключ для Libreboot 20231021, та наступних
-випусків.</p>
-<p>Завантажте ключ тут: <a href="lbkey.asc">lbkey.asc</a></p>
-<p>Випуски Libreboot підписані з використанням GPG.</p>
-<div class="h"><h3 id="старий-ключ">СТАРИЙ КЛЮЧ:</h3><a aria-hidden="true" href="#старий-ключ">[link]</a></div>
-<p>Цей ключ для Libreboot 20160907 та всіх старіших випусків:</p>
-<p>Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8
-C5B2</p>
-<p>Ключ GPG також може бути завантажений разом із цим експортованим
-дампом публічного ключа: <a href="lbkeyold.asc">lbkeyold.asc</a>.</p>
-<pre><code>sha512sum -c sha512sum.txt
-gpg --verify sha512sum.txt.sig</code></pre>
-<div class="h"><h2 id="репозиторій-git">Репозиторій Git</h2><a aria-hidden="true" href="#репозиторій-git">[link]</a></div>
-<p>Посилання на архіви регулярних випусків зазначені на цій
-сторінці.</p>
-<p>Однак, для абсолютно найновішої версії Libreboot, існує репозиторії
-Git, з якого можна завантажити. Ідіть сюди:</p>
-<p><a href="git.html">Як завантажити Libreboot через Git</a></p>
-<div class="h"><h2 id="https">Дзеркала HTTPS</h2><a aria-hidden="true" href="#https">[link]</a></div>
-<p><strong>Останнім випуском є Libreboot 20231021, в директорії
-<code>testing</code>.</strong></p>
-<p>Дані дзеркала є рекомендованими, оскільки використовують TLS
-(https://) шифрування.</p>
-<p>Ви можете завантажити Libreboot через дані дзеркала:</p>
-<ul>
-<li><a href="https://www.mirrorservice.org/sites/libreboot.org/release/"
-class="uri">https://www.mirrorservice.org/sites/libreboot.org/release/</a>
-(Кентський університет, Великобританія)</li>
-<li><a href="https://mirrors.mit.edu/libreboot/"
-class="uri">https://mirrors.mit.edu/libreboot/</a> (Університет МТІ,
-США)</li>
-<li><a href="https://mirror.math.princeton.edu/pub/libreboot/"
-class="uri">https://mirror.math.princeton.edu/pub/libreboot/</a>
-(Прінстонський університет, США)</li>
-<li><a href="https://mirror.shapovalov.tech/libreboot/"
-class="uri">https://mirror.shapovalov.tech/libreboot/</a>
-(shapovalov.tech, Україна)</li>
-<li><a href="https://mirror.koddos.net/libreboot/"
-class="uri">https://mirror.koddos.net/libreboot/</a> (koddos.net,
-Нідерланди)</li>
-<li><a href="https://mirror-hk.koddos.net/libreboot/"
-class="uri">https://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
-Гонконг)</li>
-<li><a href="https://mirror.cyberbits.eu/libreboot/"
-class="uri">https://mirror.cyberbits.eu/libreboot/</a> (cyberbits.eu,
-Франція)</li>
-<li><a href="https://mirror.mangohost.net/libreboot/"
-class="uri">https://mirror.mangohost.net/libreboot/</a> (mangohost.net,
-Moldova)</li>
-</ul>
-<div class="h"><h2 id="rsync">Дзеркала RSYNC</h2><a aria-hidden="true" href="#rsync">[link]</a></div>
-<p>Наступні дзеркала rsync доступні публічно:</p>
-<ul>
-<li><a href="rsync://rsync.mirrorservice.org/libreboot.org/release/"
-class="uri">rsync://rsync.mirrorservice.org/libreboot.org/release/</a>
-(Кентський університет, Великобританія)</li>
-<li><a href="rsync://mirror.math.princeton.edu/pub/libreboot/"
-class="uri">rsync://mirror.math.princeton.edu/pub/libreboot/</a>
-(Прінстонський університет, США)</li>
-<li><a href="rsync://rsync.shapovalov.tech/libreboot/"
-class="uri">rsync://rsync.shapovalov.tech/libreboot/</a>
-(shapovalov.tech, Україна)</li>
-<li><a href="rsync://ftp.linux.ro/libreboot/"
-class="uri">rsync://ftp.linux.ro/libreboot/</a> (linux.ro, Румунія)</li>
-<li><a href="rsync://mirror.koddos.net/libreboot/"
-class="uri">rsync://mirror.koddos.net/libreboot/</a> (koddos.net,
-Нідерланди)</li>
-<li><a href="rsync://mirror-hk.koddos.net/libreboot/"
-class="uri">rsync://mirror-hk.koddos.net/libreboot/</a> (koddos.net,
-Гонконг)</li>
-<li><a href="rsync://mirror.mangohost.net/libreboot/"
-class="uri">rsync://mirror.mangohost.net/libreboot/</a> (mangohost.net,
-Moldova)</li>
-</ul>
-<p>Ви підтримуєте роботу дзеркала? Зв’яжіться з проектом libreboot, і
-посилання буде додано до цієї сторінки!</p>
-<p>Ви можете зробити своє дзеркало rsync доступним через свій
-веб-сервер, а також налаштувати ваше <em>власне</em> дзеркало бути
-доступним через rsync. Є багато онлайн-ресурсів, які показують вам те,
-як налаштувати сервер rsync.</p>
-<p>Як створити ваше власне дзеркало rsync:</p>
-<p>Корисно для відзеркалювання повного набору архівів випусків
-Libreboot. Ви можете розмістити команду rsync в crontab та витягувать
-файли в директорію на вашому веб-сервері.</p>
-<p>Якщо ви збираєтесь відзеркалювати повний набір, рекомендовано, щоб
-вами було виділено хоча би 25 ГБ. Rsync Libreboot наразі приблизно 12
-ГБ, таким чином виділення 25 ГБ забезпечить вам багато місця на
-майбутнє. Мінімально, ви маєте переконатись, що хоча би 15-20 ГБ
-простору доступно, для вашого дзеркала Libreboot.</p>
-<p><em>Настійно рекомендується, щоб ви використовували дзеркало
-libreboot.org</em>, якщо бажаєте розміщувати офіційне дзеркало. В іншому
-випадку, якщо ви просто бажаєте створити своє власне локальне дзеркало,
-вам варто використовувати одне з інших дзеркал, яке синхронізується з
-libreboot.org.</p>
-<p>Перед створенням дзеркала, зробіть директорію на вашому веб-сервері.
-Для прикладу:</p>
-<pre><code>mkdir /var/www/html/libreboot/</code></pre>
-<p>Тепер ви можете виконувати rsync, для прикладу:</p>
-<pre><code>rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
-<p>Ви могли би розмістить це в щогодинний crontab. Для прикладу:</p>
-<pre><code>crontab -e</code></pre>
-<p>Потім в crontab, додайте цей рядок і збережіться/вийдіть (щогодинний
-crontab):</p>
-<pre><code>0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre>
-<p><strong>Це надзвичайно важливо, щоб мати в кінці косу лінію (/) в
-кінці кожного шляху, в вищезазначеній команді rsync. В інакшому випадку,
-rsync буде поводитись дуже дивно.</strong></p>
-<p><strong>ПОМІТКА: <code>rsync.libreboot.org</code> не є напряму
-доступним для громадськості, окрім тих, чиї IP у білому списку. Через
-пропускну здатність, Брандмауер, який працює на libreboot.org, блокує
-вхідні запити rsync, окрім окремих IP.</strong></p>
-<p><strong>Якщо ви бажаєте запустити дзеркало rsync, синхронізуйте з
-одного з дзеркал третіх сторін вище і встановіть своє дзеркало. Ви
-можете потім зв’язатись з Лією Роу, щоб мати ваші адреси IP внесеним в
-білий список для використання rsync - якщо адреси IP відповідають DNS
-A/AAAA записам для вашого хоста rsync, це може бути використано.
-Сценарій виконується в щогодинному crontab на libreboot.org, який
-отримує A/AAAA записи внесених в білий список дзеркал rsync, автоматично
-додаючи правила, які дозволяють їм проходити через
-брандмауер.</strong></p>
-<p>Якщо ви бажаєте регулярно тримати свої дзеркала rsync оновленими, ви
-можете додати це до crontab. Ця сторінка розповідає вам, як
-використовувати crontab: <a
-href="https://man7.org/linux/man-pages/man5/crontab.5.html"
-class="uri">https://man7.org/linux/man-pages/man5/crontab.5.html</a></p>
-<div class="h"><h2 id="http">Дзеркала HTTP</h2><a aria-hidden="true" href="#http">[link]</a></div>
-<p><strong>Останнім випуском є Libreboot 20231021, під директорією
-<code>testing</code>.</strong></p>
-<p>УВАГА: ці дзеркала є не-HTTPS, що означає, що вони незашифровані. Ваш
-трафік може бути об’єктом втручання противників. Особливо ретельно
-переконайтесь, щоб перевірити підписи GPG, передбачаючи, що ви маєте
-правильний ключ. Звісно, вам варто зробити це в будь-якому випадку,
-навіть при використанні HTTPS.</p>
-<ul>
-<li><a href="http://mirror.linux.ro/libreboot/"
-class="uri">http://mirror.linux.ro/libreboot/</a> (linux.ro,
-Румунія)</li>
-<li><a href="http://mirror.helium.in-berlin.de/libreboot/"
-class="uri">http://mirror.helium.in-berlin.de/libreboot/</a>
-(in-berlin.de, Німеччина)</li>
-</ul>
-<div class="h"><h2 id="ftp">Дзеркала FTP</h2><a aria-hidden="true" href="#ftp">[link]</a></div>
-<p><strong>Останнім випуском є Libreboot 20231021, під директорією
-<code>testing</code>.</strong></p>
-<p>УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики
-присутні.</p>
-<ul>
-<li><a href="ftp://ftp.mirrorservice.org/sites/libreboot.org/release/"
-class="uri">ftp://ftp.mirrorservice.org/sites/libreboot.org/release/</a>
-(Кентський університет, Великобританія)</li>
-<li><a href="ftp://ftp.linux.ro/libreboot/"
-class="uri">ftp://ftp.linux.ro/libreboot/</a> (linux.ro, Румунія)</li>
-</ul>
-<div class="h"><h2 id="статично-звязані">Статично зв’язані</h2><a aria-hidden="true" href="#статично-звязані">[link]</a></div>
-<p>Libreboot включає статично зв’язані виконувані файли в деяких
-випусках, побудовані з доступного джерельного кода. Ці виконувані файли
-мають деякі бібліотеки, вбудовані в них, так щоб виконувані файли
-працювали на багатьох дистрибутивах Linux.</p>
-<p>Для дотримання GPL v2, джерельні ISO постачаються проектом Libreboot.
-Ви можете знайти ці джерельні ISO в директорії <code>ccsource</code> на
-дзеркалах <code>rsync</code>.</p>
-<p>Попередні випуски Libreboot 20160907 не розповсюджують статично
-зв’язані двійкові файли. Натомість ці випуски є лише вихідними кодами,
-окрім попередньо скомпільованих образів ПЗП, для яких достатньо
-звичайних архівів джерельного коду Libreboot. Ці новіші випуски
-натомість автоматизують встановлення залежностей побудови, з інструкцієї
-в документації для побудови різних утиліт з джерельного коду.</p>
-<p>Ці виконувані файли є утилітами, подібними <code>flashrom</code>.</p>
-<div id="footer">
-<hr />
-<ul>
-<li><a href="/news/policy.html">Політика бінарних блобів</a></li>
-<li><a href="/git.html">Редагувати цю сторінку</a></li>
-<li><a href="/who.uk.html">Хто розробляє Libreboot?</a></li>
-<li><a href="/license.html">Ліцензія</a></li>
-<li><a href="/template-license.uk.html">Шаблон</a></li>
-<li><a href="/logo-license.uk.html">Логотип</a></li>
-<li><a href="/contrib.uk.html">Автори</a></li>
-</ul>
-<hr />
-</div>
-<p>Markdown: <a href="https://libreboot.org/download.uk.md"
-class="uri">https://libreboot.org/download.uk.md</a></p>
-<p><a href="/sitemap.html">Індекс сайта</a></p>
-<p>Ця сторінка була створена з <a
-href="https://untitled.vimuser.org/">untitled static site
-generator</a>.</p>
-</div>
-</div>
-</body>
-</html>

site/download.uk.md

@@ -11,51 +11,61 @@ x-toc-enable: true
 Libreboot складається разом, і як підтримувати його. Якщо ви бажаєте зібрати
 Libreboot із джерельного кода, [прочитайте цю сторінку](docs/build/).
 
-READ THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE
-====================================================================
+Buy Libreboot pre-installed
+--------------
 
-**On newer Intel platforms that require Intel ME and/or MRC firmware, such as
-ThinkPad X230 or T440p, and/or HP laptops that require KBC1126 EC firmware,
-the release ROMs of Libreboot are MISSING certain files, that you must insert
-yourself. FAILURE to adhere to this warning may result in you bricking your
-machine (rendering it unbootable), if you were to flash the release ROMs without
-modifying them in any way. For more information, please read:**
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
 
-**[Insert vendor files on Sandybridge/Ivybridge/Haswell](docs/install/ivy_has_common.md)**
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
 
-NOTE: This warning does not apply to ROMs that you compiled yourself, using
-lbmk. It only applies to release ROMs, because ME/MRC/EC firmware is *deleted*
-in release ROMs. The link above says how to re-add them. When building ROM images
-yourself, from source, Libreboot's build system automatically handles it. See:
-[Libreboot build instructions](docs/build/)
+Safety warning
+--------------
 
-This isn't required on *all* Libreboot-supported boards, but if in doubt, follow
-these instructions anyway. If you run the vendor scripts on a board that doesn't
-need vendor files, nothing will happen.
+**IMPORTANT ADVICE: [PLEASE READ THESE INSTRUCTIONS BEFORE INSTALLING/UPDATING
+LIBREBOOT](news/safety.md).**
 
 Код підпису GPG
 ---------------
 
-**Останнім випуском є Libreboot 20231021, в директорії `testing`.**
+**Останнім випуском є Libreboot 20240504, в директорії `stable`.**
 
 ### НОВИЙ КЛЮЧ
 
-Повний відбиток ключа: `98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856`
+Повний відбиток ключа: `8BB1 F7D2 8CF7 696D BF4F  7192 5C65 4067 D383 B1FF`
 
-Вищезазначений ключ для Libreboot 20231021, та наступних випусків.
+Вищезазначений ключ для Libreboot 20240126, та наступних випусків. This key
+is applicable to any release made on or after the date: 28 December 2023. It
+will expire on 26 December 2028.
 
 Завантажте ключ тут: [lbkey.asc](lbkey.asc)
 
 Випуски Libreboot підписані з використанням GPG.
 
-### СТАРИЙ КЛЮЧ:
+### СТАРИЙ КЛЮЧ
+
+Повний відбиток ключа: `98CC DDF8 E560 47F4 75C0  44BD D0C6 2464 FA8B 4856`
+
+This key is for Libreboot releases *after* the 20160907 release, and up
+to the Libreboot 20240504 release. This key *expired* during December 2023,
+so you should use the *newer* key (see above) for the releases after
+Libreboot 20240126.
+
+Завантажте ключ тут: [lbkey.asc](lbkeyold.asc)
+
+Випуски Libreboot підписані з використанням GPG.
+
+### СТАРИЙ СТАРИЙ КЛЮЧ:
 
 Цей ключ для Libreboot 20160907 та всіх старіших випусків:
 
 Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD  C804 969A 9795 05E8 C5B2
 
 Ключ GPG також може бути завантажений разом із цим експортованим дампом
-публічного ключа: [lbkeyold.asc](lbkeyold.asc).
+публічного ключа: [lbkeyold.asc](lbkeyoldold.asc).
 
 	sha512sum -c sha512sum.txt
 	gpg --verify sha512sum.txt.sig
@@ -73,22 +83,21 @@ need vendor files, nothing will happen.
 Дзеркала HTTPS {#https}
 -------------
 
-**Останнім випуском є Libreboot 20231021, в директорії `testing`.**
+**Останнім випуском є Libreboot 20240504, в директорії `stable`.**
 
 Дані дзеркала є рекомендованими, оскільки використовують TLS (https://) шифрування.
 
 Ви можете завантажити Libreboot через дані дзеркала:
 
+* <https://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський
+університет, США)
+* <https://mirror.shapovalov.website/libreboot/> (shapovalov.website, Україна)
 * <https://www.mirrorservice.org/sites/libreboot.org/release/> (Кентський
 університет, Великобританія)
 * <https://mirrors.mit.edu/libreboot/> (Університет МТІ, США)
-* <https://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський
-університет, США)
-* <https://mirror.shapovalov.tech/libreboot/> (shapovalov.tech, Україна)
 * <https://mirror.koddos.net/libreboot/> (koddos.net, Нідерланди)
 * <https://mirror-hk.koddos.net/libreboot/> (koddos.net, Гонконг)
 * <https://mirror.cyberbits.eu/libreboot/> (cyberbits.eu, Франція)
-* <https://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
 
 Дзеркала RSYNC {#rsync}
 -------------
@@ -98,11 +107,10 @@ need vendor files, nothing will happen.
 * <rsync://rsync.mirrorservice.org/libreboot.org/release/> (Кентський університет,
 Великобританія)
 * <rsync://mirror.math.princeton.edu/pub/libreboot/> (Прінстонський університет, США)
-* <rsync://rsync.shapovalov.tech/libreboot/> (shapovalov.tech, Україна)
+* <rsync://rsync.shapovalov.website/libreboot/> (shapovalov.website, Україна)
 * <rsync://ftp.linux.ro/libreboot/> (linux.ro, Румунія)
 * <rsync://mirror.koddos.net/libreboot/> (koddos.net, Нідерланди)
 * <rsync://mirror-hk.koddos.net/libreboot/> (koddos.net, Гонконг)
-* <rsync://mirror.mangohost.net/libreboot/> (mangohost.net, Moldova)
 
 Ви підтримуєте роботу дзеркала? Зв'яжіться з проектом libreboot, і посилання буде
 додано до цієї сторінки!
@@ -166,7 +174,7 @@ crontab. Ця сторінка розповідає вам, як викорис
 Дзеркала HTTP {#http}
 ------------
 
-**Останнім випуском є Libreboot 20231021, під директорією `testing`.**
+**Останнім випуском є Libreboot 20240504, під директорією `stable`.**
 
 УВАГА: ці дзеркала є не-HTTPS, що означає, що вони
 незашифровані. Ваш трафік може бути об'єктом втручання
@@ -180,7 +188,7 @@ crontab. Ця сторінка розповідає вам, як викорис
 Дзеркала FTP {#ftp}
 -----------
 
-**Останнім випуском є Libreboot 20231021, під директорією `testing`.**
+**Останнім випуском є Libreboot 20240504, під директорією `stable`.**
 
 УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики присутні.
 
@@ -205,4 +213,4 @@ Libreboot включає статично зв'язані виконувані
 випуски натомість автоматизують встановлення залежностей побудови, з інструкцієї
 в документації для побудови різних утиліт з джерельного коду.
 
-Ці виконувані файли є утилітами, подібними `flashrom`.
+Ці виконувані файли є утилітами, подібними `flashprog`.

site/download.uk.md.date

@@ -1 +0,0 @@
-1697840147

site/faq.md

@@ -3,27 +3,25 @@ title: Frequently Asked Questions
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 AKA Frequently Questioned Answers
 
+Buy Libreboot pre-installed
+==========
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
 Important issues
 ================
 
-What is the status of software freedom in Libreboot?
-----------------------------------------------------
-
-An article was written for Libreboot, to be maintained over time, that
-accurately describes the current status Libreboot in terms of software freedom,
-describing any caveats that exist for specific hardware platforms.
-
-Please read the article, thus:
-
-[Software and hardware freedom status for each mainboard supported by
-Libreboot](freedom-status.md)
-
-You may also find this other section of the FAQ useful:
-[What level of software freedom does Libreboot give
-me?](#what-level-of-software-freedom-does-libreboot-give-me)
-
 How to compile libreboot from source
 ------------------------------------
 
@@ -60,15 +58,15 @@ if you are interested in testing roms before they are released.
 Flashrom complains about DEVMEM access
 --------------------------------------
 
-If running `flashrom -p internal` for software based flashing, and
+If running `flashprog -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
+`iomem=relaxed` kernel parameter before running flashprog, or use a kernel
 that has `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` not enabled.
 
-Example flashrom output with both `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` enabled:
+Example flashprog output with both `CONFIG_STRICT_DEVMEM` and `CONFIG_IO_STRICT_DEVMEM` enabled:
 ```
-flashrom v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
-flashrom is free software, get the source code at https://flashrom.org
+flashprog v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
+flashprog is free software, get the source code at https://flashprog.org
 
 Calibrating delay loop... OK.
 Error accessing high tables, 0x100000 bytes at 0x000000007fb5d000
@@ -78,8 +76,8 @@ Error accessing DMI Table, 0x1000 bytes at 0x000000007fb27000
 /dev/mem mmap failed: Operation not permitted
 ```
 
-The backlight is darker on the left side of the screen when lowering the brightness on my ThinkPad X200/X200S/X200T, T400, T500, R400, W500, R500 and other Intel laptops
----------------------------------------------------------------------------------------------------------------
+Uneven backlight on GM45 ThinkPads
+----------------------------------
 
 We don't know how to detect the correct PWM value to use in
 coreboot, so we just use the default one in coreboot which has
@@ -88,8 +86,8 @@ this issue on some CCFL panels, but not LED panels.
 You can work around this in your distribution, by following the notes at
 [docs: backlight control](../docs/misc/#finetune-backlight-control-on-intel-gpus).
 
-The ethernet doesn't work on my X200/T400/X60/T60 when I plug in it 
--------------------------------------------------------------------
+GM45 thinkpad ethernet port doesn't autoconnect
+-----------------------------------------------
 
 This was observed on some systems using network-manager. This happens
 both on the original BIOS and in libreboot. It's a quirk in the
@@ -105,8 +103,8 @@ On systemd-based distros, you might try:
 (the service name might be different for you, depending on your
 configuration)
 
-My KCMA-D8 or KGPE-D16 doesn't boot with the PIKE2008 module installed 
------------------------------------------------------------------------
+PIKE2008 module hangs KGPE-D16 / KCMA-D8
+-----------------------------------------
 
 Loading the option ROM from the PIKE2008 module on either ASUS KCMA-D8
 or KGPE-D16 causes the system to hang at boot. It's possible to use
@@ -351,8 +349,7 @@ Technology* (AMT).
 
 Use of the `me_cleaner` utility is believed to minimize any security risk when
 using these Intel platforms, and coreboot *does* contain fully free code for
-sandybridge/ivybridge platforms. Freedom-wise, these are similar to libreboot
-compatible ThinkPads, and they are quite nice machines.
+sandybridge/ivybridge platforms.
 
 More information about the Management Engine can be found on various Web
 sites, including [me.bios.io](http://me.bios.io/Main_Page),
@@ -627,7 +624,7 @@ simply use dd(1) to extract only the non-padded portion. Continuing with the
 examples above, in order to extract a 2MiB x86 descriptorless ROM from a
 padded 16MiB image do the following:
 
-	dd if=flashromread.rom of=yourrom.rom ibs=14MiB skip=1
+	dd if=flashprogread.rom of=yourrom.rom ibs=14MiB skip=1
 
 With padding removed cbfstool will be able to operate on the image as usual.
 
@@ -960,6 +957,44 @@ OpenBSD. Other systems are untested, but should work just fine.
 See:
 [docs/bsd/](docs/bsd/)
 
+Windows??
+---------
+
+Yes, you can use Windows 10 and 11. They are not officially supported and the
+Libreboot project recommends that you *avoid* this choice, because Windows is
+proprietary software. What this means is that you do *not* have the freedom
+to use, study, adapt and share the software in any reasonable way. You are
+entirely at the mercy of Microsoft, whose motive is profit, as opposed to the
+general advancement of computer science and the welfare of everyone.
+
+See: [What is Free Software?](https://writefreesoftware.org/learn)
+
+In addition to being proprietary software, Windows is known to be full of bugs,
+including *backdoors*. When you *use* Windows, it will send information about
+you to third parties, used for a variety of purposes such as advertising, but
+it's quite possible that three-letter agencies may also receive your data if
+you use Windows.
+
+For the sake of your freedom, you should never, ever use Windows. Use Linux or
+BSD systems, which are well-supported. Anyway:
+
+[Video of Windows 10 booting up](https://yewtu.be/watch?v=BWq6XnWKQnM)
+
+[Video of Windows 11 booting up](https://yewtu.be/watch?v=OFHiMfVNNeA)
+
+Of note: Windows 11 officially requires at least TPM 1.2 to be supported, and
+it requires use of UEFI SecureBoot. To bypass this requirement, MajorGeeks has
+a guide, see: <https://www.majorgeeks.com/content/page/bypass_tpm.html>
+
+The person who tested this also stated that they were unable to perform an
+in-place upgrade from 10 to 11, so they had to wipe the drive and perform a
+clean (note: not clean, because Windows is full of NSA spyware) installation.
+
+In both cases, as shown above, the Windows operating system was booting from
+SeaBIOS, with the coreboot framebuffer initialised at startup, on an Intel GPU
+initialised via coreboot's *libgfxinit*, on November 2023 versions of Libreboot.
+We do not yet support booting with UEFI on x86 machines.
+
 Are other operating systems compatible?
 -------------------------------------------------------------------
 

site/faq.uk.md

@@ -3,27 +3,25 @@ title: Часті питання
 x-toc-enable: true
 ...
 
+NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
+now, as of 27 January 2024, which is a fork of flashrom.
+
 Також відомо як Відповіді на часті питання
 
+Buy Libreboot pre-installed
+==========
+
+If you want professional installation, Minifree Ltd sells [Libreboot
+pre-installed](https://minifree.org/) on select hardware, and it also provides
+a [Libreboot preinstall service](https://minifree.org/product/installation-service/)
+if you want to send your machine in to have Libreboot installed for you.
+
+Leah Rowe, the founder and lead developer of Libreboot, also owns and
+operates Minifree Ltd; sales provide funding for the Libreboot project.
+
 Важливі питання
 ================
 
-Який статус свободи програмного забезпечення в Libreboot?
-----------------------------------------------------
-
-Стаття була написана для Libreboot, для підтримки протягом часу, яка
-ретельно описує поточний статус Libreboot з точки зору свободи програмного забезпечення,
-пояснюючи будь-які підводні камені, які існують для конкретних платформ апаратного забезпечення.
-
-Будь ласка, прочитайте статтю щодо цього:
-
-[Статус свободи програмного та апаратного забезпечення для кожної плати, яка підтримується
-Libreboot](freedom-status.uk.md)
-
-Ви також можете знайти цю іншу секцію сторінки поширених запитань корисною:
-[Який рівень свободи програмного забезпечення Libreboot дає
-мені?](#який-рівень-програмної-свободи-дає-мені-libreboot)
-
 Як скомпілювати libreboot з джерельного коду
 ------------------------------------
 
@@ -46,15 +44,15 @@ Libreboot](freedom-status.uk.md)
 Flashrom скаржиться на доступ DEVMEM
 --------------------------------------
 
-Якщо запущено `flashrom -p internal` для програмної перепрошивки та
+Якщо запущено `flashprog -p internal` для програмної перепрошивки та
 ви отримуєте помилку, пов'язану з доступом до /dev/mem, вам слід перезавантажити систему з
-параметром ядра `iomem=relaxed` перед виконанням flashrom, або використовуйте ядро,
+параметром ядра `iomem=relaxed` перед виконанням flashprog, або використовуйте ядро,
 для якого не ввімкнено `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM`.
 
-Приклад виводу flashrom з обома `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM` ввімкненими:
+Приклад виводу flashprog з обома `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM` ввімкненими:
 ```
-flashrom v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
-flashrom is free software, get the source code at https://flashrom.org
+flashprog v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
+flashprog is free software, get the source code at https://flashprog.org
 
 Calibrating delay loop... OK.
 Error accessing high tables, 0x100000 bytes at 0x000000007fb5d000
@@ -64,7 +62,7 @@ Error accessing DMI Table, 0x1000 bytes at 0x000000007fb27000
 /dev/mem mmap failed: Operation not permitted
 ```
 
-Підсвічування в лівій частині екрана стає темнішим, якщо зменшити яскравість мого ноутбука ThinkPad X200/X200S/X200T, T400, T500, R400, W500, R500 та інших ноутбуків Intel
+Підсвічування в лівій частині екрана стає темнішим
 ---------------------------------------------------------------------------------------------------------------
 
 Ми не знаємо, як визначити правильне значення ШІМ для використання в
@@ -648,7 +646,7 @@ ROM та флеш-чіпом. Випадок вище, наприклад:
 наведені вище приклади, щоб видобути ROM без дескрипторів 2 МБ x86 із доповненого
 образа 16 МБ, виконайте наступне:
 
-	dd if=flashromread.rom of=вашrom.rom ibs=14MiB skip=1
+	dd if=flashprogread.rom of=вашrom.rom ibs=14MiB skip=1
 
 Після видалення заповнення cbfstool зможе працювати із образом як зазвичай.
 
@@ -981,6 +979,44 @@ OpenBSD. Інші системи не перевірені, але мають п
 Дивіться:
 [docs/bsd/](docs/bsd/index.uk.md)
 
+Windows??
+---------
+
+Yes, you can use Windows 10 and 11. They are not officially supported and the
+Libreboot project recommends that you *avoid* this choice, because Windows is
+proprietary software. What this means is that you do *not* have the freedom
+to use, study, adapt and share the software in any reasonable way. You are
+entirely at the mercy of Microsoft, whose motive is profit, as opposed to the
+general advancement of computer science and the welfare of everyone.
+
+See: [What is Free Software?](https://writefreesoftware.org/learn)
+
+In addition to being proprietary software, Windows is known to be full of bugs,
+including *backdoors*. When you *use* Windows, it will send information about
+you to third parties, used for a variety of purposes such as advertising, but
+it's quite possible that three-letter agencies may also receive your data if
+you use Windows.
+
+For the sake of your freedom, you should never, ever use Windows. Use Linux or
+BSD systems, which are well-supported. Anyway:
+
+[Video of Windows 10 booting up](https://yewtu.be/watch?v=BWq6XnWKQnM)
+
+[Video of Windows 11 booting up](https://yewtu.be/watch?v=OFHiMfVNNeA)
+
+Of note: Windows 11 officially requires at least TPM 1.2 to be supported, and
+it requires use of UEFI SecureBoot. To bypass this requirement, MajorGeeks has
+a guide, see: <https://www.majorgeeks.com/content/page/bypass_tpm.html>
+
+The person who tested this also stated that they were unable to perform an
+in-place upgrade from 10 to 11, so they had to wipe the drive and perform a
+clean (note: not clean, because Windows is full of NSA spyware) installation.
+
+In both cases, as shown above, the Windows operating system was booting from
+SeaBIOS, with the coreboot framebuffer initialised at startup, on an Intel GPU
+initialised via coreboot's *libgfxinit*, on November 2023 versions of Libreboot.
+We do not yet support booting with UEFI on x86 machines.
+
 Чи підтримуються інші операційні системи?
 -------------------------------------------------------------------
 

site/footer.de.include

@@ -2,6 +2,7 @@
 -------------------------------------------------------------------------------
 
 * [Binäre Blob Richtlinie](/news/policy.md)
+* [Freiheits Status](/freedom-status.md)
 * [Diese Seite bearbeiten](/git.de.md)
 * [Wer entwickelt Libreboot?](/who.de.md)
 * [Lizenz](/license.md)

site/footer.include

@@ -2,6 +2,7 @@
 -------------------------------------------------------------------------------
 
 * [Binary Blob Reduction Policy](/news/policy.md)
+* [Freedom status](/freedom-status.md)
 * [Edit this page](/git.md)
 * [Who develops Libreboot?](/who.md)
 * [License](/license.md)

site/footer.it.include

@@ -2,6 +2,7 @@
 -------------------------------------------------------------------------------
 
 * [Politica di riduzione di parti binarie proprietarie (blobs)](/news/policy.md)
+* [Grado di liberta' possibile](/freedom-status.md)
 * [Modifica questa pagina](/git.de.md)
 * [Chi sviluppa Libreboot?](/who.de.md)
 * [Licenza](/license.md)

site/footer.uk.include

@@ -2,12 +2,13 @@
 -------------------------------------------------------------------------------
 
 * [Політика бінарних блобів](/news/policy.md)
+* [Статус свободи](/freedom-status.md)
 * [Редагувати цю сторінку](/git.md)
 * [Хто розробляє Libreboot?](/who.uk.md)
 * [Ліцензія](/license.md)
 * [Шаблон](/template-license.uk.md)
 * [Логотип](/logo-license.uk.md)
-* [Автори](/contrib.uk.md)
+* [Автори](/contrib.md)
 
 -------------------------------------------------------------------------------
 

site/footer.zh-cn.include

@@ -2,6 +2,7 @@
 -------------------------------------------------------------------------------
 
 * [二进制 blob 政策](/news/policy.md)
+* [自由度现状](/freedom-status.md)
 * [编辑本页面](/git.md)
 * [谁在开发 Libreboot?](/who.md)
 * [许可证](/license.md)

site/freedom-status.md

@@ -242,8 +242,8 @@ Neutered ME required on these targets: `t420_8mb`, `t420s_8mb`, `t430_12mb`,
 `t440p_12mb`, `t440pmrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
 `w541_12mb`, `w541mrc_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
 `x230edp_12mb`, `x230t_12mb`, `x230t_16mb`, `hp8200sff`, `hp2560p_8mb`,
-`hp2570p_16mb`, `hp8300usdt_16mb`, `hp2170p_16mb`, `hp9470m_16mb`
-and `t1650_12mb`.
+`hp2570p_16mb`, `hp8300usdt_16mb`, `hp2170p_16mb`, `hp9470m_16mb`,
+`hp820g2_12mb` and `t1650_12mb`.
 
 As stated, Libreboot provides this in a state where the ME is no longer a
 threat to security. It initialises itself, but then does nothing, so it's
@@ -276,6 +276,11 @@ technically required, but highly recommended. To remove, do:
 
 	cbfstool filename.rom remove -n cpu_microcode_blob.bin
 
+On ASUS KFSN4-DRE, KCMA-D8 and KGPE-D16 boards, do this instead:
+
+	cbfstool filename.rom remove -n microcode_amd.bin
+	cbfstool filename.rom remove -n microcode_amd_fam15h.bin
+
 [Releases after Libreboot 20230423 will provide separate ROMs with microcode
 excluded, alongside default ones with microcode included.](news/microcode.md)
 

site/freedom-status.uk.md

@@ -333,7 +333,7 @@ Intel/x86
 `t440p_12mb`, `t440pmrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
 `w541_12mb`, `w541mrc_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
 `x230edp_12mb`, `x230t_12mb`, `x230t_16mb`, `hp8200sff_8mb`, `hp2560p_8mb`,
-`hp2570p_16mb`, `hp2170p_16mb`, `hp9470m_16mb` та `t1650_12mb`.
+`hp2570p_16mb`, `hp2170p_16mb`, `hp9470m_16mb`, `hp820g2_12mb` та `t1650_12mb`.
 
 Як заявлено, Libreboot надає це в стані, де ME більше не є
 загрозою для безпеки. Він ініціалізує себе, але потім нічого не робить, тому його

site/git.de.md

@@ -252,6 +252,14 @@ Ein weiterer Weg Patches zu senden ist Leah Rowe direkt eine email zu senden:
 Um den Prozess der Quelltext Überprüfung transparent zu gestalten,
 wird jedoch empfohlen künftig Codeberg zu verwenden.
 
+Mailing list
+------------
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
 Mirrors für lbmk.git
 ===================
 
@@ -261,6 +269,7 @@ Libreboot Veröffentlichungen  herstellt (inklusive kompilierter ROM Images).
 Du kannst `git clone` für alle diese Links ausführen (die Links können auch
 angeklickt werden, um Änderungen in deinem Web Browser anzusehen):
 
+* <https://git.sr.ht/~libreboot/lbmk>
 * <https://git.disroot.org/libreboot/lbmk>
 * <https://gitea.treehouse.systems/libreboot/lbmk>
 * <https://git.fosscommunity.in/libreboot/lbmk>
@@ -286,6 +295,7 @@ der Seite die Du gerade liest!
 Du kannst `git clone` für diese Links ausführen und/oder die Links
 anklicken um Änderungen in deinem Web Browser anzusehen). Siehe:
 
+* <https://git.sr.ht/~libreboot/lbwww>
 * <https://git.disroot.org/libreboot/lbwww>
 * <https://gitea.treehouse.systems/libreboot/lbwww>
 * <https://git.fosscommunity.in/libreboot/lbwww>

site/git.md

@@ -232,6 +232,14 @@ Another way to submit patches is to email Leah Rowe directly:
 However, for transparency of the code review process, it's recommended that you
 use Codeberg, for the time being.
 
+Mailing list
+------------
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
 Mirrors of lbmk.git
 ===================
 
@@ -241,6 +249,7 @@ produces Libreboot releases (including compiled ROM images).
 You can run `git clone` on any of these links (the links are also clickable,
 to view changes in your Web browser):
 
+* <https://git.sr.ht/~libreboot/lbmk>
 * <https://git.disroot.org/libreboot/lbmk>
 * <https://gitea.treehouse.systems/libreboot/lbmk>
 * <https://git.fosscommunity.in/libreboot/lbmk>
@@ -266,6 +275,7 @@ you are reading right now!
 You can run `git clone` on these links, and/or click to view changes in your
 Web browser. See:
 
+* <https://git.sr.ht/~libreboot/lbwww>
 * <https://git.disroot.org/libreboot/lbwww>
 * <https://gitea.treehouse.systems/libreboot/lbwww>
 * <https://git.fosscommunity.in/libreboot/lbwww>

site/git.uk.md

@@ -232,6 +232,14 @@ IRC-канал libreboot і повідомити канал, які виправ
 Однак, для прозорості процесу перевірки коду, ми рекомендуємо на даний момент
 використовувати Codeberg.
 
+Mailing list
+------------
+
+Libreboot has this mailing list:
+<https://lists.sr.ht/~libreboot/libreboot>
+
+The email address is [~libreboot/libreboot@lists.sr.ht](mailto:~libreboot/libreboot@lists.sr.ht)
+
 Дзеркала lbmk.git
 ===================
 
@@ -241,6 +249,7 @@ IRC-канал libreboot і повідомити канал, які виправ
 Ви можете виконати `git clone` на будь-якому з цих посилань (посилання є також доступними для натискання,
 для перегляду змін в вашому веб-браузері):
 
+* <https://git.sr.ht/~libreboot/lbmk>
 * <https://git.disroot.org/libreboot/lbmk>
 * <https://gitea.treehouse.systems/libreboot/lbmk>
 * <https://git.fosscommunity.in/libreboot/lbmk>
@@ -266,6 +275,7 @@ IRC-канал libreboot і повідомити канал, які виправ
 Ви можете виконати `git clone` на цих посиланнях, та/або натиснути для перегляду змін в вашому
 веб-браузері. Дивіться:
 
+* <https://git.sr.ht/~libreboot/lbwww>
 * <https://git.disroot.org/libreboot/lbwww>
 * <https://gitea.treehouse.systems/libreboot/lbwww>
 * <https://git.fosscommunity.in/libreboot/lbwww>

site/index.de.html

@@ -1,212 +0,0 @@
-<!DOCTYPE html>
-<html lang="de" dir="ltr">
-<head>
-  <meta charset="utf-8">
-  <meta name="generator" content="pandoc">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
-
-<!-- anti-social media tags -->
-  <meta property="og:title" content="Libreboot – Libreboot projekt">
-  <meta property="og:type" content="article" />
-  <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
-  <meta property="og:url" content="https://libreboot.org/index.de.html">
-  <meta name="twitter:card" content="summary_large_image">
-  <meta property="og:description" content="Libreboot – Libreboot projekt">
-  <meta property="og:site_name" content="Libreboot – Libreboot projekt">
-  <meta name="twitter:image:alt" content="Libreboot – Libreboot projekt">
-
-  <title>Libreboot – Libreboot projekt</title>
-  <link rel="stylesheet" href="/global.css">
-<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
-</head>
-<body>
-<div class="page">
-<header>
-<div class="title">
-<p class="title-logo">
-<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
-</p>
-<h1 class="title">Libreboot projekt</h1>
-</div>
-<ul>
-<li><a href="/index.de.html">Home</a></li>
-<li><a href="/faq.html">FAQ</a></li>
-<li><strong><a href="/freedom-status.html">Freiheits Status</a></strong></li>
-<li><strong><a href="/download.html">Download</a></strong></li>
-<li><a href="/docs/install/">Installation</a></li>
-<li><a href="/docs/">Dokumentation</a></li>
-<li><a href="/news/">Neuigkeiten</a></li>
-<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
-<li><a href="/git.de.html">Patch senden</a></li>
-<li><strong><a href="https://www.patreon.com/libreleah">Spenden</a></strong></li>
-<li><a href="/contact.de.html">Kontakt</a></li>
-<li><strong><a href="https://minifree.org/">Vorinstalliertes Gerät kaufen</a></strong></li>
-</ul>
-<hr/>
-</header>
-<nav id="TOC">
-<h1>Navigate this page:</h1>
-<ul>
-<li><a href="#warum-solltest-du-libreboot-verwenden">Warum solltest Du
-<em>Libreboot</em> verwenden?</a></li>
-<li><a href="#libreboot-ist-kein-coreboot-fork">Libreboot ist kein
-Coreboot Fork</a></li>
-<li><a href="#wie-kann-ich-helfen">Wie kann ich helfen</a></li>
-<li><a href="#übersetzungen-für-libreboot.org-benötigt">Übersetzungen
-für libreboot.org benötigt</a></li>
-</ul>
-</nav>
-<div class="pagetext">
-<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
-href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
-| <a href="index.uk.html">українська</a> | <a
-href="index.zh-cn.html">简体中文</a></p>
-<p>Das <em>Libreboot</em> Projekt bietet eine <a
-href="freedom-status.html">freie</a> <em>Boot Firmware</em> welche auf
-<a href="docs/hardware/">bestimmten Intel/AMD x86 und ARM Geräten</a>
-die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie),
-und dann einen Bootloader für dein Betriebssystem startet. <a
-href="docs/linux/">Linux</a> sowie <a href="docs/bsd/">BSD</a> werden
-gut unterstützt. Es ersetzt proprietäre BIOS/UEFI Firmware. Hilfe ist
-verfügbar via <a
-href="https://web.libera.chat/#libreboot">#libreboot</a> und <a
-href="https://libera.chat/">Libera</a> IRC.</p>
-<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
-<p><strong>NEUESTE VERSION: Die neueste Version von Libreboot ist
-20231021, veröffentlicht am 21. Oktober 2023. Siehe auch: <a
-href="news/libreboot20231021.html">Libreboot 20231021 release
-announcement</a>.</strong></p>
-<h2 id="warum-solltest-du-libreboot-verwenden">Warum solltest Du
-<em>Libreboot</em> verwenden?</h2>
-<p>Libreboot gibt dir <a
-href="https://writefreesoftware.org/">Freiheit</a> welche Du mit den
-meisten Boot Firmwares nicht hast, und zusätzlich schnellere Boot
-Geschwindigkeiten sowie <a href="docs/linux/grub_hardening.html">höhere
-Sicherheit</a>. Es ist extrem leistungsfähig und für viele Einsatzzwecke
-<a href="docs/maintain/">konfigurierbar</a>.</p>
-<p>Du hast Rechte. Das Recht auf Privatsphäre, Gedankenfreiheit,
-Meinungsäußerungsfreiheit, und Informationsfreiheit. In diesem
-Zusammenhang, Libreboot gibt dir diese Rechte. Deine Freiheit ist
-wichtig. <a href="https://yewtu.be/watch?v=Npd_xDuNi9k">Das Recht auf
-Reparatur</a> ist wichtig. Viele Menschen verwenden proprietäre
-(non-libre) Boot Firmware, sogar wenn Sie ein <a
-href="https://www.openbsd.org/">Libre OS</a> verwenden. Proprietäre
-Firmware <a href="faq.html#intel">enthält</a> häufig <a
-href="faq.html#amd">Hintertüren</a>, und kann fehlerhaft sein. Das
-Libreboot Projekt wurde im Dezember 2013 gegründet, mit dem Ziel,
-Coreboot Firmware auch für technisch unerfahrene Nutzer verfügbar zu
-machen.</p>
-<p>Das Libreboot Projekt verwendet <a
-href="https://www.coreboot.org/">Coreboot</a> für <a
-href="https://doc.coreboot.org/getting_started/architecture.html">die
-Initialiserung der Hardware</a>. Die Coreboot Installation ist für
-unerfahrene Benutzer überaus schwierig; sie übernimmt lediglich die
-Basis Initialisierung und springt dann zu einem separaten <a
-href="https://doc.coreboot.org/payloads.html">payload</a> Programm (z.B.
-<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
-href="https://www.tianocore.org/">Tianocore</a>), welche zusätzlich
-konfiguriert werden muss. <em>Libreboot löst dieses Problem</em>; es ist
-eine <em>Coreboot Distribution</em> mit einem <a
-href="docs/build/">automatisierten Build System</a> welches vollständige
-<em>ROM images</em> für eine robustere Installation erstellt.
-Dokumentation ist verfügbar.</p>
-<h2 id="libreboot-ist-kein-coreboot-fork">Libreboot ist kein Coreboot
-Fork</h2>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
-<p>Tatsächlich versucht Libreboot so nah am regulären Coreboot zu
-bleiben wie möglich, für jedes Board, aber mit vielen automatisch durch
-das Libreboot Build System zur Verfügung gestellten verschiedenen
-Konfigurationstypen.</p>
-<p>Ebenso wie <em>Alpine Linux</em> eine <em>Linux Distribution</em>
-ist, ist Libreboot eine <em>Coreboot Distribution</em>. Sofern Du ein
-ROM Image von Grund auf herstellen möchtest, musst Du zunächst
-Konfigurationen auf Experten Level durchführen, und zwar für Coreboot,
-GRUB sowie sämtliche Software die Du sonst noch verwenden möchtest um
-das ROM Image vorzubereiten. Mithilfe von <em>Libreboot</em> kannst Du
-sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen,
-anschliessend <code>make</code> ausführen, und es wird komplette ROM
-Images herstellen, ohne das Benutzer Eingaben oder Eingreifen von Nöten
-sind. Die Konfiguration wurde bereits im Vorfeld erledigt.</p>
-<p>Sofern Du das reguläre Coreboot herstellen wollen würdest, ohne
-hierfür das automatisierte Libreboot Build System zu verwenden, würde
-dies deutlich mehr Eingreifen und ein sehr tiefgreifendes technisches
-Verständnis voraussetzen um eine funktionsfähige Konfiguration
-herzustellen.</p>
-<p>Reguläre Binär Veröffentlichungen bieten diese ROM Images
-vor-kompiliert, und Du kannst dies einfach installieren ohne spezielle
-technische Kenntnisse oder Fertigkeiten abgesehen von der Fähigkeit
-einer <a href="docs/install/">vereinfachten Anleitung, geschrieben für
-technisch unerfahrene Benutzer</a> zu folgen.</p>
-<div class="h"><h2 id="wie-kann-ich-helfen">Wie kann ich helfen</h2><a aria-hidden="true" href="#wie-kann-ich-helfen">[link]</a></div>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
-<p>Der beste Weg wie Du helfen kannst, ist das <em>hinzufügen</em> neuer
-Mainboards in Libreboot, indem Du eine Konfiguration zur Verfügung
-stellst. Alles was von Coreboot unterstützt wird kann auch in Libreboot
-integriert werden, mithilfe von ROM Images in den Veröffentlichungen.
-Siehe auch:</p>
-<ul>
-<li><a href="docs/maintain/testing.html">Bewerbe dich um Boards zu
-testen oder zu pflegen</a></li>
-<li><a href="docs/maintain/porting.html">Anleitung um neue Mainboards
-hinzuzufügen</a></li>
-<li><a href="docs/maintain/">Libreboot Build System
-Dokumentation</a></li>
-</ul>
-<p>Zudem ist da noch Pflege des Build Systems (siehe oben), sowie
-<em>Dokumentation</em> welche wir sehr ernst nehmen. Dokumentation ist
-wichtig, in jedem Projekt.</p>
-<p><em>Hilfe für Benutzer</em> ist ebenso wichtig. Bleibe im IRC Chat,
-und falls Du kompetent genug bist jemandem bei seinem Problem zu helfen
-(oder bereit mit der Person gemeinsam zu lernen), dann ist dies ein
-wichtiger Beitrag zum Projekt. Viele Leute fragen zudem unter dem
-Subreddit <code>r/libreboot</code> nach Hilfe.</p>
-<p>Eine Liste mit Bugs gibt es unter <a
-href="https://codeberg.org/libreboot/lbmk/issues">Bug Tracker</a>.</p>
-<p>Sofern Du einen Bug findest oder einen Fix hast, <a
-href="git.de.html">hier sind Anleitungen um Patches zu schicken</a>,
-oder Du kannst davon berichten. Diese Website ist zudem in Markdown
-geschrieben und verfügbar in einem <a
-href="https://codeberg.org/libreboot/lbwww">separaten Repository</a> für
-welches Du auch Patches schicken kannst.</p>
-<p>Sämtliche Diskussionen über Entwicklung sowie Hilfe für Nutzer findet
-im IRC Kanal statt. Mehr Informationen gibt es unter <a
-href="contact.de.html">Kontakt</a>.</p>
-<h2 id="übersetzungen-für-libreboot.org-benötigt">Übersetzungen für
-libreboot.org benötigt</h2>
-<p>Libreboot hat derzeit übersetzte Webseiten in ukrainisch und
-französisch (aber bislang nicht für alle Seiten für keine der
-Sprachen)</p>
-<p>Sofern Du mit Übersetzungen helfen möchtest, kannst Du Seiten
-übersetzen, existierende Übersetzungen überarbeiten oder deine
-übersetzten Versionen schicken. Für Anleitungen, siehe bitte hier:</p>
-<p><a href="news/translations.de.html">Wie man Übersetzungen für
-libreboot.org bereitstellt</a></p>
-<p>Auch wenn jemand bereits an einer Übersetzung in einer bestimmten
-Sprache arbeitet, so können wir immer mehrere Leute gebrauchen. Desto
-mehr desto besser!</p>
-<div id="footer">
-<hr />
-<ul>
-<li><a href="/news/policy.html">Binäre Blob Richtlinie</a></li>
-<li><a href="/git.de.html">Diese Seite bearbeiten</a></li>
-<li><a href="/who.de.html">Wer entwickelt Libreboot?</a></li>
-<li><a href="/license.html">Lizenz</a></li>
-<li><a href="/template-license.html">Vorlage</a></li>
-<li><a href="/logo-license.html">Logo</a></li>
-<li><a href="/contrib.html">Autoren</a></li>
-</ul>
-<hr />
-</div>
-<p>Markdown-Datei: <a href="https://libreboot.org/index.de.md"
-class="uri">https://libreboot.org/index.de.md</a></p>
-<p><a href="/sitemap.html">Website karte</a></p>
-<p>Diese HTML-Seite wurde von <a
-href="https://untitled.vimuser.org/">untitled static site generator</a>
-erstellt.</p>
-</div>
-</div>
-</body>
-</html>

site/index.de.md

@@ -4,7 +4,7 @@ x-toc-enable: true
 ...
 
 Das *Libreboot* Projekt bietet
-eine [freie](freedom-status.md) *Boot
+eine [freie](https://writefreesoftware.org/) *Boot
 Firmware* welche auf [bestimmten Intel/AMD x86 und ARM Geräten](docs/hardware/)
 die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie),
 und dann einen Bootloader für dein Betriebssystem startet. [Linux](docs/linux/)
@@ -15,9 +15,15 @@ und [Libera](https://libera.chat/) IRC.
 
 <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
 
-**NEUESTE VERSION: Die neueste Version von Libreboot ist 20231021, veröffentlicht am
-21. Oktober 2023.
-Siehe auch: [Libreboot 20231021 release announcement](news/libreboot20231021.md).**
+You can also [buy Libreboot preinstalled](https://minifree.org/) from Minifree Ltd,
+on select hardware, aswell as send your compatible hardware
+for [Libreboot preinstallation](https://minifree.org/product/installation-service/).
+The founder and lead developer of Libreboot, Leah Rowe, also owns and operates
+Minifree; sales provide funding for Libreboot.
+
+**NEUESTE VERSION: Die neueste Version von Libreboot ist 20240504, veröffentlicht
+am 4. May 2024.
+Siehe auch: [Libreboot 20240504 release announcement](news/libreboot20240504.md).**
 
 Warum solltest Du *Libreboot* verwenden?
 ----------------------------
@@ -65,7 +71,7 @@ musst Du zunächst Konfigurationen auf Experten Level durchführen,
 und zwar für Coreboot, GRUB sowie sämtliche Software die Du sonst noch verwenden 
 möchtest um das ROM Image vorzubereiten. Mithilfe von *Libreboot* kannst Du 
 sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen, anschliessend 
-`make` ausführen, und es wird komplette ROM Images herstellen, ohne das Benutzer 
+ein script ausführen, und es wird komplette ROM Images herstellen, ohne das Benutzer 
 Eingaben oder Eingreifen von Nöten sind. Die Konfiguration wurde bereits im 
 Vorfeld erledigt.
 

site/index.de.md.date

@@ -1 +0,0 @@
-1697839978

site/index.fr.html

@@ -1,209 +0,0 @@
-<!DOCTYPE html>
-<html lang="fr" dir="ltr">
-<head>
-  <meta charset="utf-8">
-  <meta name="generator" content="pandoc">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
-
-<!-- anti-social media tags -->
-  <meta property="og:title" content="Libreboot – Projet Libreboot">
-  <meta property="og:type" content="article" />
-  <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
-  <meta property="og:url" content="https://libreboot.org/index.fr.html">
-  <meta name="twitter:card" content="summary_large_image">
-  <meta property="og:description" content="Libreboot – Projet Libreboot">
-  <meta property="og:site_name" content="Libreboot – Projet Libreboot">
-  <meta name="twitter:image:alt" content="Libreboot – Projet Libreboot">
-
-  <title>Libreboot – Projet Libreboot</title>
-  <link rel="stylesheet" href="/global.css">
-<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
-</head>
-<body>
-<div class="page">
-<header>
-<div class="title">
-<p class="title-logo">
-<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
-</p>
-<h1 class="title">Projet Libreboot</h1>
-</div>
-<ul>
-<li><a href="/">Home</a></li>
-<li><a href="/faq.html">FAQ</a></li>
-<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li>
-<li><strong><a href="/download.html">Download</a></strong></li>
-<li><a href="/docs/install/">Install</a></li>
-<li><a href="/docs/">Docs</a></li>
-<li><a href="/news/">News</a></li>
-<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
-<li><a href="/git.html">Send patch</a></li>
-<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li>
-<li><a href="/contact.html">Contact</a></li>
-<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li>
-</ul>
-<hr/>
-</header>
-<nav id="TOC">
-<h1>Navigate this page:</h1>
-<ul>
-<li><a href="#pourquoi-devriez-vous-utiliser-libreboot">Pourquoi
-devriez-vous utiliser <em>Libreboot</em>?</a></li>
-<li><a href="#de-quelle-façon-libreboot-diffère-de-coreboot">De quelle
-façon Libreboot diffère de Coreboot?</a></li>
-<li><a href="#comment-aider">Comment aider</a></li>
-<li><a href="#translations-needed-for-libreboot.org">Translations
-needed, for libreboot.org</a></li>
-</ul>
-</nav>
-<div class="pagetext">
-<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
-href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
-| <a href="index.uk.html">українська</a> | <a
-href="index.zh-cn.html">简体中文</a></p>
-<p>Libreboot est un micrologiciel de démarrage <a
-href="freedom-status.html">libéré</a> qui initialise le matériel (càd le
-contrôleur mémoire, CPU, périphériques) sur <a href="docs/hardware/">des
-ordinateurs x86/ARM spécifiques</a> et lance un chargeur d’amorçage pour
-votre système d’exploitation. <a href="docs/linux/">Linux</a> et <a
-href="docs/bsd/">BSD</a> sont bien supportés. C’est un remplacement pour
-le micrologiciel UEFI/BIOS propriétaire. Des canaux d’aide sont
-disponibles dans le canal <a
-href="https://web.libera.chat/#libreboot">#libreboot</a> sur le serveur
-IRC <a href="https://libera.chat/">Libera</a>.</p>
-<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
-<p><strong>NOUVELLE VERSION: La dernière version est <a
-href="news/libreboot20231021.html">Libreboot 20231021</a>, sortie le 21
-octobre 2023.</strong></p>
-<h2 id="pourquoi-devriez-vous-utiliser-libreboot">Pourquoi devriez-vous
-utiliser <em>Libreboot</em>?</h2>
-<p>Libreboot vous donne des <a
-href="https://writefreesoftware.org/">libertés</a> que nous n’auriez pas
-autrement avec d’autre micrologiciel de démarrage. Il est extremement <a
-href="docs/linux/grub_hardening.html">puissant</a> et <a
-href="docs/maintain">configurable</a> pour plein de cas
-d’utilisations.</p>
-<p>Vous avez des droits. Un droit à la vie privée, liberté de pensée,
-liberté d’espression et le droit de lire. Dans ce contexte là, Libreboot
-vous permet d’avoir ces droits. Votre liberté compte. Le <a
-href="https://yewtu.be/watch?v=Npd_xDuNi9k">Droit à la réparation</a>
-est important. Beaucoup de personnes utilisent un micrologiciel de
-démarrage propriétare (non libre), même si ils utilisent <a
-href="https://www.openbsd.org/">un système d’exploitation libre</a>. Les
-micrologiciels propriétaires <a href="faq.html#intel">contiennent</a>
-souvent des <a href="faq.html#amd">portes dérobées</a> et peuvent être
-instable. Libreboot a été fondé en Décembre 2013 avec le but de rendre
-le libre au niveau du micrologiciel accessible pour les utilisateurs
-non-techniques.</p>
-<p>Libreboot utilise <a href="https://www.coreboot.org">coreboot</a>
-pour <a
-href="https://doc.coreboot.org/getting_started/architecture.html">l’initialisation
-matérielle</a> Coreboot est renommé comme être difficilement installable
-par des utilisateurs non technique; il se charge seulement de
-l’initialisation basique puis bascule sur un programme de <a
-href="https://doc.coreboot.org/payloads.html">charge utile</a> (par ex.
-<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
-href="https://www.tianocore.org/">Tianocore</a>), qui doit lui aussi
-être configuré. <em>Libreboot règle ce problème</em>; c’est une
-<em>distribution de coreboot</em> avec un <a href="docs/builds/">système
-de compilation automatisé</a>, crééant des <em>images ROM</em> complètes
-pour une installation plus robuste. De la documentation est
-disponible.</p>
-<h2 id="de-quelle-façon-libreboot-diffère-de-coreboot">De quelle façon
-Libreboot diffère de Coreboot?</h2>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
-<p>Contrairement à l’opinion populaire, le but principal de Libreboot
-n’est pas de fournir un Coreboot déblobbé; ceci n’est simplement qu’une
-des politiques de Libreboot, une importante certes, mais qui n’est qu’un
-aspect mineur de Libreboot.</p>
-<p>De la même façon que <em>Alpine Linux</em> est une distribution
-Linux, Libreboot est une <em>distribution coreboot</em>. Si vous voulez
-compilé une image ROM en partant des bases, vous devez alors effectuer
-une configuration experte de Coreboot, GRUB et n’importe quel autre
-logiciel dont vous avez besoin afin de préparer la ROM. Avec
-<em>Libreboot</em>, vous pouvez télécharger la source depuis Git ou une
-archive, exécuter <code>make</code> etça compilera une image ROM
-entières. Le système de compilation automatisé de Libreboot nommé
-<code>lbmk</code> (Libreboot MaKe), compile ces images ROM
-automatiquement, sans besoin d’entrées utilisateur or intervention
-requise. La configuration est faite à l’avance.</p>
-<p>Si vous devriez compiler du coreboot classique sans utiliser le
-système de build automatisé de Libreboot, ça demanderait bien plus
-d’effort et de connaissances techniques décente pour écrire une
-configuration qui marche.</p>
-<p>Les versions de Libreboot fournissent ces images ROM pré-compilés et
-vous pouvez les installez simplement, sans connaissance ou compétence
-particulière à savoir, sauf <a href="docs/install/">suivre des
-instructions simplifiés écrite pour des utilisateurs non
-techniques</a>.</p>
-<div class="h"><h2 id="comment-aider">Comment aider</h2><a aria-hidden="true" href="#comment-aider">[link]</a></div>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
-<p>The <em>single</em> biggest way you can help it to <em>add</em> new
-mainboards to Libreboot, by submitting a config. Anything coreboot
-supports can be integrated in Libreboot, with ROM images provided in
-releases. See:</p>
-<ul>
-<li><a href="docs/maintain/testing.html">Apply to become a board
-maintainer/tester</a></li>
-<li><a href="docs/maintain/porting.html">Porting guide for new
-mainboards</a></li>
-<li><a href="docs/maintain/">Libreboot build system
-documentation</a></li>
-</ul>
-<p>After that, there is build system maintenance (see above), and
-<em>documentation</em> which we take seriously. Documentation is
-critical, in any project.</p>
-<p><em>User support</em> is also critical. Stick around on IRC, and if
-you’re competent to help someone with their issue (or wily enough to
-learn with them), that is a great service to the project. A lot of
-people also ask for user support on the <code>r/libreboot</code>
-subreddit.</p>
-<p>Vous pouvez allez voir les bugs listés sur le <a
-href="https://codeberg.org/libreboot/lbmk/issues">traqueur de
-bugs</a>.</p>
-<p>Si vous trouvez un bug et avez un correctif, <a href="git.html">voici
-les instructions pour envoyer des patchs</a>, et vous pouvez aussi nous
-les signaler. Par ailleurs, ce site est écrit en Markdown et hébergé
-dans un <a href="https://codeberg.org/libreboot/lbwww">dépôt séparé</a>
-où vous pouvez envoyer vos patchs.</p>
-<p>La discussion sur le dévéloppement de Libreboot et le support
-utilisateur se font toutes sur le canal IRC. Plus d’information est
-disponible sur la <a href="contact.html">page de contact</a>.</p>
-<h2 id="translations-needed-for-libreboot.org">Translations needed, for
-libreboot.org</h2>
-<p>Libreboot currently has translated Web pages in Ukrainian and French
-(but not for all pages, yet, on either language).</p>
-<p>If you want to help with translations, you can translate pages,
-update existing translations and submit your translated versions. For
-instructions, please read:</p>
-<p><a href="news/translations.html">How to submit translations for
-libreboot.org</a></p>
-<p>Even if someone is already working on translations in a given
-language, we can always use multiple people. The more the merrier!</p>
-<div id="footer">
-<hr />
-<ul>
-<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li>
-<li><a href="/git.html">Edit this page</a></li>
-<li><a href="/who.html">Who develops Libreboot?</a></li>
-<li><a href="/license.html">License</a></li>
-<li><a href="/template-license.html">Template</a></li>
-<li><a href="/logo-license.html">Logo</a></li>
-<li><a href="/contrib.html">Authors</a></li>
-</ul>
-<hr />
-</div>
-<p>Fichier Markdown pour cette page: <a
-href="https://libreboot.org/index.fr.md"
-class="uri">https://libreboot.org/index.fr.md</a></p>
-<p><a href="/sitemap.html">Plan du site</a></p>
-<p>Cette page HTML a été générée par le <em><a
-href="https://untitled.vimuser.org/">untitled static site
-generator</a></em>.</p>
-</div>
-</div>
-</body>
-</html>

site/index.fr.md

@@ -3,7 +3,7 @@ title: Projet Libreboot
 x-toc-enable: true
 ...
 
-Libreboot est un micrologiciel de démarrage [libéré](freedom-status.md)
+Libreboot est un micrologiciel de démarrage [libéré](https://writefreesoftware.org/)
 qui initialise le matériel (càd le contrôleur mémoire, CPU,
 périphériques) sur [des ordinateurs x86/ARM spécifiques](docs/hardware/)
 et lance un chargeur d'amorçage pour votre système d'exploitation. [Linux](docs/linux/) et [BSD](docs/bsd/) sont bien supportés. C'est un
@@ -13,8 +13,14 @@ dans le canal [\#libreboot](https://web.libera.chat/#libreboot) sur le serveur I
 
 <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
 
-**NOUVELLE VERSION: La dernière version est [Libreboot 20231021](news/libreboot20231021.md), sortie
-le 21 octobre 2023.**
+You can also [buy Libreboot preinstalled](https://minifree.org/) from Minifree Ltd,
+on select hardware, aswell as send your compatible hardware
+for [Libreboot preinstallation](https://minifree.org/product/installation-service/).
+The founder and lead developer of Libreboot, Leah Rowe, also owns and operates
+Minifree; sales provide funding for Libreboot.
+
+**NOUVELLE VERSION: La dernière version est [Libreboot 20240504](news/libreboot20240504.md), sortie
+le 4 May 2024.**
 
 Pourquoi devriez-vous utiliser *Libreboot*?
 -----------------------------------
@@ -62,7 +68,7 @@ en partant des bases, vous devez alors effectuer une configuration experte
 de Coreboot, GRUB et n'importe quel autre logiciel dont vous avez besoin 
 afin de préparer la ROM. Avec *Libreboot*,
 vous pouvez télécharger la source depuis Git ou une archive, exécuter
-`make` etça compilera une image ROM entières. Le système de compilation 
+and a script etça compilera une image ROM entières. Le système de compilation 
 automatisé de Libreboot nommé `lbmk` (Libreboot MaKe), compile ces images 
 ROM automatiquement, sans besoin d'entrées utilisateur or intervention
 requise. La configuration est faite à l'avance.

site/index.fr.md.date

@@ -1 +0,0 @@
-1697839885

site/index.html

@@ -1,203 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" dir="ltr">
-<head>
-  <meta charset="utf-8">
-  <meta name="generator" content="pandoc">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
-
-<!-- anti-social media tags -->
-  <meta property="og:title" content="Libreboot – Libreboot project">
-  <meta property="og:type" content="article" />
-  <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
-  <meta property="og:url" content="https://libreboot.org/">
-  <meta name="twitter:card" content="summary_large_image">
-  <meta property="og:description" content="Libreboot – Libreboot project">
-  <meta property="og:site_name" content="Libreboot – Libreboot project">
-  <meta name="twitter:image:alt" content="Libreboot – Libreboot project">
-
-  <title>Libreboot – Libreboot project</title>
-  <link rel="stylesheet" href="/global.css">
-<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
-</head>
-<body>
-<div class="page">
-<header>
-<div class="title">
-<p class="title-logo">
-<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
-</p>
-<h1 class="title">Libreboot project</h1>
-</div>
-<ul>
-<li><a href="/">Home</a></li>
-<li><a href="/faq.html">FAQ</a></li>
-<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li>
-<li><strong><a href="/download.html">Download</a></strong></li>
-<li><a href="/docs/install/">Install</a></li>
-<li><a href="/docs/">Docs</a></li>
-<li><a href="/news/">News</a></li>
-<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li>
-<li><a href="/git.html">Send patch</a></li>
-<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li>
-<li><a href="/contact.html">Contact</a></li>
-<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li>
-</ul>
-<hr/>
-</header>
-<nav id="TOC">
-<h1>Navigate this page:</h1>
-<ul>
-<li><a href="#why-should-you-use-libreboot">Why should you use
-<em>Libreboot</em>?</a></li>
-<li><a href="#libreboot-is-not-a-fork-of-coreboot">Libreboot is not a
-fork of coreboot</a></li>
-<li><a href="#how-to-help">How to help</a></li>
-<li><a href="#translations-needed-for-libreboot.org">Translations
-needed, for libreboot.org</a></li>
-</ul>
-</nav>
-<div class="pagetext">
-<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
-href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
-| <a href="index.uk.html">українська</a> | <a
-href="index.zh-cn.html">简体中文</a></p>
-<p>The <em>Libreboot</em> project provides <a
-href="freedom-status.html">free, open source</a> (<em>libre</em>) boot
-firmware based on coreboot, replacing proprietary BIOS/UEFI firmware on
-<a href="docs/hardware/">specific Intel/AMD x86 and ARM based
-motherboards</a>, including laptop and desktop computers. It initialises
-the hardware (e.g. memory controller, CPU, peripherals) and starts a
-bootloader for your operating system. <a href="docs/linux/">Linux</a>
-and <a href="docs/bsd/">BSD</a> are well-supported. Help is available
-via <a href="https://web.libera.chat/#libreboot">#libreboot</a> on <a
-href="https://libera.chat/">Libera</a> IRC.</p>
-<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
-<p><strong>NEW RELEASE: The latest release is Libreboot 20231021,
-released on 21 October 2023. See: <a
-href="news/libreboot20231021.html">Libreboot 20231021 release
-announcement</a>.</strong></p>
-<h2 id="why-should-you-use-libreboot">Why should you use
-<em>Libreboot</em>?</h2>
-<p>Libreboot gives you <a
-href="https://writefreesoftware.org/">freedoms</a> that you otherwise
-can’t get with most other boot firmware, plus faster boot speeds and <a
-href="docs/linux/grub_hardening.html">better security</a>. It’s
-extremely powerful and <a href="docs/maintain/">configurable</a> for
-many use cases.</p>
-<p><em>We</em> believe the freedom to <a
-href="https://writefreesoftware.org/">study, share, modify and use
-software</a>, without any restriction, is one of the fundamental human
-rights that everyone must have. In this context, <em>software
-freedom</em> matters. Your freedom matters. Education matters. <a
-href="https://yewtu.be/watch?v=Npd_xDuNi9k">Right to repair</a> matters.
-Many people use proprietary (non-libre) boot firmware, even if they use
-<a href="https://www.openbsd.org/">a libre OS</a>. Proprietary firmware
-often <a href="faq.html#intel">contains</a> <a
-href="faq.html#amd">backdoors</a>, and can be buggy. The Libreboot
-project was founded in December 2013, with the express purpose of making
-coreboot firmware accessible for non-technical users.</p>
-<p>The Libreboot project uses <a
-href="https://www.coreboot.org/">coreboot</a> for <a
-href="https://doc.coreboot.org/getting_started/architecture.html">hardware
-initialisation</a>. Coreboot is notoriously difficult to install for
-most non-technical users; it handles only basic initialization and jumps
-to a separate <a
-href="https://doc.coreboot.org/payloads.html">payload</a> program (e.g.
-<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
-href="https://www.tianocore.org/">Tianocore</a>), which must also be
-configured. <em>Libreboot solves this problem</em>; it is a <em>coreboot
-distribution</em> with an <a href="docs/build/">automated build
-system</a> that builds complete <em>ROM images</em>, for more robust
-installation. Documentation is provided.</p>
-<h2 id="libreboot-is-not-a-fork-of-coreboot">Libreboot is not a fork of
-coreboot</h2>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
-<p>In fact, Libreboot tries to stay as close to <em>stock</em> coreboot
-as possible, for each board, but with many different types of
-configuration provided automatically by the Libreboot build system.</p>
-<p>In the same way that <em>Alpine Linux</em> is a <em>Linux
-distribution</em>, Libreboot is a <em>coreboot distribution</em>. If you
-want to build a ROM image from scratch, you otherwise have to perform
-expert-level configuration of coreboot, GRUB and whatever other software
-you need, to prepare the ROM image. With <em>Libreboot</em>, you can
-literally download from Git or a source archive, and run
-<code>make</code>, and it will build entire ROM images. An automated
-build system, named <code>lbmk</code> (Libreboot MaKe), builds these ROM
-images automatically, without any user input or intervention required.
-Configuration has already been performed in advance.</p>
-<p>If you were to build regular coreboot, without using Libreboot’s
-automated build system, it would require a lot more intervention and
-decent technical knowledge to produce a working configuration.</p>
-<p>Regular binary releases of Libreboot provide these ROM images
-pre-compiled, and you can simply install them, with no special knowledge
-or skill except the ability to follow <a href="docs/install/">simplified
-instructions, written for non-technical users</a>.</p>
-<div class="h"><h2 id="how-to-help">How to help</h2><a aria-hidden="true" href="#how-to-help">[link]</a></div>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
-<p>The <em>single</em> biggest way you can help is to <em>add</em> new
-mainboards in Libreboot, by submitting a config. Anything coreboot
-supports can be integrated in Libreboot, with ROM images provided in
-releases. See:</p>
-<ul>
-<li><a href="docs/maintain/testing.html">Apply to become a board
-maintainer/tester</a></li>
-<li><a href="docs/maintain/porting.html">Porting guide for new
-mainboards</a></li>
-<li><a href="docs/maintain/">Libreboot build system
-documentation</a></li>
-</ul>
-<p>After that, there is build system maintenance (see above), and
-<em>documentation</em> which we take seriously. Documentation is
-critical, in any project.</p>
-<p><em>User support</em> is also critical. Stick around on IRC, and if
-you’re competent to help someone with their issue (or wily enough to
-learn with them), that is a great service to the project. A lot of
-people also ask for user support on the <code>r/libreboot</code>
-subreddit.</p>
-<p>You can check bugs listed on the <a
-href="https://codeberg.org/libreboot/lbmk/issues">bug tracker</a>.</p>
-<p>If you spot a bug and have a fix, <a href="git.html">here are
-instructions for how to send patches</a>, and you can also report it.
-Also, this entire website is written in Markdown and hosted in a <a
-href="https://codeberg.org/libreboot/lbwww">separate repository</a>
-where you can send patches.</p>
-<p>Any and all development discussion and user support are all done on
-the IRC channel. More information is on the <a
-href="contact.html">contact page</a>.</p>
-<h2 id="translations-needed-for-libreboot.org">Translations needed, for
-libreboot.org</h2>
-<p>Libreboot currently has translated Web pages in Ukrainian and French
-(but not for all pages, yet, on either language).</p>
-<p>If you want to help with translations, you can translate pages,
-update existing translations and submit your translated versions. For
-instructions, please read:</p>
-<p><a href="news/translations.html">How to submit translations for
-libreboot.org</a></p>
-<p>Even if someone is already working on translations in a given
-language, we can always use multiple people. The more the merrier!</p>
-<div id="footer">
-<hr />
-<ul>
-<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li>
-<li><a href="/git.html">Edit this page</a></li>
-<li><a href="/who.html">Who develops Libreboot?</a></li>
-<li><a href="/license.html">License</a></li>
-<li><a href="/template-license.html">Template</a></li>
-<li><a href="/logo-license.html">Logo</a></li>
-<li><a href="/contrib.html">Authors</a></li>
-</ul>
-<hr />
-</div>
-<p>Markdown file for this page: <a href="https://libreboot.org/index.md"
-class="uri">https://libreboot.org/index.md</a></p>
-<p><a href="/sitemap.html">Site map</a></p>
-<p>This HTML page was generated by the <a
-href="https://untitled.vimuser.org/">untitled static site
-generator</a>.</p>
-</div>
-</div>
-</body>
-</html>

site/index.it.html

@@ -1,213 +0,0 @@
-<!DOCTYPE html>
-<html lang="it" dir="ltr">
-<head>
-  <meta charset="utf-8">
-  <meta name="generator" content="pandoc">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
-
-<!-- anti-social media tags -->
-  <meta property="og:title" content="Libreboot – Progetto Libreboot">
-  <meta property="og:type" content="article" />
-  <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg">
-  <meta property="og:url" content="https://libreboot.org/index.it.html">
-  <meta name="twitter:card" content="summary_large_image">
-  <meta property="og:description" content="Libreboot – Progetto Libreboot">
-  <meta property="og:site_name" content="Libreboot – Progetto Libreboot">
-  <meta name="twitter:image:alt" content="Libreboot – Progetto Libreboot">
-
-  <title>Libreboot – Progetto Libreboot</title>
-  <link rel="stylesheet" href="/global.css">
-<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/>
-</head>
-<body>
-<div class="page">
-<header>
-<div class="title">
-<p class="title-logo">
-<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" />
-</p>
-<h1 class="title">Progetto Libreboot</h1>
-</div>
-<ul>
-<li><a href="/index.it.html">Home</a></li>
-<li><a href="/faq.html">FAQ</a></li>
-<li><strong><a href="/freedom-status.html">Grado di liberta' possibile</a></strong></li>
-<li><strong><a href="/download.html">Download</a></strong></li>
-<li><a href="/docs/install/">Installazione</a></li>
-<li><a href="/docs/">Documentazione</a></li>
-<li><a href="/news/">Notizie</a></li>
-<li><a href="https://codeberg.org/libreboot/lbmk/issues">Difetti (bugs)</a></li>
-<li><a href="/git.html">Spedisci correzioni (patches)</a></li>
-<li><strong><a href="https://www.patreon.com/libreleah">Donazioni</a></strong></li>
-<li><a href="/contact.html">Contatti</a></li>
-<li><strong><a href="https://minifree.org/">Compra un PC con libreboot gia' installato</a></strong></li>
-</ul>
-<hr/>
-</header>
-<nav id="TOC">
-<h1>Sfoglia questa pagina:</h1>
-<ul>
-<li><a href="#per-quale-ragione-utilizzare-libreboot">Per quale ragione
-utilizzare <em>Libreboot</em>?</a></li>
-<li><a href="#libreboot-non-deriva-da-coreboot">Libreboot non deriva da
-coreboot</a></li>
-<li><a href="#come-essere-daiuto">Come essere d’aiuto</a></li>
-<li><a href="#servono-traduzioni-per-libreboot.org">Servono traduzioni
-per libreboot.org</a></li>
-</ul>
-</nav>
-<div class="pagetext">
-<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a
-href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a>
-| <a href="index.uk.html">українська</a> | <a
-href="index.zh-cn.html">简体中文</a></p>
-<p>Il progetto <em>Libreboot</em> fornisce avvio <a
-href="freedom-status.html">libero e open source</a> grazie al firmware
-basato su coreboot, sostituendo cosi’, firmware BIOS/UEFI proprietario
-su <a href="docs/hardware/">alcune schede madri basate su Intel/AMD x86
-o ARM</a>, in computer fissi e portatili. Inizializza l’hardware
-(controller di memoria, CPU, periferiche) e avvia un bootloader per il
-tuo sistema operativo. <a href="docs/linux/">Linux</a> e <a
-href="docs/bsd/">BSD</a> sono ben supportati. L’aiuto e’ disponibile sul
-canale IRC <a href="https://web.libera.chat/#libreboot">#libreboot</a>
-su <a href="https://libera.chat/">Libera</a>.</p>
-<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p>
-<p><strong>ULTIMO RILASCIO: L’ultimo rilascio e’ Libreboot 20231021,
-rilasciato il 21 ottobre 2023. Vedi: <a
-href="news/libreboot20231021.html">Libreboot 20231021 annuncio di
-rilascio</a>.</strong></p>
-<h2 id="per-quale-ragione-utilizzare-libreboot">Per quale ragione
-utilizzare <em>Libreboot</em>?</h2>
-<p>Libreboot ti permette <a
-href="https://writefreesoftware.org/">liberta’</a> che non potresti
-ottenere con altri firmware di boot, velocita’ di avvio maggiori e <a
-href="docs/linux/grub_hardening.html">migliore sicurezza</a>. E’
-estremamente flessibile e <a href="docs/maintain/">configurabile</a> per
-la maggior parte dei casi.</p>
-<p><em>Noi</em> crediamo nella liberta’ di <a
-href="https://writefreesoftware.org/">studiare, condividere, modificare
-and usare il software</a>, senza restrizione alcuna, in quanto e’ uno
-dei fondamentali diritti umani che chiunque deve avere. In questo
-contesto, <em>il software libero</em> conta. La tua liberta’ conta. La
-formazione personale conta. <a
-href="https://yewtu.be/watch?v=Npd_xDuNi9k">Il diritto di riparare</a>
-conta. Molte persone usano firmware di boot proprietario (non-libero),
-anche se usano <a href="https://www.openbsd.org/">un sistema operativo
-libero</a>. Firmware proprietari spesso <a
-href="faq.html#intel">contengono</a> <a
-href="faq.html#amd">vulnerabilita’</a>, e possono essere difettosi. Il
-progetto libreboot venne fondato nel Dicembre 2013, con lo scopo
-prefissato di permettere che il firmware coreboot sia accessibile anche
-per utenti con scarsa formazione tecnica.</p>
-<p>Il progetto Libreboot fa uso di <a
-href="https://www.coreboot.org/">coreboot</a> per <a
-href="https://doc.coreboot.org/getting_started/architecture.html">l’inizializzazione
-hardware</a>. Coreboot e’ notoriamente difficile da installare per
-utenti che hanno una scarsa formazione tecnica; gestisce solo
-l’inizializzazione di base e successivamente carica un programma come <a
-href="https://doc.coreboot.org/payloads.html">payload</a> (ad esempio.
-<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a
-href="https://www.tianocore.org/">Tianocore</a>), i quali possono essere
-configurati a piacere. <em>Libreboot risolve questo problema</em>; e’
-una <em>distribuzione di coreboot</em> con un <a
-href="docs/build/">sistema di compilazione automatizzato</a> che produce
-<em>immagini ROM</em> complete, per una installazione piu’ robusta.
-Viene fornito con apposita documentazione.</p>
-<h2 id="libreboot-non-deriva-da-coreboot">Libreboot non deriva da
-coreboot</h2>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p>
-<p>In effetti, Libreboot tenta di essere il piu’ possibile simile alla
-versione <em>ufficiale</em> di coreboot, per ogni scheda, ma con diversi
-tipi di configurazione forniti automaticamente dal sistema di
-compilazione automatico di Libreboot.</p>
-<p>Esattamente come <em>Alpine Linux</em> e’ una <em>distribuzione
-Linux</em>, Libreboot e’ una <em>distribuzione coreboot</em>. Per fare
-un immagine ROM da zero, hai bisogno di esperienza necessaria nel
-configurare coreboot, GRUB e qualunque altra cosa ti serve. Con
-<em>Libreboot</em>, che puoi scaricare da Git o da un archivio di codici
-sorgenti, puoi far partire <code>make</code>, e questo mettera’ su
-automaticamente le immagini ROM richieste. Un sistema di compilazione
-automatico, chiamato <code>lbmk</code> (Libreboot MaKe), mettera’ su
-quelle immagini ROM automaticamente, senza troppi interventi da parte
-dell’utente. Le configurazioni di base sono gia’ state previste in
-precedenza.</p>
-<p>Se avresti voluto compilare coreboot normalmente senza il sistema di
-compilazione automatico di Libreboot, ti troveresti ad affrontare molte
-piu’ difficolta senza adeguate competenze tecniche per produrre una
-configurazione funzionante.</p>
-<p>I rilasci binari di Libreboot forniscono immagini ROM precompilate,
-che puoi semplicemente installare senza troppe conoscenze tecniche o
-abilita’ particolari ad eccezione del seguire <a
-href="docs/install/">semplici istruzioni scritte per chiunque</a>.</p>
-<div class="h"><h2 id="come-essere-daiuto">Come essere d’aiuto</h2><a aria-hidden="true" href="#come-essere-daiuto">[link]</a></div>
-<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span
-class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p>
-<p>Il <em>modo migliore</em> col quale puoi aiutarci e’ quello di
-<em>aggiungere</em> nuove schede condividendone la configurazione.
-Qualunque cosa sia supportata da coreboot puo’ essere integrata in
-Libreboot, con immagini ROM fornite nei rilasci. Vedi anche:</p>
-<ul>
-<li><a href="docs/maintain/testing.html">Richiedi di collaudare o
-mantenere una scheda</a></li>
-<li><a href="docs/maintain/porting.html">Guida per rendere nuove schede
-compatibili</a></li>
-<li><a href="docs/maintain/">Documentazione del sistema di compilazione
-automatica di Libreboot</a></li>
-</ul>
-<p>Dopo di che c’e’ da tenere seriamente in considerazione la
-manutenzione della compilazione automatica (guarda sopra), e la
-<em>documentazione</em>. La documentazione e’ critica in ogni
-progetto.</p>
-<p><em>Il supporto utente</em> e’ inoltre un fattore critico. Resta
-collegato su IRC, e se hai sufficiente esperienza puoi aiutare qualcuno
-in difficolta’ (o anche imparare insieme a loro), in questo modo sarai
-di grande aiuto al progetto. Un sacco di persone chiedono inoltre aiuto
-nel subreddit <code>r/libreboot</code>.</p>
-<p>Puoi controllare l’elenco dei bugs sul <a
-href="https://codeberg.org/libreboot/lbmk/issues">bug tracker</a>.</p>
-<p>Se hai notato un difetto (bug) e hai trovato una soluzione, <a
-href="git.html">qui puoi trovare istruzioni su come inviare delle
-correzioni (patches)</a> o puoi semplicemente farne rapporto. Inoltre
-tutto questo sito internet e’ scritto in Markdown e ospitato su un <a
-href="https://codeberg.org/libreboot/lbwww">repository separato</a>,
-dove puoi inviare correzioni (patches).</p>
-<p>Qualunque discorso relativo a sviluppo e supporto utente viene fatto
-sul canale IRC. Puoi avere piu’ informazioni sulla <a
-href="contact.html">pagina dei contatti</a>.</p>
-<h2 id="servono-traduzioni-per-libreboot.org">Servono traduzioni per
-libreboot.org</h2>
-<p>Libreboot attualmente ha pagine Web tradotte in Ucraino and Francese
-(ma non ancora in ogni pagina e per ogni lingua).</p>
-<p>Se vuoi essere d’aiuto con le traduzioni, puoi tradurre le pagine,
-aggiornare traduzioni esistenti e condividere le tue versioni tradotte.
-Per saperne di piu’ puoi leggere: <a href="news/translations.html">come
-condividere traduzioni per libreboot.org</a></p>
-<p>Anche se qualcuno sta gia’ lavorando sulle traduzioni in una
-determinata lingua, possiamo sempre avvalerci di piu’ contributori. Piu’
-siamo e meglio e’!</p>
-<div id="footer">
-<hr />
-<ul>
-<li><a href="/news/policy.html">Politica di riduzione di parti binarie
-proprietarie (blobs)</a></li>
-<li><a href="/git.de.html">Modifica questa pagina</a></li>
-<li><a href="/who.de.html">Chi sviluppa Libreboot?</a></li>
-<li><a href="/license.html">Licenza</a></li>
-<li><a href="/template-license.html">Modelli di licenze</a></li>
-<li><a href="/logo-license.html">Logo</a></li>
-<li><a href="/contrib.html">Autori</a></li>
-</ul>
-<hr />
-</div>
-<p>Markdown file: <a href="https://libreboot.org/index.it.md"
-class="uri">https://libreboot.org/index.it.md</a></p>
-<p><a href="/sitemap.html">Site map</a></p>
-<p>This HTML page was generated by the <a
-href="https://untitled.vimuser.org/">untitled static site
-generator</a>.</p>
-</div>
-</div>
-</body>
-</html>

site/index.it.md

@@ -3,7 +3,7 @@ title: Progetto Libreboot
 x-toc-enable: true
 ...
 
-Il progetto *Libreboot* fornisce avvio [libero e open source](freedom-status.md)
+Il progetto *Libreboot* fornisce avvio [libero e open source](https://writefreesoftware.org/)
 grazie al firmware basato su coreboot, sostituendo cosi', firmware BIOS/UEFI proprietario
 su [alcune schede madri basate su Intel/AMD x86 o ARM](docs/hardware/),
 in computer fissi e portatili. Inizializza l'hardware (controller di
@@ -14,8 +14,14 @@ su [Libera](https://libera.chat/).
 
 <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
 
-**ULTIMO RILASCIO: L'ultimo rilascio e' Libreboot 20231021, rilasciato il 21 ottobre 2023.
-Vedi: [Libreboot 20231021 annuncio di rilascio](news/libreboot20231021.md).**
+You can also [buy Libreboot preinstalled](https://minifree.org/) from Minifree Ltd,
+on select hardware, aswell as send your compatible hardware
+for [Libreboot preinstallation](https://minifree.org/product/installation-service/).
+The founder and lead developer of Libreboot, Leah Rowe, also owns and operates
+Minifree; sales provide funding for Libreboot.
+
+**ULTIMO RILASCIO: L'ultimo rilascio e' Libreboot 20240504, rilasciato il 4 May 2024.
+Vedi: [Libreboot 20240504 annuncio di rilascio](news/libreboot20240504.md).**
 
 Per quale ragione utilizzare *Libreboot*?
 -----------------------------------------
@@ -60,7 +66,7 @@ compilazione automatico di Libreboot.
 Esattamente come *Alpine Linux* e' una *distribuzione Linux*, Libreboot e' una
 *distribuzione coreboot*. Per fare un immagine ROM da zero, hai bisogno di esperienza necessaria
 nel configurare coreboot, GRUB e qualunque altra cosa ti serve. Con *Libreboot*,
-che puoi scaricare da Git o da un archivio di codici sorgenti, puoi far partire `make`,
+che puoi scaricare da Git o da un archivio di codici sorgenti, puoi far partire *a script*,
 e questo mettera' su automaticamente le immagini ROM richieste. Un sistema di compilazione automatico,
 chiamato `lbmk` (Libreboot MaKe), mettera' su quelle immagini ROM automaticamente, senza troppi
 interventi da parte dell'utente. Le configurazioni di base sono gia' state previste in precedenza.

site/index.it.md.date

@@ -1 +0,0 @@
-1697839851

site/index.md

@@ -4,56 +4,114 @@ x-toc-enable: true
 ...
 
 The *Libreboot* project provides
-[free, open source](freedom-status.md) (*libre*) boot
+[free, open source](https://writefreesoftware.org/) (*libre*) boot
 firmware based on coreboot, replacing proprietary BIOS/UEFI firmware
 on [specific Intel/AMD x86 and ARM based motherboards](docs/hardware/),
 including laptop and desktop computers. It initialises the hardware (e.g. memory
 controller, CPU, peripherals) and starts a bootloader for your operating
 system. [Linux](docs/linux/) and [BSD](docs/bsd/) are well-supported. Help is
 available via [\#libreboot](https://web.libera.chat/#libreboot)
-on [Libera](https://libera.chat/) IRC.
+on [Libera](https://libera.chat/) IRC. The [tasks page](tasks/) lists what
+we are working on (contributions are welcome, if you want to work on some of
+them yourself).
 
 <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span>
 
-**NEW RELEASE: The latest release is Libreboot 20231021, released on
-21 October 2023.
-See: [Libreboot 20231021 release announcement](news/libreboot20231021.md).**
+You can also [buy Libreboot preinstalled](https://minifree.org/) from Minifree Ltd,
+on select hardware, aswell as send your compatible hardware
+for [Libreboot preinstallation](https://minifree.org/product/installation-service/).
+The founder and lead developer of Libreboot, Leah Rowe, also owns and operates
+Minifree; sales provide funding for Libreboot.
 
-Why should you use *Libreboot*?
-----------------------------
-
-Libreboot gives you [freedoms](https://writefreesoftware.org/) that
-you otherwise can't get with most other boot firmware, plus faster boot speeds
-and [better security](docs/linux/grub_hardening.md). It's extremely powerful
-and [configurable](docs/maintain/) for many use cases.
+**NEW RELEASE: The latest release is Libreboot 20240504, released on
+4 May 2024.
+See: [Libreboot 20240504 release announcement](news/libreboot20240504.md).**
 
 *We* believe the freedom to [study, share, modify and use
 software](https://writefreesoftware.org/), without any
 restriction, is one of the fundamental human rights that everyone must have.
 In this context, *software freedom* matters. Your freedom matters. Education
 matters.
-[Right to repair](https://yewtu.be/watch?v=Npd_xDuNi9k) matters.
-Many people use proprietary (non-libre)
-boot firmware, even if they use [a libre OS](https://www.openbsd.org/).
+[Right to repair](https://yewtu.be/watch?v=Npd_xDuNi9k) matters; Libreboot lets
+you continue to use your hardware, with continued firmware updates. All of this
+is *why* Libreboot exists.
+
+Overview of Libreboot design
+============================
+
+<img tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span class="f"><img src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span>
+
+Libreboot provides [coreboot](https://coreboot.org/) for [machine
+initialisation](https://doc.coreboot.org/getting_started/architecture.html),
+which then jumps to a [payload](https://doc.coreboot.org/payloads.html) in
+the boot flash; coreboot works with many programs, but Libreboot specifically
+provides SeaBIOS, GNU GRUB and U-Boot as options. Memtest86+ is also provided
+in flash, on some mainboards. The payload is the program in flash that provides
+the early user interface, for booting an operating system. This *payload*
+infrastructure means you can run whatever you want (even Linux!) from the
+boot flash.
+
+Libreboot is specifically a *coreboot distribution*, in the same way that
+Debian is a *Linux distribution*. Libreboot makes coreboot easy to use for
+non-technical users, by providing a [fully automated build
+system](docs/maintain/), [automated build process](docs/build/) and
+[user-friendly installation instructions](docs/install/), in addition to
+regular binary releases that provide pre-compiled ROM images for installation
+on supported hardware. Without automation such as that provided by Libreboot,
+coreboot would be inaccessible for most users; you can also
+still [reconfigure](docs/maintain/) Libreboot however you wish.
+
+Why use Libreboot?
+==================
+
+<img tabindex=1 class="r" style="max-width:25%;" src="https://av.libreboot.org/hp2170p/hp2170p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp2170p/hp2170p.jpg" /></span>
+
+If you're already inclined towards free software, maybe already a coreboot user,
+Libreboot makes it easier to either get started or otherwise maintain coreboot
+on your machine, via build automation. It provides regular tested releases,
+pre-assembled, often with certain patches on top of coreboot (and other code)
+to ensure stability. By comparison, coreboot uses a rolling-release model, with
+a snapshot of the codebase every few months; it is very much developer-oriented,
+whereas Libreboot is specifically crafted for end users. In other words, the
+purpose of Libreboot is to *Just Work*. Direct configuration and installation
+of coreboot is also possible, but Libreboot makes it *much* easier.
+
+Libreboot gives you [freedoms](https://writefreesoftware.org/) that
+you otherwise can't get with most other boot firmware, plus faster boot speeds
+and [better security](docs/linux/grub_hardening.md). It's extremely powerful
+and [configurable](docs/maintain/) for many use cases. If you're unhappy with
+the restrictions (not to mention, security issues) imposed on you by proprietary
+BIOS vendors, then Libreboot is one possible choice for you. Since it inherits
+coreboot, it doesn't have any known backdoors in the code, nor does it contain
+legacy cruft from the 1980s. Libreboot provides a sleek, fast boot experience
+for Linux/BSD systems, based on coreboot which is regularly audited and improved.
+
+Libreboot is more reliable than proprietary firmware. Many people use proprietary
+(non-libre) boot firmware, even if they use [a libre OS](https://www.openbsd.org/).
 Proprietary firmware often [contains](faq.html#intel) [backdoors](faq.html#amd),
 and can be buggy. The Libreboot project was founded in December 2013, with the
 express purpose of making coreboot firmware accessible for non-technical users.
 
-The Libreboot project uses [coreboot](https://www.coreboot.org/) for [hardware
-initialisation](https://doc.coreboot.org/getting_started/architecture.html).
-Coreboot is notoriously difficult to install for most non-technical users; it
-handles only basic initialization and jumps to a separate
-[payload](https://doc.coreboot.org/payloads.html) program (e.g.
-[GRUB](https://www.gnu.org/software/grub/),
-[Tianocore](https://www.tianocore.org/)), which must also be configured.
-*Libreboot solves this problem*; it is a *coreboot distribution* with
-an [automated build system](docs/build/) that builds complete *ROM images*, for
-more robust installation. Documentation is provided.
+Libreboot is a community-oriented project, with a focus on helping users escape
+proprietary boot firmware; we ourselves want to live in a world where all software
+is [free](https://writefreesoftware.org/), and so, Libreboot is an effort to
+help get closer to that world. Unlike the big vendors, we don't try to stifle
+you in any way, nor do we see you as a security threat; we regard the ability
+to use, study, modify and redistribute software freely to be a human right that
+everyone must have. Extended to computers, these are products that you purchased,
+and so you should have the freedom to change them in any way you like. When you
+see Intel talk about their *Boot Guard* (which prevents coreboot by only letting
+firmware signed by them be executed) or other vendors imposing similar
+restrictions, and you hear them talk about "security", they are only talking
+about *their* security, not yours. In the Libreboot project, it is reversed; we
+see Intel Boot Guard and similar such technologies as an attack on your freedom
+over your own property (your computer), and so, we make it our mission to help
+you [wrest](https://trmm.net/TOCTOU/) back such control.
 
 Libreboot is not a fork of coreboot
------------------------------------
+===================================
 
-<img tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span class="f"><img src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span>
+<img tabindex=1 class="r" style="max-width:25%;" src="https://av.libreboot.org/t1650/t1650_grub.jpg" /><span class="f"><img src="https://av.libreboot.org/t1650/t1650_grub.jpg" /></span>
 
 In fact, Libreboot tries to stay as close to *stock* coreboot as possible,
 for each board, but with many different types of configuration provided
@@ -63,8 +121,8 @@ In the same way that *Alpine Linux* is a *Linux distribution*, Libreboot is
 a *coreboot distribution*. If you want to build a ROM image from scratch, you
 otherwise have to perform expert-level configuration of coreboot, GRUB and
 whatever other software you need, to prepare the ROM image. With *Libreboot*,
-you can literally download from Git or a source archive, and run `make`, and it
-will build entire ROM images. An automated build system, named `lbmk`
+you can literally download from Git or a source archive, and run a simple script,
+and it will build entire ROM images. An automated build system, named `lbmk`
 (Libreboot MaKe), builds these ROM images automatically, without any user input
 or intervention required. Configuration has already been performed in advance.
 
@@ -81,6 +139,10 @@ users](docs/install/).
 How to help
 -----------
 
+The [tasks page](tasks/) lists tasks that could (will) be worked on. It will
+be updated over time as more tasks are added/completede. If you want to help,
+you could pick one of these tasks and work on it.
+
 <img tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span class="f"><img src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span>
 
 The *single* biggest way you can help is to *add* new mainboards in Libreboot,