andy at openmoko.com
Tue Jul 8 18:49:31 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
| Hi All,
| The kernel issue is under study right now. I got some boot informations
| from "demsg", please check the attached file. we can see the kernel is
| doing for what at boot time.
| here are some interesting places for kernel at boot time:
| 1. Mount filesystem needs 3.6secs:
| [ 3.265000] CRCFAIL 0x1a3f
| >> [ 3.265000] Current Request Command:5, ARG:0x00000000
| flags: 0x0008
| >> [ 6.805000] VFS: Mounted root (jffs2 filesystem).
| [ 6.805000] Freeing init memory: 124K
| [ 6.935000] CRCFAIL 0x1a3f
That's not completely insane for 256MB jffs2 filesystem, but if we can
improve it that'd be nice.
| 2. Framebuffer and console stuffs need 0.5 sec:
| [ 1.010000] SMEDIA Glamo frame buffer driver (C) 2007 Openmoko, Inc.
| [ 1.610000] Console: switching to colour frame buffer device 80x58
OK, it spins waiting for PLLs, but that isn't 500ms of spinning, I guess
it can be improved a little and we find msleeps and so on that can maybe
| 3. sdio_wlan needs 1 sec or ?:
| [ 7.010000] sdio_wlan 00:01: driver attached
| [ 7.010000] sdio_wlan 00:01: SDIO device, IDs SD_0001 (active)
| [ 8.090000] Unsupported configuration opcode: 3
| [ 8.090000] Unsupported configuration opcode: 5
| 4. ar6000 needs 1 sec or?
| [ 8.225000] ar6000_avail: name=eth0 htcTarget=0xc7f46000,
| dev=0xc74b0000 (0), ar=0xc74b04a0
ar6000 is the WLAN too, I am not sure this all stalls the boot (bad) or
is happening async (good). Considering it does some nice things in the
whole time it doesn't sound so awful, despite we can give it a shave.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the openmoko-devel