I really hope they can keep the cost down, it needs to be in the "it's so cheap just hack on it" price range for not just engineers but kids too. I'm excited to see low-cost hardware put in the hands of kids with LLMs in their sails.
I'm using the 2 W for a project and one thing I would love is for a better wifi antenna, the one that's on the 2 just isn't good enough. You can hack it though, there is a spot on the board where you can solder on a connector, cut a single trace and you're good to go. But it would be great if it would do better out of the box.
Amazingly powerful hardware for the price these little things.
I wouldn't hold out hope for an easier out of the box wifi antenna. If you want a U.FL antenna for the built-in wifi, there has to be a physical switch (cost, fragility) or a built-in antenna connected to U.FL you can replace (same issues) or the same cut and solder pattern for wifi antennas across chips like ESPs, nRFs, and others.
I don't see the need for an even more powerful Pi Zero. I'd say just have a modernized version of the original $5 single core Pi Zero, or ok the wireless version was good too. Maybe even have a 128MB config (original one was 512MB before the DRAM shortage) to keep the price down. Model A same same, who needs it if it's not a lot cheaper than the B.
I do like the Pico series and it would be cool to have one of those with memory protection.
The Pi zero is dead to me. Price might be one thing but lack of availability makes it useless. I like running Merves on it but will move to AtomVM and Esp32 where I can.
there is radxa zero 3w, which on paper is nice looking board. bit dated maybe but still lot fresher than pi zero 2w. the rockchip soc should have decent mainline support and it has been around for a while
All of the boot chain is a mess because the Pi 1 used a bucket load of unused Broadcom set-top-box SoCs which were GPUs with a tiny ARM core along for the ride. Every Pi boots off the GPU first.
Yeah, it's not talked about too often but RPi 1 was basically Broadcom's "useless SoC recycling program".
If not for the success of Raspberry Pi, Broadcom would have zero SBC presence today. Like many companies chasing the high volumes and high margins, they don't see the market value in a segment like this. Thus things like poor docs and weird blobs. Raspberry Pi is open to the degree it is despite Broadcom, not because of it.
Ironically, that Broadcom tie could have caused RPi to eventually lose ground to other SBCs - because the likes of Rockchip just deliver more bang for buck in SoC dept. Broadcom doesn't seem to be investing in staying competitive in the segment. So RPi's edge is just the ecosystem being more important than raw price/performance.
For now though, that's pretty much on hold, because SBC price tags are increasingly DRAM dominated instead.
Seems like a good use for AI. If people can use it to port video games from one system to another or jailbreak consoles, surely "get this library/program compiling on this device, then get all the tests passing, here's root ssh and an internet connection" could work pretty well in most cases. I wouldn't have bothered wasting my time in the past, but now, sure why not? It's not my time anymore and AI can turn the crank until it works.
Largely agreed but very different problems between "works for me" and "ready for upstream/mainline".
I myself am guilty as hell of this, of carrying my own remixed software, juggling patches atop upstream, and feeling like getting it upstream would be far more work and labor (and ultimately like I don't really have the confidence to assert to upstream). Meanwhile upstream is screaming their heads off everywhere that they can't take it anymore, that they are not ok. It sucks that we have such amazing power, such competency, but our scaling & social functions aren't scaling into the godlike powers that are now on tap! Alas.
Yeah, agreed. I do the same. I only contribute smaller patches that definitely fix bugs, and not big vibe coded sprawls of code that happen to work for me but who knows what it breaks. For example I started using opengym which is definitely someone’s vibe code project and then grafted SSO on top for my own needs, but there’s no way I’d submit that upstream. That’s fine. I got what I wanted out of it. Things will adjust but for now just enjoy the ride :)
Yeah, I have a bunch of Radxa zero 3W, with their Rockchip rk3566. 4x A55 is just barely better than the A53 era still plaguing us 15 flipping years latter! Unbelievable. Alas just a hair before modern era of Rockchip, so it's support is much less consistent! But still pretty competent all in all!
Pine's Quartz64 has different peripherals attached but still afaik one of the best ways to track upstream support. It hasn't changed much since Linux 6.1 and I don't know if that's because there's nothing new or the page is just out of date. https://pine64.org/documentation/Quartz64/Development/
The biggest thing I want to see in a zero 3 w is not better cpu or ram, but wifi that isn't the zero 2 w spec of "2.4GHz 802.11 b/g/n wireless LAN"
Having at least 1x1 802.11ac that's capable of working in the 5050 to 5900 MHz band will be a huge feature improvement. Such as to connect to a 'modern' AP running in an 80 MHz channel.
There's tons of environments where 2.4 GHz is a CSMA hell of noise and the performance in a single 20 MHz channel will always be crap, and ranges/real world distances between AP and pi will be very limited because of the extreme noise in the 2.4 band.
It's hard to get too excited about anything coming from Raspberry Pi these days. Their anti consumer moves, weird accusatory social media positioning and obscene pricing just makes it all feel a bit like their relationship with B2C has gone very sour.
While people do often use pis to do things you could do with an esp32, an ESP32 cannot do the majority of things a Pi can do.
Amazingly powerful hardware for the price these little things.
Just use a USB adapter with a decent antenna.
I do like the Pico series and it would be cool to have one of those with memory protection.
If not for the success of Raspberry Pi, Broadcom would have zero SBC presence today. Like many companies chasing the high volumes and high margins, they don't see the market value in a segment like this. Thus things like poor docs and weird blobs. Raspberry Pi is open to the degree it is despite Broadcom, not because of it.
Ironically, that Broadcom tie could have caused RPi to eventually lose ground to other SBCs - because the likes of Rockchip just deliver more bang for buck in SoC dept. Broadcom doesn't seem to be investing in staying competitive in the segment. So RPi's edge is just the ecosystem being more important than raw price/performance.
For now though, that's pretty much on hold, because SBC price tags are increasingly DRAM dominated instead.
I myself am guilty as hell of this, of carrying my own remixed software, juggling patches atop upstream, and feeling like getting it upstream would be far more work and labor (and ultimately like I don't really have the confidence to assert to upstream). Meanwhile upstream is screaming their heads off everywhere that they can't take it anymore, that they are not ok. It sucks that we have such amazing power, such competency, but our scaling & social functions aren't scaling into the godlike powers that are now on tap! Alas.
Pine's Quartz64 has different peripherals attached but still afaik one of the best ways to track upstream support. It hasn't changed much since Linux 6.1 and I don't know if that's because there's nothing new or the page is just out of date. https://pine64.org/documentation/Quartz64/Development/
Having at least 1x1 802.11ac that's capable of working in the 5050 to 5900 MHz band will be a huge feature improvement. Such as to connect to a 'modern' AP running in an 80 MHz channel.
There's tons of environments where 2.4 GHz is a CSMA hell of noise and the performance in a single 20 MHz channel will always be crap, and ranges/real world distances between AP and pi will be very limited because of the extreme noise in the 2.4 band.