Smoku went ahead and put his experience to it and made some wonderful things. Among others he backported the n900 SGX kernel glue to our beloved (not) 2.6.27.10 franken-kernel. Long story short: Here’s handset user experience running on an A5IT!
He’s collecting his notes on this project here: http://codex.xiaoka.com/wiki/meego:archos
A5IT with handset UX
Happy hack-mas from the openAOS team!
Tags: demo, kernel, MeeGo, sgx, video
[...] to gen6 hardware wouldn’t have been possible without the reference work by Kevin Boone, Smoku’s MeeGo efforts benefited from our groundwork, [...]
its not worcking in my archos i just get a black screen
can any one help me please
Any hope of getting just the SGX stuff, or do we have to try to extract it from the image?
What are you after? Outside the MeeGo scope there is regular SGX from TI which can be compiled against our kernel with a few tweaks.
Getting SGX running under Angstrom. I’ve had issues getting the SGX stuff built in OE, so I thought taking working stuff would perhaps be a better route.
is it possible to play n64 emulateur on archos
There is only core images, not handset.
meego-core-armv7l-a5it-1.1.80.20101223.2338.img does not work because there is not display driver. To launch xserver connect via SSH and copy 20-omapfb.conf to /etc/X11/xorg.conf.d and omapfb_drv.so to /usr/lib/xorg/modules/drivers from meego-core-armv7l-a5it-1.1.80.20101222.2037.img
I tried this but with no luck – it wasn’t even shown on my Boot Menu (nothing changed). I decompressed the .lzma file downloaded then renamed the resulted file to “meego.img” and transfered it to my Archos’ root folder. Finally, I edited the “menu.lst”, so it looks like this:
Archos|ANDROID|/androidroot.cramfs.secure|/init|0
Froyo|/dev/sda1|/openaos-froyo-alpha4_20101115.img|/init|0
openAOS_Angstrom|/dev/sda1|/rootfs.img|/sbin/init|1
MeeGo 1.1.80|/dev/sda1|/meego.img|/sbin/init|1
Still, I can’t see it in my Boot Menu. Have I done something wrong during the process?
That should have worked. Try adding an empty line after the MeeGo entry. Sometimes this helps.
Also currently the image doesn’t boot for me. Need to have a look why later. It might need some kernel changes.
Should it be matter for the USB connection to be an MTP mode? or MSC?
Is the music player on this OS better than the stock Archos’ one?
I doubt so. a) the original player is very good b) MeeGo in its out of the box state doesn’t understand non-free codecs at all. This basically means ogg/vorbis and theora only.
No MP3 either? I guess it’s too much to ask for Gapless and\or crossfade playback…
MeeGo in its pure form is designed to avoid any licensing and patent problems. Hardware vendors may decide to include those of course. Community adaptations usually are hesitant of doing so as nobody wants to get their pants sued off due to an free time project. Though workarounds usually emerge alongside.
[...] This post was mentioned on Twitter by Michaël HUBERT, Archos Info. Archos Info said: Video of A5IT running handset UX of that upstream-linux-distribution: Video of Handset UX running on Archos 5 IT… http://bit.ly/eusaET [...]
Hmm, it doesn’t work for me
with |1 at the end of line in menu.lst (as written in README file) the screen just stays dark for more than 10 minutes.
with |0 screen goes green with ‘AOS open’ at the bottom
Yes I think it will need some fbset added to an init script as Smoku changed some kernel command line option instead.
Nice! Waiting for the link