Merge pull request 'sync' (#1) from libreboot/lbwww:master into master

Reviewed-on: https://codeberg.org/Peaksol/lbwww/pulls/1
master
Peaksol 2023-08-05 07:46:01 +00:00
commit 9f480c60ff
9 changed files with 169 additions and 39 deletions

View File

@ -15,8 +15,7 @@ x-toc-enable: true
| **Variants** | E6400, E6400 XFR and E6400 ATG are supported | | **Variants** | E6400, E6400 XFR and E6400 ATG are supported |
| **Released** | 2009 | | **Released** | 2009 |
| **Chipset** | Intel Cantiga GM45(Intel GPU)/PM45(Nvidia GPU) | | **Chipset** | Intel Cantiga GM45(Intel GPU)/PM45(Nvidia GPU) |
| **CPU** | Intel Core 2 Duo (Penryn family). A Quad-core | **CPU** | Intel Core 2 Duo (Penryn family). |
mod exists, replacing the Core 2 Duo with a Core Quad |
| **Graphics** | Intel GMA 4500MHD (and NVidia Quadro NVS 160M | **Graphics** | Intel GMA 4500MHD (and NVidia Quadro NVS 160M
on some models) | on some models) |
| **Display** | 1280x800/1440x900 TFT | | **Display** | 1280x800/1440x900 TFT |

View File

@ -401,6 +401,10 @@ the microcode on AMD processors:
<https://yewtu.be/watch?v=W3FbTMqYi4U> <https://yewtu.be/watch?v=W3FbTMqYi4U>
Here is another video:
<https://yewtu.be/watch?v=I6dQfnb3y0I>
The git repository for that project is here: The git repository for that project is here:
<https://github.com/RUB-SysSec/Microcode> <https://github.com/RUB-SysSec/Microcode>
@ -574,7 +578,7 @@ How do I program an SPI flash chip?
--------------------------------------------------------------------------------- ---------------------------------------------------------------------------------
Refer to:\ Refer to:\
[Externally rewrite 25xx NOR flash via SPI protocol](spi.md) [Externally rewrite 25xx NOR flash via SPI protocol](docs/install/spi.md)
It's possible to use a 16-pin SOIC test clip on an 8-pin SOIC chip, if you It's possible to use a 16-pin SOIC test clip on an 8-pin SOIC chip, if you
align the pins properly. The connection is generally more sturdy. align the pins properly. The connection is generally more sturdy.

View File

@ -389,7 +389,9 @@ Revealed (Розкрито вбудовану технологію безпек
У цьому цікавому відео розповідається про те, як група людей У цьому цікавому відео розповідається про те, як група людей
провела зворотню розробку мікрокода на процесорах AMD: провела зворотню розробку мікрокода на процесорах AMD:
<https://yewtu.be/watch?v=W3FbTMqYi4U> * <https://yewtu.be/watch?v=W3FbTMqYi4U>
* <https://yewtu.be/watch?v=I6dQfnb3y0I>
Репозиторій git для цього проекту тут: Репозиторій git для цього проекту тут:
@ -565,7 +567,7 @@ Family 15h (на стороні AMD) або будь-яке інше, випущ
--------------------------------------------------------------------------------- ---------------------------------------------------------------------------------
Зверніться до:\ Зверніться до:\
[Зовнішній перезапис 25xx NOR flash через протокол SPI](spi.md) [Зовнішній перезапис 25xx NOR flash через протокол SPI](docs/install/spi.md)
Можна використовувати 16-контактний затискач SOIC на 8-контактній мікросхемі SOIC, якщо Можна використовувати 16-контактний затискач SOIC на 8-контактній мікросхемі SOIC, якщо
правильно впорядкувати контакти. Як правило, з'єднання більш міцне. правильно впорядкувати контакти. Як правило, з'єднання більш міцне.

View File

@ -97,7 +97,7 @@ In a *descriptor* configuration, the flash is divided into regions such as:
the initialisation firmware plus operating system for it is loaded from the initialisation firmware plus operating system for it is loaded from
this dedicated region in the main boot flash. More info is available [in the this dedicated region in the main boot flash. More info is available [in the
FAQ](faq.md#intelme) - where ME firmware is otherwise present, Libreboot FAQ](faq.md#intelme) - where ME firmware is otherwise present, Libreboot
either removes it or (with the `me_cleaner` program) reconfigures it in such either [removes](docs/install/ich9utils.html) it or (with the `me_cleaner` program) [reconfigures](https://github.com/corna/me_cleaner/wiki/How-does-it-work%3F) it in such
a way where it is disabled during machine initialisation. a way where it is disabled during machine initialisation.
* Platform region: non-program data, usually just a bunch of strings put there * Platform region: non-program data, usually just a bunch of strings put there
by the hardware vendor. by the hardware vendor.
@ -207,12 +207,6 @@ Libreboot has *fully libre* initialisation available for all Intel memory
controllers on supported platforms. This *includes* Haswell (ThinkPad T440p controllers on supported platforms. This *includes* Haswell (ThinkPad T440p
and W541) as of Libreboot 20230319 or higher. and W541) as of Libreboot 20230319 or higher.
AMD platforms
=============
Libreboot currently *lacks* support for AMD platforms, but information about
them will be written when this fact changes.
ARM platforms (chromebooks) ARM platforms (chromebooks)
============= =============
@ -256,7 +250,8 @@ disabled. This is done using `me_cleaner`. See:
### KBC1126 EC firmware (HP laptops): ### KBC1126 EC firmware (HP laptops):
EC firmware is inserted into main boot flash, rather than being on a separate [EC firmware](faq.md#ec-embedded-controller-firmware)
is inserted into main boot flash, rather than being on a separate
IC. This is *better* because libre replacements would be more easy to install in IC. This is *better* because libre replacements would be more easy to install in
the future, and reverse engineering is made much easier by it. Libreboot's the future, and reverse engineering is made much easier by it. Libreboot's
build system handles such firmware in `blobutil`, automatically downloading build system handles such firmware in `blobutil`, automatically downloading
@ -266,7 +261,8 @@ at the correct offset as defined by coreboot config for each board.
### CPU microcode: ### CPU microcode:
*Microcode* updates for CPU provided on *all* x86 platforms, by default. Not [*Microcode* updates](faq.md#microcode)
for CPU provided on *all* x86 platforms, by default. Not
technically required, but highly recommended. To remove, do: technically required, but highly recommended. To remove, do:
cbfstool filename.rom remove -n cpu_microcode_blob.bin cbfstool filename.rom remove -n cpu_microcode_blob.bin

View File

@ -296,12 +296,6 @@ Libreboot має *повністю вільну* ініціалізацію, д
на платформах, які підтримуються. Це *включає* Haswell (ThinkPad T440p на платформах, які підтримуються. Це *включає* Haswell (ThinkPad T440p
та W541), станом на Libreboot 20230319 та пізніші. та W541), станом на Libreboot 20230319 та пізніші.
Платформи AMD
=============
Libreboot наразі *бракує* підтримки для платформ AMD, але інформація про
них буде написана, коли цей факт зміниться.
Платформи ARM (chromebook) Платформи ARM (chromebook)
============= =============
@ -333,6 +327,8 @@ Libreboot *наразі* не розміщує ці блоби взагалі,
Intel/x86 Intel/x86
--------- ---------
### Intel ME:
Нейтралізований ME потрібен на цих цілях: `t420_8mb`, `t420s_8mb`, `t430_12mb`, Нейтралізований ME потрібен на цих цілях: `t420_8mb`, `t420s_8mb`, `t430_12mb`,
`t440p_12mb`, `t440pmrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`, `t440p_12mb`, `t440pmrc_12mb`, `t520_8mb`, `t530_12mb`, `w530_12mb`,
`w541_12mb`, `w541mrc_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`, `w541_12mb`, `w541mrc_12mb`, `x220_8mb`, `x230_12mb`, `x230_16mb`,
@ -344,7 +340,10 @@ Intel/x86
вимкнено. Це зроблено використовуючи `me_cleaner`. Дивіться: вимкнено. Це зроблено використовуючи `me_cleaner`. Дивіться:
<https://github.com/corna/me_cleaner/wiki/How-does-it-work%3F> <https://github.com/corna/me_cleaner/wiki/How-does-it-work%3F>
KBC1126 EC firmware on `hp9470m_16mb` and `hp9470m_16mb` - on HP laptops, EC ### KBC1126 EC firmware (HP laptops):
KBC1126 [EC firmware](faq.uk.md##прошивка-ec-вбудований-контролер)
on `hp9470m_16mb` and `hp9470m_16mb` - on HP laptops, EC
firmware is inserted into main boot flash, rather than being on a separate IC. firmware is inserted into main boot flash, rather than being on a separate IC.
This is *better* because libre replacements would be more easy to install in This is *better* because libre replacements would be more easy to install in
the future, and reverse engineering is made much easier by it. Libreboot's the future, and reverse engineering is made much easier by it. Libreboot's
@ -354,7 +353,10 @@ and provide functionality in `blobutil` insert, to insert them with `cbfstool`
at the correct offset as defined by coreboot config for each board. - **TODO: at the correct offset as defined by coreboot config for each board. - **TODO:
English paragraph that needs to be translated into Ukrainian.** English paragraph that needs to be translated into Ukrainian.**
Оновлення *мікрокоду* для ЦП надано на *всіх* платформах x86, за замовчуванням. Не ### CPU microcode:
Оновлення [*мікрокоду*](faq.uk.md#microcode)
для ЦП надано на *всіх* платформах x86, за замовчуванням. Не
вимагається технічно, але надзвичайно рекомендовано. Виконайте для видалення: вимагається технічно, але надзвичайно рекомендовано. Виконайте для видалення:
cbfstool filename.rom remove -n cpu_microcode_blob.bin cbfstool filename.rom remove -n cpu_microcode_blob.bin
@ -371,6 +373,8 @@ excluded, alongside default ones with microcode included.](news/microcode.md)
в більшості випадків, їх використання надзвичайно рекомендовано. Дивіться для причин чому: в більшості випадків, їх використання надзвичайно рекомендовано. Дивіться для причин чому:
[news/policy.uk.md#більш-детальна-інформація-про-мікрокод](news/policy.uk.md#більш-детальна-інформація-про-мікрокод) [news/policy.uk.md#більш-детальна-інформація-про-мікрокод](news/policy.uk.md#більш-детальна-інформація-про-мікрокод)
### Intel Flash Descriptor (IFD):
Intel Flash Descriptor надано в якості блобів на деяких платах, але це не є Intel Flash Descriptor надано в якості блобів на деяких платах, але це не є
блобами *програмного забезпечення*. Це конфігурації, які надано в двійковому форматі, блобами *програмного забезпечення*. Це конфігурації, які надано в двійковому форматі,
повністю придатному для читання вільним програмним забезпеченням. Наприклад: повністю придатному для читання вільним програмним забезпеченням. Наприклад:
@ -392,6 +396,8 @@ Intel Flash Descriptor надано в якості блобів на деяки
ARM/chromebook ARM/chromebook
--------------- ---------------
### BL1 bootloader (peach/daisy):
BL1 завантажувач потрібен на: `daisy_snow`, `daisy_spring` та `peach_pit`. BL1 завантажувач потрібен на: `daisy_snow`, `daisy_spring` та `peach_pit`.
Висновки Висновки

View File

@ -124,6 +124,30 @@ dem `lbwww-img` Repository hinzu, indem Du diese dann jeweils mit diesem Link ve
<https://av.libreboot.org/path/to/your/new/image/in/lbwww-img>. <https://av.libreboot.org/path/to/your/new/image/in/lbwww-img>.
Wenn dein Patch der Libreboot Webseite hinzugefügt wird, werden erscheinen deine Bilder live. Wenn dein Patch der Libreboot Webseite hinzugefügt wird, werden erscheinen deine Bilder live.
If adding a photo, compress it for web distribution. Images should be about
800px wide, and usually under 100KiB in size:
First, scale your image down to approximately 800px width, using your favourite
image manipulation program. For example, with `imagemagick` you can do the
following (make sure the image isn't already smaller or equal than preferred).
convert original.jpg -resize 600000@ -quality 70% web.jpg
You should always run `jpegoptim` on jpg images before submitting them.
It strips useless metadata and *losslessly* optimises them further by cleverly
rearranging the huffman tables used in them.
jpegoptim -s --all-progressive web.jpg
If the image is a (line) drawing, vector graphics are preferable to bitmaps.
Therefore, if possible, save them as SVGs. Those are easy to modify,
and will surely make translators' work easier as well.
PNG images should be optimised with `zopfli` (this is lossless as well).
For example, this reduced the Libreboot boot logo from around 11k to 3k:
zopflipng -ym image.png image.png
Zu Entwicklungszwecken, könntest Du deine Bilder auch lokal verknüpfen, und Zu Entwicklungszwecken, könntest Du deine Bilder auch lokal verknüpfen, und
anschliesend die URLs anpassen sobald Du deine Patches für die Dokumentation/Webseite schickst. anschliesend die URLs anpassen sobald Du deine Patches für die Dokumentation/Webseite schickst.

View File

@ -114,6 +114,30 @@ Therefore, if you wish to add images to the website, please also submit to the
<https://av.libreboot.org/path/to/your/new/image/in/lbwww-img> for each one. <https://av.libreboot.org/path/to/your/new/image/in/lbwww-img> for each one.
When it is merged on the libreboot website, your images will appear live. When it is merged on the libreboot website, your images will appear live.
If adding a photo, compress it for web distribution. Images should be about
800px wide, and usually under 100KiB in size:
First, scale your image down to approximately 800px width, using your favourite
image manipulation program. For example, with `imagemagick` you can do the
following (make sure the image isn't already smaller or equal than preferred).
convert original.jpg -resize 600000@ -quality 70% web.jpg
You should always run `jpegoptim` on jpg images before submitting them.
It strips useless metadata and *losslessly* optimises them further by cleverly
rearranging the huffman tables used in them.
jpegoptim -s --all-progressive web.jpg
If the image is a (line) drawing, vector graphics are preferable to bitmaps.
Therefore, if possible, save them as SVGs. Those are easy to modify,
and will surely make translators' work easier as well.
PNG images should be optimised with `zopfli` (this is lossless as well).
For example, this reduced the Libreboot boot logo from around 11k to 3k:
zopflipng -ym image.png image.png
For development purposes, you might make your images local links first, and For development purposes, you might make your images local links first, and
then adjust the URLs when you submit your documentation/website patches. then adjust the URLs when you submit your documentation/website patches.

View File

@ -114,6 +114,30 @@ Untitled.
<https://av.libreboot.org/шлях/до/вашого/нового/зображення/в/lbwww-img> для кожного з них. <https://av.libreboot.org/шлях/до/вашого/нового/зображення/в/lbwww-img> для кожного з них.
Коли його буде поєднано на веб-сайті libreboot, ваші зображення з'являться в реальному часі. Коли його буде поєднано на веб-сайті libreboot, ваші зображення з'являться в реальному часі.
If adding a photo, compress it for web distribution. Images should be about
800px wide, and usually under 100KiB in size:
First, scale your image down to approximately 800px width, using your favourite
image manipulation program. For example, with `imagemagick` you can do the
following (make sure the image isn't already smaller or equal than preferred).
convert original.jpg -resize 600000@ -quality 70% web.jpg
You should always run `jpegoptim` on jpg images before submitting them.
It strips useless metadata and *losslessly* optimises them further by cleverly
rearranging the huffman tables used in them.
jpegoptim -s --all-progressive web.jpg
If the image is a (line) drawing, vector graphics are preferable to bitmaps.
Therefore, if possible, save them as SVGs. Those are easy to modify,
and will surely make translators' work easier as well.
PNG images should be optimised with `zopfli` (this is lossless as well).
For example, this reduced the Libreboot boot logo from around 11k to 3k:
zopflipng -ym image.png image.png
Для цілей розробки ви можете спочатку створити локальні посилання на зображення, а Для цілей розробки ви можете спочатку створити локальні посилання на зображення, а
потім налаштувати URL-адреси, коли надсилатимете документацію/патчі веб-сайту. потім налаштувати URL-адреси, коли надсилатимете документацію/патчі веб-сайту.

View File

@ -3,7 +3,7 @@
% 17 July 2023 % 17 July 2023
People have been waiting for me to break the silence about this. I go on about People have been waiting for me to break the silence about this. I go on about
it on IRC. This article is intended to address it once and for all, offically. it on IRC. This article is intended to address it once and for all, officially.
I waited so long, because until recently there really wasn't anything tangible I waited so long, because until recently there really wasn't anything tangible
to talk about; why talk about vaporware? Why indeed. to talk about; why talk about vaporware? Why indeed.
@ -15,24 +15,23 @@ This doesn't need to be an overly long post, so it won't be. There is a *fork*
of Libreboot, named GNU Boot, which you can find here: of Libreboot, named GNU Boot, which you can find here:
<https://savannah.gnu.org/projects/gnuboot/> <https://savannah.gnu.org/projects/gnuboot/>
Unofficial GNU Boot 20230717 release Long story short, when I saw this, I decided that I would try to *help* the
project. More on this next:
non-GeNUine Boot 20230717 release
------------------------------------ ------------------------------------
If you want to skip the lecture, just read these first and re-visit this If you want to skip the lecture, just read these first and re-visit this
page (the one you're reading now) afterwards for more context: page (the one you're reading now) afterwards for more context:
* **GNU Boot 20230717, unofficial release (produced by *me*): * **non-GeNUine Boot 20230717, unofficial release (produced by *me*):
<https://gnuboot.vimuser.org/news/gnuboot20230717.html> - based on the <https://notgnuboot.vimuser.org/news/nongenuineboot20230717.html> - based on the
recent [Libreboot 20230625](libreboot20230625.md) release**, but modified to recent [Libreboot 20230625](libreboot20230625.md) release**, but modified to
comply with their policy, as best as I could approximate. comply with GNU Boot policy, as best as I could approximate.
I *encourage them* to re-use this work. It's roughly *8 months* ahead I *encourage them* to re-use this work. It's roughly *8 months* ahead
of their current work. of their current work.
Or generally: **<https://gnuboot.vimuser.org/> - Unofficial GNU Boot website** Or generally: **<https://notgnuboot.vimuser.org/> - non-GeNUine Boot website**
I call this unofficial fork *GNU Boot*, specifically because I want the work
to be used *by* the real GNU Boot project. It is also clearly marked unofficial,
on that website, so people don't get confused about that.
These links, above, are for an *unofficial* fork of Libreboot that *I* have These links, above, are for an *unofficial* fork of Libreboot that *I* have
done myself, proposed for re-use by the new GNU Boot project. I am *not* a done myself, proposed for re-use by the new GNU Boot project. I am *not* a
@ -101,7 +100,7 @@ project, superior to Libreboot in many ways). I recently helped them by offering
to host tarballs for them, that they use in their build system. to host tarballs for them, that they use in their build system.
But that's just the problem: when GNU Boot first launched, as a failed *hostile But that's just the problem: when GNU Boot first launched, as a failed *hostile
fork* of Libreboot (at domain name, libreboot .dot. at), I observed: their code repository fork* of Libreboot *under the same name*, I observed: their code repository
was based on Libreboot from late 2022, and their website based on Libreboot in was based on Libreboot from late 2022, and their website based on Libreboot in
late 2021. Their same-named Libreboot site was announced during LibrePlanet late 2021. Their same-named Libreboot site was announced during LibrePlanet
2023, by this video: 2023, by this video:
@ -117,8 +116,8 @@ created on 11 June 2023. Yet no real development, in over a month since then.
I have this itch in the back of my mind, that says: if you're going to do I have this itch in the back of my mind, that says: if you're going to do
something, you should *do it*. When someone expresses disagreement with what something, you should *do it*. When someone expresses disagreement with what
I say, I can respect it if the it's more than just words. Which is precisely I say, I can respect it if it's more than just words, which is all
what they have been. what they had given at the time of this article.
I value *technical excellence*. I value *technical excellence*.
@ -132,7 +131,7 @@ Distribution Guidelines), talking favourably about FSF/GNU, and so on. I'm in
a position to *do it* (thus scratching the itch), so why not? a position to *do it* (thus scratching the itch), so why not?
**I did this release for them: **I did this release for them:
<https://gnuboot.vimuser.org/news/gnuboot20230717.html>** - it's designated *GNU <https://notgnuboot.vimuser.org/news/nongenuineboot20230717.html>** - it's designated *non-GeNUine
Boot 20230717*, and I encourage them to re-use this in their project, to get Boot 20230717*, and I encourage them to re-use this in their project, to get
off the ground. This completely leapfrogs their current development; it's off the ground. This completely leapfrogs their current development; it's
months ahead. *Months*. **It's 8 months ahead**, since their current revision months ahead. *Months*. **It's 8 months ahead**, since their current revision
@ -162,11 +161,63 @@ There were/are more things to talk about, but I'm not really interested in
writing more. Free as in freedom? Libreboot is a free software project, yet writing more. Free as in freedom? Libreboot is a free software project, yet
GNU propaganda says otherwise. GNU propaganda says otherwise.
GNU Boot is an [inferior](../policy.md#problems-with-fsdg) free software GNU Boot is [inferior](../policy.md#problems-with-fsdg) to Libreboot in every
project, and Libreboot still provides the same blob-free configurations on way, just as Libreboot was inferior to OSBoot before the Libreboot/OSBoot
mainboards when that is possible, so GNU Boot is also a *superfluous* project, merge; since modern (post-merge) Libreboot still provides the same blob-free
configurations on
mainboards when that is possible, GNU Boot is also a *pointless* project,
just as Libreboot was before I merged osboot with it, but I digress. just as Libreboot was before I merged osboot with it, but I digress.
What more is there to say? What more is there to say?
Happy hacking! Happy hacking!
UPDATE (21 July 2023)
=====================
The non-GeNUine Boot website, and the non-GeNUine release itself,
was originally *named* GNU Boot, but clearly marked as *unofficial*, with the
hope that the GNU project would adapt and re-use it for their project. I did
this, specifically to help them get up to date. They currently use Libreboot
from about 8 months ago (late 2022), and that revision used *coreboot* releases
from ~mid 2021.
Modern Libreboot uses coreboot from early 2023, and contains many bug fixes
in its build system, owing to an extensive [build system
audit](audit.html); GNU Boot still contains all of
the bugs that existed, prior to the audit. Bugs such as: errors literally not
being handled, in many critical areas of the build system, due to improper use
of subshells within shell scripts (Libreboot's build system is implemented with
shell scripts), improper handling of git credentials in the coreboot build
system, fam15h boards no longer compiling correct on modern Linux distros...
the list goes on. All fixed, in newer Libreboot, including the recent release.
GNU Boot cease and desist email
-------------------------------
The GNU Boot people actually sent me a cease and desist email, citing trademark
infringement. Amazing.
Despite the [nonGeNUine Boot](https://notgnuboot.vimuser.org/) site having
clearly stating that it's unofficial, and *not* the GNU Boot project. I
literally made it to help them. You know, to help them use newer Libreboot
because they use old Libreboot and even older coreboot.
Anyway, I complied with their polite request and have renamed the project to
non-GeNUine Boot. The release archive was re-compiled, under this new brand
name and the website was re-written accordingly.
Personally, I like the new name better.
Here is a screenshot of the cease and desist request that I received,
from *Adrien neox Bourmault* who is a founding member of the GNU Boot
project:
![](https://av.vimuser.org/email.png)
This, after they themselves tried to steal the name *Libreboot* for their
fork, when they first announced themselves on 19 March 2023 at LibrePlanet,
only renaming to *GNU Boot* months later (on 11 June 2023). Utter hypocrisy,
and a great irony to boot.
I may very well send patches. *If I want to*.