New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support to raspbian 32/64 deploy #563
Adding support to raspbian 32/64 deploy #563
Commits on Mar 26, 2022
-
src: deploy: Fix wrong progress bar
Some config files that do not enable CONFIG_MODULE_SIG do not have the extra SIGN output, making the progress bar display only half of the progress. This commit fixes this issue by first checking the CONFIG_MODULE_SIG=y option in the config; If it is not enabled, it drops the 2 factor multiply. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for 0db7e2a - Browse repository at this point
Copy the full SHA 0db7e2aView commit details -
src: deploy: Create pack function for kernel files
When deploying a kernel to a target machine, we have multiple copy steps spread in different parts of the code, which is a problem since it makes kw deploy code every trick. This commit creates a function responsible for packing all the required files for the boot folder in a single place and send to the target device. This change represents a code refactor in the deploy, which required multiple changes in the test. Since various tests broke during the development of this feature, I also took this opportunity to refactor our tests to make them more manageable. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for db205ce - Browse repository at this point
Copy the full SHA db205ceView commit details -
src: deploy: Enable support to Raspbian
This commit is the final piece for enabling kernel deploy for a Raspberry PI that uses Raspbian. This commit refactors the bootloader update part to remove unnecessary steps for non-grub-based systems and add the file responsible for manipulating the config.txt file. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for adc68d8 - Browse repository at this point
Copy the full SHA adc68d8View commit details -
src: plugin: kernel_install: utils: Fine-tuning RPI kernel removal
This commit is responsible for fine-tuning the kernel removal for raspberry pi. Related to kworkflow#354 Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for f869ae9 - Browse repository at this point
Copy the full SHA f869ae9View commit details -
src: plugins: kernel_install: rpi: Add local deploy support
This commit introduces the final adjustment to enable local deploy. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for a93b050 - Browse repository at this point
Copy the full SHA a93b050View commit details -
src: deploy: Add new kernels to the end of the file
This commit ensures that we do not pollute the config.txt file by removing kernels name duplications and adding the new kernel to the end. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for 2d222f8 - Browse repository at this point
Copy the full SHA 2d222f8View commit details -
src: deploy: Add support for Rasbian 64 bits
For deploying a new kernel to a Raspberry Pi with 32 bits, we need to copy the dtb files by using: cp arch/arm/boot/dts/*.dtb <PATH> In the 64 bits scenario we have to use: cp arch/arm64/boot/dts/broadcom/*.dtb <PATH> This tiny difference raised the attention that we need to handle dtb files deploy a little bit more carefully since any vendor can specify any boot layout (at least, this is what I understood). For this reason, this commit introduces a new config option named dtb_copy_pattern, which gives the developers the flexibility to tell kw how it should copy these dtbs files. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for d04a366 - Browse repository at this point
Copy the full SHA d04a366View commit details -
src: deploy: Use kernel_img_name for the kernel image
In the kworkflow.config file, we have a variable named kernel_img_name used to define the binary kernel prefix used during the deploy. Even though we have this variable, we were ignoring it. As a result, when we deploy a new kernel image to a rasp system, we see a kernel image with a vmlinuz prefix. This commit fixes this issue by stopping to ignore that config variable and only set vmlinuz if that variable is empty. Signed-off-by: Rodrigo Siqueira <siqueirajordao@riseup.net>
Configuration menu - View commit details
-
Copy full SHA for f02d3b3 - Browse repository at this point
Copy the full SHA f02d3b3View commit details