Wednesday, December 24, 2025

Announcing Pokey Linux, A Yocto-based distribution of distributions for embedded systems




Pokey Linux is a platform for developing many single-application OSes, using the fewest resources possible. It is of course a reference to the Poky tool in Yocto, and the Earthbound character for the 1995 SNES game. While I have read about Yocto for years, I just thought it was a convenient and funny mnemonic way to recall a tool. While I haven't developed any code for it, it aims to be a repository of binaries that one can search and download, but also locate the package dependencies and the Yocto methods for creating it (in other words, non-technical users can work their way from a GUI-based software manager like Synaptic or Cubic, and see the steps taken to develop it, or perhaps just a few steps to make a modification). I realized this might be a better approach to indecision, as indecision of what single application OS to develop first is besides the point. Someone might want a binary with just VLC, or Thunderbird, or Midori, and nothing else (and of course, a GUI for the board support). It's also a way to learn to build without knowing what OS I need to use. In a way, it's kind of like a sideshow OS (a secondary character, not the daily driver, or side driver) 

Friday, December 19, 2025

The Smartest Companies are in the Same Room, but are not Building New Products Together...for you

 A brief follow up to my previous post, "The State of Stateless Linux (And the Future of Solar Computing)" is about the technology industry as a whole.

Obviously, money drives product development - anticipated revenue streams from new products. But sometimes newer is just cheaper materials, rather than a new feature, which of course, isn't always a bad thing, since the savings can be passed down to the consumer. 

In the Qualcomm case, The UNO Q isn't really innovative in terms of features. It might be a cash cow if Raspberry Pi wants to get out of the consumer division and only focus on corporate/industry customers. That too, isn't always a bad thing- serving consumers where a former company is unable or less willing. After all, Qualcomm has a large patent portfolio, and wouldn't need to outsource every thing or anything. This is the same Qualcomm that wanted to make a bid on Intel to buy them  out, however Intel  & The U.S had "other plans.



Now, sometimes it might be a good idea to choose your battles wisely. For example, Qualcomm is known more for its mobile chipsets and wireless IP, rather than single board computers. So them amassing a war chest was probably prudent if they decided against that 10 years ago. And of course there are also potential benefits to avoiding tariffs since it is an American company, whereas the UK, however unlikely it would face tariffs to the extent of other countries, could see a surcharge on even a $35 Raspberry Pi.

Even so, product development often follows other successful products, and sometimes it is simpler/easier to develop a cheaper product that does the same thing at the same energy consumption for a lower cost, than something that uses significantly less power for the same price- because energy is still cheap, especially at the low end where devices consume just a couple watts of power.

There are certainly countless instances where companies work together to build a product- an EUV machine isn't built by one company, for example, but uses a laser from Germany and materials from the U.S. and Asia:


There are other kinds of "cooperation", of course, such as "no-poach":
A lot of times success depends on a few limited players who have the time to market and develop a product before anyone else, and true competition in a free market is rarely as fair as it is encouraged.

But what happens when the sucesssful cases become complacent? They rarely, pro-actively innovate, unless they have some guilt or a conscience.

So instead, they, the smartest people and companies in the room, gather at conferences, exchange notes, and informally focus on non-competing products in markets that don't interact, or if they do, at a minimum. It's far easier to control competition when, as Lincoln would do - he keeps his friends close, and his enemies closer (in the tent).

AI, despite all its hype, in 2025, is already considered a safer investment than legacy 32-bit linux products for the consumer market, because the reach is far greater. When you can sell 100,000 IP cameras with AI-enhanced motion detection, your most reliable and highest paying customers are surveillance customers who need panopticon technology for small business warehouses in a crime-ridden town.

In other words semiconductor companies aren't going to profit as much from a smaller market of 8-9 billion humans, when they can sell a trillion IP cameras to a few thousand companies. So that's all Big Tech is doing these days. Meeting at conferences like a plenary session for planetary domination. So it's not enough to just follow the mainstream linux anymore. Ordinary individuals have been left behind.

Open source/ Free software hobbyists who want anything more than retro technology products are going to need to consider more leading edge solutions. And forking, if necessary.







Tuesday, December 16, 2025

The State of Stateless Linux OSes, and the future of Solar Computing

The title is more of a gag on the other parodied State of the Union addresses, like State of the Onion by Perl Developer Larry Wall: https://www.perl.com/pub/2006/09/21/onion.html/

Stateless applications, or even machines, may involve some amount of storage, even if it is not local. The purpose of stateless systems may have diverged with increasing options/capabilities, but its adoption in embedded systems can still have a lot of utility.

https://www.redhat.com/en/topics/cloud-native-apps/stateful-vs-stateless

A stateless application may comprise only one part of a lightweight system, whereas the rest of the kernel and OS might have stateful applications.

What about Stateless OSes?

Depending on the need, such as a LiveCD/USB, a stateless OS isn't going to save info on ROM, but it can serve a useful purpose such as on PuppyLinux, which boots into RAM and allows a persistant storage option. One theory is that developing a new, lightweight system might be easier to select off-the-shelf stateless applications/modules, and interfaces, then integrate them into a single OS that limits where storage must take place.

