Re: My N900 experience compared to my FR experience (was: Re: [QtMoko] handset is (almost) unusable for voice calls with background noise)
On Wed, Jul 7, 2010 at 10:12 PM, Michal Brzozowski ruso...@poczta.fm wrote: [...] I'd like to hear how the N900 compares to the FR in hackability. Like replacing pieces of software, like keyboard, window manager, etc. I wasn't able to find much information about this. It seems there is only one distribution that fully works on the N900, which is quite worrying. Hi Michal, I have an n900 too since last November, here my (hoping agnostic) review: Hardware: Great, overclockable to 1Ghz (seems without problems), battery life of several days *without* suspend, 3d accelerated graphics, 32 GB eMMC (+ slot for SD expansion), 256 MB flash, 256 MB ram, nice screen resolution of 800x480, good TS (even with finger only), FM receiver and *transmitter*, proximity sensor, IR transmitter, accelerometer, 5Mb zeiss rear camera, front camera, *superb* audio quality and 3.5G module, wifi, bt, video output, stereo speaker, etc. End User Experience: Not comparable to the freerunner one. Maemo has a lot of defects but using it you feel immediately it has a common layout, defined api and gui guidelines. This may appear as a limit, but from the End User experience is very nice! All apps (nokia, community or thirdy part) follow this principles, are integrated with the DE and with the middleware quite nice. The phone application is based on telepathy, so due to its multiprotocol nature supports gsm voice calls, skype, voip, and so on. The same for sms and chat integrated in the conversation app. There are a lot of plugins (google, msn, etc.) to extend it. The DE has a nice 4 pages home, you switch by dragging them, on every page you may add shortcuts to applications, contacts (that shows the picture and the IM online status, so it's easy and natural using a skype/voip call instead of gsm one and save money!), web bookmarks and widgets that make the user able to highly customize the desktop. Finally there are pluggable status area and power button menu. Task switching is performed with a very nice composite dashboard where you see thumbnails of current running apps (that are updated in realtime). All that is full finger friendly and there is a stylo inside the n900 when you need, (actually I use it only for precise web browsing without the need of zooming in/out). The virtual keyboard is full integrated with customized input methods of gtk and qt (I do not know about other toolkits), so when you tap on a text field you'll have a qwerty (not transparent) portrait keyboard showing the current editing text. If you open/close the HW keyboard the virtual one will hide/show. As you may guess peoples does not feel the necessity to change the WM or the VK because you loose the high number of pluggable widgets in the home, the status area and the toolkit interaction with the keyboard. The package management system is apt, there is an integrated GUI that will show only a specific section of the available apps, so the end user will see only good sense applications with descriptions and icons (of course the power user may use xterm or ssh to see the full contents of the repositories). The status area will signal with a blinking square where an update is available, so you may be uptodate with a couple of finger taps. The network manager works very well and handles wifi and 3g connections. Just a concrete user experience (a my tipical day): I have a voip public telephony (like skypein) account (eutelia) and skype configured, a 5euro/month 3GB umts data option on my sim, wifi networking at home and at work, google contacts synchronization and 3 email account configured. My network manager is configured to always on. The alarm wakes up me every morning (and works reliably), then I put the device online, automagically it connects to my home wifi network, signs up to skype and eutelia, check for emails, does the first sync with google, updates the weather and the rss and the personal ip address widgets on the desktop. When going to work, as my home wifi is not more reachable the n900 automagically start a 3g connection. I may check the sent/received statistics with another widgets that updates informations in real time on the desktop to be sure I'm not reaching the 3G/month limit, and anyway in the settings manager I may set to be advised every time x MB of traffic was generated. While using my car I start the mediaplayer and the FM transmitter (with another desktop widget), put the device near the car stereo and listen for some music or use sygic voice assisted gps navigation where going to unknown places. When I arrive in the office it automagically stops it and connects to work wifi and so on until I put it offline in the night. Every x minutes it continues to update widgets, and signal incoming email, IM messages, alarms, phone calls (of course ;)) and so on. Every with this intensive usage my battery may survive to more then a day, note that it never suspends, and this is a big feature as I can always open an ssh
Re: My N900 experience compared to my FR experience (was: Re: [QtMoko] handset is (almost) unusable for voice calls with background noise)
Thanks a lot for your ffedback! hey and waht about Noko? :) CU Sylvain (aka GarthPS) 2010/7/8 Nicola Mfb nicola@gmail.com On Wed, Jul 7, 2010 at 10:12 PM, Michal Brzozowski ruso...@poczta.fm wrote: [...] I'd like to hear how the N900 compares to the FR in hackability. Like replacing pieces of software, like keyboard, window manager, etc. I wasn't able to find much information about this. It seems there is only one distribution that fully works on the N900, which is quite worrying. Hi Michal, I have an n900 too since last November, here my (hoping agnostic) review: Hardware: Great, overclockable to 1Ghz (seems without problems), battery life of several days *without* suspend, 3d accelerated graphics, 32 GB eMMC (+ slot for SD expansion), 256 MB flash, 256 MB ram, nice screen resolution of 800x480, good TS (even with finger only), FM receiver and *transmitter*, proximity sensor, IR transmitter, accelerometer, 5Mb zeiss rear camera, front camera, *superb* audio quality and 3.5G module, wifi, bt, video output, stereo speaker, etc. End User Experience: Not comparable to the freerunner one. Maemo has a lot of defects but using it you feel immediately it has a common layout, defined api and gui guidelines. This may appear as a limit, but from the End User experience is very nice! All apps (nokia, community or thirdy part) follow this principles, are integrated with the DE and with the middleware quite nice. The phone application is based on telepathy, so due to its multiprotocol nature supports gsm voice calls, skype, voip, and so on. The same for sms and chat integrated in the conversation app. There are a lot of plugins (google, msn, etc.) to extend it. The DE has a nice 4 pages home, you switch by dragging them, on every page you may add shortcuts to applications, contacts (that shows the picture and the IM online status, so it's easy and natural using a skype/voip call instead of gsm one and save money!), web bookmarks and widgets that make the user able to highly customize the desktop. Finally there are pluggable status area and power button menu. Task switching is performed with a very nice composite dashboard where you see thumbnails of current running apps (that are updated in realtime). All that is full finger friendly and there is a stylo inside the n900 when you need, (actually I use it only for precise web browsing without the need of zooming in/out). The virtual keyboard is full integrated with customized input methods of gtk and qt (I do not know about other toolkits), so when you tap on a text field you'll have a qwerty (not transparent) portrait keyboard showing the current editing text. If you open/close the HW keyboard the virtual one will hide/show. As you may guess peoples does not feel the necessity to change the WM or the VK because you loose the high number of pluggable widgets in the home, the status area and the toolkit interaction with the keyboard. The package management system is apt, there is an integrated GUI that will show only a specific section of the available apps, so the end user will see only good sense applications with descriptions and icons (of course the power user may use xterm or ssh to see the full contents of the repositories). The status area will signal with a blinking square where an update is available, so you may be uptodate with a couple of finger taps. The network manager works very well and handles wifi and 3g connections. Just a concrete user experience (a my tipical day): I have a voip public telephony (like skypein) account (eutelia) and skype configured, a 5euro/month 3GB umts data option on my sim, wifi networking at home and at work, google contacts synchronization and 3 email account configured. My network manager is configured to always on. The alarm wakes up me every morning (and works reliably), then I put the device online, automagically it connects to my home wifi network, signs up to skype and eutelia, check for emails, does the first sync with google, updates the weather and the rss and the personal ip address widgets on the desktop. When going to work, as my home wifi is not more reachable the n900 automagically start a 3g connection. I may check the sent/received statistics with another widgets that updates informations in real time on the desktop to be sure I'm not reaching the 3G/month limit, and anyway in the settings manager I may set to be advised every time x MB of traffic was generated. While using my car I start the mediaplayer and the FM transmitter (with another desktop widget), put the device near the car stereo and listen for some music or use sygic voice assisted gps navigation where going to unknown places. When I arrive in the office it automagically stops it and connects to work wifi and so on until I put it offline in the night. Every x minutes it continues to update widgets, and signal incoming email, IM messages,
Re: My N900 experience compared to my FR experience
Guys, thanks for your detailed reviews. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: can't flash kernel
Do you use Ubunu Lucid 64 bit? There has been a recent discussion on a German forum showing the same symptom [1]. The user has then tried to boot Ubuntu-koala-32bit from DVD, installed dfu-util and it did work fine. I would suspect that dfu-util or libusb is broken on some 64 bit systems. Nikolaus [1]: http://freeyourphone.de/portal_v1/viewtopic.php?f=5p=17806#p17806 Am 08.07.2010 um 20:19 schrieb Ben Ruhnow: Hello, today I tried to flash a kernel to my moko (GTA02). Dfu-util showed: No such Alternate Setting: kernel. I flashed my moko a hundred times before. Is it bricked ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: can't flash kernel
On Thu, Jul 8, 2010 at 10:42 PM, Dr. H. Nikolaus Schaller h...@goldelico.com wrote: Do you use Ubunu Lucid 64 bit? There has been a recent discussion on a German forum showing the same symptom [1]. The user has then tried to boot Ubuntu-koala-32bit from DVD, installed dfu-util and it did work fine. I would suspect that dfu-util or libusb is broken on some 64 bit systems. [1]: http://freeyourphone.de/portal_v1/viewtopic.php?f=5p=17806#p17806 Confirming this: I have Ubuntu 10.04 64-bit. I was unable to flash with dfu-util installed from the repositories, but the one that I had myself downloaded from somewhere, worked OK r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: MC Navi 0.2.10 released
Mike Crash wrote: All is here: http://www.gps-routes.info/index.php?name=Contentpa=showpagepid=1 If you have problems with boundary data, download boundary OSM file from Cloudmate at http://downloads.cloudmade.com e.g. http://downloads.cloudmade.com/north_america/united_states/washington/washington.osm.administrative.bz2 I have not tried for US, there are only boundaries for states (e.g. Washington), not the whole country, it may not have complete (closed polygon) boundaries. Also you should skip the boundaries step, but this may omit the addresses. I will do some experiments with USA and Germany in the (near) future. The development is not over, 0.2.11 is out with itinerary... If you do experiment with USA, here's a request for California. I just did the following: Downloaded: california.osm.administrative.bz2, california.osm.bz2 Extracted: both using bunzip2 Ran: osm2mcmap -bt 0 -bo boundary.mcb california.osm.administrative which created boundary.mcb without errors Ran: osm2mcmap -bi boundary.mcb -mo map.mcm california.osm which reports: Error opening file! Error parsing file california.osm as before. Is this the correct sequence? Thanks! Russell Dwiggins -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/MC-Navi-0-2-10-released-tp5158145p5272084.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi,
Thanks for your research into reclocking. I've tried the 533-CLK2
version on one of my freerunners and it seems to work well. I am trying
to put your changes into my qi build. You have one patch posted for the
500-83 uboot which wasn't too difficult to adapt to qi.
Do you have the PLL divider values (not sure if that is the correct
term) for the other speeds?
Ben
Here is is the diff for the 500mhz version with CLK 2 (be careful, might
fry your fr, etc)
diff --git a/src/cpu/s3c2442/gta02.c b/src/cpu/s3c2442/gta02.c
index e9bc0a3..aadb495 100644
--- a/src/cpu/s3c2442/gta02.c
+++ b/src/cpu/s3c2442/gta02.c
@@ -35,7 +35,7 @@
#define GTA02_DEBUG_UART 2
#define PCF50633_I2C_ADS 0x73
-#define BOOST_TO_400MHZ 1
+#define BOOST_TO_533MHZ 1
static int battery_condition_reasonable = 0;
@@ -85,12 +85,12 @@ const struct pcf50633_init pcf50633_init[] = {
{ PCF50633_REG_AUTOENA, 0x01 }, /* always on */
- { PCF50633_REG_DOWN1OUT,0x1b }, /* 1.3V (0x1b * .025V +
0.625V) */
+ { PCF50633_REG_DOWN1OUT,43 }, /* 1.3V (0x1b * .025V +
0.625V) */
{ PCF50633_REG_DOWN1ENA,0x02 }, /* enabled if GPIO1 =
HIGH */
{ PCF50633_REG_HCLDOOUT,21 }, /* 3.0V (21 * 0.1V +
0.9V) */
{ PCF50633_REG_HCLDOENA,0x01 }, /* ON by default*/
- { PCF50633_REG_DOWN1OUT,0x1b }, /* 1.3V (0x1b * .025V +
0.625V) */
+ { PCF50633_REG_DOWN1OUT,43 }, /* 1.3V (0x1b * .025V +
0.625V) */
{ PCF50633_REG_DOWN1ENA,0x02 }, /* enabled if GPIO1 =
HIGH */
{ PCF50633_REG_INT1M, 0x00 },
@@ -299,10 +299,12 @@ void port_init_gta02(void)
PCF50633_I2C_ADS,
PCF50633_REG_BVMCTL) 1);
if (battery_condition_reasonable) {
- /* change CPU clocking to 400MHz 1:4:8 */
+ /* change CPU clocking to 533MHz 1:6:12 */
- /* clock divide 1:4:8 - do it first */
- *CLKDIVN = 5;
+ /* clock divide 1:6:12 - do it first */
+ *CLKDIVN = 7;
+unsigned int* CAMDIVN = (unsigned int*)0x4C18;
+ *CAMDIVN |= (18);
/* configure UPLL */
*UPLLCON = ((88 12) + (4 4) + 2);
/* Magic delay: Page 7-19, seven nops between UPLL and
MPLL */
@@ -316,7 +318,7 @@ void port_init_gta02(void)
nop\n
);
/* configure MPLL */
- *MPLLCON = ((42 12) + (1 4) + 0);
+ *MPLLCON = ((117 12) + (1 4) + 1);
/* get debug UART working at 115kbps */
serial_init_115200_s3c24xx(GTA02_DEBUG_UART, 50 /*
50MHz */);
@@ -666,7 +668,9 @@ const struct board_api board_api_gta02 = {
.get_ui_keys = get_ui_keys_gta02,
.get_ui_debug = get_ui_debug_gta02,
.set_ui_indication = set_ui_indication_gta02,
console=tty0
console=ttySAC2,115200
init=/sbin/init
diff --git a/src/cpu/s3c2442/lowlevel_init.S
b/src/cpu/s3c2442/lowlevel_init.S
index 2a1654c..9ba45a5 100644
--- a/src/cpu/s3c2442/lowlevel_init.S
+++ b/src/cpu/s3c2442/lowlevel_init.S
@@ -105,22 +105,22 @@
#define B5_PMC 0x0 /* normal */
#define B6_MT 0x3 /* SDRAM */
-#define B6_Trcd0x1 /* 3clk */
+#define B6_Trcd0x0 /* 23clk */
#define B6_SCAN0x1 /* 9bit */
#define B7_SCAN0x1 /* 9bit */
#define B7_MT 0x3 /* SDRAM */
-#define B7_Trcd0x1 /* 3clk */
+#define B7_Trcd0x0 /* 2clk */
/* REFRESH parameter */
#define REFEN 0x1 /* Refresh enable */
#define TREFMD 0x0 /* CBR(CAS before RAS)/Auto
refresh */
-#define Trp0x1 /* 3clk */
-#define Trc0x3 /* 7clk */
-#define Tchr 0x2 /* 3clk */
-//#define REFCNT 1113/* period=15.6us,
HCLK=60Mhz, (2048+1-15.6*60) */
+#define Trp0x0 /* 2clk */
+#define Trc0x1 /* 5clk */
+#define Tchr 0x0 /* 3clk */
+//#define REFCNT 997 /* period=17.5us,
HCLK=60Mhz, (2048+1-15.6*60) */
#define REFCNT 997 /* period=17.5us, HCLK=60Mhz,
(2048+1-15.6*60) */
/**/
@@ -129,6 +129,7 @@ lowlevel_init:
ldr r0, =SMRDATA
ldr r1, =BWSCON /* Bus Width Status Controller */
+ mov r2, #0
add r2, r0, #13*4
0:
ldr r3, [r0], #4
@@ -158,5 +159,5 @@ SMRDATA:
.word
OLPC ARM
Interesting news: http://lwn.net/Articles/395544/ http://www.olpcnews.com/laptops/xo-175/multi-touch_sugar_arm_xo_laptop.html http://lists.sugarlabs.org/archive/iaep/2010-July/011319.html Some of the more interesting bits are: They're open-sourcing (almost all of) their embedded controller code and replacing the bits they can't. They're working on multi-touch stuff. They're hiring ARM hackers. -- bye, pabs http://bonedaddy.net/pabs3/ signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
