rpi-firmware | Firmware files for the Raspberry Pi

by Hexxeh C Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | rpi-firmware Summary

rpi-firmware is a C library typically used in Internet of Things (IoT), Raspberry Pi, Arduino applications. rpi-firmware has no bugs, it has no vulnerabilities and it has medium support. However rpi-firmware has a Non-SPDX License. You can download it from GitHub.

Firmware files for the Raspberry Pi. These are mirrored in a separate repo from [the official one] because for updating the firmware, we’re only interested in the files in the boot folder of the official repo. Git doesn’t provide a way to clone only a single subfolder of a repo, and downloading the entire repo including the sample code and VC libs would take too long. If the boot firmware files are split off into a seperate repo, then the tool could be pointed at that repo instead of this one, as long as the firmware files are in the root of the repo.

Support

Quality

Security

License

Reuse

Support

rpi-firmware has a medium active ecosystem.

It has 768 star(s) with 166 fork(s). There are 148 watchers for this library.

It had no major release in the last 6 months.

There are 27 open issues and 236 have been closed. On average issues are closed in 314 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of rpi-firmware is current.

Quality

rpi-firmware has no bugs reported.

Security

rpi-firmware has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

rpi-firmware has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

rpi-firmware releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rpi-firmware

Get all kandi verified functions for this library.

rpi-firmware Key Features

No Key Features are available at this moment for rpi-firmware.

rpi-firmware Examples and Code Snippets

No Code Snippets are available at this moment for rpi-firmware.

Community Discussions

Trending Discussions on rpi-firmware

Applying patch kept in br2-external to a buildroot package

QUESTION

Applying patch kept in br2-external to a buildroot package

Asked 2020-Oct-07 at 14:48

I want to apply a patch to buildroot package. I'm using br2-external tree to keep my customizations out of buildroot tree. Buildroot can find my patch, but fails when trying to apply it.

I have set BR2_GLOBAL_PATCH_DIR="${BR2_EXTERNAL_PATH}/board/myboard/patches" and put the patch in ${BR2_EXTERNAL_PATH}/board/myboard/patches/packagename/0001-name-of-patch.patch. I generated the patch by going to buildroot repo, applying the changes to package, committing them with git and creating a patch from the last commit: git format-patch HEAD~1 So the patch looks like this:

...

ANSWER

Answered 2020-Oct-07 at 14:48

As mentioned by @sawdust its not possible to patch a file in buildroot package directory buildroot/package/. You can only patch the source of the package, i.e. the source files downloaded to output/build//.

I ended up with using a post-build script to modify the file after it has been copied, as described in https://buildroot.org/downloads/manual/manual.html#rootfs-custom (option BR2_ROOTFS_POST_BUILD_SCRIPT="${BR2_EXTERNAL_PATH}/board/myboard/scripts/post-build.sh")

Source https://stackoverflow.com/questions/64233932

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rpi-firmware

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: