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 216] contacts crashes when tying to enter import widget
      ([EMAIL PROTECTED])
   2. [Bug 89] determine correct gamma calibration values and put
      them in   LCM config code ([EMAIL PROTECTED])
   3. [Bug 89] determine correct gamma calibration values and put
      them in   LCM config code ([EMAIL PROTECTED])
   4. [Bug 89] determine correct gamma calibration values and put
      them in   LCM config code ([EMAIL PROTECTED])
   5. [Bug 217] New: Implement NAND OTP area read/write as u-boot
      commands ([EMAIL PROTECTED])
   6. [Bug 217] New: Implement NAND OTP area read/write as u-boot
      commands ([EMAIL PROTECTED])
   7. [Bug 214] Add CVS_TARBALL_STASH for missing upstream sources
      ([EMAIL PROTECTED])
   8. [Bug 214] Add CVS_TARBALL_STASH for missing upstream sources
      ([EMAIL PROTECTED])
   9. [Bug 218] New: Distinguish stylus from finger via tslib
      ([EMAIL PROTECTED])
  10. [Bug 218] New: Distinguish stylus from finger via tslib
      ([EMAIL PROTECTED])
  11. [Bug 216] contacts crashes when tying to enter import widget
      ([EMAIL PROTECTED])
  12. [Bug 216] contacts crashes when tying to enter import widget
      ([EMAIL PROTECTED])
  13. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
  14. [Bug 108] allow query of manufacturer/model/revision/imei
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=216





------- Additional Comments From [EMAIL PROTECTED]  2007-02-27 13:54 -------
Could you clarify your description please? I am unsure what you are trying to do
and what widget you are referring to.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=89

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-02-27 20:09 -------
Teddy, Sean,

this bug is critical, and it's how open for some 40 days.  Is there any progress
in this area?



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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-02-27 20:09 -------
Teddy, Sean,

this bug is critical, and it's how open for some 40 days.  Is there any progress
in this area?



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=89

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-02-27 20:09 -------
Teddy, Sean,

this bug is critical, and it's how open for some 40 days.  Is there any progress
in this area?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=217

           Summary: Implement NAND OTP area read/write as u-boot commands
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: u-boot
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


We want to be able to 'nand otp write' and 'nand otp read' pages from the NAND
OTP block.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=217

           Summary: Implement NAND OTP area read/write as u-boot commands
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: u-boot
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


We want to be able to 'nand otp write' and 'nand otp read' pages from the NAND
OTP block.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=214

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-02-27 20:33 -------
in 1140 - thanks!



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=214

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-02-27 20:33 -------
in 1140 - thanks!



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=218

           Summary: Distinguish stylus from finger via tslib
           Product: OpenMoko
           Version: unspecified
          Platform: Neo1973
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: kernel
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Nokia apparantly does it by measuring pressure. See the following snippet from
Maemo's tslib:

      /* this ... is ugly.
         * basically, we need two things to support thumb cleanly:
         *  - pressure filtering.  because it's pressure-based, often we get
         *    the following sequence: pen down, thumb down, thumb up, pen down,
         *    thumb up.  so we need to filter the first n events to see whether
         *    we have a thumb event coming, and discard the first pen events if
         *    so.  we also need to check if we're trying to post a pen down
         *    after a thumb down (without an intervening thumb up, and discard
         *    it if so).
         *  - accuracy filtering.  the first n events just aren't going to be
         *    accurate.  so we need to discard them, which negates the call for
         *    keeping the initial thumb events above.
         *
         * in addition to this, we need general stability filtering, so we take
         * a three-sample filtering, and discard the result if the total 
movement
         * is less than 4px in either direction.
         *
         * i'm really, really sorry. -daniels
         */
        if (flags && private->holdEvents) {
            /* Drop pen events after a thumb stream. */
            if ((flags & KD_BUTTON_1) && (private->lastFlags & KD_BUTTON_8))
                discard = 1;
 
            /* Drop all our queued events if we have a thumb event in a
             * pen stream. */
            if ((flags & KD_BUTTON_8) && (private->lastFlags & KD_BUTTON_1))
                private->numHeldEvents = 0;
 
            /* Run the queue if we're full; drop it on the floor if the total
             * four-sample difference is less than 4px in both directions. */
            if (private->numHeldEvents >= TSLIB_QUEUE_SIZE) {
                if (abs(private->lastx - LAST_EVENT.x) < 4 &&
                    abs(private->lasty - LAST_EVENT.y) < 4 &&
                    private->lastFlags) {
                    discard = 1;
                    private->numHeldEvents = 0;
                }
                else {
                    TsRunQueue(pi);
                }
            }



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=218

           Summary: Distinguish stylus from finger via tslib
           Product: OpenMoko
           Version: unspecified
          Platform: Neo1973
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: kernel
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Nokia apparantly does it by measuring pressure. See the following snippet from
Maemo's tslib:

      /* this ... is ugly.
         * basically, we need two things to support thumb cleanly:
         *  - pressure filtering.  because it's pressure-based, often we get
         *    the following sequence: pen down, thumb down, thumb up, pen down,
         *    thumb up.  so we need to filter the first n events to see whether
         *    we have a thumb event coming, and discard the first pen events if
         *    so.  we also need to check if we're trying to post a pen down
         *    after a thumb down (without an intervening thumb up, and discard
         *    it if so).
         *  - accuracy filtering.  the first n events just aren't going to be
         *    accurate.  so we need to discard them, which negates the call for
         *    keeping the initial thumb events above.
         *
         * in addition to this, we need general stability filtering, so we take
         * a three-sample filtering, and discard the result if the total 
movement
         * is less than 4px in either direction.
         *
         * i'm really, really sorry. -daniels
         */
        if (flags && private->holdEvents) {
            /* Drop pen events after a thumb stream. */
            if ((flags & KD_BUTTON_1) && (private->lastFlags & KD_BUTTON_8))
                discard = 1;
 
            /* Drop all our queued events if we have a thumb event in a
             * pen stream. */
            if ((flags & KD_BUTTON_8) && (private->lastFlags & KD_BUTTON_1))
                private->numHeldEvents = 0;
 
            /* Run the queue if we're full; drop it on the floor if the total
             * four-sample difference is less than 4px in both directions. */
            if (private->numHeldEvents >= TSLIB_QUEUE_SIZE) {
                if (abs(private->lastx - LAST_EVENT.x) < 4 &&
                    abs(private->lasty - LAST_EVENT.y) < 4 &&
                    private->lastFlags) {
                    discard = 1;
                    private->numHeldEvents = 0;
                }
                else {
                    TsRunQueue(pi);
                }
            }



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=216





------- Additional Comments From [EMAIL PROTECTED]  2007-02-28 01:44 -------
My operation process on gta01bv3:
1.run openmoko-contacts
2.click menu "Phone Book -> Import" or "Phone Book -> Export"
3.segmentation fault

I met the same problem in appmanager while opening/closing widget.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=216





------- Additional Comments From [EMAIL PROTECTED]  2007-02-28 01:44 -------
My operation process on gta01bv3:
1.run openmoko-contacts
2.click menu "Phone Book -> Import" or "Phone Book -> Export"
3.segmentation fault

I met the same problem in appmanager while opening/closing widget.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



--- 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=69
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=192



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=108

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-02-28 08:04 -------
Hi harald, I sent you the patch file several days ago but receiving no 
comments. So I commit it today to remind you that I 've changed some src code 
for the gsmd/libgsm/utili.
the query works now, but I want to discuss with you for the accountability of 
sync command executing.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to