These things happen. :) The "message history" at the bottom of that page has exactly one message, from 2018, announcing the migration. (That's also the only message in the rss feed link.) I thought th

The "Join the developer mailing list" link on https://www.celinuxforum.org is 404. Rob

... I usually youtube-dl an archive copy, but haven't got it on any current machine and haven't hunted through the old disk pile. Rob

FYI we recently re-uploaded the j-core talk that got caught up in The Great Purge: https://www.youtube.com/watch?v=GHORpXNRJiE I don't know if anybody downloaded my 2015 toybox talk, I can't find that

Did you record video of this one? I can't find links to them on the wiki page... Rob

The j-core stuff is in english. (Thrill to my attempt to stay upright and coherent despite food poisoning! Then Geoff gave a nice VHDL tutorial.) Rob

Want I want to do is: 1) Download an archive of device tree files describing a bunch of boards. (Both dts and corresponding dtb files, with maybe a .txt telling me about the board and the -append line

<Frank.Rowand@...> wrote: Is there a device tree porting HOWTO anywhere? If I have a board that's using explicit C initialization, and I want to convert it over to device tree, step by step

You're aware that the upstream kernel guys see the lack of binary compatability as a feature, not a bug (punishing binary-only modules), so that not only will this feature probably never go upstream,

My talk was on this subject too: http://www.youtube.com/watch?v=SGmtP5Lg_t0 (What I actually talked about wasn't "what is toybox" but "_why_ is toybox". Not the implementation details but the motivati

I still can't find a link from the Linux Foundation's CELF website to where I should submit my talk outline. I emailed it to you, but it's still not on http://events.linuxfoundation.org/events/embedde

Surely there's a way to genericize this. Even on processors that don't _come_ without an mmu, in ultra-low-memory environments doing without page tables can still be a win sometimes... Considering tha

Architectural support in the kernel, or in the emulator? Not having nommu support for i386 is one thing, but why can I boot a nommu arm under qemu? (What's involved in nommu archiectural support? Runn

That's very interesting, but I'm unlikely to have time to folow up in the next few weeks. (I'm already investigating the full m68k support qemu is growing in the q800 branch Laurent Vivier's doing on

Um, they're explicitly replacing desktop computes. Mainframe -> minicomputer -> microcomputer -> smartphone. This is the third regeneration of the computer industry (we're up to Tom Baker). Nobody nee

I'm impressed. Rob

Probably was. Query: is there any way to set up a nommu system with: A) stock vanilla upstream packages (kernel, uClibc, busybox) B) running under qemu I've had a todo item to add a nommu target to Ab

You're aware that u-boot parsed this before linux did, right? I can write my own flattened device tree parser if necessary. It's a tree in an array. And having a general posix API invites code that is

Linux running in 1M of _ROM_ sure. Using the above for ram? Not a chance. Your average shell is going to use more than 64k of _stack_. You're ignoring page and dentry cache, which Linux isn't designed

Different processors have different machine code, some of which is more space-efficient than others. My Aboriginal Linux project cross compiles the same ~7 packages to a dozen different targets (with