Radek Polak writes:
> SHR kernel is > 2MB and uboot can have problems loading such kernel. You
> either need to adjust uboot env or try qi which does not have this limit.
Why would u-boot have problems with > 2MB? Isn't it just that people
have configured their u-boot to only load 2MB in the co
On Tuesday 20 July 2010 14:37:49 Thomas HOCEDEZ wrote:
> I tried on SHR-u, booted on a beautiful "openmoko" logo, then nothing.
> When I tried to boot on u-boot, a single" nokernel found" message is
> shown ...
> So here's a question : Is it only for QTmoko ?
SHR kernel is > 2MB and uboot can hav
Hi, Thomas.
> I tried on SHR-u, booted on a beautiful "openmoko" logo, then nothing.
> When I tried to boot on u-boot, a single" nokernel found" message is
> shown ...
I don't know about qi provided, but you should setup u-boot properly to boot
you distribution. To not blame glamo timings,
try f
Sounds very nice !
I tried on SHR-u, booted on a beautiful "openmoko" logo, then nothing.
When I tried to boot on u-boot, a single" nokernel found" message is
shown ...
So here's a question : Is it only for QTmoko ?
___
Openmoko community mailing lis
Attached you will find my diff.
http://openmoko-public-mailinglists.1958.n2.nabble.com/file/n5316379/qi.diff
qi.diff
Ghislain
http://www.basetrend.nl BaseTrend - http://www.openmobile.nl openmobile.nl
--
View this message in context:
http://openmoko-public-mailinglists.1958.n2.nabble.com/G
On Tue, Jul 20, 2010 at 09:17, ghislain wrote:
>
> I've applied the glamo patch to the qi-bootloader I use for the QtMoko
> installer-images. You can download the qi-bootloader here [1].
> It replaces the qi.img file in the installer image so you can reflash with
> this new bootloader.
> It is, of
>I've applied the glamo patch to the qi-bootloader I use for the QtMoko
>installer-images. You can download the qi-bootloader here [1].
>It replaces the qi.img file in the installer image so you can reflash
>with this new bootloader.
>It is, of course, also possible to flash this new bootloader usi
I've applied the glamo patch to the qi-bootloader I use for the QtMoko
installer-images. You can download the qi-bootloader here [1].
It replaces the qi.img file in the installer image so you can reflash with
this new bootloader.
It is, of course, also possible to flash this new bootloader using d
On Monday, 19. July 2010 21:04:54 Petr Vanek wrote:
> >>I prepared u-boot to set new timings by default:
> >>www.bsdmn.com/openmoko/glamo/242/u-boot_glamo242.udfu
> >
> >
> >sounds great! is there a qi version setting up these parameters?
> >running system from uSD is much easier with qi...
>
> no
>>I prepared u-boot to set new timings by default:
>>www.bsdmn.com/openmoko/glamo/242/u-boot_glamo242.udfu
>
>
>sounds great! is there a qi version setting up these parameters?
>running system from uSD is much easier with qi...
no qi? too bad :(
Petr
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 r
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 devi
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 mentioned,
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 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
On Sun, 18 Jul 2010 00:42:19 +0400
Gennady Kupava (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:
>www.bsdmn.com/openmoko/glamo/242/u-boot_glamo242.udfu
s
2010/7/17 Gennady Kupava :
> 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 the system was
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 du
Gennady Kupava writes:
> I tested default(AKA slow) and fast timing settings for -vo x11 and -vo
> fbdev. The settings with different vo's are not directly comparable, as
> different libc used occasionally, so only (slow/x11 and fast/x11) and
> (slow/fbdev and fast/fbdev) are comparable.
>
> The
Hi, list.
Here is my next rant to freerunner slowness :)
Today, topic of discussion is freerunner's most famous beast - glamo. I
want to show that it is much better than some people thinking about it.
Also i propose different significant optimizations: usage of DMA,
changing cpu<->glamo bus timin
20 matches
Mail list logo
