Assuming that iRex will release the SDK soon (and comply to GPL rules), and that we'll be able to write our own tools or even program our own OS, what do you guys think should we work on first?

I was thinking we could for instance port other open-source readers to iLiad. <<< thinking of Plucker here!

I'm all for the implementation of a Java VM.

what about porting "evince"?
since some people asked for a djvu-Viewer.

http://gnome.org/projects/evince/

Please, for us that are not the super hackers - functional web access!

I know of an developer environment that can help in creating a special iLiad linux distribution. This environment is called T2 ( http://www.t2-project.org/ ).

T2 already support the Arm architecture. So it will only be a matter of creating a so called iLiad target. I only wonder how a created distro can be installed on the device.

The best thing would be if the iLiad can boot from CF. This would make playing around with it a lot more "brick safe".

my 2 cents :)

Please, for us that are not the super hackers - functional web access!
i dont think that is a big problem. As i have understand it, the only problem is to keep the network interface opened. And a addressbar in the browser.

I know of an developer environment that can help in creating a special iLiad linux distribution. This environment is called T2 ( http://www.t2-project.org/ ).

T2 already support the Arm architecture. So it will only be a matter of creating a so called iLiad target. I only wonder how a created distro can be installed on the device. ...

um, tell it to a non-programmer (me), whats the difference to OpenEmbedded? Isn't OE also a build environment, or is it about additional functions in T2?

And about installing, i think or better hope iRex uses something similar to Routers or other embedded devices where you can flash through a tftp-server in the bootloader or over a serial interface.

Originally Posted by b_k
um, tell it to a non-programmer (me), whats the difference to OpenEmbedded? Isn't OE also a build environment, or is it about additional functions in T2?

I am a commiter to T2 and don't know how OpenEmbedded works. The T2 architect claims OpenEmbedded is a pain in the ass to use. (Sorry, these are not my words and I don't intend to start a flame war)

Originally Posted by b_k
And about installing, i think or better hope iRex uses something...

This is a great way of updating a distro to newer releases, but what about trying out new things. One mistake and your device is bricked. Using bootable CF will not brick your device when trying out new things. If new things fail, just remove the CF and reset it and you have the working old thing.

...
This is a great way of updating a distro to newer releases, but what about trying out new things. One mistake and your device is bricked. Using bootable CF will not brick your device when trying out new things. If new things fail, just remove the CF and reset it and you have the working old thing.
i dont think so. if the flasher is is in the bootloader, and the flash process won't touch it, you could always reflash.
(at least that's how the SIMPads loader works, but it seems very common most home routers do it the same way. You can update the OS and the loader separately, but i had always some fear when i was flashing the loader. Cause if you kill the loader, then the device is indeed bricked.)

But in case you would have to flash everything at once, including the loader, your option with CF-booting is for sure the better and less headaching way.