Openmoko - User contributions [en]

Who is Who

2009-07-29T09:34:02Z

Jserv: Added jserv

If you subscribe to a mailing list or join an IRC channel, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?
This page should serve as a list of community members and their areas of expertise.

= Community members =

IRC nicknames are in brackets after each name.

== [[Kernel]] ==

* Luca Capello
* Mike Westerhof (mwester)
* Nelson Castillo (Arhuaco)
* Paul Fertser (PaulFertser)
* Timo Juhani Lindfors (lindi-)
* Rod Whitby (rwhitby)
* Werner Almesberger (wpwrak)

== [[FSO]] (freesmartphone.org) ==
* Michael Lauer ([[user:Mickey|Mickey]])
* Jan Luebbe (Shoragan)
* Daniel Willmann (Alphaone)
* Stefan Schmidt

== [[Om2009]] ==
* Angus Ainslie (nytowl)

== [[SHR]] ==
* Julien Cassignol (Ainulindale)
* David Kozub (dent)
* Klaus Kurzmann (mrmoku)
* Wolfgang Kroener (azog)
* Hire
* David Wagner (deubeuliou)
* Montgoss
* Dolf
* Quickdev (RIP)
* Sebastian Spaeth (spaetz)
* Cameron Frazier (Toaster)
* Didier (ptitjes)
* Yorick (yoyo)
* Tom (Tasn)
* Morphis
* Hiciu
* Sebastian Krzyszkowiak (dos)
* Stian Skjelstad (mywave)
* Tilman Sauerbeck (tilman)
* Mike Westerhof (mwester)
* Bobby Martin (wurp2)

== [[hackable:1]] ==
* Marcus Bauer (iscape)
* Jérôme Blondon (jbl2024)
* Sébastien Bocahu (zecrazytux)
* Pierre Pronchery (khorben)
* David Wagner (deubeuliou)

== [[Paroli]] ==
* Mirko Lindner (mirko)

