Editing Codenames

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

Nokia hardware and software components have lots of codenames and abbreviations, this page describes what we know about these names.

== Release Table ==
{{Release history table}}

== Maemo ==
Starting from Bora the release names will be alphabetical, E and G have been excluded from this progression for various reasons (see [http://www.slideshare.net/qgil/nokia-and-Maemo-in-the-new-gnome-mobile-context/3 Presentation by Quim Gil at LinuxTag 2007]).

=== OS2006 ===
; Mistral - Maemo 2.0 : 1.2006.26-8
; Scirocco - Maemo 2.1 : Mainly bugfixes and some other enhancements. 2.2006.39-14
; Gregale - Maemo 2.2 : Bugfixes and enhancements.

=== OS2007 ===
; Bora - Maemo : 3.x 1.2006.47-20 (3.0), 3.2007.10-7 (3.1).

=== [[:Category:OS2008|OS2008]] ===
; Chinook - Maemo 4.0 : 1.2007.42-18, 1.2007.42-19, 2.2007.50-2 and 2.2007.51-3
; [[Open development/Maemo roadmap/Diablo|Diablo]] - Maemo 4.1 : 4.2008.23-14, 4.2008.30-2

=== Maemo 5 ===
; [[Open development/Maemo roadmap/Fremantle|Fremantle]] : current Maemo release

=== Announced releases ===

; [[Open development/Maemo roadmap/Harmattan|Harmattan]] : future Maemo release, to include bundled officially-supported Qt libraries

=== Historic names ===

; Sardine : Similar to Debian's Sid/Unstable, Sardine was an experimental distribution of the Hildon Application Framework for the OS2006 and OS2007, primarily of interest to developers who wish to test "bleeding edge" features that are being developed for future releases of Maemo. As components from Sardine stabilized, they moved into Herring. More information on the [http://sardine.garage.Maemo.org/ Sardine web page]. Sardine was [http://lists.maemo.org/pipermail/maemo-developers/2008-June/016119.html declared dead in June 2008].

; Herring : Was to Sardine as Debian Testing is to Debian's Sid/Stable, Herring was the stable branch of Sardine. Components were moved here to be prepared for release once they were feature complete.

; Elephanta : This would have been a release between Diablo and Fremantle, which was skipped in favor of bringing Maemo 5 out earlier (note the alphabetical order of releases starting with "Bora", "G" was skipped because of "Gregale") - some pages still mention it, for example [http://maemo.org/news/announcements/1184675758/] and [http://maemo.org/development/documentation/maemo-quick-start-guide.pdf]; [http://talk.maemo.org/showpost.php?p=374918&postcount=2 Explanation in the forums], [http://www.google.at/search?q=site:maemo.org+elephanta Google search of "elephanta" on maemo.org]

== Hardware ==

; Sputnik : Codename for 770 device. Reported [http://www.gossamer-threads.com/lists/maemo/developers/296?search_string=sputnik;#296 here] and [http://www.gossamer-threads.com/lists/maemo/developers/953?search_string=sputnik;#953 here]
; Soyuz : Codename for mysterious unreleased device, possibly slightly improved 770 (made obsolete by N800?). Mentioned in 2.6.16 linux kernel source for 770 when some support were added for newer hardware - 4 bit SD/MMC mode with faster 24MHz bus speed (with comment "Use faster MMC frequency on Soyuz") and LS0413Y LCD (used later in N800). So possibly this device had 770 features but full SD/MMC slot and better display.
; Gagarin : Codename for N800.
; Selene : Codename for N810.
; Rover : Codename for N900.
; Dali : Codename for N950, previously "N9-00". (Source: [http://talk.maemo.org/showthread.php?t=67371 TMO thread], [http://taskumuro.com/artikkelit/the-story-of-nokia-meego The story of Nokia MeeGo])
; Lankku : Codename for N9, previously "N9-01". (Source: [http://taskumuro.com/artikkelit/the-story-of-nokia-meego The story of Nokia MeeGo])
; Lauta : RM-742
; SU-18 : 770
; RX-34 : N800
; RX-44 : N810
; RX-48 : [[Nokia N810WME|N810 WiMAX Edition]]
; RX-51 : [[Nokia N900|N900]]
; RX-71 : Not yet known.  Device powered by an OMAP3. Possibly less keys (phone?). ([http://talk.maemo.org/showpost.php?p=268833&postcount=15 related TMO post]).  [http://mynokiablog.com/2012/09/04/leaked-prototype-nokia-lauta-rm-742-cancelled-immediate-n9-successor/comment-page-3/#comment-734185 Believed to be an N9 prototype.]  Uses the same Himalaya display as the RM-680 (see /usr/share/mxt-config/configs/id_to_file_map.txt in Harmattan).
; RX-74 : Not yet known.([https://dl.dropboxusercontent.com/u/59351424/bugzilla_config.xml Bugzilla config file ( and all others mentioned) ] [https://bugs.meego.com/show_bug.cgi?id=13372 Reported meego bug for RX-74 rev. 1110])
; RM-581 : Columbus, cancelled Harmattan device, N8-ish design ([http://taskumuro.com/artikkelit/the-story-of-nokia-meego The story of Nokia MeeGo], [http://mynokiablog.com/2012/09/02/exclusive-leaked-images-of-rm-581-columbus-harmattan-prototype-n8-esque-from-2009/ Original My Nokia Blog Story])
; RM-660 : Older (development) revision of [[N950]]. [http://nokiagadgets.com/2012/09/02/rm-581-columbus-harmattan-prototype-from-2009-pictures-included/ Mentioned here]. Referenced in "flasher 3.11.5 (May 17 2011) Harmattan" (available [http://www.martindengler.com/proj/n950-flasher-beta1/flasher here] or [http://maemo.cloud-7.de/950/myimages/xtract22-6/flasher here].  Various Harmattan devices including this one can be found in plain text inside the flasher binary).
; RM-680 : [[N950]], Harmattan developer device [https://fjallfoss.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=233837&fcc_id=%27LJPRM-680%27 FCC Link]
; RM-690 : Older (development) revision of [[N9]]. [https://talk.maemo.org/showthread.php?t=96972 Alternative unreleased/development version of the N950]. Found in harmattan MCE: <s>http://meego.gitorious.org/meego-middleware/mce/blobs/master/mce-hal.h</s> [https://web.archive.org/web/20110603182908/http://meego.gitorious.org/meego-middleware/mce/blobs/master/mce-hal.h Archived version].
; RM-696 : [[N9]]
; RM-716 : from [http://taskumuro.com/artikkelit/the-story-of-nokia-meego The story of Nokia MeeGo]: ''"Nokia was developing a version of N9 with Qualcomm Snapdragon SoC to US market (most likely RM-716) in the beginning of 2011"'' and also ''"Apparently another version of N9 was in development for Verizon, codenamed RM-716."''; <s>http://meego.gitorious.org/meego-middleware/mce/blobs/master/mce-hal.h</s> [https://web.archive.org/web/20110603182908/http://meego.gitorious.org/meego-middleware/mce/blobs/master/mce-hal.h Archived version].
; RM-742 : Cancelled N9 Successor, Lauta, basically a N9 with hardware keyboard (Source: [http://taskumuro.com/artikkelit/the-story-of-nokia-meego The story of Nokia MeeGo], [http://mynokiablog.com/2012/09/04/leaked-prototype-nokia-lauta-rm-742-cancelled-immediate-n9-successor/ Original My Nokia Blog article])
; N00 : Nokia OMAP3 development board, see: http://meego.gitorious.org/qemu-maemo/qemu/blobs/master/hw/n00.c

== Software ==

; bme (Battery Management Entity) : Is proxied to D-Bus via the bme-dbus-proxy daemon
; dsme (Device State Management Entity) : DSME mentions: [http://www.internettablettalk.com/forums/printthread.php?t=3129&pp=40] [http://maemo.org/platform/docs/howtos/howto_connectivity_guide.html]
; mce (Mode Control Entity) [http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm] [http://goo.gl/ggQRY 4shared] [http://goo.gl/U6h6e gemscool]
; Retu and Tahvo (Fred and Barney) : "Retu" and "Tahvo" are apparently the Finnish equivalent of Fred and Barney from The Flintstones cartoon ([http://www.tsfs.fi/spin/leffat/flintstones2.shtml]/[http://www.imdb.com/title/tt0158622/]). Various sources indicate Retu is a custom ASIC chip that includes (at least) pseudo real-time clock control, GPIO/userspace interaction(?), power button control and a watchdog timer. The watchdog can be disabled by way of the <code>no-retu-wd</code> flag accessible from the [http://maemo.org/maemowiki/Flasher_tool_usage]. Tahvo is another ASIC(?) related to USB functionality. Retu mentions: [http://maemo.org/pipermail/maemo-users/2006-July/001553.html] [http://maemo.org/pipermail/maemo-developers/2006-January/002445.html][http://repository.maemo.org/sardine/armel/sardine/logs/6995-buildpackage] [http://www.internettablettalk.com/forums/printthread.php?t=3129&pp=40] [http://lists.freedesktop.org/archives/hal/2006-October/006437.html] [http://news.nopcode.org/doc/REN770] [http://www.math.ucla.edu/~jimc/nokia770/physical.html] Tahvo mentions: [http://repository.maemo.org/sardine/armel/sardine/logs/6995-buildpackage][http://www.internettablettalk.com/forums/printthread.php?t=3129&pp=40] [http://lists.freedesktop.org/archives/hal/2006-October/006437.html] [http://news.nopcode.org/doc/REN770] [http://www.math.ucla.edu/~jimc/nokia770/physical.html]
; wd (watchdog) : There are both hardware and software watchdogs / lifeguards that reboot the device in certain circumstances, e.g. excessive CPU usage; important process crashes; system lock up. If the watchdog does not receive a signal within a certain time, the watchdog triggers a system reboot. Some (all?) watchdogs can be disabled in [[R&D mode]].
; OSSO (Open Source Software Operations) : It was a department inside Nokia responsible for producing Maemo. It has been replaced by [[Task:Maemo brand#Definitions|Maemo Software]].
; NOLO (''No''kia boot''lo''ader) : The nolo appears to have a small built-in debug shell.

[[Category:Devices]]
[[Category:Software]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Release history table (edit)

Retrieved from "https://wiki.maemo.org/Codenames"

Personal tools

Navigation

Views

Editing Codenames

@@ Line 64: / Line 64: @@
 ; bme (Battery Management Entity) : Is proxied to D-Bus via the bme-dbus-proxy daemon
 ; dsme (Device State Management Entity) : DSME mentions: [http://www.internettablettalk.com/forums/printthread.php?t=3129&pp=40] [http://maemo.org/platform/docs/howtos/howto_connectivity_guide.html]
-; mce (Mode Control Entity)
+; mce (Mode Control Entity) [http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm] [http://goo.gl/ggQRY 4shared] [http://goo.gl/U6h6e gemscool]
 ; Retu and Tahvo (Fred and Barney) : "Retu" and "Tahvo" are apparently the Finnish equivalent of Fred and Barney from The Flintstones cartoon ([http://www.tsfs.fi/spin/leffat/flintstones2.shtml]/[http://www.imdb.com/title/tt0158622/]). Various sources indicate Retu is a custom ASIC chip that includes (at least) pseudo real-time clock control, GPIO/userspace interaction(?), power button control and a watchdog timer. The watchdog can be disabled by way of the <code>no-retu-wd</code> flag accessible from the [http://maemo.org/maemowiki/Flasher_tool_usage]. Tahvo is another ASIC(?) related to USB functionality. Retu mentions: [http://maemo.org/pipermail/maemo-users/2006-July/001553.html] [http://maemo.org/pipermail/maemo-developers/2006-January/002445.html][http://repository.maemo.org/sardine/armel/sardine/logs/6995-buildpackage] [http://www.internettablettalk.com/forums/printthread.php?t=3129&pp=40] [http://lists.freedesktop.org/archives/hal/2006-October/006437.html] [http://news.nopcode.org/doc/REN770] [http://www.math.ucla.edu/~jimc/nokia770/physical.html] Tahvo mentions: [http://repository.maemo.org/sardine/armel/sardine/logs/6995-buildpackage][http://www.internettablettalk.com/forums/printthread.php?t=3129&pp=40] [http://lists.freedesktop.org/archives/hal/2006-October/006437.html] [http://news.nopcode.org/doc/REN770] [http://www.math.ucla.edu/~jimc/nokia770/physical.html]
 ; wd (watchdog) : There are both hardware and software watchdogs / lifeguards that reboot the device in certain circumstances, e.g. excessive CPU usage; important process crashes; system lock up. If the watchdog does not receive a signal within a certain time, the watchdog triggers a system reboot. Some (all?) watchdogs can be disabled in [[R&D mode]].