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. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
2. Re: Openmoko Bug #2104: Morse code announcing who is calling
or texting (Openmoko Public Trac)
3. Openmoko Bug #2230: Git clone on "kernel.git linux-2.6" fails
(Openmoko Public Trac)
4. Re: Openmoko Bug #2230: Git clone on "kernel.git linux-2.6"
fails (Openmoko Public Trac)
5. Re: Openmoko Bug #2230: Git clone on "kernel.git linux-2.6"
fails (Openmoko Public Trac)
6. Re: Openmoko Bug #2230: Git clone on "kernel.git linux-2.6"
fails (Openmoko Public Trac)
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by Sascha):
I think hardware handshaking works fine for GSM (no bytes get lost), but
the overrun flag is set anyway. This results in one additional 0x00 byte
for each overrun.
With the attached patch the serial driver doesn't forward the overruns,
works without problems since 1 hour (of course I still get the rxerr
messages).
So I guess the uart is not properly initialized?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2104: Morse code announcing who is calling or texting
-------------------------+--------------------------------------------------
Reporter: pander | Owner: zecke
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-------------------------+--------------------------------------------------
Comment(by pander):
Morse code and speech synthesis could be used to 'read out loud' the time
of your alarm or title and location when the device is remingind you of a
task or event.
This would result in extra configuration parameters:
enable/disable for all alarm notifications
enable/disable for all calendar event notifications
enable/disable for all calendar task notifications
enable/disable for all 'almost out of power and other system popup'
notifications
enable/disable reading out in Morse (default=false is speech synthesis)
and removal of:
enable/disable for all alerts, tasks and calendar events
See also http://wiki.openmoko.org/wiki/Wishlist/Speech_synthesis
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2104#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2230: Git clone on "kernel.git linux-2.6" fails
---------------------+------------------------------------------------------
Reporter: doxy2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
git clone git://git.openmoko.org/git/kernel.git linux-2.6
results in:
Initialized empty Git repository in /home/doxy2/temp/test/linux-2.6/.git/
remote: Generating pack...
remote: Done counting 128876 objects.
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2230>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2230: Git clone on "kernel.git linux-2.6" fails
---------------------+------------------------------------------------------
Reporter: doxy2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by andy):
Again, huh.
I have a clean local copy I will nuke it and send it back up.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2230#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2230: Git clone on "kernel.git linux-2.6" fails
---------------------+------------------------------------------------------
Reporter: doxy2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by doxy2):
oops, was supposed to place this in webserver and infrastructure. Feel
free to remove the duplicate
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2230#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2230: Git clone on "kernel.git linux-2.6" fails
---------------------+------------------------------------------------------
Reporter: doxy2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by andy):
No worries they can't fix the corruption anyway, so I would have to hear
about it. But I don't know what the underlying problem is. I opened an
admin trac about it already but the error is sporadic so it's hard to
resolve.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2230#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog