search for: mx21

Erik de Castro Lopo wrote: >> Currently, compression settings are as follows >> >> -6, -l 8 -b 4096 -m -r 6-A tukey(0.5) >> -7, -l 8 -b 4096 -m -e -r 6-A tukey(0.5) >> -8, -l 12 -b 4096 -m -e -r 6-A tukey(0.5) >> >> I suggest the following, in case my previous patch is accepted >> >> -6, -l 8 -b 4096 -m -r 6 -A tukey(0.5);partial_tukey(2)

...o > harm done with changing this too. > > Any thoughts? From <http://www.rockbox.org/wiki/CodecPerformanceComparison> it seems that the decoding of -8 is about 6% slower than -5. Sometimes the difference is bigger but doesn't exceed 10%. The only exception is "Freescale i.MX21 (454MHz ARM926EJ?-S, Fuze+)": 43x vs 35x realtime. But the decoding time is so small (4 sec vs 5 sec) that it can be some measurement error.

...s anybody have any information about ongoing projects towards the port of XEN on ARM architectures? We aim at starting a port to the XScale/PXA270 architecture in the coming months and I would like to know if we could benefit from current results; I know that Samsung performed some work along the i.MX21 architecture but so far I wasn''t able to get any inputs from them, even no answer to our mails. Wouldn''t it make sense to initiate a XEN-arm-devel mailing list as there is for ppc in order to stimulate and to have a better transparence about ongoing work in this direction? Than...

...a short notice to inform that a new mailing list (XEN-ARM) has recently been created in order to gather and to stimulate discussions around the port of XEN on ARM architectures. We''re currently working on the port of XEN on a PXA270 based board, but we are interested in the port to the i.MX21 Freescale processor. Most activities around the port on our side will start from the beginning of September although we already started the migration. We will report the state of our work soon. Look forward to reading news there! Cheers Daniel _______________________________________________ X...