Dingoo A320 forum

It would be interesting to see the memory usage with this stuff running, in general I would think X would be pretty useless since its just wasting resources in the background when that 29mb of memory is desperately needed, especially once you start getting into larger games 29mb is definitely not alot.

I agree with you about X:
for games, and for video performance in general, this is probably not a good idea.

X could be used only to execute a launcher, then quit to free some memory.

And remember that old PDAs like zaurus, that were linux-powered, had less ram than that, and were able to run a complete environment and suite of applications (gpe, opie, ...).

In other words, for some tasks, 29mo is enough.
And think about developer tools: gdb, strace and so on.
yes you can cross compile it, but it is more difficult.

I'll keep you updated and post some files soon.

That I would agree with, X could be useful for a frontend. There are many other things that are linux powered out there that do the same without X though. Some of the other stuff has already been running though, I had mplayer and gdb in one of the later rootfs releases, of course mplayer wasnt that great, I started work on using the mplayer released by ingenic and recompiling it with the uclibc toolchain since the one released by ingenic has alot of hacks for the ingenic processors. So you may want to look at using that version for mplayer. I got pretty far but ran into issues since they use a script to do conversion of assembly and it fails on one of the mplayer files.

ezelkow, could you please give me some pointers about this mplayer?
thanks

Here is the temporary status of the binaries I've tried:
Unless specified, they launch normally
That do not mean that they are usable as is...

Xfbdev
bash
dropbear (getpwd problem)
dropbearkey
elinks
epdfview (image loader missing, easily fixable)
fbgrab
fbi (font problem)
ghostscript (some files missing)
gkrellm (image loader missing, easily fixable)
htop
key2mouse
links
nc
rxvt-xterm
strace
twm
vncviewer
xev
xeyes
xosview (font problem)
xpdf.bin
dillo web browser (works with HOME=/tmp as home must be writable)
mplayer (seems decent with: -vo fbdev -nosound
xmms

#on the PC, you can control the mouse with (if plugged with USB of course ):
#x2x -to 10.1.0.2:0 -east


I'll post the files when I'm home.

I got it from the ingenic linux package, its in the apps directory under software. I noticed the same when running the previous ones I built, I figured it was an issue with the shotty OSS driver that exists and was hoping the ingenic patched version may have ways around this. The one from ingenic contains a build script that builds the necessary libraries and starts the build process so you would have to hack up this script to use your toolchain setup or attempt to build it on your own.

The problem I ran into is that the ingenic toolchain has a script, mxu_as, that does their assembly conversions. Even when using this plus the jz_mxu.h header file it seemed to convert almost all of the assembly files except for one that for some reason mxu_as would not read.

The files are here:
http://cyberic.free.fr/Dingoo/big_pack.zip

Unzip it onto you SD.

Beware, it will erase 'main' in sbin.


Please note that this is a WIP.

The 'demo' should launch a Xserver and some apps, then a video with mplayer.

You can still telnet to the dingoo.

Of course you have to add the rootfs and the correct kernel for your LCD model.

Briefly, the sbin/main launches 'boot.sh' which mounts every '.doo' package in the pkg dir. They are romfs images, containing bin/ and lib/

Then go.sh is executed. It launches the previously mounted apps with /boot/local/sbin/launch.sh <application> <arguments>

Nice demo! (just tried in train...)

So what next?
BTW, how can i create a .goo romfs? Are them just raw .img files?
Now can i try to randomly browse debian repo looking for working apps?

To create a .doo you have to have to do:
mkdir pkg
mkdir pkg/bin
mkdir pkg/lib
copy the binaries to pkg/bin, and the needed libs to pkg/lib (use ldd to find the needed deps)
then genromfs -d pkg -f pkg.doo

That's all, then you put the .doo in the pkg dir on the dingoo, (max 7 .doo files), it will be mounted automatically

Then on the dingoo you have to use launch.sh <program> to launch your binary.

I hope it was clear, I will soon release a script that does all this.


On debian, you can get packages for the mipsel architecture, they should run yes.

Keep me updated if you get some interesting app working.

I read here

post6218.html#p6218

that you've been able to set up a qemu vm. Do you mean you fully emulate hw, or are you in "user space" mode?
How can you enable a framebuffer device (not mentioned in qemu docs)?

Maybe you could share these information...
A VM would be VERY COOL both for developers to test their apps and for geeks who wants get crazy trying debian binaries, don't you think?