@Vogtinator: Don't bother with the LED. There's some weird protection that TI put on that noone could work out.
Good work on the GPIO and power management interfaces though

In other news, Clickpad support is officially working! Lionel and I are also working to get nightly builds on wheels

Quote

Good work on the GPIO and power management interfaces though

I don't know whether it actually works..
Turning off by disabling access to all peripherals is likely to be a bug or it's not off at all, but we can't see it's actually on.
Also I don't know whether GPIOs do work, I can't test it, but some values make sense.
But what could be the cause for the adc always returning 0?

Does it give you the same thing if you try to do the reads as an Ndless program? I haven't got access to my calculators at the moment.

Is there already a program for ndless to test it or I do I have to do it wrong again?

Nope, but it shouldn't be too hard to whip one up quickly

What if I make the same mistakes again and it's returning the wrong values?

I meant for the ADC. If you can get an ndless program to read the correct values, then you can get linux to read the same.

Really great !

X and directfb are working!
Now we're one step closer to minecraft
Note: I can't login on SSH because of an german umlaut in my password and I haven't changed the keyboard-layout yet.
Note2: I don't know where that segfault came from, maybe too much ctrl-c? ;-)

[/youtube]

I don't understand how you can launch this graphical program, can you help me to do so please ?

There is one thing which I don't understand:
How can the OS lock the LED when it is overwritten by linucx in the RAM?
Or how can the OS restart the calc when reset button is pressed? (In earlier OS all user data was deleted when pressing reset button on the back.)
Or why can nClock run in background with linucx? I think it does because after the 'reboot' command in linucx nClock has the right time on startup, rebooting with reset button messes up nClock and it shows the wrong time.

Are there two different RAMs?

And if you write to these addresses in the RAM to do something special (watchdog, LED, power management), wouldn't the OS or linucx (or whatever runs) be overwritten partially?

TI's OS does not lock the LED when it's overwritten by Linux; it's just that Linux doesn't activate it.

Partially wrong: We don't know how the OS can unlock the LED. Whether the LED registers are locked is saved somewhere in hardware.

In my adc test prog I had to do the following:
*((uint32_t*)0x900B0018) = 0;
*((uint32_t*)0x900B0020) = 0;What is this register "0x900B0020"? In nspire_emu *(0x900B0020) & 0x10 is tested, if it returns false, the adc value is 0x3ff=1023.

You are not using the right rootfs image.