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. [Bug 1381] New: clicking at touchscreen borders confuses
libSDL's mouse cursor ([EMAIL PROTECTED])
2. [Bug 1381] clicking at touchscreen borders confuses libSDL's
mouse cursor ([EMAIL PROTECTED])
3. [Bug 1194] Touchscreen Jitter
([EMAIL PROTECTED])
4. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
5. [Bug 1382] New: verbose mmc-related kernel messages slow down
boot process (GTA01) ([EMAIL PROTECTED])
6. [Bug 1382] verbose mmc-related kernel messages slow down boot
process (GTA01) ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1381
Summary: clicking at touchscreen borders confuses libSDL's mouse
cursor
Product: Neo1973 Hardware
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Screen
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I have this problem with my GTA01 phase-1 phone but it most likely affects the
GTA02 too since the display has not changed.
The problem can be only seen in SDL application when the use the fullscreen
mode. An app which this affects and which is in OM already is kobodeluxe however
I wrote a small test app which can be placed into an OE tree and provides some
informative output.
With this test app I was able to observe the following (IMHO wrong) behavior:
If you touch the screen with the stylus at the upper border the cursor block
will move quickly towards the left or right end depending on whether you are on
the left or right half of it. If you now move the stylus to the other side the
cursor's movement will turn as well and will soon crash into the other end.
Analogus behavior can be observed with all the other borders.
Without looking at the code my assumption is that the touchscreen driver reports
values which are outside the bounds (smaller than 0 and bigger than
width/height) of what a normal mouse driver would report and the code in SDL is
not able to deal with this.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1381
------- Additional Comments From [EMAIL PROTECTED] 2008-05-06 14:16 -------
Created an attachment (id=605)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=605&action=view)
simple SDL test app
This simple app enters fullscreen mode and draws a black box where SDL says the
cursor is.
You can unpack this archive in a "packages" directory of an OE tree and built
it with "bitbake sdltest" afterwards.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1194
------- Additional Comments From [EMAIL PROTECTED] 2008-05-06 14:17 -------
Please ignore my comment (comment 8). I think my problem is different from what
is discussed here and opened bug 1357 for it.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1012
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1189
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1193
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1197
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1199
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1200
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1201
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1206
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1212
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1215
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1216
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1217
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1218
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1292
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1382
Summary: verbose mmc-related kernel messages slow down boot
process (GTA01)
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The current kernel prints a lot of messages when accessing the MMC/SD-card (e.g.
when booting from it) which slows down the boot process considerably. The kernel
messages look like this one:
mmc0: req done (CMD18): 0: 00000900 d35983c7 befb4fff 92404021
mmc0: 1024 bytes transferred: 0
mmc0: (CMD12): 0: 00000b00 7f5983c7 befb4fff 92404021
It would be nice if their urgency level could be lowered so that they only show
up when needed.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1382
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2008-05-07 10:37 -------
This is MMC DEBUG traffic that has been enabled by accident in GTA01 config for
a while until last week. If you're still seeing it even on most recent kernels
then there is some issue about which config the OE build is using, because it is
fixed in stable git tree.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
