Tiny Core Base > Raspberry Pi
Raspberry Pi Zero Wireless and piCore14.x LAN Connectivity
Rich:
Hi CentralWare
In Tinycore there's a Core and a CorePlus. Why not just
simplify the process and make a piCorePlus that includes the
wireless extensions. Users that need the help can then download
piCorePlus and those that don't can download piCore. The
piCorePlus users can then delete the extensions they don't need.
No custom cpios and no custom extensions that way.
CentralWare:
@Rich: Being that piCore currently comes in four flavors (three of which are really viable) we would technically be doubling this -- not that this isn't the solution in the end.
Think of the differences between x86 and x86_64 - each has its own core, coreplus, etc.
With Raspberry, it's very similar: armv6, armv7, (armv7l) and now aarch64, all home to picore-####.zip (containing an .img file to burn onto SD as described previously.)
I'm sorry to say that I'm not entirely certain as to who is in charge of the piCore releases these days (bmarkus, Paul_123, etc.) so their input would be ideal as I cannot predict how much of a pain it would be to double that work-load.
ASSUMING arm 6, 7 and aarch cannot share the same wireless drivers, three cpio modules would be required (where I think 7L would function on the same arm7 drivers, but I'd have to confirm.) As such, the same should be said about creating entire releases for each - I just cannot confirm how much effort this would entail. It may be as simple as extracting the existing .IMG file, adding the contents of the mentioned extensions and re-packaging the image with a new file name.
Paul_123:
The 32bit images require 3 different kernels/modules. That’s why I separated the modules initrd from the rest of initrd, to avoid too much duplication. To add WiFi or net usb, requires all 3 variants of each extension. Plus you need to add all of the network firmware packages.
It’s very easy to do, but adds a lot to the image.
Rich:
Hi Paul_123
--- Quote from: Paul_123 on January 13, 2024, 08:43:21 AM --- ... It’s very easy to do, but adds a lot to the image.
--- End quote ---
It did the same for x86:
--- Code: ---Core-14.0.iso 12-Apr-2023 13:12 17870848
CorePlus-14.0.iso 12-Apr-2023 13:12 260046848
--- End code ---
But it provided those without a wired connection another option.
--- Quote from: CentralWare on January 13, 2024, 04:45:54 AM ---@Rich: Being that piCore currently comes in four flavors (three of which are really viable) we would technically be doubling this -- not that this isn't the solution in the end ...
--- End quote ---
Yes, but armv6, armv7, and armv7l repos all use the same piCore-14.1.0.zip file.
CentralWare:
--- Quote from: Rich on January 13, 2024, 10:09:20 AM ---Yes, but armv6, armv7, and armv7l repos all use the same piCore-14.1.0.zip file.
--- End quote ---
Sorry, I was trying to word things so that it was easier to visualize the comparative between piCore and TinyCore. ALL of the different kernels and cpios are inside the zip/img for Pi-0 through Pi-4.
@Paul_123, how challenging would this be in aarch64? (Sorry to say I haven't even opened it yet; too much still on the plate before unboxing the Pi-5.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version