== [[Smedia_Glamo_3362#Hardware_Accelerated_Projects|X.org / Glamo (Graphics subsystem)]] ==
* Lars-Peter Clausen (larsc)
* Thomas White (Weiss)
* Andreas Pokorny (DieMumiee)
* Timo Juhani Lindfors (lindi-)

== [http://activationrecord.net/radekp/openmoko/qtmoko/ QtMoko] ==
* Lorn Potter (lpotter)
* Radekp
* Franky Van Liedekerke (liedekef)
* Fabio Alessandro Locati (fale)

== [[MokoMakefile]] ==
* Rod Whitby (rwhitby)

== [[gta02-core]] ==
(community project to create a new hardware revision of the gta02 hardware)
* Werner Almesberger (wpwrak)

= Officials members of the Openmoko Team =

''Note: This is severly outdated. Most of the people listed here as officials do not work for Openmoko anymore.''

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || {{user|allen_chang}} || || GTA Hardware Engineer ('''Left Openmoko''')
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || {{user|warmcat}} || agreen || Software Developer/kernel maintainer ('''Left Openmoko'''. Here for archives.)
|-
| Anthony Chang || || || || Software Developer ('''Left Openmoko''')
|-
| Candy Chou || || {{user|candy_chou}} || || GTA/HXD Hardware Engineer ('''Left Openmoko''')
|-
| Dkay Chen || || {{user|dkay_chen}} || || GTA/HXD Hardware Engineer ('''Left Openmoko''')
|-
| Jeremy Chang || || || || Software Developer ('''Left Openmoko''')
|-
| Jollen Chen || || || || Marketing('''Left Openmoko''')
|-
| Tick Chen || || || || Software Developer('''Left Openmoko''')
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || || ('''Left Openmoko'''. Here for archives.)
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer ('''Left Openmoko''')
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer ('''Left Openmoko''')
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA || ('''Left Openmoko''')
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || ('''Left Openmoko'''. Here for archives.)
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer ('''Left Openmoko''')
|-
| Wendy Hung || || || || Testing ('''Left Openmoko''')
|-
| Regina Kim || || || || Testing ('''Left Openmoko''')
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer ('''Left Openmoko'''. Freelancer - maintains FSO.)
|-
| John Lee || || || || Software Developer ('''Left Openmoko''')
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer ('''Left Openmoko''')
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || {{user|liuxf}} || || Software Developer ('''Left Openmoko''')
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time) ('''Left Openmoko''')
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing ('''Left Openmoko''')
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Shawn Lin || || {{user|shawn_lin}} || || RF Engineer('''Left Openmoko''')
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer ('''Left Openmoko'''. Here for archives.)
|-
| Michael Shiloh || ''michael'' at openmoko dot ''org'' || {{user|Michaelshiloh}} || || Head of Developer Relations ('''Left Openmoko'''. Here for archives.)
|-
| Werner Almesberger || ''werner'' at openmoko dot ''org'' || || || ('''Left Openmoko'''. Here for archives.)
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering ('''Left Openmoko''')
|-
| Joachim Steiger || ''roh'' at openmoko dot ''org'' || {{user|Roh}} || roh || Central Services ('''Left Openmoko'''. Here for archives.)
|-
| Teenie Hung || || {{user|teenie_hung}} || || Operations Head ('''Left Openmoko''')
|-
| Harry Tsai || ''tsaiharry'' at gmail dot ''com'' || || || long time ago he was Vice President of Sales in Openmoko, but that is past. ('''Left Openmoko'''. Here for archives.)
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Project manager (gta01/02), software developer ('''Left Openmoko'''. Here for archives.)
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || {{user|Coolcat}} || || Used to Wiki editor . volunteer now. ('''Left Openmoko''')
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || ('''Left Openmoko'''. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer ('''Left Openmoko'''. Here for archives.)
|-
| Thomas Wood || || {{user|ThomasWood}} || || Was hired as part of OpenedHand. ('''No longer employed by Openmoko''')
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer ('''Left Openmoko''')
|-
| Erin Yeh || ''erin_yueh'' at openmoko dot ''org''||{{user|erin}} || || Software Developer ('''Left Openmoko''')
|-
| Mirko Lindner || ''mirko'' at openmoko dot ''com''||{{user|Vegyraupe}} || mirko-paroli || Software Developer (om2009/paroli) ('''Left Openmoko''')
|-
| Angus Ainslie || ''nytowl'' at openmoko dot ''org''||{{user|Nytowl}} || nytowl || Distribution maintainer (om2009) ('''Left Openmoko''')
|-
| Ray Chao || ''ray_chao'' at openmoko dot ''org''||{{user|Ray}} || jc || System Administrator ('''Left Openmoko''')
|-
| Chelsea Wei || ''chelsea'' at openmoko dot ''com''||{{user|Chelsea}} || || ('''Left Openmoko''')
|-
| Jim Huang || ''jserv'' at openmoko dot ''org''||{{user|jserv}} || || ('''Left Openmoko''')
|}

[[Category:Openmoko Inc]]

Regular Training Programs

2008-03-23T00:36:05Z

Jserv: /* Programs */

== Introduction ==
To practice and improve the skills for team work, every software engineer at openmoko Taipei office would attend weekly training / experience sharing events. and be one of the speakers of the regular events by turns.

== Orientations ==
The orientations and topics are dedicated to the purpose as following:
# [[OpenMoko_FOSS_Tools_Introduction]]
# Manufacturing process and Factory testing procedure
# Case study for OpenMoko software architecture and designs
# Phone functionality and inter-connectivity
# Recent development progress of [[OpenLab]]

== Programs ==
Rough schedule for each of the events/programs done and planned by openmoko software team as following:

{|
! Topic !! Speaker !! Date !! Summary / Notes !! Slides / Reference Materials
|- style="background-color:#eeeedd;"
! colspan="5"|Regular Training Program
|-
|Introduction to Autotools || [[User:jserv|Jim Huang]] || Jul 8, 2007 || Brief introduction to GNU Autotools (automake, autoconf, and libtool), which are useful for cross development and diverse environments. || [[Media:moko-autotools.pdf|moko-autotools.pdf]]
|-
|Text Layout in GTK+ World || olv || Jul 20, 2007 || An introduction to pango and text layout. || [[Media:Text_layout_in_gtk.pdf|Text_layout_in_gtk.pdf]]
|-
|Introduction to GSM Multiplexer || Sweden Hsu ||Jul 27, 2007 || Overview to GSM Multiplexer (GSM 07.10) and analyze current implementation of OpenMoko and Linux kernel support.
|-
|OpenMoko GSM/GPRS Overview || [[User:Jserv|Jim Huang]] || Aug 3, 2007 || Overview to OpenMoko gsmd/libgsmd/gsmmux for GSM/GPRS functions in the aspect of system-level architecture and designs. || [[Media:openmokogsm.pdf|openmokogsm.pdf]]
|-
|Factory and Production Test|| Nod Huang || Aug 24, 2007 || Experience for GTA01 production in Suzhou. The presentation will cover testing procedure, related software, and possible issues. Also, he will share his thoughts about GTA01/HXD8/GTA02 production considerations. ||[[Media:Dash_Production_Flow.pdf|Dash_Production_Flow.pdf]]
|-
|3G Feature Phone Case Study || Erin Yuen || Sep 7, 2007 || Take BenQ 3G Feature Phone design and production as case study. || [[Media:Benq_experiences_0907.pdf|BenQ_experiences.pdf]]
|-
|Three levels of Fun in Graphics || olv || Sep 14, 2007 || There are three things to do in designing a GUI toolkit: graphics, human interaction, and widgets... || [[Media:graphics_fun.pdf|graphics_fun.pdf]]
|-
|Automatic Approaches for Building, Deployment, and Testing || [[User:John|John Lee]] || Sep 21, 2007 || A brief introduction to the current automatic build/deploy/test method. || [[Media:auto.pdf|auto.pdf]]
|-
|Case Study: Linux-based Skype/GSM dual-mode phone || IFan "Tick" Chen || Sep 28, 2007 || Share the experience of Linux-based Skype/GSM dual-mode phone project inside Compal Communications Inc. as case study. || [[Media:Dual.pdf|dual.pdf]]
|-
|Graphics and stuff (TBD) || Raster || Nov 02, 2007 || Will talk about Graphics and stuff || TBA
|-
|EFL introduction || Jeremy Chang || Nov 16, 2007 || Enlightenment Foundation Libraries overview . || [[Media:EFL_intro.pdf|EFL introduction]]
|-
|Introduction to Boot and Application Launching Time Optimizations for Linux-based products || [[User:Jserv|Jim Huang]] || Nov 23, 2007 || How fast do we need in product expectations? Analyzing boot time and application launching. Optimizations to boot time. Tweaking in user-space. ||
|-
|Introduction of the PBE|| [[User:Nod|Nod Huang]] || Nov 30, 2007 || 1. PBE file system 2. how to create a new package in PBE 3. PBE file system 4. how to create a new package in PBE || [[Media:PBE.pdf|PBE.pdf]]
|-
|Power consumption in kernel|| [[User:Willie|Willie Chen]] || Dec 7, 2007 || 1. How to reduce power consumption 2. Utilities 3. GTA01/GTA02 issues || [[Media:power.pdf|Power]]
|-
|ARM Exception System Introduction (HXD8 example)|| [[User:Alec|Alec Tsai]] || Jan 11, 2008 || 1. Exceptions 2. System Memory Map || [[Media:Exception.pdf|Exception]]
|-
| Object files Introduction|| [[User:tick | Tick]] || Feb, 22 2008 || A brief introductions to a.out and ELF || [[Media:elf.pdf| ELF]]
|-
| Kboot || [[User:werner| Werner]] || Feb, 29 2009 || An introduction and discussion about Kboot ||
|-
| Small introduction to Qtopia || [[User: zecke | Zecke]] || Mar, 07 2008 || A small introduction to Qtopia || [[Media: qtopia.pdf | Qtopia]]
|-
| Some daemons in OM-2007.2|| [[User:olv | olv]] || Mar, 14 2008 || A brief introduction to daemons running behind OM-2007.2 || [[Media:om-daemons.pdf| om-daemons.pdf]]
|-
| Introduce to Audio || [[User:graeme | Graeme]] || Mar, 21 2008 || An introduction to the Audio system || [[Media: audio_presentation.pdf | Audio]]
|}

[[Category:Training| ]]

User:Jserv

2008-03-23T00:35:17Z

Jserv:

Jim Huang was born in Taiwan, and he usually uses "jserv" as his nickname in internet communication, including IRC, BBS, mailing-list, etc. Currently, he was working on software development for openmoko.

Regular Training Programs

2008-03-23T00:29:15Z

Jserv: /* Introduction */

== Introduction ==
To practice and improve the skills for team work, every software engineer at openmoko Taipei office would attend weekly training / experience sharing events. and be one of the speakers of the regular events by turns.

== Orientations ==
The orientations and topics are dedicated to the purpose as following:
# [[OpenMoko_FOSS_Tools_Introduction]]
# Manufacturing process and Factory testing procedure
# Case study for OpenMoko software architecture and designs
# Phone functionality and inter-connectivity
# Recent development progress of [[OpenLab]]

== Programs ==
Rough schedule for each of the events/programs done and planned by [[Software_Team]] as following:

{|
! Topic !! Speaker !! Date !! Summary / Notes !! Slides / Reference Materials
|- style="background-color:#eeeedd;"
! colspan="5"|Regular Training Program
|-
|Introduction to Autotools || [[User:jserv|Jim Huang]] || Jul 8, 2007 || Brief introduction to GNU Autotools (automake, autoconf, and libtool), which are useful for cross development and diverse environments. || [[Media:moko-autotools.pdf|moko-autotools.pdf]]
|-
|Text Layout in GTK+ World || olv || Jul 20, 2007 || An introduction to pango and text layout. || [[Media:Text_layout_in_gtk.pdf|Text_layout_in_gtk.pdf]]
|-
|Introduction to GSM Multiplexer || Sweden Hsu ||Jul 27, 2007 || Overview to GSM Multiplexer (GSM 07.10) and analyze current implementation of OpenMoko and Linux kernel support.
|-
|OpenMoko GSM/GPRS Overview || [[User:jserv|Jim Huang]] || Aug 3, 2007 || Overview to OpenMoko gsmd/libgsmd/gsmmux for GSM/GPRS functions in the aspect of system-level architecture and designs. || [[Media:openmokogsm.pdf|openmokogsm.pdf]]
|-
|Factory and Production Test|| Nod Huang || Aug 24, 2007 || Experience for GTA01 production in Suzhou. The presentation will cover testing procedure, related software, and possible issues. Also, he will share his thoughts about GTA01/HXD8/GTA02 production considerations. ||[[Media:Dash_Production_Flow.pdf|Dash_Production_Flow.pdf]]
|-
|3G Feature Phone Case Study || Erin Yuen || Sep 7, 2007 || Take BenQ 3G Feature Phone design and production as case study. || [[Media:Benq_experiences_0907.pdf|BenQ_experiences.pdf]]
|-
|Three levels of Fun in Graphics || olv || Sep 14, 2007 || There are three things to do in designing a GUI toolkit: graphics, human interaction, and widgets... || [[Media:graphics_fun.pdf|graphics_fun.pdf]]
|-
|Automatic Approaches for Building, Deployment, and Testing || [[User:John|John Lee]] || Sep 21, 2007 || A brief introduction to the current automatic build/deploy/test method. || [[Media:auto.pdf|auto.pdf]]
|-
|Case Study: Linux-based Skype/GSM dual-mode phone || IFan "Tick" Chen || Sep 28, 2007 || Share the experience of Linux-based Skype/GSM dual-mode phone project inside Compal Communications Inc. as case study. || [[Media:Dual.pdf|dual.pdf]]
|-
|Graphics and stuff (TBD) || Raster || Nov 02, 2007 || Will talk about Graphics and stuff || TBA
|-
|EFL introduction || Jeremy Chang || Nov 16, 2007 || Enlightenment Foundation Libraries overview . || [[Media:EFL_intro.pdf|EFL introduction]]
|-
|Introduction to Boot and Application Launching Time Optimizations for Linux-based products || [[User:jserv|Jim Huang]] || Nov 23, 2007 || How fast do we need in product expectations? Analyzing boot time and application launching. Optimizations to boot time. Tweaking in user-space. ||
|-
|Introduction of the PBE|| [[User:Nod|Nod Huang]] || Nov 30, 2007 || 1. PBE file system 2. how to create a new package in PBE 3. PBE file system 4. how to create a new package in PBE || [[Media:PBE.pdf|PBE.pdf]]
|-
|Power consumption in kernel|| [[User:Willie|Willie Chen]] || Dec 7, 2007 || 1. How to reduce power consumption 2. Utilities 3. GTA01/GTA02 issues || [[Media:power.pdf|Power]]
|-
|ARM Exception System Introduction (HXD8 example)|| [[User:Alec|Alec Tsai]] || Jan 11, 2008 || 1. Exceptions 2. System Memory Map || [[Media:Exception.pdf|Exception]]
|-
| Object files Introduction|| [[User:tick | Tick]] || Feb, 22 2008 || A brief introductions to a.out and ELF || [[Media:elf.pdf| ELF]]
|-
| Kboot || [[User:werner| Werner]] || Feb, 29 2009 || An introduction and discussion about Kboot ||
|-
| Small introduction to Qtopia || [[User: zecke | Zecke]] || Mar, 07 2008 || A small introduction to Qtopia || [[Media: qtopia.pdf | Qtopia]]
|-
| Some daemons in OM-2007.2|| [[User:olv | olv]] || Mar, 14 2008 || A brief introduction to daemons running behind OM-2007.2 || [[Media:om-daemons.pdf| om-daemons.pdf]]
|-
| Introduce to Audio || [[User:graeme | Graeme]] || Mar, 21 2008 || An introduction to the Audio system || [[Media: audio_presentation.pdf | Audio]]
|}

[[Category:Training| ]]

Gsmd/document

2007-10-08T16:09:25Z

Jserv: /* Gsmd */

== Overview ==
=== What is gsmd ===
'''Gsmd''' is a daemon that handles the communications between applications and GSM modem.
Applications manipulate gsmd through the APIs defined in '''libgsmd'''.
libgsmd communicates with gsmd through unix socket, and modem goes through UART.
The diagram is as following.

http://lh6.google.com/ticktock35/RwDCAWdUPEI/AAAAAAAAAD4/wBrRLv-1oyE/s400/gsmd_overview.jpg

== Gsmd ==
GSMD is an event-driven daemon. Each event shall have a response and will pass through the function '''gsmd_select_main()''' in which finding and then executing their correspond callback functions.

The last part of gsmd '''main''' function enters a infinite loop, trying to call '''gsmd_select_main'''.

while(1) {
int ret = gsmd_select_main();
...
}

=== gsmd_select_main() ===
gsmd_select_main this is core of the callback function scheme. All devices, gsmd monitors and linked in a [http://wiki.kldp.org/wiki.php/LinkedList list], are described as a struct '''gsmd_fd''', and gsmd_select_main will [http://swoolley.org/man.cgi/select select] them.
Once an event comes out from one of the devices, gsmd_select_main will try to call it's '''callback function''' that devices registered.

int gsmd_select_main()
{
struct gsmd_fd *ufd, *ufd2;
fd_set readset, writeset, exceptset;
int i;

FD_ZERO(&readset);
FD_ZERO(&writeset);
FD_ZERO(&exceptset);

/* prepare read and write fdsets */
llist_for_each_entry(ufd, &gsmd_fds, list) {
if (ufd->when & GSMD_FD_READ)
FD_SET(ufd->fd, &readset);

if (ufd->when & GSMD_FD_WRITE)
FD_SET(ufd->fd, &writeset);

if (ufd->when & GSMD_FD_EXCEPT)
FD_SET(ufd->fd, &exceptset);
}

'''i = select(maxfd+1, &readset, &writeset, &exceptset, NULL);'''
if (i > 0) {
/* call registered callback functions */
llist_for_each_entry_safe(ufd, ufd2, &gsmd_fds, list) {
int flags = 0;

if (FD_ISSET(ufd->fd, &readset))
flags |= GSMD_FD_READ;

if (FD_ISSET(ufd->fd, &writeset))
flags |= GSMD_FD_WRITE;

if (FD_ISSET(ufd->fd, &exceptset))
flags |= GSMD_FD_EXCEPT;

if (flags)
''' ufd->cb(ufd->fd, flags, ufd->data);'''
}
}
return i;
}

==== gsmd_fd ====
struct gsmd_fd {
struct llist_head list;
int fd; /* file descriptor */
unsigned int when;
'''int (*cb)(int fd, unsigned int what, void *data);'''
void *data; /* void * to pass to callback */
};

When there are anything change in fd, the gsmd_select_main will detect them and try to call it's callback function cb.

That means if you redirect the callback function cb to another implementation, the gsmd will behave very differently.

==== gsmd_atcmd ====
struct gsmd_atcmd {
'''struct llist_head list;'''
void *ctx;
'''int (*cb)(struct gsmd_atcmd *cmd, void *ctx, char *resp);'''
char *resp;
int32_t ret;
u_int32_t buflen;
u_int16_t id;
u_int8_t flags;
char *cur;
char buf[];
};

=== callback functions ===
Gsmd opens at least one devices. One is uart to modem and others are the Unix socket, communicating with libgsmd.

'''atcmd_select_cb''' is the default callback function that dealing the UART to the modem. It will handle sending AT commands to GSM modem or receive whatever return from modem and send them into parser.

The default parser callback function of UART (to modem) is '''ml_parse''', in which dealing with reading the response of modem dispatch the correct call back function to handle the response.

==== atcmd_select_cb ====

===== atcmd_fill =====

===== atcmd_submit =====

==== ml_parse ====
ml_parse is the parser callback function that handles:
* Initial GSM Modem
* handle correspond AT command callback
* handle notification callback

===== Initialize GSM Modem =====
When the modem firmware is ready to initial, it will send '''AT-Command Interpreter ready''' to gsmd. If ml_parse get this string, gsmd will try to initialize the modem.
if (strlen(buf) == 0 ||
!strcmp(buf, "'''AT-Command Interpreter ready'''")) {
g->interpreter_ready = 1;
''' gsmd_initsettings(g);'''
gmsd_alive_start(g);
return 0;
}
What modem write to gsmd will put in "buf". And if the contents of the "buf" is "AT-Command Interpreter ready" the automatic gsmd initialize will start.

gsmd_alive_start is a scheme that gsmd detect if the modem is still alive or not. It will send an "AT" to modem periodically, and check the modem's response.

===== handle correspond AT command call back =====
===== handle notification call back =====

== libgsmd ==
'''libgsmd''' is a library with C language API for application programs. Programs using this library can use the phone, e.g. make phone calls, receive incoming calls, register to the network, etc.

===='''libgsmd_sms'''====

'''libgsmd_sms''' is about all related SMS functions. The API is as below:

* '''List Messages''': can list all SMS message by 'stat' value
extern int lgsm_sms_list(struct lgsm_handle *lh, enum gsmd_msg_sms_type stat);

* '''Read Message''': It can read one SMS message by 'index' value
extern int lgsm_sms_read(struct lgsm_handle *lh, int index);

* '''Delete Message''': can delete one SMS message by 'index' and 'del_flag' values
extern int lgsm_sms_delete(struct lgsm_handle *lh, const struct lgsm_sms_delete *sms_del);

* '''Send Message''': can send one SMS message
extern int lgsm_sms_send (struct lgsm_handle *lh, const struct lgsm_sms *sms);

* '''Write Message to Memory''': can write one SMS message to preferred memory
extern int lgsm_sms_write (struct lgsm_handle *lh, const struct lgsm_sms_write *sms_write);

* '''Retrieve SMS storage Information''': retrieve all SMS storage information
extern int lgsm_sms_get_storage (struct lgsm_handle *lh);

* '''Set preferred SMS storage''': can set SMS preferred storage
extern int lgsm_sms_set_storage (struct lgsm_handle *lh, enum ts0705_mem_type mem1, enum ts0705_mem_type mem2, enum ts0705_mem_type mem3);

* '''Retrieve current default service center address'''
extern int lgsm_sms_get_smsc(struct lgsm_handle *lh);

* '''Set new default service center address'''
extern int lgsm_sms_set_smsc(struct lgsm_handle *lh, const char *number);

* '''Packing of 7-bit characters'''
extern int packing_7bit_character(const char *src, struct lgsm_sms *dest);

===='''libgsmd_phonebook'''====

'''libgsmd_phonebook''' is about all related phonebook functions. The API is as below:

* '''Store''' a specific phonebook entry 'pb' into phone
extern int lgsm_pb_set_entry(struct lgsm_handle *lh, struct lgsm_pb_entry *pb);

* '''List''' of supported phonebook memory storage
extern int lgsm_pb_list_storage(struct lgsm_handle *lh);

* '''Select''' phonebook memory storage
extern int lgsm_pb_set_storage(struct lgsm_handle *lh, char *storage);

* '''Find phonebook entires''' which alphanumeric filed start with string <findtext>
extern int lgsm_pb_find_entry(struct lgsm_handle *lh, const struct lgsm_phonebook_find *pb_find);

* '''Read phonebook entry''' in location number index
extern int lgsm_pb_read_entry(struct lgsm_handle *lh, int index);

* '''Read phonebook entries''' in location number range
extern int lgsm_pb_read_entries(struct lgsm_handle *lh, const struct lgsm_phonebook_readrg *pb_readrg);

* '''Delete''' phonebook entry in location index
extern int lgsm_pb_del_entry(struct lgsm_handle *lh, int index);

* '''Write''' phonebook entry in location
extern int lgsm_pb_write_entry(struct lgsm_handle *lh, const struct lgsm_phonebook *pb);

* '''Get the location range/nlength/tlength supported '''
extern int lgsm_pb_get_support(struct lgsm_handle *lh);

== libgsmd-tool ==
[http://wiki.openmoko.org/wiki/Gsmd#libgsmd-tool Please reference to here]

== Debug Log ==
== To-do ==

Gsmd/document

2007-10-08T15:51:54Z

Jserv: /* What is gsmd */

== Overview ==
=== What is gsmd ===
'''Gsmd''' is a daemon that handles the communications between applications and GSM modem.
Applications manipulate gsmd through the APIs defined in '''libgsmd'''.
libgsmd communicates with gsmd through unix socket, and modem goes through UART.
The diagram is as following.

http://lh6.google.com/ticktock35/RwDCAWdUPEI/AAAAAAAAAD4/wBrRLv-1oyE/s400/gsmd_overview.jpg

== Gsmd ==
GSMD is a event driven daemon. Each event shall has a response.
Every event will pass through the '''gsmd_select_main()''' in which finding and executing their correspond call back functions.

The last part of gsmd '''main''' function enters a infinite loop, trying to call '''gsmd_select_main'''.

while(1) {
int ret = gsmd_select_main();
...
}

=== gsmd_select_main() ===
gsmd_select_main this is core of the call back function scheme. All devices, gsmd monitors and linked in a [http://wiki.kldp.org/wiki.php/LinkedList list], are described as a struct '''gsmd_fd''', and gsmd_select_main will [http://swoolley.org/man.cgi/select select] them.
Once an event comes out from one of the devices, gsmd_select_main will try to call it's '''call back function''' that devices registered.

int gsmd_select_main()
{
struct gsmd_fd *ufd, *ufd2;
fd_set readset, writeset, exceptset;
int i;

FD_ZERO(&readset);
FD_ZERO(&writeset);
FD_ZERO(&exceptset);

/* prepare read and write fdsets */
llist_for_each_entry(ufd, &gsmd_fds, list) {
if (ufd->when & GSMD_FD_READ)
FD_SET(ufd->fd, &readset);

if (ufd->when & GSMD_FD_WRITE)
FD_SET(ufd->fd, &writeset);

if (ufd->when & GSMD_FD_EXCEPT)
FD_SET(ufd->fd, &exceptset);
}

'''i = select(maxfd+1, &readset, &writeset, &exceptset, NULL);'''
if (i > 0) {
/* call registered callback functions */
llist_for_each_entry_safe(ufd, ufd2, &gsmd_fds, list) {
int flags = 0;

if (FD_ISSET(ufd->fd, &readset))
flags |= GSMD_FD_READ;

if (FD_ISSET(ufd->fd, &writeset))
flags |= GSMD_FD_WRITE;

if (FD_ISSET(ufd->fd, &exceptset))
flags |= GSMD_FD_EXCEPT;

if (flags)
''' ufd->cb(ufd->fd, flags, ufd->data);'''
}
}
return i;
}

==== gsmd_fd ====
struct gsmd_fd {
struct llist_head list;
int fd; /* file descriptor */
unsigned int when;
'''int (*cb)(int fd, unsigned int what, void *data);'''
void *data; /* void * to pass to callback */
};

When there are anything change in fd, the gsmd_select_main will detect them and try to call it's call back function cb.

That means if you redirect the cb to another implementation, the gsmd will behave very differently.

==== gsmd_atcmd ====
struct gsmd_atcmd {
'''struct llist_head list;'''
void *ctx;
'''int (*cb)(struct gsmd_atcmd *cmd, void *ctx, char *resp);'''
char *resp;
int32_t ret;
u_int32_t buflen;
u_int16_t id;
u_int8_t flags;
char *cur;
char buf[];
};

=== call back functions ===
Gsmd opens at least one devices. One is uart to modem and others are the Unix socket, communicating with libgsmd.

'''atcmd_select_cb''' is the default call back function that dealing the uart to the modem. It will handle sending AT command to modem or receive whatever return from modem and send them into parser.

The default parser call back function of uart (to modem) is '''ml_parse''', in which dealing with reading the response of modem dispatch the correct call back function to handle the response.

==== atcmd_select_cb ====

===== atcmd_fill =====

===== atcmd_submit =====

==== ml_parse ====
ml_parse is the parser call back function that handles:
* Initial GSM Modem
* handle correspond AT command call back
* handle notification call back

===== initial GSM Modem =====
When the modem firmware is ready to initial, it will send '''AT-Command Interpreter ready''' to gsmd. If ml_parse get this string, gsmd will try to initialize the modem.
if (strlen(buf) == 0 ||
!strcmp(buf, "'''AT-Command Interpreter ready'''")) {
g->interpreter_ready = 1;
''' gsmd_initsettings(g);'''
gmsd_alive_start(g);
return 0;
}
What modem write to gsmd will put in "buf". And if the contents of the "buf" is "AT-Command Interpreter ready" the automatic gsmd initialize will start.

gsmd_alive_start is a scheme that gsmd detect if the modem is still alive or not. It will send an "AT" to modem periodically, and check the modem's response.

===== handle correspond AT command call back =====
===== handle notification call back =====

== libgsmd ==
'''libgsmd''' is a library with C language API for application programs. Programs using this library can use the phone, e.g. make phone calls, receive incoming calls, register to the network, etc.

===='''libgsmd_sms'''====

'''libgsmd_sms''' is about all related SMS functions. The API is as below:

* '''List Messages''': can list all SMS message by 'stat' value
extern int lgsm_sms_list(struct lgsm_handle *lh, enum gsmd_msg_sms_type stat);

* '''Read Message''': It can read one SMS message by 'index' value
extern int lgsm_sms_read(struct lgsm_handle *lh, int index);

* '''Delete Message''': can delete one SMS message by 'index' and 'del_flag' values
extern int lgsm_sms_delete(struct lgsm_handle *lh, const struct lgsm_sms_delete *sms_del);

* '''Send Message''': can send one SMS message
extern int lgsm_sms_send (struct lgsm_handle *lh, const struct lgsm_sms *sms);

* '''Write Message to Memory''': can write one SMS message to preferred memory
extern int lgsm_sms_write (struct lgsm_handle *lh, const struct lgsm_sms_write *sms_write);

* '''Retrieve SMS storage Information''': retrieve all SMS storage information
extern int lgsm_sms_get_storage (struct lgsm_handle *lh);

* '''Set preferred SMS storage''': can set SMS preferred storage
extern int lgsm_sms_set_storage (struct lgsm_handle *lh, enum ts0705_mem_type mem1, enum ts0705_mem_type mem2, enum ts0705_mem_type mem3);

* '''Retrieve current default service center address'''
extern int lgsm_sms_get_smsc(struct lgsm_handle *lh);

* '''Set new default service center address'''
extern int lgsm_sms_set_smsc(struct lgsm_handle *lh, const char *number);

* '''Packing of 7-bit characters'''
extern int packing_7bit_character(const char *src, struct lgsm_sms *dest);

===='''libgsmd_phonebook'''====

'''libgsmd_phonebook''' is about all related phonebook functions. The API is as below:

* '''Store''' a specific phonebook entry 'pb' into phone
extern int lgsm_pb_set_entry(struct lgsm_handle *lh, struct lgsm_pb_entry *pb);

* '''List''' of supported phonebook memory storage
extern int lgsm_pb_list_storage(struct lgsm_handle *lh);

* '''Select''' phonebook memory storage
extern int lgsm_pb_set_storage(struct lgsm_handle *lh, char *storage);

* '''Find phonebook entires''' which alphanumeric filed start with string <findtext>
extern int lgsm_pb_find_entry(struct lgsm_handle *lh, const struct lgsm_phonebook_find *pb_find);

* '''Read phonebook entry''' in location number index
extern int lgsm_pb_read_entry(struct lgsm_handle *lh, int index);

* '''Read phonebook entries''' in location number range
extern int lgsm_pb_read_entries(struct lgsm_handle *lh, const struct lgsm_phonebook_readrg *pb_readrg);

* '''Delete''' phonebook entry in location index
extern int lgsm_pb_del_entry(struct lgsm_handle *lh, int index);

* '''Write''' phonebook entry in location
extern int lgsm_pb_write_entry(struct lgsm_handle *lh, const struct lgsm_phonebook *pb);

* '''Get the location range/nlength/tlength supported '''
extern int lgsm_pb_get_support(struct lgsm_handle *lh);

== libgsmd-tool ==
[http://wiki.openmoko.org/wiki/Gsmd#libgsmd-tool Please reference to here]

== Debug Log ==
== To-do ==

OpenMoko under QEMU

2007-06-24T18:10:01Z

Jserv: /* Pre-built binaries */

QEMU can basically be used in three ways to run [[OpenMoko]]. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.

*''PC'' - OpenMoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get OpenMoko running if you want to get an impression of how it looks. In this scenario QEMU would only serve for isolating your [[OpenMoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].

*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]].

*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] hardware, although not all of it at this moment. It is a work-in-progress and when it's more mature it is going to be submitted for merging to the main QEMU development tree.

== Neo1973 emulation ==

This target will (obviously) run original OpenMoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the emulator are: [[Hardware:AGPS|AGPS]] and [[Bluetooth]] - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.

What QEMU can '''*not*''' be used for, and probably no other emulator can, is speed measures and getting the general feel of OpenMoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).

=== What hardware is supported ===

Rough status for each of the components that need emulation, following the outline of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] page.
{|
! Hardware !! Status !! Usage notes
|- style="background-color:#eeeedd;"
! colspan="3"|S3C2410A Processor
|-
|ARM920T core || Works || Already in mainline QEMU.
|-
|Basic guts || Work || This includes GPIO interface, DMA, Interrupt Controller, Timers, NAND controller, MMC/SD host, [[I2C]] and IIS interfaces, Memory & Clock & Power management controllers, RAM.
|-
|Serial ports || Works || Use the "-serial" switch (maybe be specified multiple times) to tell QEMU where serial input/output should go to. GSM module will be connected on UART0.
|-
|RTC || Works || On start QEMU will load it with current time/date - the Neo1973 [[kernel]] doesn't use it for time/date source currently.
|-
|SPI || Works || The guest kernel can drive it using either the SPI interface or raw GPIO bitbanging.
|-
|LCD || Works || The virtual LCD will display as in QEMU window iff "-nographic" is not specified.
|-
|ADC || Works || Mouse events in QEMU window generate what would be touchscreen events on a Neo1973 and are passed to the guest OS through the on-chip ADC.
|-
|OHCI USB || Works || This part is in mainline QEMU. Use the "-usb" switch to enable the controller and "usb_add" in QEMU monitor to attach new virtual or physical USB devices.
|-
|Slave USB || Works || Linux's dummy HCD in conjunction with gadget filesystem API is used to make the virtual Neo appear as a real one connected to the host computer. See [[#Setting up USB connection|Setting up USB connection]] below. (Experimental)
|-
|Watchdog || Works || This is one of the less important on-chip peripherals in S3C2410. It is however used by Linux for rebooting the board.
|- style="background-color:#eeeedd;"
! colspan="3"|[[I2C]] bus peripherals
|-
|[[PCF50606]] || Works || (Aka PMU) Fakes the battery charge level (set at 88%), POWER button, etc. Also contains and RTC, also unused by Linux.
|-
|[[LM4857]] || Works
|-
|[[WM8753L]] || Works || The CODEC is also connect to the CPU's IIS port. Basic [[Neo1973 Audio Subsystem|audio functionality]] is supported - see QEMU documentation on getting audio input/output from the emulator. Volume control has no effects.
|- style="background-color:#eeeedd;"
! colspan="3"|Other peripherals
|-
|NAND Flash || Works || However, some pieces are not confirmed to be completely compatible with the real hardware because of lack thereof. Use "-mtdblock flashimagefilenamehere" switch to point QEMU to your flash image. The file should be at least 69206016 bytes big.
|-
|JBT6K74-AS(PI) || Works || (Aka LCM) Wired to the SPI channel 1
|-
|Buttons || Work || Enter is the AUX button, Space is the POWER button. Wired to on-chip GPIO and PCF50606.
|-
|SD card || Works || This part is already in mainline QEMU. Use the "-sd cardimagegoeshere" switch to point QEMU to the card image. The regular QEMU monitor commands for removable media can also be used. The card works, however the on-chip host controller gave block length errors on heavy I/O despite working as described in specification. I suspect the kernel driver. DMA operation is not tested.
|-
|Bluetooth
|style="background-color:#ffffcc;"|Works
|A generic Bluetooth HCI (just like the BlueCore4 chip) is connected to internal USB hub (just like the Delta DBFM dongle). Currently qemu emulates no other bluetooth devices, so the dongle behaves as if there was no BT-enabled slaves around, being the only device on the piconet, i.e. is not really useful. Likely a Bluetooth keyboard will be emulated. A physical Bluetooth dongle can also be attached to the emulator (see USB documentation in QEMU).
|-
|[[GSM]] || Works || A fake modem is connected to UART0 understanding a (currently quite limited) subset of AT commands. Ultimately it should support as much functionality as possible (basic AT command set, fake GPRS connections, dialing and SMS send/receive). This way all parts of the phone subsystem (CALYPSO, TWL3014, TRF6151) will not have to be emulated. There is a possibility to wire a real GSM modem to QEMU's serial port.
|-
|[[Hardware:AGPS|AGPS]]
|style="background-color:#ffcccc;"|To Do
|There are obvious difficulties emulating the chip, but hopefully it can be made to present the guest OS with some fixed coordinates later when more is known about the chip. Again a real chip could be connected to QEMU's serial port.
|}

Current development is aiming for [[:Category:Neo1973_Hardware#GTA01Bv4 | GTA01Bv4]] compatibility; [[:Category:Neo1973_Hardware#GTA01Bv3 | earlier revisions]] can also be emulated if needed. The differences between the hardware revisions currently only manifest themselves in GPIO wiring. Hardware emulation is implemented in a clean-room manner using official specifications where possible.

== How to get it running ==

=== Using MokoMakefile ===

This is the easiest way since you won't need to deal with the compiling and flashing processes yourself. See [[MokoMakefile#QEMU|MokoMakefile]] for details.

=== Manual setup ===

To obtain the latest source code for the emulator, you will want to do something like the following:
<pre>
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
$ cd qemu-neo1973
</pre>
Now, we're going to configure and build the emulator (Note [[#Requirements|Requirements]] below):
<pre>
$ ./configure --target-list=arm-softmmu # GCC 3.x will be required, see --cc=
$ make
</pre>
See other available options for the configure script by appending "--help".
Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run OpenMoko you will also need to somehow install OpenMoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run
<pre>$ openmoko/download.sh</pre>
which will look up the list of latest available OpenMoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the next command:
<pre>$ openmoko/flash.sh</pre>
which runs the emulator, loads u-boot into it and then uses u-boot's capability to program the Flash memory to install all the necessary parts of the system into the virtual Flash. It will also set up all the bootloading process including a boot menu (ENTER is [AUX] and SPACE is [POWER]), splash, u-boot environment and some default kernel parameters. If everything goes OK, the script should print a command which you can use to start using the emulator.

QEMU has '''*tons*''' of commandline switches and things that can be configured. You can look them up in [http://www.qemu.org/user-doc.html QEMU user docs]. You will probably want to use the "-snapshot" switch, among other ones. Saving and restoring emulation state at any point (unrelated to "-snapshot") should work as per QEMU user docs too.

=== Pre-built binaries ===

Win32 binaries shipped with firmware can be downloaded from [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070625.zip openmoko-emulator-win32-bin-20070625.zip]. Tested on MS Windows XP and Vista Business.

== Requirements ==

This QEMU tree has only been tested on GNU/Linux. To get graphical (not counting VNC) and/or audio output from the emulator you will need either SDL or Cocoa installed on your computer. To enable audio, see the available switches to the ./configure script.

The scripts that sit in openmoko/ require lynx, wget, python and most GNU base utilities installed in standard locations.

All of the build-time and run-time requirements listed in [http://www.qemu.org/user-doc.html QEMU documentation] apply. This includes zlib, etc. On distributions that use binary packages, remember that you need the packages ending in '''-dev''' or '''-devel'''.

== QEMU and GNU debugger ==

QEMU lets you debug operating system kernels and bootloaders like you debug all other programs. To do this you will need a debugger that speaks the GDB remote debugging protocol - [http://sourceware.org/gdb/ GDB] is the obvious choice. Some cross toolchains come with GDB already set up. Otherwise building cross-GDB yourself is quick and easy (compared to building binutils and cross-gcc).

To debug u-boot, load the file "u-boot" into gdb (not "u-boot.bin") that is produced by "make" when building u-boot. To debug a Linux kernel, load the file "vmlinux" from the main source directory into gdb. These files are in ELF format and contain all the symbol information and are not stripped of debugging data until you run "strip" on them, unlike "u-boot.bin" and "Image"/"zImage"/"uImage". Next, tell QEMU to enable the gdbserver by appending the "-s" switch or issuing "gdbserver" in the monitor. Use the command <pre>(gdb) target remote localhost:1234</pre> to make a connection to the emulator. From there you should be able to use all the usual GDB commands, including stepping instructions, setting breakpoints, watchpoints, inspecting stack, variables, registers and more. If gdb is running in the same directory from which it grabbed the ELF executable, the "edit" command should work so you can jump right to the source line which is executing.

== Setting up USB connection ==

It is possible (although not very straight forward, probably about the complexity of tun-tap networking) to connect the virtual, emulated Neo1973 to the Linux PC on which the emulator is running, and work with it as if a real Neo1973 was plugged into the computer's USB port, but no twiddling with cables is needed. If you're testing your applications on the Neo, it may be worth setting up this kind of connection because it lets you enable normal [[USB_Networking|networking between the PC and the phone and ssh into it]] (which is much more comfortable than typing commands into the OpenMoko's terminal emulator via on-screen keyboard). Here's what you will need in order to get this working:

A Linux host with a 2.6 series kernel. The following drivers compiled-in or in modules: dummy_hcd, gadgetfs, usbnet, cdc_ether. Note that you need root access to perform most actions described here. Here's how to enable them in menuconfig.

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Support for USB Gadgets'''

Find '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''USB Peripheral Controller''' and set it to '''Dummy HCD (DEVELOPMENT)'''

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Gadget Filesystem (EXPERIMENTAL)''' (this one is good to have as a module)

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework'''

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''CDC Ethernet support (smart devices such as cable modems)'''

These last two drivers are the same [[Getting Started with your Neo1973#By using Ethernet emulation over a USB cable|drivers that you need to work with a real Neo over USB network]]. After you've built the drivers, make sure that the copy of kernel headers in /usr/include/linux is up to date. In particular the file /usr/include/linux/usb_gadgetfs.h needs to be present and if your distribution came with headers older than 2.6.18 or so, then you need tell the package manager to update them, or you can do that manually with
<pre> # cp -a /usr/src/linux/include/linux/* /usr/include/linux/</pre>
(assuming that your kernel sources are in /usr/src/linux). It is important that this is done before building qemu because the build system checks if these headers are functional and in case they aren't found it will disable the USB Slave functionality.

After building qemu and before running it, make sure that the modules are loaded into the kernel. I found it useful to load gadgetfs with the following command:
<pre> # modprobe gadgetfs default_uid=1000 # assuming my User ID is 1000</pre>
and added the following line to my /etc/fstab:
<pre>gadget /dev/gadget gadgetfs noauto,user,group 0 0</pre>
Make sure that the mountpoint /dev/gadget exists:
<pre> # mkdir -p /dev/gadget</pre>
After that the rest of the procedure can be performed from your regular user account. Mounting gadgetfs is done with:
<pre> $ mount /dev/gadget</pre>
The "default_uid" parameter changes the ownership on all files under /dev/gadget to your own and since the files there are created and destroyed dynamically, there's no easy way to have that performed by ''udev''. Now running qemu as you usually do but appending "-usb -usbgadget" should enable the USB Slave functionality. The qemu monitor commands "info usbslave" and "usb_add gadget" will be useful. The former instruction asks the OS running under the emulator (OpenMoko) to describe its slave features (that's what ''lsusb'' does after a Neo1973 is connected to a PC). You can see the available USB configurations in this command's output. Since gadgetfs allows only one configuration, we will need to choose the desired configuration - most device have only one such configuration, in which case you can use just "usb_add gadget" to connect to host; CDC ethernet devices however usually include a second configuration for RNDIS networking (i.e. Ms Windows compatibility) and so does OpenMoko when using the g_ether driver. Hence, to get this right, wait for OpenMoko to fully boot up and execute the following in QEMU monitor:
<pre>
QEMU 0.9.0 monitor - type 'help' for more information
(qemu) info usbslave
USB2.2 device 1457:5122:
Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc
Product: RNDIS/Ethernet Gadget
Configuration 0: RNDIS
Configuration 1: CDC Ethernet
(qemu)
(qemu) usb_add gadget:1
</pre>
The "1" in "usb_add gadget:N" is the number of the USB configuration that we want to use. If everything went correctly - you can check that in dmesg - you should now have a new network interface called ''usb0'' on the PC, through which you can talk to the OpenMoko running in QEMU:
<pre>
$ dmesg | tail
<6>gadgetfs: bound to dummy_udc driver
<7>hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
<6>usb 3-1: new high speed USB device using dummy_hcd and address 3
<6>gadgetfs: connected
<7>usb 3-1: default language 0x0409
<7>usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
<6>usb 3-1: Product: RNDIS/Ethernet Gadget
<6>usb 3-1: Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc
<6>usb 3-1: configuration #1 chosen from 1 choice
<7>usb 3-1: adding 3-1:1.0 (config #1, interface 0)
<7>usb 3-1:1.0: uevent
<7>cdc_ether 3-1:1.0: usb_probe_interface - got id
<7>cdc_ether 3-1:1.0: status ep3in, 16 bytes period 14
<7>usb 3-1: adding 3-1:1.1 (config #1, interface 1)
<7>usb 3-1:1.1: uevent
$ su -
Password:
# tail /var/log/everything/current
May 8 19:25:32 [kernel] gadgetfs: connected
May 8 19:25:32 [kernel] gadgetfs: disconnected
May 8 19:25:32 [kernel] gadgetfs: configuration #1
May 8 19:25:32 [kernel] usb0: register 'cdc_ether' at usb-dummy_hcd-1, CDC Ethernet Device, 52:e7:eb:76:0a:d0
# lsusb -vvv
Bus 003 Device 003: ID 1457:5122
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1457
idProduct 0x5122
bcdDevice 2.12
iManufacturer 1 Linux 2.6.20.7-moko8/s3c2410_udc
iProduct 2 RNDIS/Ethernet Gadget
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 80
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 7 CDC Ethernet
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Communications Control
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 3 52E7EB760AD0
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 14
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1

# ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0
# exit
$ ssh root@192.168.0.202
The authenticity of host '192.168.0.202 (192.168.0.202)' can't be established.
RSA key fingerprint is de:21:87:93:52:1c:6b:c7:69:29:6c:af:66:50:02:02.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.202' (RSA) to the list of known hosts.
root@192.168.0.202's password:
root@fic-gta01:~$ uname -a
Linux fic-gta01 2.6.20.7-moko8 #1 PREEMPT Wed Apr 25 11:13:52 UTC 2007 armv4tl unknown

Press Coverage

2007-05-22T19:11:05Z

Jserv: /* Chinese */

{|align=right
|__TOC__
|}
[http://www.google.com/trends?q=openmoko%2Cneo1973&ctab=1&geo=all&date=all OpenMoko and Neo1973 on google trends.]

This site contains the press coverage about OpenMoko and the Neo 1973 sorted by language and date. Newest on top.

== Languages ==

=== English ===
==== May 2007 ====
* [http://blogs.sun.com/brewin/entry/fic_and_openmoko_thank_you blog.SUN.com] FIC and OpenMoko - Thank You
* [http://www.pikesoft.com/blog/index.php?itemid=174 PikeSoft.com] JavaFX Mobile: a new smartphone OS contender
* [http://www.sfgate.com/cgi-bin/blogs/sfgate/detail?blogid=19&entry_id=16310 SFGate.com] Here comes the Sun Conference
* [http://www.linuxdevices.com/news/NS7539760574.html LinuxDevices.com] Sun beams Linux/Java at mobile phon

==== April 2007 ====
* [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ Palm Infcenter] OpenMoko running on a palm TX
* [http://jaidev.info/home/blog/archives/2007/04/13/openmoko.html JaidevInfo] OpenMoko
* [http://www.wirelessweek.com/newsletter.aspx?id=137388 Wirelessweek.com] Democracy Hits the Mobile Phone
* [http://elearner.edublogs.org/2007/04/11/technologies-is-that-a-word/ Edublogs.org] Technologies is that a word?
* [http://www.linuxdevices.com/news/NS4777580627.html Linuxdevices.com] 200 million Linux phones to ship by 2012
* [http://arstechnica.com/news.ars/post/20070415-palm-embracing-linux-in-the-hopes-of-being-relevant-again.html Ars Technica] Palm embracing Linux in the hopes of being relevant again] (Mentions Neo1973 in passing)

==== March 2007 ====
* [http://www.smartdevicecentral.com/article/OpenMokos+Open+Source+Phone/202546_1.aspx smartdevicecentral.com] OpenMoko's open source phone
* [http://www.zdnetasia.com/news/communications/0,39044192,61996003,00.htm zdnet asia] Passing mention in an article on the Iphone.
* [http://www.wikio.com/news/Sean+Moss-Pultz wikio.com] Sean Moss-Pultz News
* [http://www.edparsons.com/?p=438 edparsons.com] iPhone chipping away at the walls
* [http://blogs.pcworld.co.nz/pcworld/techsploder/2007/03/openmoko_makes_total_sense.html blogs.pcworld.co.nz] OpenMoko makes total sense
* [http://www.totalueberwachung.de/blog/articles/2007/03/08/neo1973-arrived totalueberwachung.de] Neo1973 arrived
* [http://www.makuchaku.info/blog/im-gonna-get-this-one makuchaku.info] I'm gonna get this one
* [http://www.kitenet.net/~joey/blog/entry/openmoko_and_n800.html kitenet.net] OpenMoko and n800
* [http://dominion.kabel.utwente.nl/koen/cms/the-neo1973-unboxed dominion.kabel.utwente.nl] The Neo1973 unboxed
* [http://atulchitnis.net/diary/showentry/421 atulchitnis.net] An OpenMoko Phone arrives
* [http://blog.matthewgast.com/2007/03/03/good-luck-openmoko blog.matthewgast.com] Good luck OpenMoko
* [http://vaandoo.blogspot.com/2007/03/openmoko-neo1973-opensource-software.html vaandoo.blogspot.com] OpenMoko Neo1973 opensource software
* [http://www.linuxdevices.com/news/NS7653749655.html linuxdevices.com] OpenMoko update; Neo1973 on sale in March
* [http://www.ministryoftech.com/2007/03/05/the-5-hottest-phones-for-linux-fanatics/ ministryoftech.com] Brief line-up of the 5 hottest phones for Linux fans
* [http://voxilla.com/soapvox/2007/03/01/industry-disruption-really-168 voxilla.com] Article about ETel Sean Moss-Pultz presentation
* [http://blog.wired.com/gadgets/2007/03/eight_great_lin.html blog.wired.com] Gadget Lab: Eight Great Linux Smartphones
* [http://gigaom.com/2007/03/01/openmoko-phone/ gigaom.com] OpenMoko Open-Source Mobile, coming soon - Interview with Sean Moss-Pultz
* [http://www.oreillynet.com/etel/blog/2007/03/openmoko_1.html www.oreillynet.com] ETel coverage
* [http://gordoncook.net/wp/?p=146 gordoncook.net] Short history of Neo1973 and other stuff
* [http://www.engadget.com/2007/03/03/openmoko-details-pricing-availability-for-neo1973/ engadget.com] OpenMoko details pricing, availability for Neo1973
* [http://www.uberpulse.com/us/2007/03/fic_wants_to_rewrite_the_rules_with_open_moko_mobile_phone.php www.uberpulse.com] Some images from ETel

==== February 2007 ====
* [http://www.scullen.ca/2007/02/15/forget-about-the-iphone-neo1973-is-far-more-exciting/ scullen.ca] Forget about the iPone, Neo1973 is far more exciting
* [http://www.mobileread.com/forums/showpost.php?p=59124&postcount=4 mobileread.com] Show post
* [http://www.pdasnews.com/articles/2568/1/ pdasnews.com] Linux-powered iPhone killer available online in March
* [http://www.belutz.net/2007/02/05/openmoko/ belutz.net] OpenMoko
* [http://www.mail-archive.com/community@lists.openmoko.org/msg03686.html mail-archive.com] OpenMoko community mail archive
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena maclife.com] Is there a crowd in the touch screen phone arena
* [http://gopaultech.com/2007/02/fic-neo1973-linux-smartphone/ gopaultech.com] FIC Neo1973 Linux smartphone
* [http://www.volweb.cz/horvitz/os-info/news-feb07-014.html volweb.cz] Open-source smartphone, with WiFi in version 2
* [http://www.oreillynet.com/etel/blog/2007/02/etel_coverage_openmoko_opens_t.html oreillynet.com] ETel coverage OpenMoko opens
* [http://www.mobilewhack.com/openmoko-neo1973-open-source-phone/ mobilewhack.com] OpenMoko Neo1973 open source phone
* [http://www.engadget.com/2007/02/19/what-tech-would-the-presidents-rock-in-2007/ engadget.com] What tech would the presidents rock in 2007
* [http://www.tuxmachines.org/node/13602 tuxmachines.org] What participation culture
* [http://www.vanille-media.de/site/index.php/category/opensource/openmoko/ vanille-media.de] Opensource OpenMoko
* [http://www.joetech.com/2007/02/15/openmoko-open-source-cell-phone/ joetech.com] OpenMoko open source cell phone
* [http://www.makezine.com/blog/archive/2007/02/openmoko_open_s.html makezine.com] OpenMoko open
* [http://www.linuxdevices.com/news/NS9706477996.html linuxdevices.com] Announce of the Openembedded booth at FOSDEM in Brussels.
* [http://www.linuxdevices.com/news/NS2657814070.html linuxdevices.com] Quick interview with Sean and some pictures
* [http://gizmodo.com/gadgets/smartphones/first-look-the-antiiphone-openmokos-neo1973-236841.php gizmodo.com] Photos and comments on hardware and software
* [http://www.onecompare.com/mobile-news/article-asp~aid~244~pub~56321102~story~openmoko-launch-the-official-portal-for-development-of-the-openmoko-platform onecompare.com] Short news article
* [http://crunchgear.com/2007/02/15/openmokos-open-source-mobile-os crunchgear.com] Holding the phone upside down
* [http://www.slashgear.com/openmoko-and-fic-neo1973-updates-153926.php slashgear.com] Video interview and many pictures
* [http://www.djlosch.com/article_Comparison%3A_iPhone_vs_A1200_vs_Neo1973 djlosch.com] Article comparing the Neo to the iPhone and A1200
* [http://popsci.typepad.com/popsci/2007/02/up_close_and_pe.html popsci.typepad.com] Screenshot of Linux booting on the Neo
* [http://video.google.de/videoplay?docid=-3742589179435830945&q=Openmoko video.google.com] Presentation of OpenMoko at the FOSDEM
* [http://www.manilastandardtoday.com/?page=business6_feb27_2007 manilastandardtoday.com] Tale of two phones
* [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone blog.printf.net] OLPC and older Neo1973.
* [http://mako.cc/copyrighteous/freesoftware/20070228-00.html mako.cc] OLPC and older Neo1973 again.
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena MacLife] Is Three a Crowd among Touch-Screen Phones?

==== January 2007 ====
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html blogs.ft.com] OpenMoko harks back to hello moto
* [http://opensource.sfsu.edu/node/258 opensource.sfsu.edu] Can you hear me now?
* [http://losca.blogspot.com/2007/01/maemo-nokia-n800-has-competitor-in.html losca.blogspot.com] Maemo Nokia n800 has competitor in openness - OpenMoko
* [http://21talks.net/voip/openmoko 21talks.net] OpenMoko: Not as sexy as the iPhone, but it’s a Linux phone
* [http://www.linuxinfusion.com/openmoko-schedule-announced linuxinfusion.com] OpenMoko schedule announced
* [http://users.livejournal.com/_paladine_/tag/smartphone users.livjournal.com] The Worlds First Opensource Linux Smartphone
* [http://www.nungee.com/2007/01/25/openmoko/ nungee.com] OpenMoko
* [http://www.sda-asia.com/sda/features/psecom,id,880,srn,2,channel,developer,nodeid,21,_language,Singapore.html sda-asia.com] OpenMoko Offers Open-source Smart phone T
* [http://www.regdeveloper.co.uk/2007/01/15/open_phone/ regdeveloper.co.uk] Open Phone
* [http://www.product-reviews.net/2007/01/17/fic-neo1973-smartphone-open-source-phone/ product-reviews.net] FIC Neo1973 smartphone open source phone
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php gizmodo.com] OpenMoko smartphone did they have a time machine or what
* [http://www.oreillynet.com/conferences/blog/2007/01/openmoko_workshop_added_to_ete.html oreillynet.com] OpenMoko workshop added to ETel
* [http://www.gadgetell.com/2007/01/openmoko-gets-interviewed-about-new-open-source-fic-neo1973/ gadgetell.com] OpenMoko gets interviewed about new open source FIC Neo1973
* [http://www.slashgear.com/openmoko-interface-im-loving-it-173496.php slashgear.com] OpenMoko interface I'm loving it
* [http://www.gadgetorama.com/news/news_details.php?gorid=2008 gadgetorama.com] OpenMoko news details
* [http://tech.cybernetnews.com/2007/01/17/openmoko-vs-iphone-did-apple-copy/ tech.cybernetnews.com] OpenMoko vs iPhone did Apple copy
* [http://techtrails.blogspot.com/2007/01/open-phones-with-open-moko-while.html techtrails.blogspot.com] Open phones with OpenMoko while
* [http://blogger.xs4all.nl/jurjen1/archive/2007/01/17/174341.aspx bloger.xs4all.nl] OpenMoko open source mobile phone
* [http://www.ringnokia.com/2007/01/i_am_highly_cur.html ringnokia.com] I'm highly curious
* [http://www.oreillynet.com/etel/blog/2007/01/iclone_1.html oreillynet.com] iClone
* [http://forums.scotsnewsletter.com/index.php?showtopic=17685 forums.scotsnewsletter.com] Show topic
* [http://understandinglimited.com/2007/01/15/iphone/ understandinglimited.com] iPhone and OpenMoko
* [http://robertogaloppini.net/2007/01/12/openmoko-the-integrated-os-mobile-communications-platform-2/ robertogaloppini.net] OpenMoko the intergrated OS mobile communications platform
* [http://www.funambol.com/blog/capo/2007/01/apple-please-do-not-forget-developers.html funambol.com] Apple please do not forget developers
* [http://chopey.blogspot.com/2007/01/iphone-or-not-to-iphone.html chopey.blogspot.com] iPhone or not to iPhone
* [http://opendotdotdot.blogspot.com/2007/01/openmoko.html opendotdotdot.blogspot.com] OpenMoko
* [http://www.e-pcmag.gr/forum/index.php?showtopic=19505 e-pcmag.gr] Show topic
* [http://www.costpernews.com/2007/01/12/anything-you-can-do-we-can-do-better/ costpernews.com] Anything you can do we can do better
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs OpenMoko - the Open Alternative
* [http://lwn.net/Articles/217020/rss lwn.net] An OpenMoko update
* [http://www.networkworld.com/news/2007/010907-moss-pultz.html networkworld.com] Q&A Building a new open source phone platform
* [http://www.networkcomputing.com/showArticle.jhtml?articleID=196802226 networkcomputing.com] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.osweekly.com/index.php?option=com_content&task=view&id=2420&Itemid=449 osweekly.com] Mobile Devices Adopt Open Source
* [http://www.linuxdevices.com/news/NS8591201260.html linuxdevices.com] Linux phone market open up?
* [http://www.pcmag.com/article2/0,1895,2080727,00.asp pcmag.com] Cell phone open up
* [http://sonyericssonz558i.blogurple.com/2007/01/06/23/ sonyericssonz558i.blogurple.com] Sony Ericsson Z558i
* [http://www.sannes.org/?p=5 sannes.org] An Open mobile phone that does what you want
* [http://popsci.typepad.com/ces2007/2007/01/opensource_stri.html Popsci.com] Open Source Strikes Again
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php Gizmodo.com] OpenMoko interface compared to iPhone
* [http://www.linuxjournal.com/xstatic/abstracts/upfront Linux Journal] Doc Searls in the feb 2007 issue
* [http://www.osdir.com/Article9642.phtml OSDir.com] Mobile Linux for the Mobile Fan] -> [http://www.madpenguin.org/cms/?m=show&id=7710 MadPenguin] Mobile Linux for the Mobile Fan
* [http://www.usnews.com/usnews/biztech/davesdownload/archive/070112/a_populist_challenge_to_apples.htm US News] A Populist Challenge to Apple's iPhone
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs OpenMoko: The open alternative
* [http://www.informationweek.com/news/showArticle.jhtml?articleID=196802206&subSection=All+Stories InformationWeek] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.theregister.co.uk/2007/01/15/open_phone/ The Register] Open Phones with Open Moko
* [http://techreport.com/onearticle.x/11589 The Tech Report] OpenMoko offers open-source smart phone
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html Financial Times] OpenMoko harks back to Hello Moto
* [http://hardware.slashdot.org/article.pl?sid=07/01/20/1551200 Slashdot] OpenMoko Schedule Announced
* [http://www.youtube.com/watch?v=jRvtAAXTIlg Youtube] Interview with Sean Moss-Pultz ([http://www.monoploid.be/dl/openmoko_sean_interview.ogm mirror in Ogg format])
* [http://www.libervis.com/article/forget_iphone_hail_openmoko_the_true_revolution Libervis.com] Forget iPhone, hail OpenMoko, the true revolution
* [http://gizmodo.com/gadgets/smartphones/sizemodo-iphone-vs-openmoko-neo1073-229294.php Gizmodo]iPhone vs. Openmoko Neo1973] (please, don't mind the typo i n the title)

==== December 2006 ====
* [http://www.pikesoft.com/blog/index.php?itemid=133 pikesoft.com] Cheap, totally open Linux phone will ship next month
* [http://www.cdrinfo.com/Sections/News/Details.aspx?NewsId=19254 cdrinfo.com] FIC to release Linux based Smartphone

==== November 2006 ====
* [http://www.ministryoftech.com/2006/11/09/fic-neo1973-smartphone-with-linux-based-openmoko-open-source-platform/ ministryoftech.com] FIC Neo1973 smartphone with linux-based OpenMoko open source platform
* [http://www.mobiletechnews.com/info/2006/11/09/124614.html mobiletechnews.com] OpenMoko Linux mobile platform and Neo1973 smartphone announced
* [http://news.softpedia.com/news/FIC-Neo1973-for-all-the-Linux-Lovers-out-There-40344.shtml news.softpedia.com] FIC Neo1973 for all the Linux lovers out there
* [http://www.openembedded.org/openmoko-fic-choosing-openembedded openembedded.org] OpenMoko FIC choosing openembedded
* [http://news.com.com/2300-1037_3-6134795-1.html news.com.com] FIC's Linux handset
* [http://www.slashphone.com/77/5784.html slashphone.com] OpenMoko Announces Open Source Mobile Communications Platform
* [http://www.arm.com/iqonline/news/marketnews/15616.html arm.com] Open Linux Based, ARM Powered Mobile In Wings
* [http://news.com.com/Second+open+Linux+handset+unveiled/2100-1039_3-6133974.html news.com.tw] Second open Linux handset unveiled
* [http://www.infoworld.com/article/06/11/08/HNlinuxphone_1.html?COMMERCIAL%20LINUX infoworld.com] FIC debuts open Linux-based smartphone
* [http://www.michaeldolan.com/431 michaeldolan.com] A must have: OpenMoko cell phone with GPS and...apt-get
* [http://nandz.blogspot.com/2006/11/my-dream-phone.html nandz.blogspot.com] My dream phone
* [http://www.linuxdevices.com/news/NS2986976174.html linuxdevices.com] Cheap, hackable Linux smartphone due soon
* [http://www.linuxdevices.com/news/NS7056478804.html linuxdevices.com] First OpenMoKo phone taps dual-licensed SyncML stack
* [http://lwn.net/Articles/208298/ lwn.net] The OpenMoko open phone
* [http://www.theinquirer.net/default.aspx?article=35590 theinquirer.net] A truly open Linux phone with GPS debuts

=== German ===

==== April 2007 ====
* [http://www.pro-linux.de/news/2007/11133.html pro-linux] - OpenMoko produziert erste Muster
* [http://www.golem.de/0704/51970.html golem.de] - Open-Source-Handy vor Produktionsbeginn

==== March 2007 ====
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express] - Das neue Projekt zur Entwicklung eines Telefons mit freier Software
* [http://www.pro-linux.de/news/2007/10966.html pro-linux] - OpenMoko sucht Unterstützung

==== February 2007 ====
* [http://www.digital-living-magazin.de/index.php?pid=17&art=2050&cid=DLnewsletter digital-living-magazin.de] - Linux erobert Mobilfunkmarkt
* [http://www.heise.de/tr/artikel/85138 Technology Review] - Open-Source-Handy, nächster Versuch
* [http://www.pro-linux.de/news/2007/10833.html pro-linux] - OpenMoko-Quellcode angekündigt
* [http://www.heise.de/newsticker/meldung/85354 heise online] - OpenMoko: Linux-Plattform für Handys freigegeben
* [http://www.mobile2day.de/news/news_details.html?nd_ref=6870&n_multi=0&nf_id=0&nt_id=0&f_date_m=01&f_date_y=2007&t_date_m=04&t_date_y=2007&from=archive Mobile2Day] - OpenMoko bringt Details zum Neo1973

==== November 2006 ====

* [http://golem.de/0611/48824.html golem.de] - OpenMoko kündigt Open-Source-Handy an
* [http://www.heise.de/newsticker/meldung/80714 heise online] - Smartphone mit offener Linux-Plattform
* [http://www.pro-linux.de/news/2006/10448.html pro-linux] - Offenes Linux-Smartphone »OpenMoko« für Januar 2007 angekündigt

=== Scandinavian ===
* [http://www.amobil.no/nyhet/mobiltelefoner/openmoko_klart_for_verden/36554 Amobil.no] OpenMoko klart for verden
* [http://www.nyteknik.se/art/48697 NyTeknik] Snart är den öppna Linuxtelefonen här (Swedish) (Translation: this article states free release to selected developers Feb 11, commercial release to developers March 11, and main release to market Sep 11. See also [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html])

=== French ===
* [http://linuxfr.org/2006/11/08/21596.html LinuxFR] OpenMoko : sortie en janvier d'un téléphone-GPS enfin libre!

=== Chinese ===
* [http://people.debian.org.tw/~chihchun/2007/05/17/openmoko-at-tossug/ debian.org.tw] OpenMoko at TOSSUG
* [http://magicdesign.blogspot.com/2007/05/free-your-phoneopenmoko.html MagicDesign] Free your phone OpenMoko
* [http://people.debian.org.tw/~chihchun/2007/04/30/have-fun-with-openmokoneo1973/ Debian.org.tw] Have fun with OpenMoko Neo1973
* [http://orzlab.blogspot.com/ Orzlab] When Java meets OpenMoko
* [http://blog.footoo.org/?p=115 FooToo.org] Install OpenMoko Emulator
* [http://www.jollen.org/blog/2007/01/openmoko_announce.html Jollen.org] OpenMoko Kick-Off
* [http://zh.wikipedia.org/wiki/OpenMoko Wikipedia.org] OpenMoko Chinese Wiki
* [http://tw.myblog.yahoo.com/champ_yen/article?mid=211&prev=212&next=-1 Yahoo.com.tw] Forget about iPhone, Hail OpenMoko
* [http://www.jollen.org/blog/2006/11/mobile_20_openmoko_linux_smart.html Jollen.org] OpenMoko Linux Smartphone
* [http://blog.roodo.com/ystuan/archives/2733869.html Roodo.com] OpenMoko

OpenMoko under QEMU

2007-05-14T19:31:59Z

Jserv: /* Pre-built binaries */

QEMU can basically be used in three ways to run [[OpenMoko]]. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.

*''PC'' - OpenMoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get OpenMoko running if you want to get an impression of how it looks. In this scenario QEMU would only serve for isolating your [[OpenMoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].

*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]].

*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] hardware, although not all of it at this moment. It is a work-in-progress and when it's more mature it is going to be submitted for merging to the main QEMU development tree.

== Neo1973 emulation ==

This target will (obviously) run original OpenMoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the emulator are: [[GSM]] modem, [[Hardware:AGPS|AGPS]] and [[Bluetooth]] - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.

What QEMU can '''*not*''' be used for, and probably no other emulator can, is speed measures and getting the general feel of OpenMoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).

=== What hardware is supported ===

Rough status for each of the components that need emulation, following the outline of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] page.
{|
! Hardware !! Status !! Usage notes
|- style="background-color:#eeeedd;"
! colspan="3"|S3C2410A Processor
|-
|ARM920T core || Works || Already in mainline QEMU.
|-
|Basic guts || Work || This includes GPIO interface, DMA, Interrupt Controller, Timers, NAND controller, MMC/SD host, [[I2C]] and IIS interfaces, Memory & Clock & Power management controllers, RAM.
|-
|Serial ports || Work || Use the "-serial" switch (maybe be specified multiple times) to tell QEMU where serial input/output should go to. GSM module will be connected on UART0.
|-
|RTC || Works || On start QEMU will load it with current time/date - the Neo1973 [[kernel]] doesn't use it for time/date source currently.
|-
|SPI || Works || The guest kernel can drive it using either the SPI interface or raw GPIO bitbanging.
|-
|LCD || Works || The virtual LCD will display as in QEMU window iff "-nographic" is not specified.
|-
|ADC || Works || Mouse events in QEMU window generate what would be touchscreen events on a Neo1973 and are passed to the guest OS through the on-chip ADC.
|-
|OHCI USB || Works || This part is in mainline QEMU. Use the "-usb" switch to enable the controller and "usb_add" in QEMU monitor to attach new virtual or physical USB devices.
|-
|Slave USB || Works || Linux's dummy HCD in conjunction with gadget filesystem API is used to make the virtual Neo appear as a real one connected to the host computer. See [[#Setting up USB connection|Setting up USB connection]] below. (Experimental)
|-
|Watchdog
|style="background-color:#ffcccc;"|To Do
|This is one of the less important on-chip peripherals in S3C2410. It is however used by Linux for rebooting the board.
|- style="background-color:#eeeedd;"
! colspan="3"|[[I2C]] bus peripherals
|-
|[[PCF50606]]||Works||(Aka PMU) Fakes the battery charge level (set at 88%), POWER button, etc. Also contains and RTC, also unused by Linux.
|-
|[[LM4857]]||Works
|-
|[[WM8753L]]||Works||The CODEC is also connect to the CPU's IIS port. Basic [[Neo1973 Audio Subsystem|audio functionality]] is supported - see QEMU documentation on getting audio input/output from the emulator. Volume control has no effects.
|- style="background-color:#eeeedd;"
! colspan="3"|Other peripherals
|-
|NAND Flash||Works||However, some pieces are not confirmed to be completely compatible with the real hardware because of lack thereof. Use "-mtdblock flashimagefilenamehere" switch to point QEMU to your flash image. The file should be at least 69206016 bytes big.
|-
|JBT6K74-AS(PI)||Works|| (Aka LCM) Wired to the SPI channel 1
|-
|Buttons||Work||Enter is the AUX button, Space is the POWER button. Wired to on-chip GPIO and PCF50606.
|-
|SD card||Works||This part is already in mainline QEMU. Use the "-sd cardimagegoeshere" switch to point QEMU to the card image. The regular QEMU monitor commands for removable media can also be used. The card works, however the on-chip host controller gave block length errors on heavy I/O despite working as described in specification. I suspect the kernel driver. DMA operation is not tested.
|-
|Bluetooth
|style="background-color:#ffcccc;"|To Do
|Will require implementing the Delta DBFM chip and connecting it to USB. The ROM will likely be replaced with code to translate communication directly to TCP/UDP networking (like Slirp). A real bluetooth dongle can also be attached to the emulator (see USB documentation in QEMU).
|-
|[[GSM]]
|style="background-color:#ffcccc;"|In Progress
|A fake modem will be connected to UART0 with as much functionality as possible (basic AT commands understanding, fake GPRS connections and SMS send/receive). This way all parts of the phone subsystem (CALYPSO, TWL3014, TRF6151) will not have to be emulated. There is a possibility to wire a real GSM modem to QEMU's serial port.
|-
|[[Hardware:AGPS|AGPS]]
|style="background-color:#ffcccc;"|To Do
|There are obvious difficulties emulating the chip, but hopefully it can be made to present the guest OS with some fixed coordinates later when more is known about the chip. Again a real chip could be connected to QEMU's serial port.
|}

Current development is aiming for [[:Category:Neo1973_Hardware#GTA01Bv4 | GTA01Bv4]] compatibility; [[:Category:Neo1973_Hardware#GTA01Bv3 | earlier revisions]] can also be emulated if needed. The differences between the hardware revisions currently only manifest themselves in GPIO wiring.

== How to get it running ==

=== Using MokoMakefile ===

This is the easiest way since you won't need to deal with the compiling and flashing processes yourself. See [[MokoMakefile#QEMU|MokoMakefile]] for details.

=== Manual setup ===

To obtain the latest source code for the emulator, you will want to do something like the following:
<pre>
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
$ cd qemu-neo1973
</pre>
Now, we're going to configure and build the emulator (Note [[#Requirements|Requirements]] below):
<pre>
$ ./configure --target-list=arm-softmmu # GCC 3.x will be required, see --cc=
$ make
</pre>
See other available options for the configure script by appending "--help".
Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run OpenMoko you will also need to somehow install OpenMoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run
<pre>$ openmoko/download.sh</pre>
which will look up the list of latest available OpenMoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the next command:
<pre>$ openmoko/flash.sh</pre>
which runs the emulator, loads u-boot into it and then uses u-boot's capability to program the Flash memory to install all the necessary parts of the system into the virtual Flash. It will also set up all the bootloading process including a boot menu (ENTER is [AUX] and SPACE is [POWER]), splash, u-boot environment and some default kernel parameters. If everything goes OK, the script should print a command which you can use to start using the emulator.

QEMU has '''*tons*''' of commandline switches and things that can be configured. You can look them up in [http://www.qemu.org/user-doc.html QEMU user docs]. You will probably want to use the "-snapshot" switch, among other ones.

=== Pre-built binaries ===

Win32 binaries shipped with firmware can be downloaded from [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070514.zip openmoko-emulator-win32-bin-20070514.zip]. Tested on MS Windows XP.

== Requirements ==

This QEMU tree has only been tested on GNU/Linux. To get graphical (not counting VNC) and/or audio output from the emulator you will need either SDL or Cocoa installed on your computer. To enable audio, see the available switches to the ./configure script.

The scripts that sit in openmoko/ require lynx, wget, python and most GNU base utilities installed in standard locations.

All of the build-time and run-time requirements listed in [http://www.qemu.org/user-doc.html QEMU documentation] apply. This includes zlib, etc. On distributions that use binary packages, remember that you need the packages ending in '''-dev''' or '''-devel'''.

== QEMU and GNU debugger ==

QEMU lets you debug operating system kernels and bootloaders like you debug all other programs. To do this you will need a debugger that speaks the GDB remote debugging protocol - [http://sourceware.org/gdb/ GDB] is the obvious choice. Some cross toolchains come with GDB already set up. Otherwise building cross-GDB yourself is quick and easy (compared to building binutils and cross-gcc).

To debug u-boot, load the file "u-boot" into gdb (not "u-boot.bin") that is produced by "make" when building u-boot. To debug a Linux kernel, load the file "vmlinux" from the main source directory into gdb. These files are in ELF format and contain all the symbol information and are not stripped of debugging data until you run "strip" on them, unlike "u-boot.bin" and "Image"/"zImage"/"uImage". Next, tell QEMU to enable the gdbserver by appending the "-s" switch or issuing "gdbserver" in the monitor. Use the command <pre>(gdb) target remote localhost:1234</pre> to make a connection to the emulator. From there you should be able to use all the usual GDB commands, including stepping instructions, setting breakpoints, watchpoints, inspecting stack, variables, registers and more. If gdb is running in the same directory from which it grabbed the ELF executable, the "edit" command should work so you can jump right to the source line which is executing.

== Setting up USB connection ==

It is possible (although not very straight forward, probably about the complexity of tun-tap networking) to connect the virtual, emulated Neo1973 to the Linux PC on which the emulator is running, and work with it as if a real Neo1973 was plugged into the computer's USB port, but no twiddling with cables is needed. If you're testing your applications on the Neo, it may be worth setting up this kind of connection because it lets you enable normal [[USB_Networking|networking between the PC and the phone and ssh into it]] (which is much more comfortable than typing commands into the OpenMoko's terminal emulator via on-screen keyboard). Here's what you will need in order to get this working:

A Linux host with a 2.6 series kernel. The following drivers compiled-in or in modules: dummy_hcd, gadgetfs, usbnet, cdc_ether. Note that you need root access to perform most actions described here. Here's how to enable them in menuconfig.

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Support for USB Gadgets'''

Find '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''USB Peripheral Controller''' and set it to '''Dummy HCD (DEVELOPMENT)'''

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Gadget Filesystem (EXPERIMENTAL)''' (this one is good to have as a module)

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework'''

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''CDC Ethernet support (smart devices such as cable modems)'''

These last two drivers are the same [[Getting Started with your Neo1973#By using Ethernet emulation over a USB cable|drivers that you need to work with a real Neo over USB network]]. After you've built the drivers, make sure that the copy of kernel headers in /usr/include/linux is up to date. In particular the file /usr/include/linux/usb_gadgetfs.h needs to be present and if your distribution came with headers older than 2.6.18 or so, then you need tell the package manager to update them, or you can do that manually with
<pre> # cp -a /usr/src/linux/include/linux/* /usr/include/linux/</pre>
(assuming that your kernel sources are in /usr/src/linux). It is important that this is done before building qemu because the build system checks if these headers are functional and in case they aren't found it will disable the USB Slave functionality.

After building qemu and before running it, make sure that the modules are loaded into the kernel. I found it useful to load gadgetfs with the following command:
<pre> # modprobe gadgetfs default_uid=1000 # assuming my User ID is 1000</pre>
and added the following line to my /etc/fstab:
<pre>gadget /dev/gadget gadgetfs noauto,user,group 0 0</pre>
Make sure that the mountpoint /dev/gadget exists:
<pre> # mkdir -p /dev/gadget</pre>
After that the rest of the procedure can be performed from your regular user account. Mounting gadgetfs is done with:
<pre> $ mount /dev/gadget</pre>
The "default_uid" parameter changes the ownership on all files under /dev/gadget to your own and since the files there are created and destroyed dynamically, there's no easy way to have that performed by ''udev''. Now running qemu as you usually do but appending "-usb -usbgadget" should enable the USB Slave functionality. The qemu monitor commands "info usbslave" and "usb_add gadget" will be useful. The former instruction asks the OS running under the emulator (OpenMoko) to describe its slave features (that's what ''lsusb'' does after a Neo1973 is connected to a PC). You can see the available USB configurations in this command's output. Since gadgetfs allows only one configuration, we will need to choose the desired configuration - most device have only one such configuration, in which case you can use just "usb_add gadget" to connect to host; CDC ethernet devices however usually include a second configuration for RNDIS networking (i.e. Ms Windows compatibility) and so does OpenMoko when using the g_ether driver. Hence, to get this right, wait for OpenMoko to fully boot up and execute the following in QEMU monitor:
<pre>
QEMU 0.9.0 monitor - type 'help' for more information
(qemu) info usbslave
USB2.2 device 1457:5122:
Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc
Product: RNDIS/Ethernet Gadget
Configuration 0: RNDIS
Configuration 1: CDC Ethernet
(qemu)
(qemu) usb_add gadget:1
</pre>
The "1" in "usb_add gadget:N" is the number of the USB configuration that we want to use. If everything went correctly - you can check that in dmesg - you should now have a new network interface called ''usb0'' on the PC, through which you can talk to the OpenMoko running in QEMU:
<pre>
$ dmesg | tail
<6>gadgetfs: bound to dummy_udc driver
<7>hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
<6>usb 3-1: new high speed USB device using dummy_hcd and address 3
<6>gadgetfs: connected
<7>usb 3-1: default language 0x0409
<7>usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
<6>usb 3-1: Product: RNDIS/Ethernet Gadget
<6>usb 3-1: Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc
<6>usb 3-1: configuration #1 chosen from 1 choice
<7>usb 3-1: adding 3-1:1.0 (config #1, interface 0)
<7>usb 3-1:1.0: uevent
<7>cdc_ether 3-1:1.0: usb_probe_interface - got id
<7>cdc_ether 3-1:1.0: status ep3in, 16 bytes period 14
<7>usb 3-1: adding 3-1:1.1 (config #1, interface 1)
<7>usb 3-1:1.1: uevent
$ su -
Password:
# tail /var/log/everything/current
May 8 19:25:32 [kernel] gadgetfs: connected
May 8 19:25:32 [kernel] gadgetfs: disconnected
May 8 19:25:32 [kernel] gadgetfs: configuration #1
May 8 19:25:32 [kernel] usb0: register 'cdc_ether' at usb-dummy_hcd-1, CDC Ethernet Device, 52:e7:eb:76:0a:d0
# lsusb -vvv
Bus 003 Device 003: ID 1457:5122
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1457
idProduct 0x5122
bcdDevice 2.12
iManufacturer 1 Linux 2.6.20.7-moko8/s3c2410_udc
iProduct 2 RNDIS/Ethernet Gadget
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 80
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 7 CDC Ethernet
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Communications Control
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 3 52E7EB760AD0
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 14
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1

# ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0
# exit
$ ssh root@192.168.0.202
The authenticity of host '192.168.0.202 (192.168.0.202)' can't be established.
RSA key fingerprint is de:21:87:93:52:1c:6b:c7:69:29:6c:af:66:50:02:02.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.202' (RSA) to the list of known hosts.
root@192.168.0.202's password:
root@fic-gta01:~$ uname -a
Linux fic-gta01 2.6.20.7-moko8 #1 PREEMPT Wed Apr 25 11:13:52 UTC 2007 armv4tl unknown

OpenMoko under QEMU

2007-04-17T09:59:10Z

Jserv: Added "Pre-built binaries"

QEMU can basically be used in three ways to run [[OpenMoko]]. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.

*PC - OpenMoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get OpenMoko running if you want to get an impression of how it looks. In this scenario QEMU would only serve for isolating your [[OpenMoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].

*Integrator/CP - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the CPU. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]].

*Neo1973 - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] hardware, although not all of it at this moment. It is a work-in-progress and when it's more mature it is going to be submitted for merging to the main QEMU development tree.

== Neo1973 emulation ==
This target will (obviously) run original OpenMoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the emulator are: [[GSM]] modem, [[Hardware:AGPS|AGPS]] and [[Bluetooth]], as well as the USB slave functionality - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.

What QEMU can *not* be used for, and probably no other emulator can, is speed measures and getting the general feel of OpenMoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).

=== What hardware is supported ===

Rough status for each of the components that need emulation, following the outline of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] page.
{|
! Hardware !! Status !! Usage notes
|- style="background-color:#eeeedd;"
! colspan="3"|S3C2410A Processor
|-
|ARM920T core || Works || Already in mainline QEMU.
|-
|Basic guts || Work || This includes GPIO interface, DMA, Interrupt Controller, Timers, NAND controller, MMC/SD host, [[I2C]] and IIS interfaces, Memory & Clock & Power management controllers, RAM.
|-
|Serial ports || Work || Use the "-serial" switch (maybe be specified multiple times) to tell QEMU where serial input/output should go to. GSM module will be connected on UART0.
|-
|RTC || Works || On start QEMU will load it with current time/date - the Neo1973 [[kernel]] doesn't use it for time/date source currently.
|-
|SPI || Works || The guest kernel can drive it using either the SPI interface or raw GPIO bitbanging.
|-
|LCD || Works || The virtual LCD will display as in QEMU window iff "-nographic" is not specified.
|-
|ADC || Works || Mouse events in QEMU window generate what would be touchscreen events on a Neo1973 and are passed to the guest OS through the on-chip ADC.
|-
|OHCI USB || Works || This part is in mainline QEMU. Use the "-usb" switch to enable the controller and "usb_add" in QEMU monitor to attach new virtual or physical USB devices.
|-
|Slave USB
|style="background-color:#ffcccc;"|To Do
|Possibly Linux's dummy HCD in conjunction with gadget filesystem API can be make the virtual Neo appear as a real one connected to your computer. Otherwise different host functions (usbtty, usbnet) could be emulated.
|-
|Watchdog
|style="background-color:#ffcccc;"|To Do
|This is one of the less important on-chip peripherals in S3C2410. It is however used by Linux for rebooting the board.
|- style="background-color:#eeeedd;"
! colspan="3"|[[I2C]] bus peripherals
|-
|[[PCF50606]]||Works||(Aka PMU) Fakes the battery charge level (set at 88%), POWER button, etc. Also contains and RTC, also unused by Linux.
|-
|[[LM4857]]||Works
|-
|[[WM8753L]]||Works||The CODEC is also connect to the CPU's IIS port. Basic [[Neo1973 Audio Subsystem|audio functionality]] is supported - see QEMU documentation on getting audio input/output from the emulator. Volume control has no effects.
|- style="background-color:#eeeedd;"
! colspan="3"|Other peripherals
|-
|NAND Flash||Works||However, some pieces are not confirmed to be completely compatible with the real hardware because of lack thereof. Use "-mtdblock flashimagefilenamehere" switch to point QEMU to your flash image. The file should be at least 69206016 bytes big.
|-
|JBT6K74-AS(PI)||Works|| (Aka LCM) Wired to the SPI channel 1
|-
|Buttons||Work||Enter is the AUX button, Space is the POWER button. Wired to on-chip GPIO and PCF50606.
|-
|SD card||Works||This part is already in mainline QEMU. Use the "-sd cardimagegoeshere" switch to point QEMU to the card image. The regular QEMU monitor commands for removable media can also be used. The card works, however the on-chip host controller gave block length errors on heavy I/O despite working as described in specification. I suspect the kernel driver. DMA operation is not tested.
|-
|Bluetooth
|style="background-color:#ffcccc;"|To Do
|Will require implementing the Delta DBFM chip and connecting it to USB. The ROM will likely be replaced with code to translate communication directly to TCP/UDP networking (like Slirp). A real bluetooth dongle can also be attached to the emulator (see USB documentation in QEMU).
|-
|[[GSM]]
|style="background-color:#ffcccc;"|In Progress
|A fake modem will be connected to UART0 with as much functionality as possible (basic AT commands understanding, fake GPRS connections and SMS send/receive). This way all parts of the phone subsystem (CALYPSO, TWL3014, TRF6151) will not have to be emulated. There is a possibility to wire a real GSM modem to QEMU's serial port.
|-
|[[Hardware:AGPS|AGPS]]
|style="background-color:#ffcccc;"|To Do
|There are obvious difficulties emulating the chip, but hopefully it can be made to present the guest OS with some fixed coordinates later when more is known about the chip. Again a real chip could be connected to QEMU's serial port.
|}

== How to get it running ==

=== Using MokoMakefile ===

This is the recommended way since you won't need to deal with the compiling and flashing processes yourself. See [[MokoMakefile#QEMU|MokoMakefile]] for details.

=== Building the environment manually ===
To obtain the latest source code for the emulator, you will want to do something like the following:
<pre>
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
$ cd qemu-neo1973
</pre>
Now, we're going to configure and build the emulator:
<pre>
$ ./configure --target-list=arm-softmmu # GCC 3.x will be required
$ make
</pre>
See other available options for the configure script by appending "--help".
Now you have should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run OpenMoko you will also need to somehow install OpenMoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First, run
<pre>$ openmoko/download.sh</pre>
which will look up the list of latest available OpenMoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the next command:
<pre>$ openmoko/flash.sh</pre>
which runs the emulator, loads u-boot into it and then uses u-boot's capability to program the Flash memory to install all the necessary parts of the system into the virtual Flash. It will also set up all the bootloading process including a boot menu, splash, u-boot environment and some default kernel parameters. If everything goes OK, the script should print a command which you can use to start using the emulator.

QEMU has *tons* of commandline switches and things that can be configured. You can look them up in [http://www.qemu.org/user-doc.html QEMU user docs]. You will probably want to use the "-snapshot" switch, among other ones.

== Requirements ==
The QEMU tree has only been tested on GNU/Linux. To get graphical and/or audio output from the emulator you will need SDL installed on your computer. To enable audio, see the available switches to the ./configure script.
All of the requirements listed in [http://www.qemu.org/user-doc.html QEMU documentation] apply.

== QEMU and GNU debugger ==
QEMU lets you debug operating system kernels and bootloaders like you debug all other programs. To do this you will need a debugger that speaks the GDB remote debugging protocol - [http://sourceware.org/gdb/ GDB] is the obvious choice. Some cross toolchains come with GDB already set up. Otherwise building cross-GDB yourself is quick and easy (compared to building binutils and cross-gcc).

To debug u-boot, load the file "u-boot" into gdb (not "u-boot.bin") that is produced by "make" when building u-boot. To debug a Linux kernel, load the file "vmlinux" from the main source directory into gdb. These files are in ELF format and contain all the symbol information and are not stripped of debugging data until you run "strip" on them, unlike "u-boot.bin" and "Image"/"zImage"/"uImage". Next, tell QEMU to enable the gdbserver by appending the "-s" switch or issuing "gdbserver" in the monitor. Use the command <pre>(gdb) target remote localhost:1234</pre> to make a connection to the emulator. From there you should be able to use all the usual GDB commands, including stepping instructions, setting breakpoints, watchpoints, inspecting stack, variables, registers and more. If gdb is running in the same directory from which it grabbed the ELF executable, the "edit" command should work so you can jump right to the source line which is executing.

== Pre-built binaries ==

Win32 binaries shipped with firmware could be downloaded: [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070416.zip openmoko-emulator-win32-bin-20070416.zip]. Tested on Windows XP. Screenshot:
[[Image:MokoWin32Emu.jpg|OpenMoko emulator running on Windows XP]]