Openmoko - User contributions [en]

Who is Who

2008-08-07T11:17:13Z

CesarB: add wiki user for Brenda

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Anthony Chang || || || || Software Developer
|-
| Candy Chou || || {{user|candy_chou}} || || GTA/HXD Hardware Engineer
|-
| Dkay Chen || || {{user|dkay_chen}} || || GTA/HXD Hardware Engineer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA ||
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Shawn Lin || || {{user|shawn_lin}} || || RF Engineer
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || ''michael'' at openmoko dot ''org'' || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || {{user|Coolcat}} || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

== Proeminent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Lorn Potter || ''lpotter'' at ''trolltech'' dot ''com'' || || lpotter || Qtopia developer
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

== See also ==

* [[The original core team]]

[[Category:Openmoko Inc]]

Wiki statistic numbers

2008-08-07T11:14:51Z

CesarB: fix links; fmt

Openmoko uses Google Analytics to get visitor's information. On this page, you can find every kind of wiki statistic numbers.

==July, 2008==

*[[Media:Top250content.pdf|Top 250 content]]
*[[Media:Keyword.pdf|Search Keyword]]
*[[Media:Exitpage.pdf|Top leaving pages]]

Who is Who

2008-08-05T00:18:29Z

CesarB: another email

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA ||
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || ''michael'' at openmoko dot ''org'' || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

== Proeminent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Lorn Potter || ''lpotter'' at ''trolltech'' dot ''com'' || || lpotter || Qtopia developer
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

== See also ==

* [[The original core team]]

[[Category:Openmoko Inc]]

Who is Who

2008-08-04T11:12:19Z

CesarB: lpotter

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA ||
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

== Proeminent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Lorn Potter || ''lpotter'' at ''trolltech'' dot ''com'' || || lpotter || Qtopia developer
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

== See also ==

* [[The original core team]]

[[Category:Openmoko]]

Who is Who

2008-08-04T11:10:16Z

CesarB: graeme/XorA

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA ||
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

== Proeminent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

== See also ==

* [[The original core team]]

[[Category:Openmoko]]

Who is Who

2008-08-04T01:59:03Z

CesarB: add community members section

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

== Proeminent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

== See also ==

* [[The original core team]]

[[Category:Openmoko]]

Who is Who

2008-08-04T01:49:45Z

CesarB: add see also

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

== See also ==

* [[The original core team]]

[[Category:Openmoko]]

Who is Who

2008-08-04T01:47:31Z

CesarB: use {{user}} template

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| 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
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || {{user|Roh}} || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

[[Category:Openmoko]]

Template:User

2008-08-04T01:44:13Z

CesarB: based on Wikipedia's Template:User

[[User:{{{1}}}|{{{1}}}]] ([[User talk:{{{1}}}|talk]] '''·''' [[Special:Contributions/{{{1}}}|contribs]])

Who is Who

2008-08-04T01:41:14Z

CesarB: add another email and nickname

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || [[User:allen_chang|allen_chang]] || || GTA Hardware Engineer
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || Software Developer
|-
| Matt Hsu || || [[User:Matt|Matt]] || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || [[User:Mickey|Mickey]] || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || [[User:Tim|Tim]] || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || [[User:steve|steve]] || || Vice President of Marketing
|-
| Sean Moss-Pultz || || [[User:Sean|Sean]] || || CEO
|-
| Joerg Reisenweber || || [[User:jOERG|jOERG]] || || Hardware Engineer
|-
| Michael Shiloh || || [[User:Michaelshiloh|Michaelshiloh]] || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || [[User:Roh|Roh]] || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || [[User:Tony Tu|Tony Tu]] || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || [[User:HaraldWelte|HaraldWelte]] || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || [[User:DanielWillmann|DanielWillmann]] || || Software Developer
|-
| Thomas Wood || || [[User:ThomasWood|ThomasWood]] || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:38:51Z

CesarB: add a couple of IRC nicknames

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || [[User:allen_chang|allen_chang]] || || GTA Hardware Engineer
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || || Software Developer
|-
| Matt Hsu || || [[User:Matt|Matt]] || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || [[User:Mickey|Mickey]] || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || [[User:Tim|Tim]] || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || [[User:steve|steve]] || || Vice President of Marketing
|-
| Sean Moss-Pultz || || [[User:Sean|Sean]] || || CEO
|-
| Joerg Reisenweber || || [[User:jOERG|jOERG]] || || Hardware Engineer
|-
| Michael Shiloh || || [[User:Michaelshiloh|Michaelshiloh]] || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || [[User:Roh|Roh]] || roh || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || [[User:Tony Tu|Tony Tu]] || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || || [[User:HaraldWelte|HaraldWelte]] || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || [[User:DanielWillmann|DanielWillmann]] || || Software Developer
|-
| Thomas Wood || || [[User:ThomasWood|ThomasWood]] || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:34:09Z

CesarB: clear unknown cells in the last column too

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || [[User:allen_chang|allen_chang]] || || GTA Hardware Engineer
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || || Software Developer
|-
| Matt Hsu || || [[User:Matt|Matt]] || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || [[User:Mickey|Mickey]] || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || [[User:Tim|Tim]] || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || [[User:steve|steve]] || || Vice President of Marketing
|-
| Sean Moss-Pultz || || [[User:Sean|Sean]] || || CEO
|-
| Joerg Reisenweber || || [[User:jOERG|jOERG]] || || Hardware Engineer
|-
| Michael Shiloh || || [[User:Michaelshiloh|Michaelshiloh]] || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || [[User:Roh|Roh]] || || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || [[User:Tony Tu|Tony Tu]] || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || || [[User:HaraldWelte|HaraldWelte]] || || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || [[User:DanielWillmann|DanielWillmann]] || || Software Developer
|-
| Thomas Wood || || [[User:ThomasWood|ThomasWood]] || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:33:16Z

CesarB: clear unknown table cells; show real wiki username instead of hiding it within the link

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || [[User:allen_chang|allen_chang]] || || GTA Hardware Engineer
|-
| Anthony Chang || || || || Software Developer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || || (title unknown)
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || || Software Developer
|-
| Matt Hsu || || [[User:Matt|Matt]] || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || [[User:Mickey|Mickey]] || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || [[User:Tim|Tim]] || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || [[User:steve|steve]] || || Vice President of Marketing
|-
| Sean Moss-Pultz || || [[User:Sean|Sean]] || || CEO
|-
| Joerg Reisenweber || || [[User:jOERG|jOERG]] || || Hardware Engineer
|-
| Michael Shiloh || || [[User:Michaelshiloh|Michaelshiloh]] || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || [[User:Roh|Roh]] || || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || [[User:Tony Tu|Tony Tu]] || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || || [[User:HaraldWelte|HaraldWelte]] || || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || [[User:DanielWillmann|DanielWillmann]] || || Software Developer
|-
| Thomas Wood || || [[User:ThomasWood|ThomasWood]] || || (title unknown)
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || || || || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:30:45Z

CesarB: split columns

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || [[User:allen_chang|Allen Chang]] || || GTA Hardware Engineer
|-
| Anthony Chang || ''?'' at openmoko dot ''?'' || || || Software Developer
|-
| Jeremy Chang || ''?'' at openmoko dot ''?'' || || || Software Developer
|-
| Jollen Chen ||''jollen'' at openmoko dot ''org'' || || || Marketing
|-
| Tick Chen || ''tick'' at openmoko dot ''com'' || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || || (title unknown)
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || || || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || || Software Developer
|-
| Matt Hsu || || [[User:Matt|Matt_Hsu]] || || Software Developer
|-
| Wendy Hung || ''?'' at openmoko dot ''?'' || || || Testing
|-
| Regina Kim || ''?'' at openmoko dot ''?'' || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || [[User:Mickey|Mickey]] || || Software Developer
|-
| John Lee || ''?'' at openmoko dot ''?'' || || || Software Developer
|-
| Tim Lee || || [[User:Tim|Tim_Lee]] || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer
|-
| Jan 'Shoragan' Luebbe || ''?'' at openmoko dot ''?'' || || || Openmoko student (part-time)
|-
| Steven Mosher || || [[User:steve|steve]] || || Vice President of Marketing
|-
| Sean Moss-Pultz || || [[User:Sean|Sean]] || || CEO
|-
| Joerg Reisenweber || || [[User:jOERG|jOERG]] || || Hardware Engineer
|-
| Michael Shiloh || || [[User:Michaelshiloh|Michaelshiloh]] || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || || [[User:Roh|Roh]] || || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || || [[User:Tony Tu|Tony Tu]] || || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || || || Wiki editor
|-
| Harald Welte || || [[User:HaraldWelte|LaForge]] || || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || [[User:DanielWillmann|DanielWillmann]] || || Software Developer
|-
| Thomas Wood || || [[User:ThomasWood|ThomasWood]] || || (title unknown)
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || ''?'' at openmoko dot ''?'' || || || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:26:05Z

CesarB: reorder columns in preparation to split username/email column

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! Username / email !! Position
|-
| Allen Chang || [[User:allen_chang|Allen Chang]] || GTA Hardware Engineer
|-
| Anthony Chang || ''?'' at openmoko dot ''?'' || Software Developer
|-
| Jeremy Chang || ''?'' at openmoko dot ''?'' || Software Developer
|-
| Jollen Chen ||''jollen'' at openmoko dot ''org'' || Marketing
|-
| Tick Chen || ''tick'' at openmoko dot ''com'' || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || (title unknown)
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || Software Developer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || Software Developer
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || Software Developer
|-
| Matt Hsu || [[User:Matt|Matt_Hsu]] || Software Developer
|-
| Wendy Hung || ''?'' at openmoko dot ''?'' || Testing
|-
| Regina Kim || ''?'' at openmoko dot ''?'' || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || [[User:Mickey|Mickey]] || Software Developer
|-
| John Lee || ''?'' at openmoko dot ''?'' || Software Developer
|-
| Tim Lee || [[User:Tim|Tim_Lee]] || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || Software Developer
|-
| Jan 'Shoragan' Luebbe || ''?'' at openmoko dot ''?'' || Openmoko student (part-time)
|-
| Steven Mosher || [[User:steve|steve]] || Vice President of Marketing
|-
| Sean Moss-Pultz || [[User:Sean|Sean]] || CEO
|-
| Joerg Reisenweber || [[User:jOERG|jOERG]] || Hardware Engineer
|-
| Michael Shiloh || [[User:Michaelshiloh|Michaelshiloh]] || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || Vice President of Engineering
|-
| Joachim Steiger || [[User:Roh|Roh]] || Central Services
|-
| Harry Tsai || ''harry'' at openmoko dot ''com'' || Vice President of Sales
|-
| Neng-Yu 'Tony' Tu || [[User:Tony Tu|Tony Tu]] || Software Developer
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || Wiki editor
|-
| Harald Welte || [[User:HaraldWelte|LaForge]] || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || [[User:DanielWillmann|DanielWillmann]] || Software Developer
|-
| Thomas Wood || [[User:ThomasWood|ThomasWood]] || (title unknown)
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || Software Developer
|-
| Erin Yeh || ''?'' at openmoko dot ''?'' || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:21:21Z

