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 394] In Call Mode/Unable to adjust the speaker volume
      level. ([EMAIL PROTECTED])
   2. [Bug 394] In Call Mode/Unable to adjust the speaker volume
      level. ([EMAIL PROTECTED])
   3. [Bug 394] In Call Mode/Unable to adjust the speaker volume
      level. ([EMAIL PROTECTED])
   4. [Bug 1178] iron out XVideo support in Xglamo
      ([EMAIL PROTECTED])
   5. [Bug 799] data abort while reading from SD Cards
      ([EMAIL PROTECTED])
   6. [Bug 799] data abort while reading from SD Cards
      ([EMAIL PROTECTED])
   7. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=394





------- Additional Comments From [EMAIL PROTECTED]  2008-01-11 12:56 -------
I'm nearly there on this, all I need to know is what channel on what card to
control, and how to identify them (either by name or by number) - I've written a
generic volume control widget using libasound that controls the volume of a
specific mixer element on a specific card.

I'll add this to the dialer later today.



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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From [EMAIL PROTECTED]  2008-01-11 14:52 -------
Working code is in r3814, but not integrated with the dialer yet - I'm working
on refactoring it so it's more flexible/usable. This won't take long, but I have
an appointment so will be leaving early today; I'll probably finish it up on 
Monday.



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





------- Additional Comments From [EMAIL PROTECTED]  2008-01-11 15:27 -------
Took far less time to refactor than I thought - code in r3815. Again, still not
integrated in dialer yet, could do with hints on card/channel names and expected
behaviour.



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





------- Additional Comments From [EMAIL PROTECTED]  2008-01-11 20:29 -------
So my first test with mplayer on the device shows that trying to play a video of
mine does not work. It the mplayer window is created but its content stays 
black.

xvinfo does report something that looks good though:

[EMAIL PROTECTED]:~$ DISPLAY=:0 xvinfo
X-Video Extension version 2.2
screen #0
  Adaptor #0: "GLAMO Texture Video"
    number of ports: 1
    port base: 56
    operations supported: PutImage 
    supported visuals:
      depth 16, visualID 0x21
    no port attributes defined
    maximum XvImage size: 2048 x 2048
    Number of image formats: 2
      id: 0x32315659 (YV12)
        guid: 59563132-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x30323449 (I420)
        guid: 49343230-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)

So I will need to look into that now.



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





------- Additional Comments From [EMAIL PROTECTED]  2008-01-11 21:15 -------
Obri, does it fix it for you as well?



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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #447 is|0                           |1
           obsolete|                            |



------- Additional Comments From [EMAIL PROTECTED]  2008-01-11 23:07 -------
Created an attachment (id=491)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=491&action=view)
Previous patch, diffed from a higher directory level so it can be applied by
bitbake's do_patch




------- 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=934
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=935
  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



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

Reply via email to