Re: When is the next and more powerful openmoko releasing
"Dr. Michael Lauer" writes: > > as far as i know, openmoko is no longer working on phones. > > Unfortunately the freedom loving people are doomed to either work on > anti-vendor-ports (such as HTC devices etc.) or live with one of the > semi-free alternatives (Palm Pre, Nokia N900). Right now there is no > device rivaling the FreeRunner's openness, nothing comes close. > > I don't see that changing soon. Do you have any insights regarding Bluebird's `Pidion' devices (beyond `wow, they're expensive' :))? cf.: http://www.sdgsystems.com/ -- "Don't be afraid to ask (λf.((λx.xx) (λr.f(rr." ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v27
Alex Samorukov writes: >> With http://lindi.iki.fi/lindi/openmoko/compare-clock-sources.pl > Also it can compare only system clock with RTC, so we always assume compare-clock-sources.pl compares 1) GPS to system time 2) GPS to pcf time 3) GPS to calypso time. It does not compare system time with RTC. > Calypso time - do we need it at all? Probably not since it is reset so easily. > It will not do circular buffer then. Log rotation should do that? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: dbus moving into kernel?
Il giorno sab, 25/09/2010 alle 19.57 +0400, Gennady Kupava ha scritto: > В Птн, 24/09/2010 в 15:11 +0200, Marco Trevisan (Treviño) пишет: > > > Some days ago I've tried to port this patch to the Openmoko kernel, > > after applying it to the SHR 2.6.32 kernel (patches at [1]), I got > > these results (in average): > > > > dbus-ping-pong test: > > Pingdbus-daemon (s) kdbus (s) speedup > > 500 ping3.332.1336.2% > > 5000 ping 32.59 26.09 19.9% > > 5 ping 313.56 176.35 43.8% > > > > > > Adrien Bustany’s ipc-performances tool with 6 random 10 char > > strings: > > > > dbus-daemon query (s) kdbus query (s) speedup > > 102.75 74.71 27.29% > > > > Interesting, how adding FCSE will influence this dbus test? > I've tried FCSE too, but I can't get a working kernel after patching... I should retest. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v27
On 09/25/2010 10:45 PM, Timo Juhani Lindfors wrote: > Alex Samorukov writes: > >> Thank you for update. How did you measure this drift? Anyway, i don`t >> > With http://lindi.iki.fi/lindi/openmoko/compare-clock-sources.pl > Thanks. Also it can compare only system clock with RTC, so we always assume that system time is correct. Calypso time - do we need it at all? I think right scenario is to get ntptime (slow op), and then - RTC + system, and compare them. Not sure that system clock is really accurate :) > >> hwclock changes are not important for qtmoko, because rtc driver >> controls /dev/rtc elusively (its very easy to change, but i don`t >> think that it needs to be changed). >> > Hmm, what driver is that in qtmoko btw? > Not driver, daemon. atd from qpe. >> Thank you, need to check. If it is - then its a serious argument >> against this change. Do you know any other syslogd with in-memory >> buffer? >> > How about just using normal syslogd with tmpfs as storage? > It will not do circular buffer then. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Translate into Danish
Rune Gangstø wrote: > I could be interested in translating into norwegian, is it possible for > me to use the same files and just send them via e-mail when they are > translated? Hi, yes, it is possible. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
