Tiny Core Base > Raspberry Pi
Raspberry Pi Zero 2 W
Paul_123:
--- Quote from: vandiwa on January 25, 2022, 11:12:34 AM ---Generally speaking, is there a way to include packages for the RPiZW and the RPiZ2W in the filesystem and take two different paths to installing them depending on the processor it's running on?
--- End quote ---
Been discussed many times. The default images are kept very small on purpose. We provide toolkits to build a highly customizable small footprint system.
Rich:
Hi vandiwa
--- Quote from: vandiwa on January 25, 2022, 11:12:34 AM ---Generally speaking, is there a way to ...
--- End quote ---
Generally speaking, all non kernel related extensions are compiled to be backwards compatible with ARMv6, though
there may be a few exceptions. So the nano.tcz you find in the ARMv7 repo is identical to the one in the ARMv6 repo.
For kernel related extensions, they have unique names, wireless-5.10.77-piCore-v7.tcz vs wireless-5.10.77-piCore.tcz.
You can have both in your tce/optional/ directory. If you list it like this in your onboot.lst:
--- Code: ---wireless-KERNEL.tcz
--- End code ---
then the correct version will be loaded depending on the processor that is being booted.
vandiwa:
Thanks Rich, and I can confirm that the same image I have booting and starting WiFi on the ARMv7 now will also boot and start WiFi on the ARMv6, and that was a pleasant surprise.
Greg Erskine:
As you build your system, keep in mind, tce-ab will only download from the repository the correct kernel version of a (kernel dependant) extension.
bmarkus:
--- Quote from: vandiwa on January 25, 2022, 08:32:17 AM ---Wait - I stripped the timestamps to do a dmesg compare side by side, and I didn't even realize the RPIZ2W has an ARMV7 processor where the RPIZW has an ARMv6 - do I need to be using the packages from armv7?
--- End quote ---
32-bit TCZ packages, except kernel modules are built for arm v6 architecture, you can use them on v7 and v7l.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version