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 1262] X dies just before loading the desktop
      ([EMAIL PROTECTED])
   2. [Bug 1339] New: matchbox-keyboard sometimes has a locked
      enter key ([EMAIL PROTECTED])
   3. [Bug 79] suspend/resume to RAM support
      ([EMAIL PROTECTED])
   4. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
   5. [Bug 1313] GTA01 POWER button does nothing after resume
      ([EMAIL PROTECTED])
   6. [Bug 79] suspend/resume to RAM support
      ([EMAIL PROTECTED])
   7. [Bug 79] suspend/resume to RAM support
      ([EMAIL PROTECTED])
   8. [Bug 79] suspend/resume to RAM support
      ([EMAIL PROTECTED])
   9. [Bug 79] suspend/resume to RAM support
      ([EMAIL PROTECTED])
  10. [Bug 79] suspend/resume to RAM support
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1262

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2008-04-12 13:31 -------
fixed in svn r4351.



------- 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=1339

           Summary: matchbox-keyboard sometimes has a locked enter key
           Product: OpenMoko
           Version: 2007.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: openmoko-keyboard
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


I have replaced the multitap-thing with the matchbox-keyboard!
If i
1. start openmoko-contacts
3. press the ADD button
4. enter a name and a number
5. press the enter key of the keyboard, right after i entered the number

the application switches between keyboard and no-keyboard very fast, it can't
decide what it wants.
If i switch to another application, i can see that the enter-key is still
pressed. If if press it again, blinking stops...

I noticed this, because openmoko-contacts just dials the last selected number if
i get back to the main list, with this locked enter key.



------- 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=79





------- Additional Comments From [EMAIL PROTECTED]  2008-04-13 04:17 -------
Created an attachment (id=586)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=586&action=view)
Patch to register the SPI device and thus the save/resume for the display

This patch does *NOT* resolve this problem, but it does make things a bit
better.  The SPI device name changed with 2.6.24, and the change was made for
the gta02 but never propagated to the gta01.  With this change, you'll now see
the entries for the spi bus and the display controller in /sys; and the display
controller suspend/resume functions will be called.

Several other problems remain.  Additional comments will be added to this bug
report as these problems are better defined, or as resolutions for various
problems are made.



------- 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=1081
  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=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=1276
  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=1313

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |79

Bug 1313 depends on bug 79, which changed state.

Bug 79 Summary: suspend/resume to RAM support
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=79

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From [EMAIL PROTECTED]  2008-04-13 08:08 -------
Marked as depending on bug #79. Patch (and follow-up discussion,if any)are
associated with that bug report in order to keep all the save/resume issues in
one spot for the moment.



------- 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=79

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |1313
              nThis|                            |





------- 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=79





------- Additional Comments From [EMAIL PROTECTED]  2008-04-13 08:11 -------
Created an attachment (id=587)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=587&action=view)
Restore power button functionality after resume operation

Per Werner's suggestion, run the PMU interrupt handler immediately after resume
to clear/handle any pending interrupts from that device.  This appears to
resolve the  dead-powerbutton-after-resume problem.  This is not well-tested;
need feedback to see if there are any side-effects or other problems.



------- 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=79





------- Additional Comments From [EMAIL PROTECTED]  2008-04-13 08:17 -------
Created an attachment (id=588)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=588&action=view)
Preserve the GPS power state over suspend/resume - temporary patch

This is a hack in the form of a patch - it will be obsoleted and replaced after
discussion.

On suspend, the GPS is powered off -- this is reasonable.  On resume, the GPS
is always powered on, even if it was off at time of suspend.  This patch saves
the state so that the GPS is only powered up if it was powered up at time of
suspend.

Comments are required on the patch technique (yes, the variable names need
changing too).  Some feedback on whether we really even need to save state
would be helpful -- does it make sense to simply leave the GPS off after a
resume, and let something like apmd in user-space power it back up if
necessary?  Or is the current behavior of powering it up unconditionally the
right solution?



------- 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=79





------- Additional Comments From [EMAIL PROTECTED]  2008-04-13 08:32 -------
Thanks for the SPI patch, this is in stable and andy now.

Can you please add Signed-off-by: though?  Upstream won't accept patches
without it.  I added it in this case but I can't go on doing that.



------- 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=79





------- Additional Comments From [EMAIL PROTECTED]  2008-04-13 08:36 -------
I also added the 50606 missed edge after resume patch to stable.

On GPS power, Holger has been here already a few days ago and it is in stable
git branch for some days.

http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=73a213f11aed2b9328ebd01de




------- 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

Reply via email to