Linux on an 8-bit micro? (2012)
dmitry.gr
dmitry.gr
Also Fuzix, which can run a Unix-like on a variety of tiny, ancient processors like the Z80 and 6809; I've ported it to the MSP430, a modern micontroller, and I also have a half-finished port to the Raspberry Pi that I must get round to fixing one day (hilariously, the Pi has more RAM than Fuzix can handle)...
https://github.com/EtchedPixels/FUZIX
Both of those run natively, of course.
https://sourceforge.net/projects/picix/
Hey at least it doesn't take 2 hours to boot :)
Personally I like the idea behind RetroBSD [1] - port of 2.11BSD Unix intended for microcontrollers.
I was thinking if a system like this powered by solar panel would be a good idea for poor countries. The idea is to have computing of the past in sustainable form available for poor. The main problem is probably to have a cheap and low energy display. Maybe epaper made in bulk would be enough? But probably such a computer can only be cheap if made in bulk. Maybe it could be cheaper than RaspberryPi? The question that remains is what about networking? Maybe they could function in similar fashion to BBS, but using shortwave radio?
The one thing people in poor countries do not want is special weird incompatible systems designed for the poor. They want a solution which is adequately close to the western ones, just cheaper. Look at cellphones: http://qz.com/451844/africas-smartphone-market-is-on-the-ris...
However I think OLPC is different from what I have in mind. OLPC targeted children with OS designed for children. I am thinking about something more like RaspberryPi with integrated power and display systems, but with external keyboard. Also I think about it to be extremely cheap. $100 laptop is already done by Chromebooks, but it is not cheap enough. It would have to be around $25 or less. It should expose GPIOs like RaspberryPi so it could be used in more settings. It would be black and white and mostly text only. Basically my pipe dream. Maybe I would just like to go back in time sometimes and I am just projecting?
It is just a loose idea, but outside of people's preferences economics of scale are certainly supporting smartphones.
For something like what you've described, the cost is driven by casework, screens, touchscreen components and batteries. Not the processing electronics. It sounds like something halfway between a Kindle with a keyboard and one of the cheap Windows tablets, now below $100. (http://www.dx.com/p/onda-8-v820w-quad-core-dual-os-tablet-pc...)
I reckon it's probably the SIMM soldered to the breadboard.
The reason why...
"uARM is certainly no speed demon. It takes about 2 hours to boot to bash prompt ("init=/bin/bash" kernel command line). Then 4 more hours to boot up the entire Ubuntu ("exec init" and then login)."
It is so slow. Btw if you ever ask about system compiles of Elm on RaspberryPi which requires Haskell, you'll get similar responses.
> That’s why Chrome will start the process of sunsetting SHA-1 (as used in certificate signatures for HTTPS) with Chrome 39 in November. HTTPS sites whose certificate chains use SHA-1 and are valid past 1 January 2017 will no longer appear to be fully trustworthy in Chrome’s user interface.
I voiced the same complaint when somebody claimed to “run” Windows 3 on an Apple watch (IIRC), which also was achieved by running a standard PC-hardware emulator, and running Windows 3 on that.
These are somewhat interesting accomplishments, but the click-bait factor is high.
Come on. There is a 8-bit microcontroller running a linux system, the rest is implementation details and semantics.
These are not the big issues in porting the Linux kernel to an AVR. The major problem is that AVR is Harvard architecture and there's probably tons of assumptions in the kernel that code and data resides in the same memory space.
The crux of both the article and the accomplishment is writing an 32-bits ARM emulator that works on an 8-bit machine.
Definitely not child's play, and a valid route to run Linux on 8-bit.
Instead, they used the headline and article content to heavily imply to actually have ported Linux to an 8-bit processor. It’s not until into about half the article that they reveal the emulation bit. Therefore, click bait, pure and simple.
Its very easy to use something limited, say a HP48 in RPN mode and some arrays as "memory" and variables as registers to implement a couple opcodes of say a 68hc11. I did that around '93 or so when the 'hc11 was contemporary (its ancient history now, but it was kind of a 6809-like microcontroller with pretty good specs for the era)
On the other hand its hard to get a complete emulator working of everything, or at least close enough to everything to boot a major software project on top of it.
Sort of like implement a system/360 emulator that only does opcode ADD, well, ok cool, but when you can boot MVS/360 thats a whole nother level of wow.
If you don't have time to read HN, and need TL:DRs then you should question why you are here in the first place.
--
Vote down if you like, I joined HN to get away from inane commentary and TL:DR nonsense that's so prevalent on other sites.
Next, we'll have people just copy-pasting the entire article body as a comment ... :(
You read the links? I'm just here for the commenting. If the comments imply the article is good enough I'll read it.
(This effect used to be very strong on the Guardian's commentisfree site, where the top comments often contained valuable correction/context to the tritness of the article)
> Next, we'll have people just copy-pasting the entire article body as a comment
I've seen that done a few times; it's useful if it's paywalled/adwalled/unusuable-crashy-javascript-walled.
There is no joy in being fooled by a clickbaity title. Also, HN is not a novel book, therefore I do not feel spoiled. I always silently thank people that write tl;dr. They try to save my time.
In this case I did it because the title made me wonder if this was the article I read years ago about implementing an ARM emulator for AVR to boot linux. I clicked through, confirmed it was, and that it was a 2012 article. I figured I'd leave the TL;DR as a shortcut for others to confirm they've already read it, not as a replacement of the article for those that haven't.