Rather than starting from scratch, like Gentoo (which itself isn't technically from scratch), building an OS with predefined and pretested benchmarked applications can produce a list of memory requirements, and then the applications can be loaded as separate, single application OSes. This might allow bypassing higher memory needs, at the expense of a "truly" userspace OS.

Stateful Userspace, just not all at once

"The sum of the parts is less than the whole" can alternately be written as "The whole is greater than the sum of the parts." Unless multitasking and time is of essence. The tradeoff of serial applications (RISC analogy and CISC comparisons are somewhat congruent) is at the expense of time and processing needs. 

Deliberately limiting IPC bandwith/memory cache and clockrate is only to meet energy constraints, not to artificially limit processing for useless reasons. Not use less, although that sounds like a joke. Get it? While there are certainly efficiency cases where clock rate improves throughput, there are many edge/niche cases where that may not apply.

The purpose of solar femtoTX motherboard and Solar Kernel is to explore those edge cases.

Another Four Core A53... in 2025?

Just 2 months ago, Qualcomm, one of the wealthiest chipmakers in the world, just behind Apple, Nvidia, and Intel (historically), with a market capitalization of $188 Billion, decided to release yet another Quad Core Single Board Computer, to win perhaps a 10-15% share of the Single Board Computer Market.


My guess is that someone in the product development meeting at Qualcomm had this idea:

Developer Jerry: "Hey, let's take on Raspberry Pi!"

Manager Tom: That's a great idea! We've got the cash! SEO assistant, let's get on the first page of Google Search results.

Developer Berry (SEO Whiz): Sure thing! On it.

Developer Jerry: We'll have the Raspberry Pi cornered in time for our 2nd quarterly results!

What I think is needed

More 16MB-128MB SoCs with Display Interfaces & GUIS and boring bootloaders - Towboot, Coreboot (for 386 and 486, etc) or kexecboot. Bootloaders that are standardized and don't require a highly proprietary or convoluted boot processes across boards, especially using the same architecture.


Memory in Pixel display controllers (present on the Ambiq Micro Apollo 510): https://contentportal.ambiq.com/documents/20123/387733/Apollo-SoC-Selector-Guide.pdf


SAM9X60 https://ww1.microchip.com/downloads/aemDocuments/documents/MPU32/ProductDocuments/DataSheets/SAM9X60-SIP-Data-Sheet-DS60001580.pdf



Why 16-128MB? Because the era of Solar is upon us.


Today you can solar power 4MB without much of a sweat. 5 years ago you could solar power around 384KB or RAM. The Apollo 3 was released in 2020. The Apollo 510 in 2025. I'm referring to portable solar panels that can fit inside a pocket, or maybe a briefcase, not a foldout panel that is as large as a newspaper. The purpose of portable solar mobile devices is just that, as most commuters aren't setting up a camping spot in the middle of rush hour on 5th Avenue.

That's only when paired with a lightweight processor no larger than a Pentium. At 32nm or less, and at 60MHz or less. That was in 2011, but Intel never released it and that didn't include RAM. The Quark was released and even partnered with the Arduino to create the Galileo Board. But very little RAM, and it was a microcontroller for all intents and purposes (Windows IoT, not 10, or 98). Has anyone soldered 4MB low power MRAM to a standalone chip like the D2000 with 0.025W (25mW) power consumption and installed Windows 3.1? Maybe. But it was never sold separately like a loose diamond (because it's diamond, silly!). Intel knows that, but just won't admit it. Available to Intel partners for development only, and today Intel Foundry advertises its services but the Quark is not on the menu (I've tried to reach out to them multiple times but never got a response). 
 
(Edit: 1/7/26: A correction was made to the X1000- the lowest power Lakemont Quarks were actually the "D" series Silver Butte & Mint Valley D2000, along with the Atlas Peak SE C1000 (Curie), as the Clanton based X1000 used 2.5W, which is still relatively low, but not as low as the D-series, which resembled the Claremont. The D2000's were sold (and still are, by third parties from the available remaining stock), except for the D1000. Yet so much emphasis on the Edison and Galileo boards was on underselling them as "microcontrollers" and not computers that could once display much more graphically rich user interfaces. Almost in the sense of "Use this 586 to blink LEDs!" instead of "You can run Netscape Navigator!" Or maybe that was their challenge?

By comparison, a Cortex M4 uses around the same number or slight more than and ARM1 processor (25,000 transistors).


The 80386 had 275,000. The 486 had 1.2 million. The Pentium 3.3m. When RAM is 90% of your SBC's energy consumption, the motivation to create a low RAM board (w/ ultra low voltage and power - 0.6V-0.8V) increases.

Because then you don't need a USB port in your bill of materials to recharge/power it (unless you want to).

Millions of computer users worldwide could type on a solar powered laptop, with a solar powered keyboard by ONiO, and a board that uses a 10mW of power. Set the ceiling, and the applications will follow.

A microcontroller such as the Arduino or a Single Board computer requires access to either another PC/laptop, or a power supply. One can plug in a microcontroller to a USB or a Serial TTL interface. Boards should be standalone and require just a lightweight (low power) monitor and keyboard to run.  

Remember when these could run on their own? (Some had a backup battery, but still)




Low Power Memory makers typically sell just a few MB, at most: . https://www.sure-core.com/memory-products/ (SRAM), https://www.crossbar-inc.com/,  https://www.weebit-nano.com/ (ReRAM) I am not really sure which memory suppliers are developing for the high end (many MB), but I imagine if it's really leading edge, their partners aren't publically advertising it, esp if they are using it internally to confer or research some further competitive advantage)

When I was a kid, my uncle took me strawberry picking. The farm charged by the basket. Whatever you could fit in the basket was yours. Software development should follow that principle.