it was necessary for a few days, to let people know, but i think
people all got the message by now.
the substance of the announcement has been moved to the main
article, summarised
the removed page will be redirected in libreboot.org's httpd
the removed info is a relic, from before all information was
centralised in docs/install/spi.md
remove it, because it is extremely confusing for new readers
for bandwidth reasons, i've disabled use
of https://rsync.libreboot.org/
it redirects to mirrorservice.org
the rsync stays up, itself, for now - this will also
be tweaked later (whitelist only those IPs of the mirrors,
and add instructions for how to get whitelisted, for people
who want to set up new mirrors - plenty more rsync mirrors
exist, so there's no need for everyone to download from
libreboot.org directly)
The U-Boot documentation is in the "uboot" directory, but the hardware
index page links to a nonexistent "u-boot". Fix the typo.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Add myself, my contributions, and what I'll try to do in Libreboot to
the contributors and developer pages. I might not always have enough
time to work on things, though. Let's see how it goes.
It feels weird to place my section next to Leah and Caleb, mostly due to
not matching the bullet point format and contribution volume. It also
feels weird placing it to the top of the alphabetical-order contributors
list without mentioning the order, so do that as a title. Add a title
for projects as well.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
The payloads Libreboot uses are listed in contrib. Add a section for
U-Boot as well, now used by supported Chromebooks.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Update the Chromebook codenames in the 20221214 release news page, and
remove part of the note about missing documentation added in previous
commits.
Remove note about me doing "extensive changes to U-Boot" regarding it
being a coreboot payload, that's not exactly true. The patches in lbmk
are optional, quality of life stuff, and mostly other people's. Upstream
basically happens to work fine this way but integration could be much
much better (which I will try to work on in the future).
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Replace the placeholder "U-Boot instructions" page with initial
documentation about the U-Boot payload. Move the warnings in the
hardware index to this document, but keep a small warning with a link.
This is light on installation instructions compared to what's there on
GRUB, since U-Boot's UEFI support means generic installer images should
work and at that point I think it becomes distro developers' job. But
the added links should be enough as a good start otherwise.
Also add a section for known issues that people might want to know.
Not sure about opening lbmk issues for those, because they're mostly
long-standing upstream things and I'm not really as invested in the
issue tracker.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Add initial documentation about flashing Libreboot on supported ChromeOS
devices. Link the Chromebooks in the hardware index to it. I only have
tried firmware work on gru-kevin, so there is an implicit focus on that,
but most others should be similar.
The one exception is gru-bob, as it is new enough to support Closed Case
Debugging which can be used to disable write-protect and flash the
firmware externally. Provide links to the ChromiumOS docs for that.
Although not supported on Libreboot, x86 Chromebooks still carry the
curse that is unreadable non-redistributable Intel ME firmware, so
provide a warning against flashing x86 images without it just in case.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
At least one Chromebook (gru-kevin) has GD25LQ64C [1], which is a 1.8V
8MB SPI NOR flash chip. Although it can be flashed internally, it has to
be flashed externally when a broken image is flashed. I have been using
an unmodified bad CH341A with a 1.8V adapter which works fine so far.
Try to replace mentions of 3.3V with either nondescript terms like
"power" or "VCC", or both 1.8V and 3.3V, except where it's specifically
about 3.3V. Add warnings to check the part number and datasheet for the
rated supply voltage for the chips, and to make sure to match the
flashing hardware's supply to that.
[1] https://www.gigadevice.com/flash-memory/gd25lq64c/
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Leah Rowe