-
Notifications
You must be signed in to change notification settings - Fork 207
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
rpi-updating on Raspbian Bullseye 32 bit (platform RPI4b), 64 bit kernel is installed #275
Comments
Both 32-bit and 64-bit kernels are installed. However, on a Pi 4 the default kernel is now the 64-bit one. Is there a specific reason why you need the 32-bit kernel? You can force the firmware to load it by including We believe the 64-bit kernel should be the best for most people. We are anticipating a few problems building software packages that assume the kernel architecture matches the userland architecture, but otherwise things should continue to work as (or better than) before. |
Thank you. Right now we are using Raspbian 32 bit just because we started building sw on that distro, and we match kernel architecture with userland architecture, both 32bits. Woud it be safe continue using this approach? Please, an argument that does not directly concern this aspect: we are looking for graphical improvements; for instance we notice that rescaling rendering chromium window (on xorg) to FHD (1920x1080), reduces global fps rendered. In your opinion is there still room for improvement (on RAspberry Pi 4 b) in the use of VideoCore VI from this point of view? |
Heads up that you can preface commands with |
By the way, the rpi-update and rpi-firmware repos are now officially hosted in our GitHub organisation: https://github.com/raspberrypi/rpi-update and https://github.com/raspberrypi/rpi-firmware. |
Executing rpi-update on Raspbian Bullseye 32 bit using latest commit ( rpi-update cba2ae16185afbb4895673b6c2ef7d4078abd65f ), 64 bit kernel (6.1.19-v8+) is installed instead of 32 bit one.
The text was updated successfully, but these errors were encountered: