On Sun, 18 Jul 2010 08:45:37 +0300
Risto H. Kurppa ri...@kurppa.fi wrote:
Hi there!
The latest SHR-testing images are available at
http://build.shr-project.org/tests/shr-testing/images/om-gta02/
Martin Jansa / JaMa prepared them in the end of May but it wasn't
announced anywhere - so
On Sun, Jul 18, 2010 at 09:14:16AM +0200, omcomali@porcupinefactory.org
wrote:
On Sun, 18 Jul 2010 08:45:37 +0300
Risto H. Kurppa ri...@kurppa.fi wrote:
Hi there!
The latest SHR-testing images are available at
http://build.shr-project.org/tests/shr-testing/images/om-gta02/
O Sábado, 17 de Xullo de 2010 22:42:19 Gennady Kupava escribiu:
Hi, list.
Here is my next rant to freerunner slowness :)
Being a FR user since the beginning, it's really amazing to see how it
improved since 2007.2 and 2008.x/2009.x distros, in usability, prettiness and
speed (specially due
2010/7/17 Gennady Kupava g...@bsdmn.com:
Here is my next rant to freerunner slowness :)
A great way to rant :)
The glamo timing fix seems to work great here so far. Regarding the
older thread, I finally tested also it with the 500/83 CPU/memclock
setting (533/88 hanged during boot when most of
On Sun, 18 Jul 2010 00:42:19 +0400
Gennady Kupava g...@bsdmn.com (GK) wrote:
1.6. --- How to test/use it
I used this settings by default for several days with qtmokoV24 and
with debian on usd.
I prepared u-boot to set new timings by default:
O Sábado, 17 de Xullo de 2010 22:42:19 Gennady Kupava escribiu:
Hi, list.
Here is my next rant to freerunner slowness :)
You should get for new timings:
Old value:
addr[4808]=0x80 0x13 0x00 0x00
Expecting some reports from users, did it work for you flawlessly?
r...@om-gta02
Hi list.
I decided to do and share some additional tests related to glamo bus
speed.
This tests related to change found by Thomas White early this year to
GLAMO_REG_LCD_A_BASE2 which change some kind of fifo.
Goal of this test is to find out how this change influence glamo speed
and how
O Domingo, 18 de Xullo de 2010 18:17:07 David Garabana Barro escribiu:
O Sábado, 17 de Xullo de 2010 22:42:19 Gennady Kupava escribiu:
I'm currently using shr-u, will report any problem...
I had a WSOD shutting down, but not yet during normal use.
As with new kernel WSOD are back again (at
O Domingo, 18 de Xullo de 2010 18:52:39 Gennady Kupava escribiu:
Hi list.
First i did tests with different FIFO settings and 2-4-2 timings, and go
absolutely same results in each tests. So here is only test results for
FIFO = 0 or FIFO = 1 (0x4000):
FIFO 0 1
2-4-2, 10Mb/s
David,
According to your previous mail (Glamo slowness question...) it seems
it is 1, am I right?
Sure, by default we have 4-4-4 fifo 1 since beginning of 2010, this is
just testing which may be interesting to whoose who wonder about FIFO
depths.
Gennady.
Wow, you're doing an awesome job here!! I've tried it on my QtMoko V24
running from NAND and it works great, the interface is noticeably faster and
so is a more intensive program like Navit. Everything seems to work as it
should, suspending and resuming is fine.
As Timo Jyrinki already
O Sábado, 17 de Xullo de 2010 22:42:19 Gennady Kupava escribiu:
Hi, list.
Expecting some reports from users, did it work for you flawlessly?
One small problem I found
When you get a WSOD (rotating screen), if you just reboot, you obtain a WSOD
on every following reboot
You MUST halt device
When you get a WSOD (rotating screen)
Fixes exist to fix this (for both xrandr rotation, resolution switch and
screen blanking), this not related to timings.
When you get a WSOD (rotating screen), if you just reboot, you obtain a
WSOD on every following reboot. You MUST halt device for getting
Could somebody please update the:
NOR-flash booter
u-boot
- that also works with a bootkernel bigger that 2MB?
Instead of this:
# From:
http://wiki.openmoko.org/wiki/Kernel#.22Verifying_Checksum_..._Bad_Data_CRC.22_with_U-boot
setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\;
One more thing, if cpu load look like too high for some exprienced
mplayer users, this may be caused by my mplayer version - it is built
with -fno-omit-frame-pointer and with run in parallel with _callgraph_
profiling, which seem adds some additional cpu load.
For pure timings, here is cpu load
15 matches
Mail list logo