So, after all of this hard work, what can you do on Linux? 

Pretty much anything you can do normally on a desktop Linux distro.

You use 80% of the available RAM so you can do what with it? 

You'd be surprised to know that Linux only uses about 8MB of RAM on my development build (potentially much lower without a ramdisk) which works out to be about 13% of the total available RAM on CX models (about 25% on the classic models). Nothing close to your estimate of 80%.

Of course, by today's desktop/laptop/mobile/tablet standards, the remaining 56MB wouldn't be enough to run anything. But in this case, we're talking about an embedded device running low overhead applications. In the embedded world of computing, 56MB is actually a huge amount of free memory with lots of potential. For example, I have in the past, ran a X server with Xterm, Xclock, Xeyes, Mathomatic open and plot a graph with GNUplot all at the same time with still plenty of RAM to spare.

Run small programs on it?

Sure, if that's what you want

Don't forget that we're aren't a corporation or business trying to 'sell' Nspire Linux. I ported Linux to the Nspire simply because I could and it's something I can enjoy working on. I didn't and still don't think about how this could be useful at all when I develop for it. Plus, I learned a ton about kernel development on the way.

And come on, when was there ever a time when Linux being ported to a new platform wasn't cool?

oh OK, still not very appealing to me until you make a video showing all of the cool stuff you can do on it. 

It's totally cool if you don't find it appealing. I understand that not everyone sees things that same way as some of us do.

As developers, we generally engage more with the people who are more interested in our work but, for the heck of it, here's a few videos from the past that shows some interesting things with Linux

CONFIG_LOCALVETSION, too?

Oh, almost forgot that one. Yep, committed!

If nspire os is gone, where does rebooting get it from?

Basically, on reset, control is handed back to the bootloader which loads the nspire OS from flash again.

@Vogtinator, also, flash write support is tested to be broken - lots of 'I/O error' and my calculator didn't brick.

reboot

Quote

Just emailed you something that may be of interest. Linux doesn't run on nspire_emu right now though

I read it, but seems to be not very useful :-(

Quote

I also added MTD partitions into the mix so you can dump your boot2 and diags via Linux if you really wanted to

Could you implement one for the filesystem, too?
I'd experiment a bit with flashfx support. (Which seems to be harder than reliance)

Quote

The worst that can happen is that I have to reinstall the OS

Actually (but not very likely) you could damage boot2 if you write to the wrong bytes.

You'll find that the filesystem partition already exists. I assumed the filesystem comes after diags (hence the question mark in the mtd partition list).

As to writing to boot2 accidentally, that should be mitigated because of partitioning. Linux won't let you write to something outside it's partition range.

Edit: Heh

@Vogtinator, we could use this to write a read-only filesystem driver for FlashFX and Reliance? http://ourl.ca/99835

I don't want to lose my loved boot2
Does is work in nspire emu?
You could easily compare the image with your bytes read.

Weird. It's the same but the bytes are reversed. :S

Never mind. Wrong parameters to hexdump.

Now, how should I test write support without killing it?

NAND driver is coming along slowly. I got it to detect the chip properly at the very least.