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 #1336: screen shifted and duplicated after
resume in landscape mode (Openmoko Public Trac)
2. Re: Openmoko Bug #2209: alsactl restore wakes up X
(Openmoko Public Trac)
3. Re: Openmoko Bug #2243: [Xglamo] some motion events are
thrashed (Openmoko Public Trac)
4. Re: Openmoko Bug #2243: [Xglamo] some motion events are
thrashed (Openmoko Public Trac)
5. Re: Openmoko Bug #2243: [Xglamo] some motion events are
thrashed (Openmoko Public Trac)
--- Begin Message ---
#1336: screen shifted and duplicated after resume in landscape mode
------------------------------------+---------------------------------------
Reporter: wer...@… | Owner: andy
Type: defect | Status: assigned
Priority: high | Milestone:
Component: System Software | Version: current svn head
Severity: normal | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
------------------------------------+---------------------------------------
Comment(by andy):
This has already been fixed in andy-tracking head.
the kernel version you mention is confusing because our stable has never
been 2.6.28, it jumped from 2.6.24 to 2.6.29-rc2. So I dunno what it is
you are running there really.
I'll backport any missing fixes on to the stable branch later and maybe
someone can clarify what the patchlevel of that kernel actually is.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1336#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2209: alsactl restore wakes up X
-----------------------------+----------------------------------------------
Reporter: lindi | 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 lindi):
Huh, I seem to have forgotten to mention what kernel version I was
running. It was andy-tracking b8b36e5ec3db71d5. I'll try newer andy-
tracking soon and if that fails I'll try stable as well.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2209#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2243: [Xglamo] some motion events are thrashed
------------------------------+---------------------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version: FSO-MS2
Severity: normal | Keywords: Xglamo
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------------+---------------------------------------------
Comment(by Richard.Kralovic):
Many thanks for clarifying the function of the buffer. I was not sure
about this one, I'll put it back to the old size and test it. I am quite
sure that the QUEUE_SIZE in mieq.c in Xglamo is relevant. I am still not
sure about the buffer size in evdev (kernel), but it seems to me that if
this is small, then slow clients (Xglamo) must miss some events.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2243#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2243: [Xglamo] some motion events are thrashed
------------------------------+---------------------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version: FSO-MS2
Severity: normal | Keywords: Xglamo
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------------+---------------------------------------------
Comment(by arhuaco):
Are many of them trashed?
About half?
I guess that a good way to start is rule out kernel interference.
You might want to try two things:
1) Enable CONFIG_TOUCHSCREEN_S3C2410_DEBUG in your config.
2) Try with this app (which also prints messages, you might want to modify
to measure what you need to).
http://svn.openmoko.org/developers/tick/touchtest/touch_test.py
This way you see if something is actually getting lost and you will check
what the kernel actually sends.
When you move the stylus fast the TS driver might send points at half of
the rate it usually sends them it I think. Perhaps this is what you're
seeing.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2243#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2243: [Xglamo] some motion events are thrashed
------------------------------+---------------------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version: FSO-MS2
Severity: normal | Keywords: Xglamo
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------------+---------------------------------------------
Comment(by Richard.Kralovic):
I think the kernel driver works fine. My major concern is the way how
Xglamo handles movement events. I'll make some more tests if the kernel
modifications are necessary at all, maybe this is not the case. I am not
sure about how exactly the in-kernel evdev framework works, but if I
understood the source correctly, then at least the queue size in evdev.c
(EVENT_BUFFER_SIZE) needs to be larger. Otherwise, if there is a slow
client (such as Xglamo), some events (correctly reported by the neo
touchscreen driver) are forgotten due to queue overfull before Xglamo
actually reads them from /dev/input/eventX.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2243#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
