Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2136: Freerunner QVGA portrait mode wrong
colors (Openmoko Public Trac)
2. Re: Openmoko Bug #2095: Sound not found with qi bootloader
(Openmoko Public Trac)
3. Re: Openmoko Bug #930: kexec fails on the neo; requires
existing kexec ATAG patch (Openmoko Public Trac)
4. Re: Openmoko Bug #2135: write kernel crash message somewhere
where it can be retrieved after reboot? (Openmoko Public Trac)
5. Re: Openmoko Bug #2095: Sound not found with qi bootloader
(Openmoko Public Trac)
6. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
7. Re: Openmoko Bug #2095: Sound not found with qi bootloader
(Openmoko Public Trac)
8. Re: Openmoko Bug #2137: stable-tracking lacks touchscreen
jitter reduction patch (Openmoko Public Trac)
--- Begin Message ---
#2136: Freerunner QVGA portrait mode wrong colors
-----------------------------+----------------------------------------------
Reporter: Vladimir.Koutny | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.9-dev
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by Leonti):
From http://wiki.openmoko.org/wiki/Video_Player:
{{{
* 240x320 mode has some quirks:
o The gamma/brightness/contrast is weird. Encoding adjustments
into the media is a workaround.
o Vertical banding (as seen in landscape position) is quite
noticeable.
}}}
I think this is the same bug.
Leonti
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2136#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2095: Sound not found with qi bootloader
---------------------+------------------------------------------------------
Reporter: newkirk | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by Leonti):
I'm using 2.6.24 kernel with SHR and I have sound.
Is it me who is lucky or the problem is solved?
If so please confirm, so I(or anyone else) can edit wiki page.
Leonti
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2095#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#930: kexec fails on the neo; requires existing kexec ATAG patch
-----------------------------+----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: 2007.2
Severity: normal | Resolution: fixed
Keywords: | Blockedby:
Blocking: |
-----------------------------+----------------------------------------------
Comment(by lindi):
[ I don't seem to have permission to reopen this bug, could somebody with
sufficient permissions do it? ]
Re #2135 I was investigating different ways to save kernel panic
messages so that they can be retrieved later and thought I should try
kdump which uses kexec only to notice that kexec does not quite work:
With stable-tracking at 1b17c67794364bee I built kexec-tools from the
debian source package 20080324-2 and tried
{{{
sudo kexec -l /boot/uImage2.bin --append="`cat /proc/cmdline`"
sudo kexec -e
}}}
but got only WSOD. The device also did not show up as usb device or
blink any leds.
My /proc/cmdline contains
{{{
rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0
loglevel=8 regular_boot mtdparts=physmap-
flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
}}}
in case it matters.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/930#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2135: write kernel crash message somewhere where it can be retrieved after
reboot?
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
http://docs.openmoko.org/trac/ticket/930 seems to discuss kexec on
openmoko and has been marked fixed 14 months ago. I reported what I tried
and how it failed (but could not reopen the bug due to lack of
permissions).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2135#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2095: Sound not found with qi bootloader
------------------------+---------------------------------------------------
Reporter: newkirk | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
------------------------+---------------------------------------------------
Changes (by andy):
* status: new => closed
* resolution: => fixed
Comment:
Yes it's solved... Qi did not bring up the regulator used to power the
codec.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2095#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by quatrox):
This might be relevant.
I am using a current kernel and a current ver of SHR (just a one or two
days old).
I had Numpty Physics running on my GTA02v5.
I suspended the phone.
When I woke it up again, only every thing was a little smaller - i.e. only
half the screen width where used. I could hear a high frequency sound from
the phone (from somewhere close to the handset speaker at the top).
Aditional suspend/resume did not help.
After a full reboot, everything worked great again:)
Note that this does not happen all the time... This was the first time
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:77>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2095: Sound not found with qi bootloader
------------------------+---------------------------------------------------
Reporter: newkirk | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
------------------------+---------------------------------------------------
Comment(by werner):
Considering the 100mA envelope, shouldn't we leave regulators not
essential for booting off until the kernel decides it's safe to
turn them on ?
In the u-boot current-reduction work, keeping unused regulators off
made a significant difference, 40mA in total for LDO1, 2, 5, and 6.
See also u-boot commit 77ef5a9f920092fcebfe592607b7866ac36e3c8e
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2095#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2137: stable-tracking lacks touchscreen jitter reduction patch
-----------------------------+----------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by Treviño):
I've just tested this patch and the touchscreen implementation in stable-
tracking now seems a little better than the previous one, but it's still
buggy (and quite far from the latest stable implementation).
The main bug I've found in my first test (mostly done writing on illume
keyboard and using the tick's touch screen test pyhton app) is that quite
often happens that the touchscreen send a "push" event to the gui also if
I've no finger over it (practically the release event is not sent!).
I got also other errors while scrolling the illume desktop (some
applications started while I was still dragging my finger and keep in mind
that I've configured illume to start an application only after a double-
click! So the touchscreen has sent more than a wrong click).
Up-down-clicks are not always fixed, btw... :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2137#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