CesarB: lead section should not have a heading; rm useless tags; minor whitespace fixes

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Username / email !! Name !! Position
|-
| [[User:allen_chang|Allen Chang]] || Allen Chang || GTA Hardware Engineer
|-
| ''?'' at openmoko dot ''?'' || Anthony Chang || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Jeremy Chang || Software Developer
|-
| ''jollen'' at openmoko dot ''org'' || Jollen Chen || Marketing
|-
| ''tick'' at openmoko dot ''com'' || Tick Chen || Software Developer
|-
| ''charlie'' at openmoko dot ''org'' || Guillaume 'Charlie' Chereau || (title unknown)
|-
| ''julian_chu'' at openmoko dot ''com'' || Julian Chu || Software Developer
|-
| ''zecke'' at openmoko dot ''org'' || Holger 'Zecke' Freyther || Software Developer
|-
| ''andy'' at openmoko dot ''com'' || Andy Green || Software Developer
|-
| ''raster'' at openmoko dot ''org'' || Carsten Haitzler || Software Developer
|-
| [[User:Matt|Matt_Hsu]] || Matt Hsu || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Wendy Hung || Testing
|-
| ''?'' at openmoko dot ''?'' || Regina Kim || Testing
|-
| ''will'' at openmoko dot ''com'' || William Lai || Design Team Project Manager
|-
| [[User:Mickey|Mickey]] || Michael 'Mickey' Lauer || Software Developer
|-
| ''?'' at openmoko dot ''?'' || John Lee || Software Developer
|-
| [[User:Tim|Tim_Lee]] || Tim Lee || Hardware Manager
|-
| ''marek'' at openmoko dot ''com'' || Marek Lindner || Software Developer
|-
| ''xiangfu'' at openmoko dot ''org'' || Xiangfu Liu || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Jan 'Shoragan' Luebbe || Openmoko student (part-time)
|-
| [[User:steve|steve]] || Steven Mosher || Vice President of Marketing
|-
| [[User:Sean|Sean]] || Sean Moss-Pultz || CEO
|-
| [[User:jOERG|jOERG]] || Joerg Reisenweber || Hardware Engineer
|-
| [[User:Michaelshiloh|Michaelshiloh]] || Michael Shiloh || Head of Developer Relations
|-
| ''wolfgang'' at openmoko dot ''com'' || Wolfgang Spraul || Vice President of Engineering
|-
| [[User:Roh|Roh]] || Joachim Steiger || Central Services
|-
| ''harry'' at openmoko dot ''com'' || Harry Tsai || Vice President of Sales
|-
| [[User:Tony Tu|Tony Tu]] || Neng-Yu 'Tony' Tu || Software Developer
|-
| ''brenda_wang'' at openmoko dot ''com'' || Brenda Wang || Wiki editor
|-
| [[User:HaraldWelte|LaForge]] || Harald Welte || (Left Openmoko. Here for archives.)
|-
| [[User:DanielWillmann|DanielWillmann]] || Daniel 'Alphaone' Willmann || Software Developer
|-
| [[User:ThomasWood|ThomasWood]] || Thomas Wood || (title unknown)
|-
| ''olv'' at openmoko dot ''org'' || OLV Wu || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Erin Yeh || Software Developer
|}

[[Category:Openmoko]]

Who is Who

2008-08-04T01:18:31Z

CesarB: Whoiswho moved to Who is Who

==Why this page ?==

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something ?

So I propose to fill out this list to help people get to know each other
 

==Officials members of the Openmoko Team==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Username / email !! Name !! Position
|-
| [[User:allen_chang|Allen Chang]] || Allen Chang || GTA Hardware Engineer
|-
| ''?'' at openmoko dot ''?'' || Anthony Chang || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Jeremy Chang || Software Developer
|-
| ''jollen'' at openmoko dot ''org'' || Jollen Chen || Marketing
|-
| ''tick'' at openmoko dot ''com'' || Tick Chen || Software Developer
|-
| ''charlie'' at openmoko dot ''org'' || Guillaume 'Charlie' Chereau || (title unknown)
|-
| ''julian_chu'' at openmoko dot ''com'' || Julian Chu || Software Developer
|-
| ''zecke'' at openmoko dot ''org'' || Holger 'Zecke' Freyther || Software Developer
|-
| ''andy'' at openmoko dot ''com'' || Andy Green || Software Developer
|-
| ''raster'' at openmoko dot ''org'' || Carsten Haitzler || Software Developer
|-
| [[User:Matt|Matt_Hsu]] || Matt Hsu || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Wendy Hung || Testing
|-
| ''?'' at openmoko dot ''?'' || Regina Kim || Testing
|-
| ''will'' at openmoko dot ''com'' || William Lai || Design Team Project Manager
|-
| [[User:Mickey|Mickey]] || Michael 'Mickey' Lauer || Software Developer
|-
| ''?'' at openmoko dot ''?'' || John Lee || Software Developer
|-
| [[User:Tim|Tim_Lee]] || Tim Lee || Hardware Manager
|-
| ''marek'' at openmoko dot ''com'' || Marek Lindner || Software Developer
|-
| ''xiangfu'' at openmoko dot ''org'' || Xiangfu Liu || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Jan 'Shoragan' Luebbe || Openmoko student (part-time)
|-
| [[User:steve|steve]] || Steven Mosher || Vice President of Marketing
|-
| [[User:Sean|Sean]] || Sean Moss-Pultz || CEO
|-
| [[User:jOERG|jOERG]] || Joerg Reisenweber || Hardware Engineer
|-
| [[User:Michaelshiloh|Michaelshiloh]] || Michael Shiloh || Head of Developer Relations
|-
| ''wolfgang'' at openmoko dot ''com'' || Wolfgang Spraul || Vice President of Engineering
|-
| [[User:Roh|Roh]] || Joachim Steiger || Central Services
|-
| ''harry'' at openmoko dot ''com'' || Harry Tsai || Vice President of Sales
|-
| [[User:Tony Tu|Tony Tu]] || Neng-Yu 'Tony' Tu || Software Developer
|-
| ''brenda_wang'' at openmoko dot ''com'' || Brenda Wang || Wiki editor
|-
| [[User:HaraldWelte|LaForge]] || Harald Welte || (Left Openmoko. Here for archives.)
|-
| [[User:DanielWillmann|DanielWillmann]] || Daniel 'Alphaone' Willmann || Software Developer
|-
| [[User:ThomasWood|ThomasWood]] || Thomas Wood || (title unknown)
|-
| ''olv'' at openmoko dot ''org'' || OLV Wu || Software Developer
|-
| ''?'' at openmoko dot ''?'' || Erin Yeh || Software Developer
|}

 

[[Category:Openmoko]]

Neo 1973 hardware

2008-03-08T22:23:59Z

CesarB: /* Analog wired Headset */ copy pinout from mailing list

[[OpenMoko]] is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo1973]] phone is the first hardware platform to take advantage of OpenMoko. You can find specifics of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] by reviewing this introduction page and the pages in the category as shown at the bottom of this page.

'''Note that this page is about the first OpenMoko phone which is now discontinued. See details on the second OpenMoko phone at this page - [[Neo FreeRunner GTA02 Hardware]].'''

[[Image:Gta01b v3 top.jpg|thumb|400px|display (top) side]]
[[Image:Gta01b v3 bottom.jpg|thumb|400px|component (back) side]]

==User experiences of Phase 0 hardware==
[[Wishlist:Neo1973_P0_Review]]

==User reports of robustness==
User experiences - drops onto concrete - ... [[Neo1973 Robustness]]

== Physical Dimensions ==
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)
* 184 +/- 5 g (6.5 ounces)
* For the purposes of acquiring/cutting a properly sized screen protector, the display hole of the case is about 45 x 59 mm, while the top cover internal frame can house up to a 53 x 74 mm protector; sizes much larger than the display hole would obviously necessitate removing the front cover for installation.
* A Useful size comparison between the Neo1973, iPhone, Motorola A1200 and the SEM600i can be seen at [http://www.sizeasy.com/page/size_comparison/5512-Neo1973-vs-Apple-iPhone-vs-M600i-2-vs-A-1200 sizeasy]

== Main components ==
=== Processor ===
The main Processor (CPU) of the Neo1973 is a Samsung S3C2410AL-26 (Capable of running up to 266 MHz)

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2410 S3C2410.htm]
* User Manual: [http://www.samsung.com/global/business/semiconductor/productRightMenuDown.do?doc_file=26537 2410UserManual.pdf]
* Core: ARM920T
* Instruction Set: ARMv4 (Android ''currently'' requires ARMv5)
* BSDL File: [http://www.samsung.com/global/business/semiconductor/productRightMenuDown.do?doc_file=26554 S3C2410_BGA_BSDLJTAGFILE.bsd]
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA01Bv4/gpio.txt

=== Flash ===
64MB Samsung NAND flash (K9F1208U0B) attached to S3C2410 NAND controller.

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=158&partnum=K9F1208U0B]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/NANDFlash/SLC_SmallBlock/512Mbit/K9F1208U0B/ds_k9f1208x0b_rev03.pdf]
* Connected to: S3C2410 NAND controller

This is the only flash memory in the device. The S3C2410 boots directly from nand, using the [[S3C2410 Steppingstone]].

We only use free software, no proprietary flash file systems. For a full description of how it is used, see [[NAND bad blocks]]

=== RAM ===
128MB SDRAM (2x Samsung K4M511633C) attached to S3C2410 SDRAM controller
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M511633C]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M511633C/ds_k4m511633c.pdf]
* Connected to: S3C2410

=== GSM/GPRS ===
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.

* Connected to: S3C2410 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* Accessible GSM/GPRS antenna jack (if battery cover is removed)

==== CALYPSO digital baseband ====
Unfortunately we cannot provide many details on the GSM chipset due to very tight NDAs. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2410. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.

==== TWL3014 analog baseband ====
Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014]

==== TRF6151 RF Transceiver ====
Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] 
GPRS Class12/CS4 

=== [[Hardware:AGPS|AGPS]] ===
Hammerhead PMB 2520 AGPS from Global Locate.

* Product Homepage: [http://www.globalocate.com/SEMICONDUCTORS/SEMI_HAMMER_Frameset.htm Hammerhead]
* Connected to: S3C2410 UART2 (full-uart, RxD, TxD, CTS, RTS) /dev/ttySAC1 in userspace
* Driver: Implemented as a binary with NMEA output suitable for the gpsd daemon ([[gpsd]])
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* Externally-accessible GPS antenna connector of type MMCX

The binary driver is available - see [[GLLIN]].
Efforts to reverse engineer the protocol are partially detailed in [[Hammerhead/Protocol]], these have stalled since the announcement that [[FreeRunner]] will use a different GPS.

=== microSD-Card ===
The Neo1973 has one microSD aka Transflash slot.
It supports SDHC. MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].
* Connected to: S3C2410 MMC/SD controller
* Mounted to: /media/card
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/confirm/confirm_memorycard.aspx SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]

=== LCD Module (LCM) ===
This is a 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 toppoly (tpo) TD028TTEC1 module (283 DPI), using a Toshiba JBT6K74 TFT LCD Driver Chipset.
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch
* Connected to: S3C2410 Display Controller and S3C2410 SPI Interface channel 1
* Backlight controllable via /sys/class/backlight/gta01-bl

==== Touch Screen ====
* Connected to: S3C2410 TS controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_touchscreen.patch

