Go to file
Erico Nunes e14102c6f2 linux-firmware: bump version and fix hash
Bump the package to the most up to date version and fix the sha256 hash.
linux-firmware was failing due to an incorrect sha256 hash, as follows:

Fetching all references
warning: redirecting to https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
remote: Counting objects: 6972, done.
remote: Total 6972 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (6972/6972), 196.63 MiB | 4.22 MiB/s, done.
Resolving deltas: 100% (4516/4516), done.
>From http://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware
 * [new branch]      master     -> origin/master
warning: redirecting to https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
warning: refname '8d69bab7a3da1913113ea98cefb73d5fa6988286' is ambiguous.
Git normally never creates a ref that ends with 40 hex characters
because it will be ignored when you just specify 40-hex. These refs
may be created by mistake. For example,

  git checkout -b $br $(git rev-parse ...)

where "$br" is somehow empty and a 40-hex ref is created. Please
examine these refs and maybe delete them. Turn this message off by
running "git config advice.objectNameWarning false"
ERROR: linux-firmware-8d69bab7a3da1913113ea98cefb73d5fa6988286.tar.gz has wrong sha256 hash:
ERROR: expected: 905be20e4e2d7628dea4e2e99195520fc0cce8b247faabdc52fc44a3ff2ceb04
ERROR: got     : b9fce72a7b0b55eb311701dfd47914bc9e037134fa401d33e6e73ab9ebc9d116
ERROR: Incomplete download, or man-in-the-middle (MITM) attack

Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-09-27 20:42:00 +02:00
arch arch: add support for RISC-V 64-bit (riscv64) architecture 2018-09-23 23:42:41 +02:00
board configs/qemu_riscv64_virt: new defconfig 2018-09-25 21:40:10 +02:00
boot boot/riscv-pk: add bootloader for RISC-V architecture 2018-09-25 21:39:52 +02:00
configs configs/pc: bump kernel version 2018-09-27 14:12:16 +02:00
docs docs/website: add paragraph about the IRC channel restrictions 2018-09-11 15:47:06 +02:00
fs fs/btrfs: remove destination file before generation 2018-08-25 23:59:23 +02:00
linux linux-headers: bump 4.{4, 9, 14, 18}.x series 2018-09-26 19:50:59 +02:00
package linux-firmware: bump version and fix hash 2018-09-27 20:42:00 +02:00
support support/kconfig: bump to kconfig from Linux 4.17-rc2 2018-09-20 23:14:38 +02:00
system system: update Config.in comment about systemd dependencies 2018-09-15 00:05:48 +02:00
toolchain arch: add support for RISC-V 64-bit (riscv64) architecture 2018-09-23 23:42:41 +02:00
utils utils/scancpan: refactor license name adjustment 2018-09-25 22:57:54 +02:00
.defconfig
.flake8
.gitignore
.gitlab-ci.yml configs/qemu_riscv64_virt: new defconfig 2018-09-25 21:40:10 +02:00
.gitlab-ci.yml.in Makefile: introduce check-package target 2018-08-12 14:39:32 +02:00
CHANGES Update for 2018.08 2018-09-06 22:11:06 +02:00
Config.in Config.in: add BR2_HOST_GCC_AT_LEAST_8 2018-05-02 14:50:14 +02:00
Config.in.legacy package/{mesa3d, mesa3d-headers}: bump version to 18.2.0 2018-09-10 21:58:42 +02:00
COPYING
DEVELOPERS sedutil: new package 2018-09-27 13:59:09 +02:00
Makefile arch: add support for RISC-V 64-bit (riscv64) architecture 2018-09-23 23:42:41 +02:00
Makefile.legacy
README

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on Freenode IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches