| Age | Commit message (Collapse) | Author |
|---|
|
When building Coreboot or Libreboot with CONFIG_SPKMODEM, the boot
messages data is encoded as sound and sent to the sound card.
To receive them you can record them with another computer (and ideally
you need an audio cable for that and to make sure that the volume is
not too low or not too high), and you can then decode them in real
time with a command similar to that one:
parec --channels=1 --rate=48000 --format=s16le | spkmodem-recv
This also works with grub spkmodem console output.
Note that the messages speed is relatively slow, so if you build
Coreboot or Libreboot with that option, your boot might take a long
time (like 30min for instance) if you have a lot of messages.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
This makes sure that all the tools are installed. Some tools like
cbfstool also have other tools like fmaptool that are really useful.
fmaptool can be used to work with Chromebook images for instance.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The warning about bucts was removed as in fact most of these tools are
probably dangerous in one way or another if used improperly.
Flashrom which is packaged in most GNU/Linux distributions is also very
dangerous if used improperly, though it comes with warnings and safe
defaults.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Now that it builds for all architectures we can also ship it.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
On i686, cbfstool wasn't build because it failed to compile, and on
armv7h, the build fail with an error similar to this one:
host/lib/extract_vmlinuz.c: In function ‘ExtractVmlinuz’:
host/lib/extract_vmlinuz.c:67:9: warning:
‘memcpy’ specified bound between 2147483648 and 4294967295
exceeds maximum object size 2147483647 [-Wstringop-overflow=]
67 | memcpy(vmlinuz, kpart_data + vmlinuz_header_offset,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
68 | vmlinuz_header_size);
| ~~~~~~~~~~~~~~~~~~~~
This fixes that build error and enables cbfstool to be built on all the
architectures supported by Parabola.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Since there is more than one utility in this package it's
more clear if it is named libreboot-utils.
In addition, this packages has part from the nvramtool I made
from scratch so I added myself in the header in addition of
Wael Karramas who is the main author of this package.
I also fixed the Maintainers line as more than one person involved in
Parabola has some knowledge about Libreboot and Coreboot.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Without that fix, it wokrs fine with makepkg but fails with libremakepkg
with the following error:
| ==> Starting prepare()...
| /startdir/PKGBUILD: line 141: unzip: command not found
| ==> ERROR: A failure occurred in prepare().
| Aborting...
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The cglib project has the following in its README.md:
IMPORTANT NOTE: cglib is unmaintained and does not work well (or
possibly at all?) in newer JDKs, particularly JDK17+. If you need
to support newer JDKs, we will accept well-tested well-thought-out
patches... but you'll probably have better luck migrating to
something like ByteBuddy.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The http://excalibur.apache.org/ website has a banner that states on its main
page:
2010/12/15 - Apache Excalibur has been retired.
For more information, please explore the Attic.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
We now have a package named libreboot-utils that contain nvramtool and
other Libreboot/Coreboot related utilities.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The 1.2 version of log4j is not only unmaintained / End of life, but it
also has lot of security vulnerabilities[1] including at least one
critical CVE, 4 high CVEs and 1 moderate CVE.
[1]https://logging.apache.org/log4j/1.2/
Link: https://labs.parabola.nu/issues/3261
Reported-by: gap
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Despite what its name suggest, the PCR repository is not only for
PKGBUILDs that come from AUR.
In the Parabola wiki[1], there is the criteria for packages meant to
go in PCR, and we can deduce from what is written there that PCR is
for packages that both:
* "are not included on official repos of Arch Linux"[1]
* "are not considered to be essential enough for the base system."[1]
So here even if the nvramtool PKGBUILD doesn't come from AUR, it is
meant to go in PCR.
[1]https://wiki.parabola.nu/Repositories#.5Bpcr.5D
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
|
|
The status quo is that any Parabola hacker is expected to (be able to)
modify any packages, and having a single maintainer of a package
discourages that practice as people would typically send a patch to
the maintainer instead of pushing it directly.
So for a start we can add common maintainership on package lacking any
"Maintainer: " header for packages in repositories that are supposed
to be maintained.
As for finding who worked on a given package (in case it could be
needed), the git log should have all the information.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The status quo is that any Parabola hacker is expected to (be able to)
modify any packages, and having a single maintainer of a package
discourages that practice as people would typically send a patch to
the maintainer instead of pushing it directly.
So for a start we can add common maintainership on package lacking any
"Maintainer: " header for packages in repositories that are supposed
to be maintained.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Not only it is already in community, but it also needs to be removed
(along with the community version) due to licensing issue: some artworks
are under a CC-BY-NC license.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
asciidoctor is already in Arch Linux community, and it is more
recent.
On armv7h we have:
community/asciidoctor 2.0.17-1
An implementation of AsciiDoc in Ruby
and on i686 we have:
community/asciidoctor 2.0.17-1.0 [installed]
An implementation of AsciiDoc in Ruby
and on x86_64 we have:
community/asciidoctor 2.0.17-1
An implementation of AsciiDoc in Ruby
So we don't need the pakcage from pcr anymore.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
same software is in [community]
|
|
|
|
Without that fix it builds fine with makepkg if you have libusb
installed but it fails with libremakepkg with the following error:
| checking for LIBUSB... no
| configure: error: Package requirements (libusb-1.0) were not met:
|
| Package 'libusb-1.0', required by 'virtual:world', not found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables LIBUSB_CFLAGS
| and LIBUSB_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
In the commit a15f2642006a122148c28e2f9d1032b07c8d082d (aur: simtrace:
update from AUR) I accidentally ovewrote the simtrace PKGBUILD with
the simtrace 2 one.
Both are different software projects meant for two different sim tracer
hardware generations.
The simtrace software supports only one device named simtrace
which uses an AT91SAM7S microcontroller.
The simtrace 2 software supports the simtrace 2 hardware that use a
SAM3S microcontroller, and it also supports other hardware like the
sysmoQMOD that have the same SAM3S microcontroller.
This reverts commit a15f2642006a122148c28e2f9d1032b07c8d082d.
|
