I still have my Zauruses, but they don't get used any more (batteries are pretty knackered now). I moved to the Nokia internet tablets, which are pretty cool, just waiting for the next gen tablet to come out with an omap3430 or similar. I'm working on a variety of things, but mainly DSP programming (SBC encoder, Vorbis decoder, MP3 decoder).

Cheers all

Simon

Da_Blitz informed me by PM of the "hack", but was not sure whether to delete the posts. I emailed Offroadgeek and I also thought that the "report a post" link goes to all Admins.

Therefore, where are the admins? I have some admin rights in certain fora, but not enough to look at the details of the posts in question.

Anyway I have locked the topic for the time being.


Si

P.S. Bloody Firefox, will not let me type an apostrophe, nor use the cursor keys, nor copy & cut & paste. Need to restart it me thinks, grrrr

Ah, I missed the GUI bit.

The 'easy' way to get around this is to use ipkg from the command line.



Yep, these issues (with the gpe and opie versions) have been ongoing for a long time. The problem is that no-one has yet decided to fix/write a new GUI package manager. If there's anyone out there who fancies the task, then I'm sure you'll get a lot of kudos.


Si

Post the full output...

Si

You could always choose a different xserver, e.g. xorg rather than kdrive.

This is as easy as changing the xserver preferred_provider line in one of the .conf files and re-issuing the bitbake gpe-image command.

Though this sounds like it might be partly window manager related too. Again, you can change this by altering a conf file and letting it build the new requirements.

I also understand that there's acceleration for the PXA270 machines' graphics now which may improve the speed issues you were having.



Did you add it to the bugtracker?


Si

There are a fair few steps to set it up, but if you follow the instructions it will just work. The biggest issue I imagine you'll have is filling out your local.conf with the correct paths, and the correct distribution, etc. (not very hard

Learning to write a .bb file is a bit of extra work, but there are lots of examples, and we'll will be happy to talk you through it.


Si

Yes, on a normal desktop Linux machine.

It's a build tool that builds various things, including a cross-toolchain which it then uses to build the apps you want.


Si

You should start on http://openembedded.org with the GettingStarted page.

This will build the cross toolchain (etc.) for you, then you just need to write the .bb file for the game.


Simon

You sure it's not compiled in?

Take a look in (iirc) /sys/modules/


Si

The other option is that you could be talked through the process on irc...


Si

There will be some as hrw is working on the oz 3.5.5 release.

See the oz.org webpage,


Si

It should download and extract them somewhere under /tmp, which is mounted as a tmpfs (in RAM).

Try rebooting, you may find that the jffs2 garbage collector just hasn't got round to reclaiming the (flash) space used by firefox before you uninstalled it.


Si

Don't use halt, use suspend (or apm -s).

It'll switch on faster that way


Si

Perhaps you have kernel issues, as this is what detects the keypress.

What are you running on the machine?


Si

They all come from the same OE information (afaik) so I wouldn't expect any major changes.

Try an Angstrom build (or an openzaurus-unstable).



Si

Someone needs to look at the work the pdaX people did to allow a single partition and implement this for OZ (flasher and some kernel changes iirc).


Si

Do you want to post the error message?


Si

Unstable or just hard to access - I think this is an issue with its being hosted on berlios.


Si

Is the missing memory allocated as a ram-disk in the same way the original Sharp images worked?

what does 'cat /proc/meminfo' show?

I'd expect a small amount of memory to be missing in an OZ image to mount things like /tmp, /var in a tmpfs (though I don't know whether Cacko does this), but certainly not 17Mb straight after boot (I assume that's where you are). If you've actually been doing things, and do have a tmpfs, then (on OZ at least) it's allowed to grow up to half the available memory, so you might want to check this too.


Si

I can't do that I'm afraid.

Have to wait for one of the higher powers to look


Si

Even more so in that case!



I'd test whatever it is you want to optimise - mplayer for example. On the other hand you could try some benchmarking programs (though these just test single things - floating point, integer operations, etc.).

See this thread for some results from a long time back: https://www.oesf.org/forums/index.php?showtopic=3451&hl=

and here for some Nokia binaries (not that useful of course) plus download URLs and compilation command lines: http://people.bath.ac.uk/enpsgp/benchmarks...ling_things.txt

Opie has an applet which provides some benchmarks for various things: This can be found here: http://handhelds.org/cgi-bin/cvsweb.cgi/op...ttings/sysinfo/ (benchmarkinfo*)

And those files say they were inspired by zbench, the original URL for which is gone, but some source is here: http://linuxtogo.org/~mickeyl/mirror/zbench-2.0.tar.bz2


Si

Seems fair to me, there's not much traffic there so it shouldn't get confusing.


Si

I may be very wrong about this as I've not used a Sharp-derived image for a long long time....

You might try using/modifying (it's only a script) ipkg-link as used by OpenZaurus. This allows you to install anywhere, then create symlinks as if the package were installed to /, something similar is used in PdaXrom.

Also take a look in /etc/ipkg.conf (assuming this is the same file that the Sharp-based images use to decide on the installation locations).


Si

Building with f2c always used to fail for me, eventually I had to find/build a cross toolchain with f77/g77.

With that said, I've not got round to doing anything more on it (there is/was a segfault in the f77/g77 compiler iirc).

I must have another go now that I have broadband (late starter )


Si

Serge,

I'll build your comparison benchmarks for the PXA255 (and SA1110 if it's of interest) once I've got over some minor (I hope) OE build issues.

Si