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>
Add new U-Boot related options to coreboot board.cfg section. Fix a
remark about not being able to build non-x86 roms. Copy the sections
documenting coreboot resources and other payload scripts, and modify
them to document U-Boot resources and scripts.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Add codenames for the Chromebooks now supported in Libreboot. The names
of the per-board lbmk resources directories are slightly different than
these for naming consistency (e.g. "gru-kevin" instead of "kevin"). The
names in the coreboot src/mainboard are usually of the baseboard
("google/gru" instead of "kevin").
Also add a link to a ChromiumOS docs page listing most if not all
Chromebooks and their codename information among other things.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Add an example qemu-system invocation for the qemu_x86_12mb board's
U-Boot payload. List the QEMU arm64 board in the supported hardware page
and an example invocation for that as well.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Add some lbmk invocation examples for U-Boot. Try to keep it light in
the section that tells people to just use "build boot roms" instead,
but have more detail in the payload-specific section.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
http2 now enabled on the server, so multiple http requests
are a bit more efficient for modern browsers
this will save a bit of bandwidth, at the expense of causing
additional delay on high latency connections:
someone on 500ms latency and using http1.1 basically has to
wait an extra half-second for the site to load
(however, that's only the first time, assuming their browser
caches the css file)
mistakes made during osbwww->lbmk merge have been corrected
mostly a few search/replace errors, and deleted pages that have since
been restored, or pages that were incorrectly scrubbed are now full; for
example, pages that said there are no releases yet (from osboot) have
been replaced with the version from libreboot that links to release archives,
which *do* exist in libreboot
i generally fixed all other minor issues with paragraphs that i found, where
the paragraphs made sense in osboot.org but did not so on libreboot.org
this is all of my fixes, after auditing the recent merge. no point splitting
them up. just patch it up and go!
this is imported from osbwww, based on a change shmalebx9 made.
this patch is a rebase/cherry-pick from osbwww performed by leah rowe,
based off of shmalebx9's work
the substance of the message is no different, but the message is now much more
effective and the reader is less likely to turn away; much of the arguments
are emotionally driven, as opposed to factual, so using such "insulting"
language is probably not a good idea
my motivation is to encourage the fsf to improve, not to attack it. the fsf
should work with the community, not against it; similarly, libreboot and
osboot should not be seen to attack the fsf. however, constructive criticism
is ok, and that is entirely the purpose of this article
Each page had the GFDL license declaration on it, but this is unnecessary due
to <https://libreboot.org/license.html> being linked in the footer on each
page. It clearly defines your rights when accessing the site.
and host it on libreboot.org/ instead of av.libreboot.org/
the PNG "light" libreboot logo is well-optimized, and still opens properly in
most browsers even if named favicon.ico. the icon is going to be loaded on
pages anyway. having a separate favicon.ico adds an extra http request, which
causes seconds of lag on some connections
so make sl.png the favicon, and use that in the img tag on pages
The CSS is light enough now that, in terms of compression, it makes more sense
to merge it in each HTML page. It's small enough to make virtually no
difference, and this cuts down on HTTP requests.
This change will save literally seconds of time, for those who are on high
latency internet services (satellite based internet services, slow tor relays,
etc).
Leah Rowe