@fast_code_r_us You have any recommendation for a tiny, HDMI-driven screen that does at least 800*480p60 or an #eInk screen like that?

Cuz I want to try some #FrugalComputing with a #Pi0 / #Pi0W and @OS1337 and that only suppirts #MDA…

@betelgeuse93 @itsfoss OFC the main benefit of a #Pi5 with 1GB isn't for #consumers but #industrial customers.

• #Broadcom uses @RaspberryPi / #RaspberryPi as a "#GatewayDrug" to ease #embedded systems designers/integrators into #ARM / #ARM64 systems and get those big enough to want something custom to contact Broadcom.

Also in many systems like #automation, 1GB is more than sufficient (Given that @OS1337 can run on 32 MB RAM in a VM) it's safe to assume the $5 in shave without MOQ is worth it for most buyers who want the extra compute power and I/O compared to a #Pi0W / #Pi0W2 or #Pi3B+ ...

@0x47df I still think the OG #RaspberryPi is good.

• OFC the #Pi0 / #Pi0W & #Pi0W2 are way better options unless one needs Ethernet but even with a USB-Hub integrating it they're smaller...

@silvermoon82 if you allow that connector to be longer and/or include an RP-SMA & USB-C/Barrel Jack for power than that should be possible.

• Personally I'd take a #Pi0W with a USB-Adaptor and hook that together so it can run fully-fledged #CUPS an one could just send it a #PDF for print via #Bluetooth or #WiFi...

@tobias_kleine aww... it's cute.

Reminds me of those classic portable CD/Tape/Radio combo units and the #Tonies-like functionality to select content besides a (presumably touch-)screen is nice.

• I wounder if a #Pi0 / #Pi0W is enough to drive it or if it needs like the onboard audio out of a regular #RaspberryPi Model A(+) / B(+)…

Still, very nice...

This + #Pi0W and some USB+Ethernet Hub & Keyboard seems to me the more reasonable and cheaper alternative to trying to get a working #DEC #Terminal at a reasonable price + Wifi232 module [video via @lazygamereviews]...

I really hope @paulrickards releases the #WiFi232 modules' #schematics and #firmware as #OpenSource since that thing seems to be #unobtanium still...

@r @fluffykittycat @flower Obviously people have used the #RP2040 for many projects and given it's ease of programming, low price, excellent documentation and easy availability it's no wounder it does put pressue on #ATmega / #ATtiny, #Arduino, #Teensy, etc.

• At least for low volume productions and prototypes as proof of concept.

#RaspberryPi shure are more and more targeting #embedded & #industrial clients given they do in fact disrupt the market as one can get proper #documentation and #tools without paying $$$$ upfront (AND sign NDAs) just to be able to boot #Linux on it.

• And competitors fail at understanding that this makes #Broadcom look good and is their entry-way into acquiring new clients. Because selling hardware purely off specs may work in #amd64 land where shit's legacy and the way things work is so entrenched that basic stuff just works as in booting. #ARM and even #ARM64 fail at having that level of #standardization.

OFC the #Pi0 / #Pi0W / #Pi0W2 doesn't need to innovate since every competitor isn't even trying to compete but merely farting out boards with 0 documentation and some halfassed boot images and no post-sales support so they keep dominating by virtue of being the only ones that just work...

@krutonium @landley @geerlingguy IDK but I also didn't knew that #32bit #ARM (i.e. #AMRv5r11 as used by the #RaspberryPi #Pi0 / #Pi0W) is out of patent protection...

• I started @OS1337 as an effort to build a "legacy-friendy" minimalist #toybox + #musl / #linux distro as a basis for #firmware (i.e. for a #minimalist #embedded system like an applianced "#SSH-#Terminal" in critical IT)…

Killing non-#64bit support in Linux would be a death sentence for many #EmbeddedSystems.

• And I don't think they can all be migrated to i.e. #NetBSD, as it already took huge efforts to get them away from #MSDOS & #WindowsEmbedded…