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 781] LM4857 should be turned off on a reboot notifier
([EMAIL PROTECTED])
2. [Bug 736] the 2007.2 software doesn't let you calibrate your
screen ([EMAIL PROTECTED])
3. [Bug 739] svnREV missing from uImage
([EMAIL PROTECTED])
4. [Bug 773] Qemu should support -net usb -redir ......
([EMAIL PROTECTED])
5. [Bug 781] LM4857 should be turned off on a reboot notifier
([EMAIL PROTECTED])
6. [Bug 775] bluetooth can not be enabled (kernel
2.6.22.5-moko11 / 20070829) ([EMAIL PROTECTED])
7. [Bug 115] A2DP / alsa integration
([EMAIL PROTECTED])
8. [Bug 776] X crashes when terminal is closed with power button
([EMAIL PROTECTED])
9. [Bug 802] New: openmoko-dialer2 segfaults when first digit
entered is '#' ([EMAIL PROTECTED])
10. [Bug 781] LM4857 should be turned off on a reboot notifier
([EMAIL PROTECTED])
11. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
12. [Bug 115] A2DP / alsa integration
([EMAIL PROTECTED])
13. [Bug 776] X crashes when terminal is closed with power button
([EMAIL PROTECTED])
14. [Bug 776] X crashes when terminal is closed with power button
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=781
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 17:22 -------
In fact I miss-understood your comment, you were saying that in fact the
suspend/shutdown functions of the driver are not called at all. I do not have a
clue here but when I've tested, the shutdown and resume printk were issued.
------- 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=736
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 17:35 -------
The S3C ADC now returns scaled values, starting with svn r2920.
------- 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=739
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 17:53 -------
We have two different uboot recipes in OE now. One using a pinned svn and git
rev which gets displayed in the filename. This is the default recipe.
The other one pulls bleeding edge git revs and our newest patches in and tries
to build it. This one now shows the rev for our svn but only the date for the
git rev. It's not possible to use the git rev in the filename in this way atm.
------- 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=773
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 18:01 -------
It would work in Windows and MacOS if they didn't lack gadgetfs support - this
lack should be compensated for in these projects instead of in qemu. Ofcourse if
someone implements a workaround in qemu (which shouldn't be difficult because it
would mainly consist of copying and pasting the kernel code into qemu) it can be
merged into qemu-neo1973 tree, but not upstream. See the problems qemu already
has with maintaining slirp in our cvs - this would add a very similar issue of
maintaining code that belongs in a separate project.
For networking, fixing the USB NIC from
http://lists.gnu.org/archive/html/qemu-devel/2006-11/msg00044.html may be
easier. Other possibilities are networking over emulated bluetooth or GPRS but
they will have the same problems of a lot of code not fitting in qemu.
------- 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=781
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
Status|ASSIGNED |NEW
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 19:07 -------
the lack of a call to shutdown/resume might be related to i2c power management
API changes that were introduced somewhere between 2.6.17 and the current
kernel...
you might want to compare the suspend/resume functions with other i2c drivers.
------- 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=775
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 22:48 -------
I just build uImage-2.6.22.5-moko11-r2-fic-gta01.bin where I can power up
bluetooth by issuing:
echo -n 1 >/sys/bus/i2c/devices/0-0008/gta01-pm-bt.0/power_on
Don't know about uImage-2.6.22.5-moko11-r1-fic-gta01.bin since I looked in the
wrong path there.
Closing
------- 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=115
------- Additional Comments From [EMAIL PROTECTED] 2007-09-06 01:03 -------
Okay, I have set up A2DP for the first time today on both my laptop and my Neo.
I've been following http://wiki.bluez.org/wiki/HOWTO/Bonding for bonding and
http://wiki.bluez.org/wiki/HOWTO/AudioDevices for activating A2DP.
On the Neo I needed to install bluez-utils-alsa before it would work.
However, on the Neo A2DP is mono - on my laptop I have stereo sound.
------- 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=776
------- Additional Comments From [EMAIL PROTECTED] 2007-09-06 01:24 -------
This doesn't seem to happen anymore with the new terminal. Olaf, could you
please confirm that a new build indeed seems to fix this?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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=802
Summary: openmoko-dialer2 segfaults when first digit entered is
'#'
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Version is 0.1.0+svnr2869-r5
I can enter numeric digits (and dial) successfully.
But to check my GSM account balance I need to dial #999#, and it crashes
(segfault, according to the terminal) as soon as I hit that first '#'.
------- 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=781
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
------- 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=41
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=129
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=276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=115
------- Additional Comments From [EMAIL PROTECTED] 2007-09-06 05:34 -------
Welcome to our world. There are some minor glitches in some situations and on
some devices where something totally unexpected happens. Run "hcidump -X -V" and
catch the AVDTP control channel setup. It will tell you what your headset
supports and what the audio service actually selected. Highly likely we have
another bug in the stream setup. This is under a lot of development since in the
end a stream configuration can be changed on-the-fly and we have to deal with it
and provide the path with the best latency.
------- 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=776
------- Additional Comments From [EMAIL PROTECTED] 2007-09-06 11:37 -------
yes, it is fixed with the new terminal
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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=776
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-06 11:40 -------
changed status to fixed
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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