==== Stylus ====

Seemingly identical to [http://cgi.ebay.com/4in1-PDA-Stylus-LED-Light-Torch-Laser-Pointer-Pen-h7_W0QQitemZ280089656134QQihZ018QQcategoryZ48677QQrdZ1QQcmdZViewItem this one on ebay]

=== Bluetooth ===
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4 (V2.0+EDR).

* Data Sheet: [http://www.delta.com.tw/product/cp/vco/BT/download/pdf/CS/2.DFBM-CS320.pdf 2.DFBM-CS320.pdf]
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]
* Driver: Stock Linux Kernel BlueZ
* Connected to: S3C2410 USB Host controller (OHCI)
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch

=== Vibrator ===
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch
* Connected to: S3C2410 GPIO
* Controllable via /sys/class/leds/gta01:vibrator

=== USB Host ===
The USB Host controller is inside the S3C2410
* Driver: Stock Linux kernel ohci_hcd

=== USB Device ===
The USB Device controller is inside the S3C2410
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use
* 1200mAh lithium battery charges when connected to powered host.
* Mini-B connector [http://www.cypressindustries.com/enlarge.asp?Img=products/images/ccmusbb-32005-601.gif this one].
* This can be used as a USB host: [[Neo1973_USB_host]]

=== I2C Devices ===
The I2C is a simple communication standard intended to move small amounts of data a few inches between chips.
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.

=== Audio ===
See also: [[Neo1973 Audio Subsystem]]

==== Wolfson Codec ====

''Main article: [[WM8753]]''

There's a [[WM8753]] Wolfson Microelectronics ''codec'' (This is not a "smart" codec that can interpret MP3/... it is a simple dumb "sound card".

==== Stereo Amplifier ====
There's a National Semiconductor [[LM4857]] Stereo Amplifier at the analog audio output of the WM8753

* Product Homepage: [http://www.national.com/pf/LM/LM4857.html LM4857.html]
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4857.pdf LM4857.pdf]
* Connects to: S3C2410 I2C (Control)

==== Analog wired Headset ====
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.

The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration.

Pinout: [http://lists.openmoko.org/pipermail/community/2008-March/013791.html]

<pre><nowiki>
base = ground
speaker left (internal impedance 33R) to ground. (+jackinsert detection)
speaker right (internal impedance 33R) to ground.
tip = mic electret condenser type, to ground.
bias (power for mic) 2K2 from +3.3v(wolfson codec)
(+HoldButton shortcircuit to ground)
</nowiki></pre>

==== Bluetooth Headset ====
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec.

=== Power Management ===
A Philips PCF50606 is used for [[Neo1973_Power_Management|power management]].

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2410 via I2C, client address is 0x08.
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-pcf50606.patch

=== Battery ===
The [[Neo1973 Battery]] is compatible with a Nokia BL5C battery.
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.

=== Buttons ===
The Neo1973 features two buttons:
# [[Neo1973 Power Button|The Power Button]]
# [[Neo1973 AUX Button|The "Aux" button]]

=== Alternate cases ===
A number of alternate case designs have been suggested and requested.

[[Neo1973 case schematics]]

[[Alternate Neo1973 case designs]]

== History ==
=== GTA01 ===
This is the most simple, non-bluetooth version of the prototype.

==== GTA01v3 ====
First generation of prototypes that was given to internal OpenMoko software developers.

Unfortunately not useful at all due to non-working touchscreen.

* ATAG_REVISION: 0x0000130

==== GTA01v4 ====
Second generation of prototypes that was given to [[User:HaraldWelte|Harald]] +[[User:Mickey|Mickey]].

Unfortunately still not useful due to half-working touchscreen.

* ATAG_REVISION: 0x00000140

=== GTA01B ===
This is the bluetooth-enabled fork of GTA01

==== GTA01Bv2 ====
This is the first produced version of the bluetooth-enabled version.

* ATAG_REVISION: 0x00000220

==== GTA01Bv3 ====
This is the second produced version of the bluetooth-enabled version. It contains mainly GPS-related fixes.

* ATAG_REVISION: 0x00000230

This is the version that is shipped in [[Neo1973#Phase_0_.28GTA01Bv3.29|Phase 0]].

===== GTA01Bv3 Errata =====
====== PMU unable to resume from suspend ======
Due to use of wrong GPIO/EINT pin, the PMU cannot wake-up the phone after suspend. This means, specifically, '''the following events can not bring the phone back from suspend-to-ram''':
* PMU RTC Alarm
* Power button press
* Charger events (charger insertion/removal/error)
* Low battery

====== Stand-by time extremely low ======
This is due to a design bug resulting in at least 30mA additional standby current, since we cannot properly switch off the power supply to the S3C2410 PLL's. There is nothing we can do to change this with post-production fixes. GTA01Bv4 will address this issue.

====== GSM doesn't resume phone from suspend ======
The GSM modem currently doesn't signalize a wakeup interrupt to the S3C2410 in case there's some noteworthy event, such as incoming call, loss of network, incoming SMS or the like.

This is a serious issue, but can be fixed with a GSM Modem Firmware update.

====== GSM Sidetone too loud ======
The local feedback sidetone (see [http://en.wikipedia.org/wiki/Sidetone]) is too loud. This will be addressed in a GSM firmware update

====== Bad block ======
Due to an error in the production process, the factory-programmed NAND bad block information has been lost. This means that some blocks in the flash will wear out rapidly, which might become as bad as rendering the device unusable.

==== GTA01Bv4 ====
This is the version that is being shipped in [[Neo1973#Phase_1_.28GTA01Bv4.29|Phase 1]]

===== Looks =====
This is what the GTA01Bv4 PCB looks like without the shielding cans, which will be fitted later.
[[Image:Gta01b_v4_front.jpg|thumb|400px|Component side]]
[[Image:Gta01b_v4_back.jpg|thumb|400px|Display side]]

===== Errata =====

There were two versions of GTA01Bv4: some were given away (red mainboard), and some were sold (green mainboard). The given-away have [[one transistor too many]].

===== Changes from GTA01Bv3 =====
# Fix all Errata items from GTA01Bv3
# Add I2C, SPI and one irq and wakeup capable GPIO pin to debug port plus have test pads for all these signals (for soldering wires directly on the pcb)
# Fix a number of production related details and minor hardware details that are not user-visible

===GTA02===
The [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]] is now called the Neo FreeRunner and shipped within the "Mass Market launch" (see [http://wiki.openmoko.org/wiki/Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|timeline]).
It is a new main release with [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|features added]]

===Debug Connector===
This is the connector used to connect the [[Debug Board]] and possibly other hardware.

Connections are:
* 39 - GND
* 38 - STDI
* 37 - _RESET
* 36 - STMS
* 35 - STCK
* 34 - STDO
* 33 - GSM_EN
* 29 - _STRST
* 19 - X_I2C_SCL (H-TP4703)
* 18 - X_I2C_SDA (H-TP4704)
* 17 - SPI_CLK0
* 16 - SPI_MOSI0
* 15 - SPI-MISO0
* 14 - SS0
* 13 - EINT3 (H-TP4705)
* 3 - MODEM_TXD (H-TP4701)
* 2 - MODEM_RXD (H-TP4702)

Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].

== Distinguishing hardware revisions ==
=== Inside the [[Bootloader]] ===
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)

=== Inside the [[Kernel]] ===
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.

=== From Userspace ===
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.

??? So does GTA01Bv4 equal the cat /proc/cpuinfo output of
Hardware : GTA01
Revision : 0240

== Approval ==
*CE compliance is needed before a product can be sold in the EU. The CE mark indicates that a product complies to the relevant legislation, defined in the [http://ec.europa.eu/enterprise/newapproach/standardization/harmstds/reflist.html harmonised standards]. This refers also to the most relevant, for the Neo1973, [http://ec.europa.eu/enterprise/newapproach/standardization/harmstds/reflist/emc.html Directive 89/336/EEC on electromagnetic compatibility] (EMC is the art of assuring [http://en.wikipedia.org/wiki/Electromagnetic_compatibility electromagnetic compatibility] between products). The standards are defined by [http://www.cenelec.org CENELEC] (European Committee for Electrotechnical Standardization), but not verified by any authority. It is the responsibilty of the manufacturer to convince himself that a product is in compliance, and is obligated to be able to prove this (with relevant technical documentation) for a specific product to the authorities on request. Whether the current Phase 1 devices are actually tested against the directives are unknown, no documentation has been disclosed, other than the fact that the devices bear the CE mark.

*[http://www.fcc.gov/ FCC]

{{Languages|Neo1973 Hardware}}

[[Category:Neo1973 Hardware| ]]
[[Category:Hardware ]]
[[Category:Supported Phone| ]]

User:CesarB/cpufreq

2008-02-13T01:27:32Z

CesarB: link to ML post

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the s3c2410-cpufreq-om branch.

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is mostly untested, and changes frequently. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-om branch (or the wip branch for work in progress)
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* Do not compile the cpufreq driver as a module, since several of the notifiers depend on functions defined in it and would thus end up being compiled as modules too.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master-om..s3c2410-cpufreq-om</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).
* When trying for the first time, it's best to start slow:
*# Do all the tests without the USB cable (disconnect before changing the governor/frequencies), since it misbehaves (will be later changed to prohibit changing frequencies when the cable is connected). It's best to also remove the SD card and SIM, just in case.
*# Boot with <code>cpufreq.debug=7</code> on the kernel command line and carefully inspect the kernel output for any incorrect output.
*# Disable the cpufreq printk rate limit (<code>cpufreq.debug_ratelimit=0</code>; it can be set via <code>/sys/modules/cpufreq/parameters</code>).
*# Set the governor to <code>userspace</code> and switch to the second highest frequency. Check the kernel output again (be on the lookout in particular for frequency mismatch messages from the cpufreq core).
*# Work down the list of frequencies and check if they all work correctly (not all can be selected since the drivers reject some of them).
*# Edit the code to disable the policy rejection of frequencies (returning at the top of <code>s3c2410_cpufreq_adjust_table</code> and <code>s3c2410_cpufreq_adjust_pin</code> should be enough) to be able to test all frequencies. Start again from the top of the list; watch in particular for the SLOW mode ones (12000 and below). There's no need to go all the way down to 1000; all SLOW mode ones should work the same, and it's very annoying. Test going back from SLOW mode to the lowest non-SLOW frequency, and jumping from SLOW mode to the maximum frequency (this last case can cause misterious crashes if the registers were set out of order, causing the bus to go too fast).
*# Revert the changes made to the code above.
*# Try the <code>conservative</code> governor.
*# Try the <code>ondemand</code> governor (it's the one which stresses the most the cpufreq mechanism).

== What's already done ==

{| border="1"
|-
! Driver !! Status (GTA01) !! Status (GTA02)
|-
| core || Working || '''Untested'''
|-
| timer || Working || '''Untested'''
|-
| nand || Working || '''Untested'''
|-
| serial || Working || '''Untested'''
|-
| framebuffer || Working || '''Untested'''
|}

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for dynamically changing the frequency divider used to derive the video clocks.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

== Frequency restrictions ==

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.
* The serial baudrate generator might not have a good enough divider value for some baud rates and some clock frequencies (for instance, 115200 at 12000 kHz)

== See also ==

* [[Neo1973 GTA01 Power Management]]

== External links ==

* [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-February/001021.html Experimental S3C2410A cpufreq driver] (2008-02-12)

User:CesarB/cpufreq

2008-02-07T23:57:56Z

CesarB: /* Hints */ testing hints

User:CesarB/cpufreq

2008-02-07T23:40:52Z

CesarB: update

User:CesarB/cpufreq

2008-02-06T21:37:45Z

CesarB: update

User:CesarB/cpufreq

2008-02-04T23:25:55Z

CesarB: /* Frequency restrictions */ change heading level

User:CesarB/cpufreq

2008-02-04T23:25:32Z

CesarB: /* What's missing */ update

User:CesarB/cpufreq

2008-02-04T20:09:55Z

CesarB: /* Hints */ modules

User:CesarB/cpufreq

2008-02-03T02:53:37Z

CesarB: /* To build */ wip branch

User:CesarB/cpufreq

2008-02-03T02:53:07Z

CesarB: /* What's already done */ framebuffer -> working

User:CesarB/cpufreq

2008-02-02T01:25:56Z

CesarB: update

User:CesarB/cpufreq

2008-01-27T20:47:41Z

CesarB: /* Testing report */

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.
* The serial baudrate generator might not have a good enough divider value for some baud rates and some clock frequencies (for instance, 115200 at 12000 kHz)

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

=== 2008-01-22 ===

After a few more bugfixes, still 2.6.22.5, also tested from the terminal (untethered).

This time, due to the nature of the tests, I commented out all speeds below 12000 kHz.

* Setting governor to "conservative": works, and the flicker patterns shows neatly the change of operating frequencies.
* Setting governor to "ondemand": works, however after a few seconds on 12000 kHz it got "stuck" there. For some reason, <code>cat scaling_cur_speed</code> locked up (not answering to Ctrl-C/Ctrl-Z); requested a shutdown via the power menu, which worked (still with the severe flicker showing it was still at 12000 kHz.

Another test was to see if gsmd still worked.

* With "conservative": timeout.
* With "userspace", testing by changing the frequency and typing "at" at <code>libgsmd-tool -m atcmd</code> and checking for the response: worked at 266000, 133000, 66000, 33000, and ''failed'' at 12000 (timeout).

=== 2008-01-26 ===

Trying to find out why gsmd stops working at 12000.

* Adding a debug printk to the end of s3c24xx_serial_getclk, the error is 7% with 12000, while below 2% at the other frequencies tested above.
* Trying to make gsmd run at 57600 instead of 115200 didn't work, even after making the kernel use the same speed for the serial console. Changing from 57600 to 115200 worked without even rebooting; looks like the modem doesn't autodetect the serial speed.
* Calculations with all the frequencies at/below 12000 (plus 5000 and 3000 which can be derived from them) show none will work with the serial (the error is too large on all of them).

=== 2008-01-27 ===

After writing more code to fix the serial issue.

* gsmd works fine with "conservative"
* gsmd works fine with "ondemand"
* The minimum frequency the new code selected was 45000.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-26T23:51:43Z

CesarB: /* 2008-01-26 */

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.
* The serial baudrate generator might not have a good enough divider value for some baud rates and some clock frequencies (for instance, 115200 at 12000 kHz)

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

=== 2008-01-22 ===

After a few more bugfixes, still 2.6.22.5, also tested from the terminal (untethered).

This time, due to the nature of the tests, I commented out all speeds below 12000 kHz.

* Setting governor to "conservative": works, and the flicker patterns shows neatly the change of operating frequencies.
* Setting governor to "ondemand": works, however after a few seconds on 12000 kHz it got "stuck" there. For some reason, <code>cat scaling_cur_speed</code> locked up (not answering to Ctrl-C/Ctrl-Z); requested a shutdown via the power menu, which worked (still with the severe flicker showing it was still at 12000 kHz.

Another test was to see if gsmd still worked.

* With "conservative": timeout.
* With "userspace", testing by changing the frequency and typing "at" at <code>libgsmd-tool -m atcmd</code> and checking for the response: worked at 266000, 133000, 66000, 33000, and ''failed'' at 12000 (timeout).

=== 2008-01-26 ===

Trying to find out why gsmd stops working at 12000.

* Adding a debug printk to the end of s3c24xx_serial_getclk, the error is 7% with 12000, while below 2% at the other frequencies tested above.
* Trying to make gsmd run at 57600 instead of 115200 didn't work, even after making the kernel use the same speed for the serial console. Changing from 57600 to 115200 worked without even rebooting; looks like the modem doesn't autodetect the serial speed.
* Calculations with all the frequencies at/below 12000 (plus 5000 and 3000 which can be derived from them) show none will work with the serial (the error is too large on all of them).

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-26T23:00:22Z

CesarB: /* Frequency restrictions */ baud rate problem

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.
* The serial baudrate generator might not have a good enough divider value for some baud rates and some clock frequencies (for instance, 115200 at 12000 kHz)

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

=== 2008-01-22 ===

After a few more bugfixes, still 2.6.22.5, also tested from the terminal (untethered).

This time, due to the nature of the tests, I commented out all speeds below 12000 kHz.

* Setting governor to "conservative": works, and the flicker patterns shows neatly the change of operating frequencies.
* Setting governor to "ondemand": works, however after a few seconds on 12000 kHz it got "stuck" there. For some reason, <code>cat scaling_cur_speed</code> locked up (not answering to Ctrl-C/Ctrl-Z); requested a shutdown via the power menu, which worked (still with the severe flicker showing it was still at 12000 kHz.

Another test was to see if gsmd still worked.

* With "conservative": timeout.
* With "userspace", testing by changing the frequency and typing "at" at <code>libgsmd-tool -m atcmd</code> and checking for the response: worked at 266000, 133000, 66000, 33000, and ''failed'' at 12000 (timeout).

=== 2008-01-26 ===

Trying to find out why gsmd stops working at 12000.

* Adding a debug printk to the end of s3c24xx_serial_getclk, the error is 7% with 12000, while below 2% at the other frequencies tested above.
* Trying to make gsmd run at 57600 instead of 115200 didn't work, even after making the kernel use the same speed for the serial console. Changing from 57600 to 115200 worked without even rebooting; looks like the modem doesn't autodetect the serial speed.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-26T22:33:01Z

CesarB: /* Testing report */ gsmd speed

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

=== 2008-01-22 ===

After a few more bugfixes, still 2.6.22.5, also tested from the terminal (untethered).

This time, due to the nature of the tests, I commented out all speeds below 12000 kHz.

* Setting governor to "conservative": works, and the flicker patterns shows neatly the change of operating frequencies.
* Setting governor to "ondemand": works, however after a few seconds on 12000 kHz it got "stuck" there. For some reason, <code>cat scaling_cur_speed</code> locked up (not answering to Ctrl-C/Ctrl-Z); requested a shutdown via the power menu, which worked (still with the severe flicker showing it was still at 12000 kHz.

Another test was to see if gsmd still worked.

* With "conservative": timeout.
* With "userspace", testing by changing the frequency and typing "at" at <code>libgsmd-tool -m atcmd</code> and checking for the response: worked at 266000, 133000, 66000, 33000, and ''failed'' at 12000 (timeout).

=== 2008-01-26 ===

Trying to find out why gsmd stops working at 12000.

* Adding a debug printk to the end of s3c24xx_serial_getclk, the error is 7% with 12000, while below 2% at the other frequencies tested above.
* Trying to make gsmd run at 57600 instead of 115200 didn't work, even after making the kernel use the same speed for the serial console. Changing from 57600 to 115200 worked without even rebooting; looks like the modem doesn't autodetect the serial speed.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-23T00:47:34Z

CesarB: /* 2008-01-22 */ gsmd (serial) test

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

=== 2008-01-22 ===

After a few more bugfixes, still 2.6.22.5, also tested from the terminal (untethered).

This time, due to the nature of the tests, I commented out all speeds below 12000 kHz.

* Setting governor to "conservative": works, and the flicker patterns shows neatly the change of operating frequencies.
* Setting governor to "ondemand": works, however after a few seconds on 12000 kHz it got "stuck" there. For some reason, <code>cat scaling_cur_speed</code> locked up (not answering to Ctrl-C/Ctrl-Z); requested a shutdown via the power menu, which worked (still with the severe flicker showing it was still at 12000 kHz.

Another test was to see if gsmd still worked.

* With "conservative": timeout.
* With "userspace", testing by changing the frequency and typing "at" at <code>libgsmd-tool -m atcmd</code> and checking for the response: worked at 266000, 133000, 66000, 33000, and ''failed'' at 12000 (timeout).

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-23T00:01:53Z

CesarB: /* Testing report */

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

=== 2008-01-22 ===

After a few more bugfixes, still 2.6.22.5, also tested from the terminal (untethered).

This time, due to the nature of the tests, I commented out all speeds below 12000 kHz.

* Setting governor to "conservative": works, and the flicker patterns shows neatly the change of operating frequencies.
* Setting governor to "ondemand": works, however after a few seconds on 12000 kHz it got "stuck" there. For some reason, <code>cat scaling_cur_speed</code> locked up (not answering to Ctrl-C/Ctrl-Z); requested a shutdown via the power menu, which worked (still with the severe flicker showing it was still at 12000 kHz.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-20T22:45:51Z

CesarB: add more info

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.
* To test on 2.6.22.5, use <code>git format-patch -o ''dir'' master..s3c2410-cpufreq</code> to generate a set of patches, and apply them all on top of the OpenMoko patches 2.6.22.5 kernel, ''except'' the framebuffer patch(es) (the 2.6.24.x code for the framebuffer is different from the 2.6.22.5 one).

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer; not a problem with full brightness)
* Vibrator (uses a PWM timer)
* MMC/SD (can be avoided by not plugging it in)
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-20T22:41:58Z

CesarB: /* Hints */ changing afer boot

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output. You can also enable it after boot by going to the correct place at /sys/modules and changing the values there.

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer)
* Vibrator (uses a PWM timer)
* MMC/SD
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-20T22:40:27Z

CesarB: /* Testing report */

The cpufreq subsystem is a Linux kernel subsystem responsible for managing the CPU frequency. It's commonly used in laptops to reduce power usage when idle.

On the S3C2410, adjusting the CPU frequency changes the clocks for almost all devices on the chip. This means that, to write a cpufreq driver for the S3C2410, you have to also adjust some values on almost all devices.

This project aims to implement the cpufreq driver (which manages the CPU frequency transitions) and a cpufreq notifier for all the affected drivers (to do two things: quiesce the device before the change, and adjust the frequency after the change). Deciding which frequency to use is the responsability of code from somewhere else (either cpufreq governors or userspace).

The most recent version of the code can be found at http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git on the branches s3c2410-cpufreq (for code which applies on top of the upstream "git HEAD" kernel) and s3c2410-cpufreq-gta01 (for code which applies on top of the OpenMoko patched kernel).

== To build ==

{{note|Do not run on real hardware, unless you '''''really''''' know what you are doing. This code is completely untested. It might even not compile.}}

You need a fully built OpenMoko tree for the cross-compiler and uboot tools.

# Checkout the s3c2410-cpufreq-gta01 branch
# Copy the defconfig file from branches/src/target/kernel/2.6.24.x/config on the OpenMoko svn as the <code>.config</code> file
# Set the PATH to the correct value (check the run.* temporary files bitbake generates to find out the correct value)
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- oldconfig</code> and answer correctly the questions
# Run <code>make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage</code>
# The last line of the output tells you the correct file which should be flashed on the emulator.

=== Hints ===

* Enable <code>CONFIG_CPU_FREQ_DEBUG</code> and add <code>cpufreq.debug=7</code> to the kernel command line to enable the relevant debug output.

== What's already done ==

=== S3C2410A cpufreq driver ===

This code resides on <code>arch/arm/mach-s3c2410/s3c2410-cpufreq.c</code> and is responsible for actually changing the frequency.

The list of available frequencies and their parameters (HCLK/PCLK dividers) can be found on this file.

=== Timer 4 driver ===

Timer 4 is used by the kernel as the periodic tick timer. The cpufreq notifier on <code>arch/arm/plat-s3c24xx/time.c</code> is responsible for adjusting the current and reload values of the timer to match the new frequency.

=== Serial driver ===

The cpufreq notifier on <code>drivers/serial/s3c2410.c</code> is responsible for (if possible) pausing both sides of the serial transmission before the frequency change and reloading the baud generator (and unpausing the serial transmission) after the change.

Pausing the transmission is currently only possible with hardware flow control. Since both serial ports on GTA01 use hardware flow control, that's not a problem (unless you are using the serial console).

=== Framebuffer driver ===

The cpufreq notifier on <code>drivers/video/s3c2410fb.c</code> is responsible for turning off the video before the frequency change and reloading its configuration after the frequency change.

=== NAND driver ===

The cpufreq notifier on <code>drivers/mtd/nand/s3c2410.c</code> is responsible for reprogramming the NAND timings after a frequency change.

== What's missing ==

=== S3C2410A cpufreq driver ===

The frequency table should be checked for better divisor values (1:1:1 might be appropriate in more situations), and the code should be able to deal with HDIVN1 and different bus modes.

=== Timer 4 driver ===

The cpufreq notifier should perhaps use a higher priority, so as to run before all the others for more precise timekeeping.

=== NAND driver ===

The cpufreq notifier should make sure the NAND is quiesced before the frequency change, or change the timings to the most conservative ones before the frequency change.

=== Missing drivers ===

* Backlight (uses a PWM timer)
* Vibrator (uses a PWM timer)
* MMC/SD
* I2C (without a notifier and booting at the maximum speed, it can only get slower; there should be no side effects, since there's no minimum bus speed)
* IIS
* SPI

=== Frequency restrictions ===

Some drivers need specific frequencies. Currently there's no way to tell the cpufreq core of that, but at minimum a cpufreq notifier should be used to turn them off if they won't be able to work with that frequency.

* The datasheet says the USB device gets unstable if the frequency is below a minimum value
* When using the IIS device, changing the frequency might not be a good idea, since it can cause audio glitches. It also probably needs a minimum frequency depending on the output audio frequency and sample size.
* The LCD device might also need a minimum frequency.

== Testing report ==

=== 2008-01-19 ===

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-January/000452.html 2.6.24.x doesn't boot on GTA01]. I hand-extracted the patches and applied them all on top of GTA01's 2.6.22.5 kernel, except for the framebuffer patch (which depends on some changes made after 2.6.24). It was booted on a GTA01 without the SD card or the SIM attached (just in case). The results were:

* Setting to 202800 kHz: lost the USB connection. It would be recovered only after rebooting (setting the frequency back to 266000 wasn't enough). The rest of the tests were made with the on-screen terminal.
* Setting to 133000 kHz (actually 135000 kHz): noticeable flicker, possibly because the framebuffer patch wasn't applied. The timer seems to be running at exactly half the correct rate (running "date" twice with 10s delay showed the GTA01's clock advanced only 5s).
* Rebooting (after coming back to 266000 kHz) fixed the USB connection.

=== 2008-01-20 ===

Same 2.6.22.5 kernel, with several bugfixes applied (in particular, the problem which prevented the timer notifier from running was fixed).

This time, the whole test was done from the terminal, to avoid the USB lockup.

* Setting to 133000 kHz (actually 135000 kHz): same flicker. Plugging briefly the USB shows it to still be alive. Time runs at the correct speed.
* Setting to 100000 kHz (actually 101250 kHz): even worse flicker.
* Setting to 12000 kHz (SLOW mode on): the flicker gets psychedelic (colors start oscillating). VERY slow (taking about a second to register a "key" press).
* Back to 266000 kHz: works normally. Plugging briefly the USB again shows it to still be alive. Time still running at correct speed.

== See also ==

* [[Neo1973 GTA01 Power Management]]

User:CesarB/cpufreq

2008-01-20T02:35:45Z

CesarB: testing report

User:CesarB/cpufreq

2008-01-19T20:24:13Z

CesarB: /* To build */ hints

Neo 1973 GTA01 Power Management

2008-01-19T19:07:43Z

CesarB: change s3c2410-cpufreq url

{{InProgress}}
This page details the power management of the Phase 1 Neo1973. Much of it is inapplicable to earlier models.

Power management is of utmost concern to any mobile device.
Battery power is quite limited, so we need to make sure we try our best to conserve it. (See also [[Power management requirements]].)

This is very much unimplemented at the moment.

Current projects:

{|border="1"
|+Projects
!User||Project||details||URL
|-
|[[User:CesarB|cesarb]]||Cpufreq||Varying clock speed, including making peripherals work over during transitions||
[[User:CesarB/cpufreq]]
|}

{|border="3"
|+Required kernel mode power saving, and relative saving of battery life.
!Option ||Note||Average saving over next lowest power state the description is the total effect on battery life ||Status
|-
|External peripheral control || Ability to dim backlight, turn on and off GSM, GPS, and other devices outside the CPU || Huge (700mW) ||Implemented
|-
|Slow Mode || The CPU clock is 12MHz, this is the lowest power mode with the CPU awake ||Huge(300mW)|| Not implemented
|-
|Variable CPU core voltage || Dynamically alter CPU core voltage according to frequency ||Moderate(50mW)|| Not implemented, limited by PMU to .3V steps
|-
|CPU Idle mode|| Turn off CPU clock while rest of SoC remains awake||Large(150mW)||Not implemented
|-
|Variable CPU frequency ~20Mhz to 266Mhz||Vary CPU frequency to lower power consumption.||Huge(250mW)||Not implemented
|-
|Tickless Kernel||Remove periodic timer interrupts in kernel||Modest(10mW?)||Not implemented
|-
|Rapid Suspend-RAM||Suspend CPU totally and resume when required in under 1s.||Moderate (50mW)||Not implemented

|}

{|border="3"
|+Required user-mode power saving
!Option||Note||Saving||Status
|-
|General speed optimization of all software||With variable CPU clock, the less CPU needed, the less power.||Moderate (Large with backlight off)||In Progress
|-
|Smart turning off unused peripherals||Interacting with kernel mode drivers to turn off bits the user isn't using||Large
|-
|Seamlessly switching to 256 colour||The LCD controller supports pallete mode. This would reduce memory bus traffic by a third.||Small||Of debatable value - only for P1 (?)
|}

This page tries to describe the various power management features of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]], their states, transitions, etc. First, we start by describing the power states of the individual hardware components. Then we look at it from a System Integration point of view.

== S3C2410 SoC ==

The [[Neo1973 Power Management#S3C2410 SoC | S3C2410 SoC section]] is an overview of the S3C2410 power states or modes and their capabilities. The S3C2410 has the following modes:

{| border="3"
|+ Power states for the [[Neo1973 Power Management#S3C2410 SoC | S3C2410 SoC(CPU)]] including approx memory bus current
! Mode || Frequency || Power consumption || Wakeup sources||Note
|-
! Normal Mode
| 33-266Mhz || (around 50-335mW depending on speed) || Awake
|-
! Idle Mode
|33-266Mhz||around 50-170mW depending on speed || Any interrupt || FCLK disconnected
|-
! Slow Mode
| 12Mhz||40mW || Awake, can vary clock speed as desired on interrupts. || CPU clock (FCLK), SDRAM, bus clocks set by 12Mhz crystal.
|-
! Power_off Mode
| off|| .2mW (@2V) || GSM, buttons, touchscreen, charger/USB connect, low battery|| EINT[0...15], RTC Alarm Interrupt, nBATT_FAULT pin. SDRAM self-refresh, RTC powered.
|-
!Peripheral||Power||Note||constraints
|-
!USB-H
|1mW||The USB host driver
|-
!USB-D
|6mW||The USB device driver||PCLK>20Mhz
|-
!LCD driver
|20(qvga)-80mW||LCD driver||HCLK>VCLK*4 (p386) VCLK(vga)=19Mhz VCLK(qvga)=4.75Mhz = CPU clock 80Mhz min(seems to work at 50Mhz according to u-boot pll set) or 32Mhz (min variable CPU speed)
|-
!PLL
|?mW||Phase locked loop, needed if not in slow mode.
|-
!Serial
|7mW||2/3 integrated serial ports
|}

==== System design considerations ====
In order to fully support Power_off mode, we need to
* Be able to switch off VDDi/VDDiarm/VDDi_MPLL/VDDi_UPLL separately from VDDalive

== PCF50606 PMU ==

This is an overview of the PCF50606 power modes / state transitions

=== NOPOWER ===

Condition: Vbat < Vverylowbat && Vback < Vlowback && Vchgvin < Vlowchg

Human-Readable: If main battery voltage < 2.7V and backup battery voltage < 1.3V and charger voltage < 2.7V

=== SAVE ===

Condition: Vbat < Vverylowbat && (Vback > Vlowback || Vchgvin > Vlowchg)

Human-readable: If main battery voltage < 2.7V and at least backup battery voltage > 1.3V or charger voltage > 2.7V.

=== STANDBY ===

Condition: Vbat > Vverylowbat

Human-readable: If main battery voltage > 2.7V

=== ACTIVE ===

Condition: Vbat > Vlowbat
Human-Readable: If main battery voltage > 2.8V (configurable up to 3.4V)
Transition from STANDBY to ACTIVE: If ONKEY button is pressed, or RTC Alarm, or EXTON or charger insert or pen-down by touchscreen (we don't use the PMU TS controller)

== JBT6K74 LCM ==

=== Deep Standby ===

In this mode, only the supply power is activated

=== Sleep ===

Holds register data with clock stopped

=== Normal ===

Fully powered up and operational

== System Level ==

This is a description of the system-level power management.

=== System Power states ===

In order to do system-level power management, we need to introduce state definitions with their according state names. The state names are prefixed by SYS_POWER_.

{|border="1"
|+System power management states. Name prefixed with SYS_POWER_ PMU off is turned off by switching off the requisite output of the PCF50606
!Name||Note||PCF50606 PSU chip||S3C2410 CPU||JBT6K74 LCD driver||GSM||GPS||Bluetooth||Backlight
|-
|NO||No main battery or USB charger. Backup battery operational||Save||Off||PMU off||Off - no Vbatt||PMU off||PMU off||off
|-

|OFF||"Switched Off" - no functionality||Standby||PMU off||PMU off||Off by MODEM_ON to LOW||PMU off||PMU off||off
|-
|SLEEP||Suspend-RAM (in pocket waiting for a call)||Active||Power_Off||PMU Off||On by MODEM_ON to HIGH||Optional||Deep Standby||Off
|-
|SCRSAVE||Screen Saver||Active||SLOW, IDLE||SLEEP||On by MODEM_ON to HIGH||Optional||Optional||Off
|-
|ON||Normal active state||Active||On||Normal||On by MODEM_ON to HIGH||Optional||On||On, PWM'd brightness
|-
|}

=== Wake-up reasons ===

In the following events, we want the main CPU to be able to be woken up from Power_off (SYS_POWER_SLEEP) state:

==== Events from GSM ====

* Incoming phone call
* Incoming SMS
* Loss of network signal

===== Implementation =====

The GSM daemon configures the GSM Modem so as to wake the CPU when events happen.

The S3C2410 has the EINT0 pin of the S3C2410 connected to the GSM modem, which wakes it on configured events.

==== GPIO from Bluetooth ====

PIO_2 of the DFBM-CS320 is connected to GPC7 of the s3c2410. 
PIO_5 of the DFBM-CS320 is connected to GPC5 of the s3c2410. 
BT_EN of the DFBM-CS320 is connected to GPB5 if the s3c2410. [http://svn.openmoko.org/trunk/doc/hardware/GTA01Bv4/gpio.txt]

==== Button Press ====

If somebody pushes either the [[Neo1973 Aux Button]] or the [[Neo1973 Power Button]], the system shall wake up.
===== Implementation =====

====== Power Button ======
During suspend, the PMU is configured to allow PWRONF events to generate interrupts to the CPU.
(This is if PWR_IRQ is the internal signal from the PMU, mentioned in gpio.txt)

====== Aux Button ======
The Aux button is connected the EINT6 pin, which can wake-up the CPU from Power_off.

This means that resuming on Aux button will work out-of-the-box

==== Charger Events ====

If a charger plug (or any other USB device) is connected, the device shall resume and update the battery [charger] status. Also, charger errors such as over/undervoltage, over/under-temperature shall be reported.

===== Implementation =====
During suspend, the PMU is configured to allow EXTONR,CHGERR and related events to generate interrupts to the CPU.

In GTA01Bv4, the PMU IRQ is connected to EINT9.

{{note|Up to GTA01Bv3, the PMU IRQ is connected to EINT16, i.e. an interrupt source that cannot wake-up from Power_off mode!}}

== Voltages ==
{{note | This section reflects the wiring of power rails in GTA01Bv04 }}

=== VB ===

* Battery terminal voltage
* Used by
** [[LM4857]] Amplifier (vdd1-4)
** [[PCF50606]] PMU
** LCM Backlight (via U6001)
** U7602 AVDD/GL_3V3 regulator
** GSM Modem

=== CORE_1V8 ===

* This is the S3C2410 Core Voltage
* Generated by PMU DCUD
* Used by
** S3C2410 (vddiarm/vddi/vddi_mpll/vddi_upll)

=== STBY_1V8 ===

* Standby Voltage for S3C2410
* Generated by PMU D3REG
* Used by
** S3C2410 (vddalive/rtc)

=== IO_3V3 ===

* Generated by PMU DCDE
* Used by
** lots of pullups
** U1502 (latch for GSM UART)
** S3C2410 VDDMOP
** S3C2410 VDDOP
** S3C2410 VDDA_ADC
** S3C2410 nBATT_FLT
** S3C2410 !EXTCLK
** SDRAM_VCC3
** FLASH_3V3
** [[LM4857]] Amplifier (i2cvdd)
** Vibrator
** Touch panel transistors
** SD_3V3 via U7501
** PMU (avdd)

=== GL_1V5 ===

* Generated by PMU DCDF
* Used by
** AGPS (vdd_core)

=== GL_2V5 ===

* Generated by PMU D2REG
* Used by
** AGPS (vdd_pllreg)

=== GL_3V3 ===

* Generated by U7602
* Used by
** AGPS (vdd_io/vdd_lpreg)
** AGPS (X7601 -> rtcclk)

* Controlled by
** EN_AGPS3V3 GPIO

=== AVDD ===
3V
* Generated by U7602
* Used by
** AGPS (lna power int/ext, antenna switch)

* Controlled by
** EN_AGPS3V GPIO

=== CODEC_3V3 ===

* Generated by PMU IOVDD
* Used for
** Audio Codec (digital and analog)

=== BT_3V15 ===

* Generated by PMU D1REG
* Used by
** Bluetooth Module

=== LCM_3V3 ===

* Generated by PMU LPVDDD
* Used by
** Headset/GSM Uart Latch
** LCM

=== FLASH_3V3 ===

* Derived from IO_3V3
* Used by
** NAND Flash

=== SDRAM_VCC3 ===

* Derived from IO_3V3
* Used by
** SDRAM

=== SD_3V3 ===

* Generated by U7501
* Used by
** microSD slot

* Controlled by
** SD_ON GPIO

== Kernel API ==

== Userspace API ==

== Approximate power draw of various subsystems ==

In P0 and P1 phones, the battery has a total of 1200mAh, at 3.6V. This is approximately 3500mWh, once power supply losses are taken into account. The figures below are estimates from datasheets.

These do not take into account the severe hardware bugs of phase 0 hardware, which severely affect power use.

* LCD
** 150mW with backlight at full brightness
** 15mW with backlight at 10%
* CPU
** 320mW @ 200MHz
** 450mW @ 266MHz
** 140mW @ 200MHz idle.
** 50mW @ 12MHz (slow mode)
*** These include fudge factors for RAM and other systems, from the CPU datasheet.
*RAM 600mW at 600Mbytes/sec, power use broadly proportional to transfer rate.
* Bluetooth
** 63mW @ Tx Burst (file transfer, send)
** 36mW @ Rx Burst (file transfer, receive)
** 3.6mW @ Idle, beacon only
*** Based on the datasheets provided
* GSM ?
**Idle, but connected to network, 45mW
**Active on a call - up to 600mW, closer to tower less.
* GPS
** 45mW
*** Rough measurement

{|border="1"
|+CPU clock speed constraints
!Frequency(Mhz)||Notes||QVGA LCD||VGA LCD||USB device
|-
|12||Slow mode||No||No||No
|-
|12-33.74||Impossible or violates PLL spec
|-
|33.75-67.5|| ||Yes||No||Yes (with proper setting of HCLK divider)
|-
|79-266|| ||Yes||Yes||Yes
|-
|268-300||Overclocking||?||?||?
|}

Recommended clock speeds: 12 33.75 45 48 50.7 56.25 67.5 79 84.75 90 101.25 113.0 118.5 124.0 135.0 147.0 152 158 170 180 186 192 202.8 266 268 270

Other clock speeds are possible (in the 33.75-266Mhz range) by setting the PLL, however, the datasheet strongly recommends these, and recommends contacting samsung for speeds not listed above.

This would imply that with the CPU constantly on in low power mode, GPS and GSM blipping on and off, and display off, the worst case power consumption is probably around 70mW, leading to a battery life of 2 days.
If the CPU is turned off, battery life rises significantly.

With everything on, playing video with sound, for example should get well over 3 hours. (500mW LCD + 320mW CPU + 200mW audio + 50mW GPS. 4.5Wh at 1.1W draw)

Both voltage and clock speed to the CPU core can be altered.
Exactly how this will work with the hardware is yet to be determined.
It is possible that it may be capable of playing MP3s with the CPU clock at 60Mhz. This would considerably extend battery to well over 10 hours. Optimistically >24 hours of mp3.

The lowest power state I have gotten the Neo1973 phase-1 to run in is 90mA or so, for a life of some 12 hours.
This is with backlight, GSM modem, bluetooth, GPS, off, the CPU clocked at 100Mhz, and undervolted to 1.8V, connected over usb-net (not powered via USB)

8 hours playing mp3 at moderate volume. (same caveats as above.)

== Measured power draw on phase 0 neo1973 ==

I played with old ampermeter, old nokia 3110 (as a power supply) and phase0 neo1973 a bit. It appears to eat 1.02 mW while powered off, 1.02W while booted (backlight on), ~0.51W while sleeping (with backlight on) and 1.4W while loading applications.

== Logging battery parameters to troubleshoot charging ==

'''WARNING'''

'''After installing and starting this script my Neo battery went flat in < 1 hour. Previously it was fine even overnight. If your battery is so flat that the Neo will not boot then leave it plugged in to a USB port for 15-20 minutes before powering up.'''

Some neos have managed to discharge their battery down to empty while off, plugged in, and supposedly charging from a 500ma-capable usb device. In order to help figure out how the state of charge changes while charging, running of battery, sleeping on battery, and sleeping while connected to usb, download two scripts in http://wile.org/stuff/power.tar Put the power-watch script in /usr/local/bin/ and the powerlog script in /etc/init.d, then

# ln -s ../init.d/powerlog /etc/rc5.d/S15powerlog

so that it starts up with the neo.

The script logs the time, battery voltage, charging current, battery temperature, charging mode, bluetooth-on status, gps-on status, gsm-on status, and backlight brightness numbers. The [[Kernel#Battery_charging_current|kernel page]] claims the charging current is in ma, but that does not appear to be the case for all builds? eg 2.6.21.6-moko10. The battery temperature does not always appear to be in degrees C, either.

After a few runs we can calibrate volts-to-remaining power, and then estimate off or sleep current draw and charging rate by observing the power drop [or rise] vs time between successive os boots.

[[Category:Documentation]]
[[Category:Neo1973 Phase 0 related]]
[[Category:Neo1973 Phase 1 related]]

User:CesarB/cpufreq

2008-01-19T19:06:52Z

CesarB: done

User:CesarB/cpufreq

2008-01-19T18:40:23Z

CesarB: draft

User:CesarB/cpufreq

2008-01-19T18:34:37Z

CesarB: draft

User:CesarB

2008-01-19T18:08:12Z

CesarB: /* Subpages */ +cpufreq

I am a Bachelor of Computer Science from the Universidade Federal do Rio de Janeiro.

I am a Linux user since 1997. The distribution I currently use is Kubuntu.

== Subpages ==

* [[/Using a local overlay]]
* [[/Compiling for EABI]]
* [[/Things not to do with your Neo]]
* [[/cpufreq]]

Neo 1973 GTA01 Power Management

2008-01-16T23:35:56Z

CesarB: link to user page

{{InProgress}}
This page details the power management of the Phase 1 Neo1973. Much of it is inapplicable to earlier models.

Power management is of utmost concern to any mobile device.
Battery power is quite limited, so we need to make sure we try our best to conserve it. (See also [[Power management requirements]].)

This is very much unimplemented at the moment.

Current projects:

{|border="1"
|+Projects
!User||Project||details||URL
|-
|[[User:CesarB|cesarb]]||Cpufreq||Varying clock speed, including making peripherals work over during transitions||
http://repo.or.cz/w/linux-2.6/s3c2410-cpufreq.git (branch s3c2410-cpufreq)
|}

{|border="3"
|+Required kernel mode power saving, and relative saving of battery life.
!Option ||Note||Average saving over next lowest power state the description is the total effect on battery life ||Status
|-
|External peripheral control || Ability to dim backlight, turn on and off GSM, GPS, and other devices outside the CPU || Huge (700mW) ||Implemented
|-
|Slow Mode || The CPU clock is 12MHz, this is the lowest power mode with the CPU awake ||Huge(300mW)|| Not implemented
|-
|Variable CPU core voltage || Dynamically alter CPU core voltage according to frequency ||Moderate(50mW)|| Not implemented, limited by PMU to .3V steps
|-
|CPU Idle mode|| Turn off CPU clock while rest of SoC remains awake||Large(150mW)||Not implemented
|-
|Variable CPU frequency ~20Mhz to 266Mhz||Vary CPU frequency to lower power consumption.||Huge(250mW)||Not implemented
|-
|Tickless Kernel||Remove periodic timer interrupts in kernel||Modest(10mW?)||Not implemented
|-
|Rapid Suspend-RAM||Suspend CPU totally and resume when required in under 1s.||Moderate (50mW)||Not implemented

|}

{|border="3"
|+Required user-mode power saving
!Option||Note||Saving||Status
|-
|General speed optimization of all software||With variable CPU clock, the less CPU needed, the less power.||Moderate (Large with backlight off)||In Progress
|-
|Smart turning off unused peripherals||Interacting with kernel mode drivers to turn off bits the user isn't using||Large
|-
|Seamlessly switching to 256 colour||The LCD controller supports pallete mode. This would reduce memory bus traffic by a third.||Small||Of debatable value - only for P1 (?)
|}

This page tries to describe the various power management features of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]], their states, transitions, etc. First, we start by describing the power states of the individual hardware components. Then we look at it from a System Integration point of view.

== S3C2410 SoC ==

The [[Neo1973 Power Management#S3C2410 SoC | S3C2410 SoC section]] is an overview of the S3C2410 power states or modes and their capabilities. The S3C2410 has the following modes:

{| border="3"
|+ Power states for the [[Neo1973 Power Management#S3C2410 SoC | S3C2410 SoC(CPU)]] including approx memory bus current
! Mode || Frequency || Power consumption || Wakeup sources||Note
|-
! Normal Mode
| 33-266Mhz || (around 50-335mW depending on speed) || Awake
|-
! Idle Mode
|33-266Mhz||around 50-170mW depending on speed || Any interrupt || FCLK disconnected
|-
! Slow Mode
| 12Mhz||40mW || Awake, can vary clock speed as desired on interrupts. || CPU clock (FCLK), SDRAM, bus clocks set by 12Mhz crystal.
|-
! Power_off Mode
| off|| .2mW (@2V) || GSM, buttons, touchscreen, charger/USB connect, low battery|| EINT[0...15], RTC Alarm Interrupt, nBATT_FAULT pin. SDRAM self-refresh, RTC powered.
|-
!Peripheral||Power||Note||constraints
|-
!USB-H
|1mW||The USB host driver
|-
!USB-D
|6mW||The USB device driver||PCLK>20Mhz
|-
!LCD driver
|20(qvga)-80mW||LCD driver||HCLK>VCLK*4 (p386) VCLK(vga)=19Mhz VCLK(qvga)=4.75Mhz = CPU clock 80Mhz min(seems to work at 50Mhz according to u-boot pll set) or 32Mhz (min variable CPU speed)
|-
!PLL
|?mW||Phase locked loop, needed if not in slow mode.
|-
!Serial
|7mW||2/3 integrated serial ports
|}

==== System design considerations ====
In order to fully support Power_off mode, we need to
* Be able to switch off VDDi/VDDiarm/VDDi_MPLL/VDDi_UPLL separately from VDDalive

== PCF50606 PMU ==

This is an overview of the PCF50606 power modes / state transitions

=== NOPOWER ===

Condition: Vbat < Vverylowbat && Vback < Vlowback && Vchgvin < Vlowchg

Human-Readable: If main battery voltage < 2.7V and backup battery voltage < 1.3V and charger voltage < 2.7V

=== SAVE ===

Condition: Vbat < Vverylowbat && (Vback > Vlowback || Vchgvin > Vlowchg)

Human-readable: If main battery voltage < 2.7V and at least backup battery voltage > 1.3V or charger voltage > 2.7V.

=== STANDBY ===

Condition: Vbat > Vverylowbat

Human-readable: If main battery voltage > 2.7V

=== ACTIVE ===

Condition: Vbat > Vlowbat
Human-Readable: If main battery voltage > 2.8V (configurable up to 3.4V)
Transition from STANDBY to ACTIVE: If ONKEY button is pressed, or RTC Alarm, or EXTON or charger insert or pen-down by touchscreen (we don't use the PMU TS controller)

== JBT6K74 LCM ==

=== Deep Standby ===

In this mode, only the supply power is activated

=== Sleep ===

Holds register data with clock stopped

=== Normal ===

Fully powered up and operational

== System Level ==

This is a description of the system-level power management.

=== System Power states ===

In order to do system-level power management, we need to introduce state definitions with their according state names. The state names are prefixed by SYS_POWER_.

{|border="1"
|+System power management states. Name prefixed with SYS_POWER_ PMU off is turned off by switching off the requisite output of the PCF50606
!Name||Note||PCF50606 PSU chip||S3C2410 CPU||JBT6K74 LCD driver||GSM||GPS||Bluetooth||Backlight
|-
|NO||No main battery or USB charger. Backup battery operational||Save||Off||PMU off||Off - no Vbatt||PMU off||PMU off||off
|-

|OFF||"Switched Off" - no functionality||Standby||PMU off||PMU off||Off by MODEM_ON to LOW||PMU off||PMU off||off
|-
|SLEEP||Suspend-RAM (in pocket waiting for a call)||Active||Power_Off||PMU Off||On by MODEM_ON to HIGH||Optional||Deep Standby||Off
|-
|SCRSAVE||Screen Saver||Active||SLOW, IDLE||SLEEP||On by MODEM_ON to HIGH||Optional||Optional||Off
|-
|ON||Normal active state||Active||On||Normal||On by MODEM_ON to HIGH||Optional||On||On, PWM'd brightness
|-
|}

=== Wake-up reasons ===

In the following events, we want the main CPU to be able to be woken up from Power_off (SYS_POWER_SLEEP) state:

==== Events from GSM ====

* Incoming phone call
* Incoming SMS
* Loss of network signal

===== Implementation =====

The GSM daemon configures the GSM Modem so as to wake the CPU when events happen.

The S3C2410 has the EINT0 pin of the S3C2410 connected to the GSM modem, which wakes it on configured events.

==== GPIO from Bluetooth ====

PIO_2 of the DFBM-CS320 is connected to GPC7 of the s3c2410. 
PIO_5 of the DFBM-CS320 is connected to GPC5 of the s3c2410. 
BT_EN of the DFBM-CS320 is connected to GPB5 if the s3c2410. [http://svn.openmoko.org/trunk/doc/hardware/GTA01Bv4/gpio.txt]

==== Button Press ====

If somebody pushes either the [[Neo1973 Aux Button]] or the [[Neo1973 Power Button]], the system shall wake up.
===== Implementation =====

====== Power Button ======
During suspend, the PMU is configured to allow PWRONF events to generate interrupts to the CPU.
(This is if PWR_IRQ is the internal signal from the PMU, mentioned in gpio.txt)

====== Aux Button ======
The Aux button is connected the EINT6 pin, which can wake-up the CPU from Power_off.

This means that resuming on Aux button will work out-of-the-box

==== Charger Events ====

If a charger plug (or any other USB device) is connected, the device shall resume and update the battery [charger] status. Also, charger errors such as over/undervoltage, over/under-temperature shall be reported.

===== Implementation =====
During suspend, the PMU is configured to allow EXTONR,CHGERR and related events to generate interrupts to the CPU.

In GTA01Bv4, the PMU IRQ is connected to EINT9.

{{note|Up to GTA01Bv3, the PMU IRQ is connected to EINT16, i.e. an interrupt source that cannot wake-up from Power_off mode!}}

== Voltages ==
{{note | This section reflects the wiring of power rails in GTA01Bv04 }}

=== VB ===

* Battery terminal voltage
* Used by
** [[LM4857]] Amplifier (vdd1-4)
** [[PCF50606]] PMU
** LCM Backlight (via U6001)
** U7602 AVDD/GL_3V3 regulator
** GSM Modem

=== CORE_1V8 ===

* This is the S3C2410 Core Voltage
* Generated by PMU DCUD
* Used by
** S3C2410 (vddiarm/vddi/vddi_mpll/vddi_upll)

=== STBY_1V8 ===

* Standby Voltage for S3C2410
* Generated by PMU D3REG
* Used by
** S3C2410 (vddalive/rtc)

=== IO_3V3 ===

* Generated by PMU DCDE
* Used by
** lots of pullups
** U1502 (latch for GSM UART)
** S3C2410 VDDMOP
** S3C2410 VDDOP
** S3C2410 VDDA_ADC
** S3C2410 nBATT_FLT
** S3C2410 !EXTCLK
** SDRAM_VCC3
** FLASH_3V3
** [[LM4857]] Amplifier (i2cvdd)
** Vibrator
** Touch panel transistors
** SD_3V3 via U7501
** PMU (avdd)

=== GL_1V5 ===

* Generated by PMU DCDF
* Used by
** AGPS (vdd_core)

=== GL_2V5 ===

* Generated by PMU D2REG
* Used by
** AGPS (vdd_pllreg)

=== GL_3V3 ===

* Generated by U7602
* Used by
** AGPS (vdd_io/vdd_lpreg)
** AGPS (X7601 -> rtcclk)

* Controlled by
** EN_AGPS3V3 GPIO

=== AVDD ===
3V
* Generated by U7602
* Used by
** AGPS (lna power int/ext, antenna switch)

* Controlled by
** EN_AGPS3V GPIO

=== CODEC_3V3 ===

* Generated by PMU IOVDD
* Used for
** Audio Codec (digital and analog)

=== BT_3V15 ===

* Generated by PMU D1REG
* Used by
** Bluetooth Module

=== LCM_3V3 ===

* Generated by PMU LPVDDD
* Used by
** Headset/GSM Uart Latch
** LCM

=== FLASH_3V3 ===

* Derived from IO_3V3
* Used by
** NAND Flash

=== SDRAM_VCC3 ===

* Derived from IO_3V3
* Used by
** SDRAM

=== SD_3V3 ===

* Generated by U7501
* Used by
** microSD slot

* Controlled by
** SD_ON GPIO

== Kernel API ==

== Userspace API ==

== Approximate power draw of various subsystems ==

In P0 and P1 phones, the battery has a total of 1200mAh, at 3.6V. This is approximately 3500mWh, once power supply losses are taken into account. The figures below are estimates from datasheets.

These do not take into account the severe hardware bugs of phase 0 hardware, which severely affect power use.

* LCD
** 150mW with backlight at full brightness
** 15mW with backlight at 10%
* CPU
** 320mW @ 200MHz
** 450mW @ 266MHz
** 140mW @ 200MHz idle.
** 50mW @ 12MHz (slow mode)
*** These include fudge factors for RAM and other systems, from the CPU datasheet.
*RAM 600mW at 600Mbytes/sec, power use broadly proportional to transfer rate.
* Bluetooth
** 63mW @ Tx Burst (file transfer, send)
** 36mW @ Rx Burst (file transfer, receive)
** 3.6mW @ Idle, beacon only
*** Based on the datasheets provided
* GSM ?
**Idle, but connected to network, 45mW
**Active on a call - up to 600mW, closer to tower less.
* GPS
** 45mW
*** Rough measurement

{|border="1"
|+CPU clock speed constraints
!Frequency(Mhz)||Notes||QVGA LCD||VGA LCD||USB device
|-
|12||Slow mode||No||No||No
|-
|12-33.74||Impossible or violates PLL spec
|-
|33.75-67.5|| ||Yes||No||Yes (with proper setting of HCLK divider)
|-
|79-266|| ||Yes||Yes||Yes
|-
|268-300||Overclocking||?||?||?
|}

Recommended clock speeds: 12 33.75 45 48 50.7 56.25 67.5 79 84.75 90 101.25 113.0 118.5 124.0 135.0 147.0 152 158 170 180 186 192 202.8 266 268 270

Other clock speeds are possible (in the 33.75-266Mhz range) by setting the PLL, however, the datasheet strongly recommends these, and recommends contacting samsung for speeds not listed above.

This would imply that with the CPU constantly on in low power mode, GPS and GSM blipping on and off, and display off, the worst case power consumption is probably around 70mW, leading to a battery life of 2 days.
If the CPU is turned off, battery life rises significantly.

With everything on, playing video with sound, for example should get well over 3 hours. (500mW LCD + 320mW CPU + 200mW audio + 50mW GPS. 4.5Wh at 1.1W draw)

Both voltage and clock speed to the CPU core can be altered.
Exactly how this will work with the hardware is yet to be determined.
It is possible that it may be capable of playing MP3s with the CPU clock at 60Mhz. This would considerably extend battery to well over 10 hours. Optimistically >24 hours of mp3.

The lowest power state I have gotten the Neo1973 phase-1 to run in is 90mA or so, for a life of some 12 hours.
This is with backlight, GSM modem, bluetooth, GPS, off, the CPU clocked at 100Mhz, and undervolted to 1.8V, connected over usb-net (not powered via USB)

8 hours playing mp3 at moderate volume. (same caveats as above.)

== Measured power draw on phase 0 neo1973 ==

I played with old ampermeter, old nokia 3110 (as a power supply) and phase0 neo1973 a bit. It appears to eat 1.02 mW while powered off, 1.02W while booted (backlight on), ~0.51W while sleeping (with backlight on) and 1.4W while loading applications.

== Logging battery parameters to troubleshoot charging ==

'''WARNING'''

'''After installing and starting this script my Neo battery went flat in < 1 hour. Previously it was fine even overnight. If your battery is so flat that the Neo will not boot then leave it plugged in to a USB port for 15-20 minutes before powering up.'''

Some neos have managed to discharge their battery down to empty while off, plugged in, and supposedly charging from a 500ma-capable usb device. In order to help figure out how the state of charge changes while charging, running of battery, sleeping on battery, and sleeping while connected to usb, download two scripts in http://wile.org/stuff/power.tar Put the power-watch script in /usr/local/bin/ and the powerlog script in /etc/init.d, then

# ln -s ../init.d/powerlog /etc/rc5.d/S15powerlog

so that it starts up with the neo.

The script logs the time, battery voltage, charging current, battery temperature, charging mode, bluetooth-on status, gps-on status, gsm-on status, and backlight brightness numbers. The [[Kernel#Battery_charging_current|kernel page]] claims the charging current is in ma, but that does not appear to be the case for all builds? eg 2.6.21.6-moko10. The battery temperature does not always appear to be in degrees C, either.

After a few runs we can calibrate volts-to-remaining power, and then estimate off or sleep current draw and charging rate by observing the power drop [or rise] vs time between successive os boots.

[[Category:Documentation]]
[[Category:Neo1973 Phase 0 related]]
[[Category:Neo1973 Phase 1 related]]

User:CesarB/Things not to do with your Neo

2007-10-12T15:23:28Z

CesarB:

These all come from things heard on IRC or on this wiki.

== Be careful when upgrading your u-boot partition ==

If the flashing your u-boot partition is interrupted, you can end up with an unbootable device, which can only be recovered with a debug board. If possible, don't do it unless you either have a debug board or live near someone who has one. Always do it with a battery-backed computer (either a notebook or a computer on a UPS), in case the power goes out. And, if you don't have a debug board or live near someone who has one, always flash a well-tested u-boot (don't use daily builds, for instance, unless you know of other people who had success with that particular build), and don't flash a self-compiled u-boot.

== Be careful when playing with your u-boot environment ==

Wrong commands on the u-boot environment can make u-boot malfunction, with the same consequences as above. If you are lucky, you can still boot and overwrite it with a sane copy from within linux; if you are unlucky, you need a debug board. Always double-check (with <code>printenv</code>) what you have done before doing a <code>saveenv</code>. In particular, always double-check if you didn't mistype a number; see [[Bricked]] for an example.

== Never use "nand erase" unless you really mean it ==

The correct command is "nand erase rootfs" (or whatever the partition you want to erase is).

== Never plug the USB cable without a battery ==

Unless you want very scary noises and strange smells coming from your phone.

Mokomakefile

2007-10-12T13:33:43Z

CesarB:

#REDIRECT [[MokoMakefile]]

User:CesarB/Requirements

2007-09-14T00:30:42Z

CesarB:

:''Note: this is just my personal opinion of what the Neo should have before it's usable as someone's primary cell phone.''

== Must have ==

=== Phone calls ===

* Dialing/answering/hangup from the GUI
* Phone address book
* SIM address book
* Record of received/made/missed calls
* Ringing/vibrator
* Selection of ringtone/vibrator mode and volume from the GUI
* Call volume changing on the GUI, during a call
* Audio device selection (handset, headset, bluetooth)
* Supplementary services (parsing of +CUSD and display on the GUI)

=== SMS ===

* SMS receiving
* SMS composing/sending
* SMS storage
* Tone/vibrator on SMS receive
* Selection of tone/vibrator mode and volume from the GUI

=== Power management ===

* Show battery charge level
* Tone when battery low
* Auto suspend when battery low ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847 bug 847])
* Turn all chips off correctly on shutdown
* Turn the unneeded chips off on suspend (phone idle)

== Should have ==

=== CB ===

* Display of cell broadcast

=== Networking ===

* GPRS/CSD GUI configuration, with multiple profiles
* Usable as a GSM modem (both bluetooth and USB; better as a AT interpreter instead of passthrough)
* Automatic network up/down when needed/idle (configurable as never/ask/always)
* Bytes sent/receive counter (both per-use and resetable total)
* WAP browser

=== MMS ===

* MMS receiving
* MMS composing/sending
* MMS storage
* Tone/vibrator on MMS receive
* Selection of tone/vibrator mode and volume from the GUI

=== File transfer ===

* Bluetooth OBEX (at least send/receive OPUSH)

=== File management ===

* GUI file/object manager
* Free space monitor

=== Packaging ===

* GUI package installation
* GUI repository configuration

=== Date/Time ===

* Timezone selection on GUI
* Getting time from either GPS or GSM

== Nice to have ==

=== Phone calls ===

* Hands-free mode (using the more powerful ringtone speakers)

=== Networking ===

* Web browser
* Bluetooth PAN AP (with GUI configuration)
* Using a bluetooth PAN (with GUI configuration)
* Using a bluetooth modem/dialup (with GUI configuration)
* Automatic network selection based on available networks and a set of rules

=== Applications ===

* Alarm
* Calendar
* Media player
* Picture viewer

=== SIM ===

* STK

[[Category:Requirements]]

Power management requirements

2007-09-14T00:30:22Z

CesarB: Category:Requirements

Here are some non-specific requirements for OpenMoko regarding power management of the phone. There are two general classes of requirements:

# The phone should take the necessary actions for the battery to never run too empty.
# The phone should save power as much as possible to keep run times as long as possible.

Like so many requirements, we would want more than is possible in theory or than is possible in practise with our resources. Like in all design, trade-offs have to be made between various desirable properties. For details about the hardware and drivers, and what's actually possible, see [[Neo1973 GTA01 Power Management]]. An important part of the implementation regarding management is being able to follow the charge state accurately and to forecast what the state is in say 10 minutes. This is made more difficult by battery aging.

== Battery level maintenance ==

Here the trade-off is between system simplicity and using all the power we get versus being easy to use and tolerant to "user errors". It's actually always possible that we lose all charge due to the small current drawn even while the system is fully off, but we can make this a very special corner-case.

Battery is too empty if:
# the battery is damaged for being too empty (this is taken care of by the battery itself).
# we are not able to start uboot to show the user messages about charging and to negotiate the 500 mA fast charge mode when available.
# we can't shut down the phone cleanly and have enough power left to get back to the boot loader.

We need to have separate checks for these cases:
# The system is fully operational and we need to shut it down cleanly. ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847 Bug #847: Shutdown if battery level goes too low])
# The system is in a sleep mode and we need to wake it up so that it can be shut down cleanly.
# The system is off and we need to stop the user from accidentally booting it if we couldn't shut it down cleanly. ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=848 Bug #848: A charger mode for uboot])

== Power saving ==

Here the trade-off is between system simplicity and responsiveness and quality of all features versus longer run-times without the need to charge. Typically the return from a slow-power mode is not instant and the user will have to wait a moment (short or long).

Power saving options we have in general:
# Keep subsystems powered down when they are not needed. ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=770 Bug #770: Battery discharging while phone is off (GSM part)], [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=842 Bug #842: Whenever possible, Amp Mode should be Off])
# Use suspend-to-ram sleep when we don't need to control any subsystems with the CPU.
# Use lower operational modes: dimmer screen, slower CPU frequency.

[[Category:Requirements]]

User:CesarB/Requirements

2007-09-14T00:24:34Z

CesarB: /* Power management */

User:CesarB/Requirements

2007-09-13T23:45:35Z

CesarB: /* Power management */

:''Note: this is just my personal opinion of what the Neo should have before it's usable as someone's primary cell phone.''

== Must have ==

=== Phone calls ===

* Dialing/answering/hangup from the GUI
* Phone address book
* SIM address book
* Record of received/made/missed calls
* Ringing/vibrator
* Selection of ringtone/vibrator mode and volume from the GUI
* Call volume changing on the GUI, during a call
* Audio device selection (handset, headset, bluetooth)
* Supplementary services (parsing of +CUSD and display on the GUI)

=== SMS ===

* SMS receiving
* SMS composing/sending
* SMS storage
* Tone/vibrator on SMS receive
* Selection of tone/vibrator mode and volume from the GUI

=== Power management ===

* Tone when battery low
* Auto suspend when battery low ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847 bug 847])
* Turn all chips off correctly on shutdown
* Turn the unneeded chips off on suspend (phone idle)

== Should have ==

=== CB ===

* Display of cell broadcast

=== Networking ===

* GPRS/CSD GUI configuration, with multiple profiles
* Usable as a GSM modem (both bluetooth and USB; better as a AT interpreter instead of passthrough)
* Automatic network up/down when needed/idle (configurable as never/ask/always)
* Bytes sent/receive counter (both per-use and resetable total)
* WAP browser

=== MMS ===

* MMS receiving
* MMS composing/sending
* MMS storage
* Tone/vibrator on MMS receive
* Selection of tone/vibrator mode and volume from the GUI

=== File transfer ===

* Bluetooth OBEX (at least send/receive OPUSH)

=== File management ===

* GUI file/object manager
* Free space monitor

=== Packaging ===

* GUI package installation
* GUI repository configuration

=== Date/Time ===

* Timezone selection on GUI
* Getting time from either GPS or GSM

== Nice to have ==

=== Phone calls ===

* Hands-free mode (using the more powerful ringtone speakers)

=== Networking ===

* Web browser
* Bluetooth PAN AP (with GUI configuration)
* Using a bluetooth PAN (with GUI configuration)
* Using a bluetooth modem/dialup (with GUI configuration)
* Automatic network selection based on available networks and a set of rules

=== Applications ===

* Alarm
* Calendar
* Media player
* Picture viewer

=== SIM ===

* STK