eLinux.org - User contributions [en]

DLNA Open Source Projects

2011-06-01T21:10:14Z

Jsujjava: Add Category Networking

Here is some random information about DLNA open source projects:

== UPnP media servers ==
Here is a list of UPnP media servers for Windows, Linux, MAC and [[Python_Language|Python]]:
(some links obtained from http://ps3mods.blogspot.com/2007/05/upnp-media-servers-for-windows-mac.html)

I only list the open source ones.

* [http://www.cybergarage.org/net/cmgate/cc/index.html CyberMediaGate] (C++) - UPnP A/V Media Server, using cyberlink
* [http://ushare.geexbox.org/ uShare] (Linux) - UPnP A/V and DLNA Media Server, using libupnp
* [http://www.gnu.org/software/gmediaserver/ GMediaServer] (Linux) -
* [http://mediatomb.cc/ MediaTomb] (Linux, port to NAS has been reported)
* [http://www.mythtv.org/wiki/index.php/UPnP#UPnP_in_MythTV MythTV] - MythTV UPnP A/V Media Server support
* [http://www.cidero.com/radioServer.html Cidero Internet Radio Server] (Java)
* [http://fuppes.ulrich-voelkel.de/ Fuppes] (Windows, Linux) - FUPPES is a free multiplatform UPnP (TM) A/V Media Server.
* [http://resnet.uoregon.edu/~gurney_j/jmpc/pymeds.html PyMedS] (Python) - Python UPnP Media Server
* [http://openpfc.org/ OpenPFC] - Media device engine
** John Gildred of Pioneer stated: Pioneer published an LGPL implementation of an HD DVR called Digital Library with support for DMS and DMP features. It uses the OpenPFC DTV middleware. It was never put through certification, and it's a bit outdated now.

== UPnP Media Players ==

I only list the open source ones.

* [http://enna.geexbox.org/ Enna] (Linux) - An embedded Media Center with GUPnP-based UPnP A/V Media Browser and Player capabilities
* [http://xbmc.org/ XBMC] (Linux | Windows | MacOSX) - A multi-platforms Media Center with UPnP A/V plugin

== DLNA media servers ==
* [http://ushare.geexbox.org/ uShare] (Linux) - Free UPnP and DLNA Media Server for Linux
* [http://live.gnome.org/Rygel Rygel] - GNOME UPnP/DLNA Media Server
* [http://sourceforge.net/projects/minidlna/ minidlna] (Linux) DLNA server working whit Sony Bravia 46W4500

== UPnP libraries and middleware ==
* [http://platinum.sourceforge.net Platinum] - Platinum UPnP SDK
* [http://upnp.sourceforge.net/ libupnp] - Linux SDK for UPnP Devices
** Originally donated by Intel, this library serves as the foundation for some other projects
* [http://pupnp.sourceforge.net/ pupnp] - A Portable Open Source UPnP Development Kit
** This looks like the successor to libupnp??
* [http://www.cybergarage.org/net/upnp/java/ Cyberlink for Java] (Java) - Development package for UPnP applications
* [http://www.cybergarage.org/net/upnp/c/index.html Cyberlink for C] (C) - Development package for C UPnP applications
* [http://www.cybergarage.org/net/upnp/cc/index.html Cyberlink for C++] (C++) - Development package for C++ UPnP applications
* [http://search.cpan.org/~skonno/Net-UPnP/ Net::UPnP] (Perl) - Development package for Perl UPnP applications
* [http://www.cidero.com/ Cidero] - Cidero UPnP Control Point and Bridge Software

== DLNA and UPnP libraries and middleware ==
* [http://libdlna.geexbox.org/ libdlna] (C) - Reference DLNA open-source implementation for Linux
* [http://coherence.beebits.net/ coherence] (Python) - DLNA/UPnP framework for existing applications
** ''Building bridges - coherence, a DLNA/UPnP framework'' talk, by Frank Scholz at ELCE 2008. [http://free-electrons.com/pub/video/2008/elce/elce2008-scholz-coherence.ogv Video] available.
* [http://gupnp.org GUPnP] (C) - GObject/GLib based UPnP framework

=== Other lists ===
* There's also a good list of projects at: https://coherence.beebits.net/wiki/Resources
[[Category:Networking]]

Category:Move proposal

2011-05-19T14:57:11Z

Jsujjava: Categorize

[[Category:Community]]

eLinux.org:Site support

2011-05-19T14:55:50Z

Jsujjava: wording

== Volunteering to improve the wiki ==
Below please find links to various pages with information and ideas for content and feature additions
to the eLinux wiki.

(Various lists have crept up over the years, lets try to gather links to them here:)

Lists of editor tasks:
* [[Volunteer editor tasks]]
* [[Embedded wiki issues list]]
** Specific cleanup tasks
*** Resolve duplication between [[Embedded Linux Distributions]] and [[Hardware Hacking]] pages (and one other page mentioned by Klaas) -- seems to be resolved by 20100514, (broeggle)
*** Resolve duplication between [[Embedded Linux Distributions]] and [[Toolchains]] (broeggle)

* Create [[Wanted]] pages
** See also [[Special:Wantedpages]]
A lot of wanted pages are just dangling links from the Help pages, for pages that were not
created when we initially set up the wiki. I think most of these types of pages can just be
set to stubs. Alternatively, we can look at the MediaWiki site and copy the page from their
site for these dangling help examples.

Another big set of wanted pages are for links between pages that were copied from
the old CELF public wiki to here. This was done with some automated tools, which I think
made some errors in the translation from MoinMoin to MediaWiki. If the
legacy CELF page exists in this site, the link on the "requesting" page just needs to
be repaired. If there is not matching page, then the link should just be removed.

Just for fun, I'm keeping track over time of some metrics:
=== Wanted page count history ===
{| border="1"
||Date||Wanted page count
|-
||Dec 12, 2008||233
|-
||April 6, 2009||241 (why up?)
|-
||April 15, 2010||122
|-
||April 12, 2011||50 (but only few really relevant)
|}

Why do these stats occasionally rise?
On occasion, the Help pages are re-imported to pick up new pages. This can cause increases in Wanted Pages when the new pages have new page links on them that are not yet present in the new pages set.

* add categories to [[Special:Uncategorizedpages|Uncategorized pages]]
* de-orphan [[Special:Lonelypages|Orphaned pages]]
To de-orphan a page, follow the link to the page, and create a link to it from
an appropriate other page in the wiki. Before doing that, check to make sure that the
information on the page is not duplicated somewhere else in the wiki (maybe by doing
a search). Alternatively, sometimes the information can be copied from the orphan
to someplace else, and the orphan removed. If you copy the information to somewhere else,
just edit the orphan to make it empty, and add the page name to the list here, and an
administrator will remove the page.

List of empty orphan pages:
* <put page name here>

=== Orphan page count history ===
{| border="1"
||Date||Orphan page count
|-
||Dec 12, 2008||122
|-
||April 6, 2009||134 (what the heck?)
|-
||Dec 2, 2009||89
|-
||Dec 9, 2009||30
|-
||April 13, 2011||26
|}

Lists of administrator tasks:
* [[Embedded wiki to-do list]] - a task list for administrators
* [[Embedded Wiki wanted features]]

Other lists:
* [[Elinux issues]] - miscellaneous ideas of things to do

=== Templates ===

Wikipedia style templates can be used to flag pages that may require an action. The tranclusion causes a box to appear at the top of the page and causes the page is added to a category for action. These categories can be seen for a list of pages to work on.

Some template/category combinations include:
* [[Template:NeedsMerge]] - [[:Category:NeedsMerge]]
* [[Template:Incomplete]] - [[:Category:NeedsMaterial]]
* [[Template:Move]] - [[:Category:Move proposal]]

See also [[:Category:Templates]]

== Resources for volunteers and wiki administrators ==
To communicate with other elinux wiki volunteers, editors and administrators, please join
our
* [[ELinuxWiki:Mailing List|Mailing list]]
* [[eLinuxWiki:History|History page]] - has information about how we got here and why. Also, has links to pages used for previous activities, like contests and promotions.

== Ideas to encourage contributions ==

=== systems to facilitate exiting content review ===
* create email system that people can subscribe to, to review wiki pages a little at a time

=== systems to facilitate addition of content ===
* ability to bounce an LKML email to a collector, possibly adding a tag
** collector would post to wiki, with tag
* ability to forward and LKML email to a site, which returns you a URL (on e.g. lkml.org) for that message
** This makes it easier to link to an LKML message or thread.
* ability to rate LKML messages on a web site

== Donations ==
We don't really have an official mechanism for donations of money.

We are, however, looking for donations of items we can use for prizes
for some of our upcoming contests. Embedded Linux-based products,
or tools or books related to embedded Linux, would be most appreciated.

If you have something like this, or a large donation (greater than $100), please
contact [[User:TimBird|Tim Bird]] or [[User:wmat|Bill Traynor]].

Tim is available at: tim (dot) bird (at) am (dot) sony (dot) com.
Bill is available at: wmat (at) naoi (dot) ca.

[[Category:Community]]

Template:Incomplete

2011-05-19T14:54:43Z

Jsujjava: Categorize

<hr>
<table border="0" width="80%" class="solid">
<tr>
<td>
[[Image:Imbox_content.png]]
</td>
<td> This page is incomplete and may require expansion or cleanup. Please help to improve the article, or discuss the issue on the talk page.</td>
</tr>
</table>
<hr>

<noinclude>
== Template Documentation ==
This template is on pages which need new material added to fill out the article.

Pages which use this template are added to the category [[:Category:NeedsMaterial]].

Add <nowiki>{{Incomplete}}</nowiki> at the top of the page to include this.

</noinclude>

<includeonly>
[[Category:NeedsMaterial]]
</includeonly>
<noinclude>
[[Category:Templates]]
</noinclude>

eLinux.org:Site support

2011-05-19T14:52:51Z

Jsujjava: Add section on templates

== Volunteering to improve the wiki ==
Below please find links to various pages with information and ideas for content and feature additions
to the eLinux wiki.

(Various lists have crept up over the years, lets try to gather links to them here:)

Lists of editor tasks:
* [[Volunteer editor tasks]]
* [[Embedded wiki issues list]]
** Specific cleanup tasks
*** Resolve duplication between [[Embedded Linux Distributions]] and [[Hardware Hacking]] pages (and one other page mentioned by Klaas) -- seems to be resolved by 20100514, (broeggle)
*** Resolve duplication between [[Embedded Linux Distributions]] and [[Toolchains]] (broeggle)

* Create [[Wanted]] pages
** See also [[Special:Wantedpages]]
A lot of wanted pages are just dangling links from the Help pages, for pages that were not
created when we initially set up the wiki. I think most of these types of pages can just be
set to stubs. Alternatively, we can look at the MediaWiki site and copy the page from their
site for these dangling help examples.

Another big set of wanted pages are for links between pages that were copied from
the old CELF public wiki to here. This was done with some automated tools, which I think
made some errors in the translation from MoinMoin to MediaWiki. If the
legacy CELF page exists in this site, the link on the "requesting" page just needs to
be repaired. If there is not matching page, then the link should just be removed.

Just for fun, I'm keeping track over time of some metrics:
=== Wanted page count history ===
{| border="1"
||Date||Wanted page count
|-
||Dec 12, 2008||233
|-
||April 6, 2009||241 (why up?)
|-
||April 15, 2010||122
|-
||April 12, 2011||50 (but only few really relevant)
|}

Why do these stats occasionally rise?
On occasion, the Help pages are re-imported to pick up new pages. This can cause increases in Wanted Pages when the new pages have new page links on them that are not yet present in the new pages set.

* add categories to [[Special:Uncategorizedpages|Uncategorized pages]]
* de-orphan [[Special:Lonelypages|Orphaned pages]]
To de-orphan a page, follow the link to the page, and create a link to it from
an appropriate other page in the wiki. Before doing that, check to make sure that the
information on the page is not duplicated somewhere else in the wiki (maybe by doing
a search). Alternatively, sometimes the information can be copied from the orphan
to someplace else, and the orphan removed. If you copy the information to somewhere else,
just edit the orphan to make it empty, and add the page name to the list here, and an
administrator will remove the page.

List of empty orphan pages:
* <put page name here>

=== Orphan page count history ===
{| border="1"
||Date||Orphan page count
|-
||Dec 12, 2008||122
|-
||April 6, 2009||134 (what the heck?)
|-
||Dec 2, 2009||89
|-
||Dec 9, 2009||30
|-
||April 13, 2011||26
|}

Lists of administrator tasks:
* [[Embedded wiki to-do list]] - a task list for administrators
* [[Embedded Wiki wanted features]]

Other lists:
* [[Elinux issues]] - miscellaneous ideas of things to do

=== Templates ===

Wikipedia style templates can be used to flag pages may require an action. The tranclusion causes a box to appear at the top of the page and causes the page is added to a category for action. These categories can be seen for a list of pages to work on.

Some template/category combinations include:
* [[Template:NeedsMerge]] - [[:Category:NeedsMerge]]
* [[Template:Incomplete]] - [[:Category:NeedsMaterial]]
* [[Template:Move]] - [[:Category:Move proposal]]

See also [[:Category:Templates]]

== Resources for volunteers and wiki administrators ==
To communicate with other elinux wiki volunteers, editors and administrators, please join
our
* [[ELinuxWiki:Mailing List|Mailing list]]
* [[eLinuxWiki:History|History page]] - has information about how we got here and why. Also, has links to pages used for previous activities, like contests and promotions.

== Ideas to encourage contributions ==

=== systems to facilitate exiting content review ===
* create email system that people can subscribe to, to review wiki pages a little at a time

=== systems to facilitate addition of content ===
* ability to bounce an LKML email to a collector, possibly adding a tag
** collector would post to wiki, with tag
* ability to forward and LKML email to a site, which returns you a URL (on e.g. lkml.org) for that message
** This makes it easier to link to an LKML message or thread.
* ability to rate LKML messages on a web site

== Donations ==
We don't really have an official mechanism for donations of money.

We are, however, looking for donations of items we can use for prizes
for some of our upcoming contests. Embedded Linux-based products,
or tools or books related to embedded Linux, would be most appreciated.

If you have something like this, or a large donation (greater than $100), please
contact [[User:TimBird|Tim Bird]] or [[User:wmat|Bill Traynor]].

Tim is available at: tim (dot) bird (at) am (dot) sony (dot) com.
Bill is available at: wmat (at) naoi (dot) ca.

[[Category:Community]]

Category:NeedsMerge

2011-05-19T14:48:13Z

Jsujjava: Add to :Category:Community

This category denotes pages which are thought to require a merge. Don't add pages directly, use [[Template:NeedsMerge]].

[[Category:Community]]

Category:NeedsMerge

2011-05-19T14:46:13Z

Jsujjava: Add Category page

This category denotes pages which are thought to require a merge. Don't add pages directly, use [[Template:NeedsMerge]].

Template:NeedsMerge

2011-05-19T14:44:18Z

Jsujjava: Add reference to :Category:NeedsMerge

<center><div align="left" style="border: 1px solid silver; width: 80%;">
<table border="0" class="solid">
<tr>
<td>
[[Image:Merge-arrows.png]]
</td>
<td> This page is may need to be merged with other page(s) including [[{{{1}}}]]. Please help to merge the articles, or discuss the issue on the talk page.</td>
</tr>
</table>
</div></center>

<noinclude>
== Template Documentation ==
This template is used on pages which need to be merged with other pages. The first argument is the suggested page to be merged with.

Pages which use this template are added to the category [[:Category:NeedsMerge]].

Add <nowiki>{{NeedsMerge|SomeOtherPage}}</nowiki> at the top of the page to include this.

</noinclude>

<includeonly>
[[Category:NeedsMerge]]
</includeonly>
<noinclude>
[[Category:Templates]]
</noinclude>

Template:NeedsMerge

2011-05-18T18:04:11Z

Jsujjava: Change to a fancy box

<center><div align="left" style="border: 1px solid silver; width: 80%;">
<table border="0" class="solid">
<tr>
<td>
[[Image:Merge-arrows.png]]
</td>
<td> This page is may need to be merged with other page(s) including [[{{{1}}}]]. Please help to merge the articles, or discuss the issue on the talk page.</td>
</tr>
</table>
</div></center>

<noinclude>
== Template Documentation ==
This template is used on pages which need to be merged with other pages. The first argument is the suggested page to be merged with.

Add <nowiki>{{NeedsMerge|SomeOtherPage}}</nowiki> at the top of the page to include this.

</noinclude>

<includeonly>
[[Category:NeedsMerge]]
</includeonly>
<noinclude>
[[Category:Templates]]
</noinclude>

Template:Delete

2011-05-18T15:28:43Z

Jsujjava: Change to a fancy box

<center><div align="left" style="border: 1px solid silver; width: 80%;">
<table border="0" width="100%" class="solid">
<tr>
<td>
[[Image:Edit-clear.png]]
</td>
<td>This page may be a candidate for <b>speedy deletion</b>. Please discuss the issue on the talk page, or delete if you are an administrator.</td>
</tr>
</table>
</div></center>

<noinclude>
== Template Documentation ==
This template is on pages which should be deleted.

Add <nowiki>{{Delete}}</nowiki> at the top of the page to include this.

</noinclude>

<includeonly>{{{category|[[Category:Candidates for speedy deletion]]}}}</includeonly>
<noinclude>
[[Category:Templates]]
</noinclude>

eLinux.org:Site support

2011-05-18T13:18:18Z

Jsujjava: Add Category Community

== Volunteering to improve the wiki ==
Below please find links to various pages with information and ideas for content and feature additions
to the eLinux wiki.

(Various lists have crept up over the years, lets try to gather links to them here:)

Lists of editor tasks:
* [[Volunteer editor tasks]]
* [[Embedded wiki issues list]]
** Specific cleanup tasks
*** Resolve duplication between [[Embedded Linux Distributions]] and [[Hardware Hacking]] pages (and one other page mentioned by Klaas) -- seems to be resolved by 20100514, (broeggle)
*** Resolve duplication between [[Embedded Linux Distributions]] and [[Toolchains]] (broeggle)

* Create [[Wanted]] pages
** See also [[Special:Wantedpages]]
A lot of wanted pages are just dangling links from the Help pages, for pages that were not
created when we initially set up the wiki. I think most of these types of pages can just be
set to stubs. Alternatively, we can look at the MediaWiki site and copy the page from their
site for these dangling help examples.

Another big set of wanted pages are for links between pages that were copied from
the old CELF public wiki to here. This was done with some automated tools, which I think
made some errors in the translation from MoinMoin to MediaWiki. If the
legacy CELF page exists in this site, the link on the "requesting" page just needs to
be repaired. If there is not matching page, then the link should just be removed.

Just for fun, I'm keeping track over time of some metrics:
=== Wanted page count history ===
{| border="1"
||Date||Wanted page count
|-
||Dec 12, 2008||233
|-
||April 6, 2009||241 (why up?)
|-
||April 15, 2010||122
|-
||April 12, 2011||50 (but only few really relevant)
|}

Why do these stats occasionally rise?
On occasion, the Help pages are re-imported to pick up new pages. This can cause increases in Wanted Pages when the new pages have new page links on them that are not yet present in the new pages set.

* add categories to [[Special:Uncategorizedpages|Uncategorized pages]]
* de-orphan [[Special:Lonelypages|Orphaned pages]]
To de-orphan a page, follow the link to the page, and create a link to it from
an appropriate other page in the wiki. Before doing that, check to make sure that the
information on the page is not duplicated somewhere else in the wiki (maybe by doing
a search). Alternatively, sometimes the information can be copied from the orphan
to someplace else, and the orphan removed. If you copy the information to somewhere else,
just edit the orphan to make it empty, and add the page name to the list here, and an
administrator will remove the page.

List of empty orphan pages:
* <put page name here>

=== Orphan page count history ===
{| border="1"
||Date||Orphan page count
|-
||Dec 12, 2008||122
|-
||April 6, 2009||134 (what the heck?)
|-
||Dec 2, 2009||89
|-
||Dec 9, 2009||30
|-
||April 13, 2011||26
|}

Lists of administrator tasks:
* [[Embedded wiki to-do list]] - a task list for administrators
* [[Embedded Wiki wanted features]]

Other lists:
* [[Elinux issues]] - miscellaneous ideas of things to do

== Resources for volunteers and wiki administrators ==
To communicate with other elinux wiki volunteers, editors and administrators, please join
our
* [[ELinuxWiki:Mailing List|Mailing list]]
* [[eLinuxWiki:History|History page]] - has information about how we got here and why. Also, has links to pages used for previous activities, like contests and promotions.

== Ideas to encourage contributions ==

=== systems to facilitate exiting content review ===
* create email system that people can subscribe to, to review wiki pages a little at a time

=== systems to facilitate addition of content ===
* ability to bounce an LKML email to a collector, possibly adding a tag
** collector would post to wiki, with tag
* ability to forward and LKML email to a site, which returns you a URL (on e.g. lkml.org) for that message
** This makes it easier to link to an LKML message or thread.
* ability to rate LKML messages on a web site

== Donations ==
We don't really have an official mechanism for donations of money.

We are, however, looking for donations of items we can use for prizes
for some of our upcoming contests. Embedded Linux-based products,
or tools or books related to embedded Linux, would be most appreciated.

If you have something like this, or a large donation (greater than $100), please
contact [[User:TimBird|Tim Bird]] or [[User:wmat|Bill Traynor]].

Tim is available at: tim (dot) bird (at) am (dot) sony (dot) com.
Bill is available at: wmat (at) naoi (dot) ca.

[[Category:Community]]

Category:Disable Console

2011-05-16T17:52:01Z

Jsujjava: Undo revision 48049 by Jsujjava (talk)

{{delete}}
[[Category:Categories]]

Category:Disable Console

2011-05-16T17:50:55Z

Jsujjava: Delete content

Kgdb

2011-05-15T20:52:11Z

Jsujjava: Add Category Development Tools

It is fascinating to think that you have control over running Linux Kernel. You can stop, can single-step, can resume and even can put break-points on running Kernel. In fact, you can debug the kernel as easily as you debug any application.

== How to setup kgdb ==

The steps mentioned here are with reference to 2.6.26 Kernel. The main reason is KGDB code is merged into Linux tree from 2.6.26-RC5 kernel.
(As a side note, for kernel < 2.6.26-RC5, you have to get kgdb patch from [ http://kgdb.linsyssoft.com/kernel.htm] and apply them to kernel)

== Hardware Requirements ==

Two x86 machines are required for using KGDB. One of the machines runs a kernel to be debugged called "TEST MACHINE". The other machine runs gdb "DEVELOPMENT MACHINE".
A serial line is required between the development and the test machine. And so obviously, machines need one serial port each. Basically, you will be sending "Debugging Commands" from "DEVELOPMENT MACHINE" to "TEST MACHINE".

== Preparing Kernel to be Debugged ==

1. Download the source of kernel (for e.g., 2.6.26.2)from kernel.org

2. Recompile the Kernel on "DEVELOPMENT MACHINE".
Go to Kernel Hacking and Enable the following options:
-*- Magic SysRq key
[*] Compile the kernel with debug info
[*] KGDB: kernel debugging with remote gdb --->
And in n KGDB:
--- KGDB: kernel debugging with remote gdb
<*> KGDB: use kgdb over the serial console
[ ] KGDB: internal test suite
3. Build kernel and modules
make -j 12 && make modules && make modules_install

4. Transfer the vmlinux and system.map and initrd.img files on "TEST MACHINE".

5. Now, edit the GRUB entry for that kernel on "TEST MACHINE". Add kernel options/kernel parameters like kgddbwait and kgdboc=ttyS0,115200
For e.g., kernel /vmlinux ro root=LABEL=/ rhgb quiet crashkernel=128M@16M kgddbwait kgdboc=ttyS0,115200
kgdbwait -- > This will make Kernel to wait on boot time and will expect someone to connect to it and give further commands
kgdboc --> This is a KGDB I/O driver and we are supplying two arguments. ttyS0 will tell that communication will happen on Serial Port 0 and 115200 is the baudrate.

6. Now boot the Kernel with those kernel parameters.

7. On dev machine, start GDB session.
[dev@einfochips]gdb vmlinux
The argument vmlinux file is the file that is created with Debug symbols.
It will be of much larger size and more than likely to be in the directory where you gave "make" command..

8. Assuming that on "DEVELOPMENT MACHINE" you have set serial interface baudrate as 115200. Connect to the "TEST MACHINE" with target command.
(gdb)target remote /dev/ttyS0

9. This will stop your Kernel booting on "TEST MACHINE" and will give control to your "DEVELOPMENT MACHINE". Now, you can do Single-stepping or put breakpoints and etc.

10. Once your Kernel is running on "TEST MACHINE" and you want control over your running kernel from "DEVELOPMENT MACHINE",
You have to send MANUALLY on TEST machine SysRq command. So, on "TEST MACHINE" press SysRq + g
(i.e., press "ALT" key then Press "PrintScreen" Key and then Press "g" key)

== There are several possible problems that you may face ==
1. Your Kerenel is booted and SysRq+g is not working.
[r00t@einfochips] echo 1 > /proc/sys/kernel/sysrq
This will enable sending SysRq commands.

2. You may find some time that while stopping execution through SysRq key on "TEST MACHINE", it stops but then it is not able to communicate over serial cable with "DEVELOPMENT MACHINE". The reason can be, your KGDB I/O driver is not passed arguments properly and you may need to reconfigure the driver by following way,
[root@einfochips]echo "ttyS0,115200" > /sys/modules/<module name>/parameters

[[Category:Development Tools]]

Embedded wiki issues list

2011-05-14T23:53:11Z

Jsujjava: Change to a redirect

#REDIRECT [[Elinux issues]]

Elinux issues

2011-05-14T23:53:05Z

Jsujjava: Merge from Embedded wiki issues list

{{NeedsMerge|Volunteer_editor_tasks}}
This is the eLinux issues page. This is a raw list of items that need to be worked on for this wiki, based on feedback from various sources.

Here is a list of issues to fix on the eLinux wiki:

== missing pages (top list) ==
* missing Project:Copyrights from link in statement on edit form

== content fixes ==
Have [[Category:Needs Update]], but maybe need simple list of items to fix (maybe this page is it)
** something someone can fix with 10 minutes or less time
*** one possible suggestion, global page review - review a page, take it off the list

=== events page ===
*events page is out of date
** recent events:
*** kernel summit
*** LinuxConf EU
*** O'reilley thing?
*** Ubuntu have something?
*** The PPC conference http://www.power.org/devcon/07/schedule/
** can possibly cherry-pick from
*** the LWN events/calendar page
*** linuxdevice events page

* Would be nice if "recent changes" was a human edited weekly pick of important page updates.

== content building ==
* need to create a list of authored content
* need a template for professional papers
* need recent periodical content
* monthly feature is empty
* Do we want pages listing all kind of products (like here: [[Products]]). There are way too many products to list, so such a list is unwieldy and hardly to maintain.
** The same might hold for chips & vendors and maybe even for distributions.
* Although contributions are under GPL it would be nice if there was some form of attribution. http://www.nslu2-linux.org/ does that (imho) nicely (but they use PMwiki).
* http://www.elinux.org/Special:Wantedcategories seems to suggest that there are some categories that are never made and actually only have one or two pages. Guess this should be resolved as well.

== site management ==
* admins needs ssh access to eLinux.org site
* Tim doesn't have sysop privileges on the site
* Organisational issues have their own page at [[Embedded wiki to-do list]]

== Uncategorized issues ==

[[Category:Community]]

Embedded wiki issues list

2011-05-14T23:46:58Z

Jsujjava: Merge with [Elinux issues]

{{NeedsMerge|Elinux_issues}}

This page contains issues relating to the content of the wiki.
Organisational issues have their own page at [[Embedded wiki to-do list]]

Embedded wiki issues list

2011-05-14T23:37:28Z

Jsujjava: Remove duplicated material

{{NeedsMerge|Elinux_issues}}

This page contains issues relating to the content of the wiki.
Organisational issues have their own page at [[Embedded wiki to-do list]]

* Do we want pages listing all kind of products (like here: [[Products]]). There are way too many products to list, so such a list is unwieldy and hardly to maintain.
* The same might hold for chips & vendors and maybe even for distributions.
* Although contributions are under GPL it would be nice if there was some form of attribution. http://www.nslu2-linux.org/ does that (imho) nicely (but they use PMwiki).
* http://www.elinux.org/Special:Wantedcategories seems to suggest that there are some categories that are never made and actually only have one or two pages. Guess this should be resolved as well.

Elinux issues

2011-05-14T23:28:12Z

Jsujjava: Removed obsolete items

Hammer Uart2 Configuration

2011-05-14T16:48:43Z

Jsujjava: Change to Category TCT-Hammer

The default configuration for the GPH6 and GPH7 pins on the s3c2410 are as GPIO inputs. To configure these pins for usage as a second uart add the following commented section to the arch/arm/mach-s3c2410/mach-tct_hammer.c in the linux source tree, future versions of the Hammer kernel source will include this entry:
<pre>
static void __init tct_hammer_init(void)
{

s3c2410_gpio_cfgpin(S3C2410_GPF0, S3C2410_GPIO_OUTPUT);
s3c2410_gpio_setpin(S3C2410_GPF0, 1);

s3c2410_gpio_cfgpin(S3C2410_GPC12, S3C2410_GPIO_OUTPUT);
s3c2410_gpio_setpin(S3C2410_GPC12, 1);

/* uncomment these to enable the second serial port */
/*
s3c2410_gpio_cfgpin(S3C2410_GPH6, S3C2410_GPH6_TXD2);
s3c2410_gpio_pullup(S3C2410_GPH6, 1);
s3c2410_gpio_cfgpin(S3C2410_GPH7, S3C2410_GPH7_RXD2);
s3c2410_gpio_pullup(S3C2410_GPH7, 1);
*/
#ifdef CONFIG_FB_S3C2410
s3c24xx_fb_set_platdata(&tct_hammer_lcd_info);
#endif
platform_add_devices(tct_hammer_devices, ARRAY_SIZE(tct_hammer_devices));
}

</pre>

after recompiling the kernel and loading it onto the Hammer, the port will be accessable via /dev/ttySAC2.

[[Category:TCT-Hammer]]

Hammer LED Userspace App

2011-05-14T16:48:30Z

Jsujjava: Change to Category TCT-Hammer

This is an example program that uses the /dev/mem device node to access the physical memory registers directly([[media:ledblink.c|source]])

==Usage==
to compile the source use your toolchain command line

<pre>
#arm-linux-uclibc-gcc -o ledblink ledblink.c
</pre>

then transfer the ledblink binary to the hammer file system. make sure that the permissions on the file are set to executable.

<pre>
#chmod 755 ledblink
#./ledblink

Usage: ./ledblink { seconds }
seconds : number of seconds to blink

#./ledblink 20
</pre>

this will cause the onboard LED to blink for 20 seconds

==Source==
<pre>
/*
* ledblink.c: Simple program to blink a led on GPIO F0
*
* Copyright (c) 2008 TinCanTools
* David Anders <danders@amltd.com>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*
*/

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>

#define MAP_SIZE 4096UL /* the size of one page of virtual memory */
#define MAP_MASK (MAP_SIZE - 1) /* mask used for the one page of virtual memory */

#define GPIOF_CON 0x56000050 /* physical address of the GPIO F control register */
#define GPIOF_DAT 0x56000054 /* physical address of the GPIO F data register */

int main(int argc, char **argv) {
int fd,count;
void *map_base, *virt_addr;
unsigned long read_result, writeval;

if(argc < 2) {
fprintf(stderr, "\nUsage:\t%s { seconds }\n"
"\tseconds : number of seconds to blink\n\n",
argv[0]);
exit(1);
}

count = strtoul(argv[1], 0, 0);

/* open the memory device file descriptor */
if((fd = open("/dev/mem", O_RDWR | O_SYNC)) == -1)
return -1;

/* Map one page */
map_base = mmap(0, MAP_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED, fd, GPIOF_CON & ~MAP_MASK);
if(map_base == (void *) -1)
return -1;

/* set the virtual memory address to the GPIO F control register */
virt_addr = map_base + (GPIOF_CON & MAP_MASK);

/* read the current value for GPIO F control register */
read_result = *((unsigned long *) virt_addr);

writeval = read_result;
writeval &= ~0x03; /* mask off the first two bits */
writeval |= 0x01; /* set gpio f0 to output with value of 0x01 */

/* write the modified value to GPIO F0 control register to set GPIO F0 to output */
*((unsigned long *) virt_addr) = writeval;

/* change virtual memory address to GPIO F data register */
virt_addr = map_base + (GPIOF_DAT & MAP_MASK);

for ( count ; count > 0 ; count--) {

/* read the current value for GPIO F data register */
read_result = *((unsigned long *) virt_addr);
writeval = read_result;

if ( (read_result&(1<<0)) )
writeval &= ~(1<<0); /* set GPIO F0 to a value of 0(low-on) */
else
writeval |= (1<<0); /* set GPIO F0 to a value of 1(high-off) */

/* write the modified value to the GPIO F0 data register */
*((unsigned long *) virt_addr) = writeval;
sleep(1);

}

/* read the current value for GPIO F control register */
read_result = *((unsigned long *) virt_addr);

/* make sure the LED is off when leaving the program */
writeval = read_result;
writeval |= (1<<0); /* set GPIO F0 to a value of 1(high-off) */

/* write the modified value to the GPIO F0 data register */
*((unsigned long *) virt_addr) = writeval;

/* unmap the virtual memory before exiting the program */
if(munmap(map_base, MAP_SIZE) == -1)
return -1;

close(fd);
return 0;

}

</pre>

[[Category:TCT-Hammer]]

Hammer LED Driver Module

2011-05-14T16:48:15Z

Jsujjava: Change to Category TCT-Hammer

this is an example kernel module that will blink the onboard LED connected to GPIO F0 ([[media:ledblink.tar.gz|source]])

==Usage==

<pre>
#tar zxvf ledblink.tar.gz
#cd ledblink
</pre>
NOTE: If trying to make against kernel 2.6.29 change #include of arch/arm/regs-gpio to
<pre>
#include <mach/regs-gpio.h>
</pre>
<pre>
#make KERNEL_SRC=/home/foo/bar/hammer/linux-2.6.22
</pre>

NOTE: for more information about the contents and function of the <br>
included Makefile please see the [http://tldp.org/LDP/lkmpg/2.6/html/ The Linux Kernel Module Programming Guide]

this will generate the ledblink.ko file which can be transfer to your hammer and loaded using the insmod command
<pre>
#insmod ledblink.ko
LED Blink Module Loaded
Dec 31 17:10:05 Hammer user.info kernel: LED Blink Module Loaded
</pre>

to remove the module use the rmmod command
<pre>
#rmmod ledblink.ko
LED Blink Module Unloaded
Dec 31 17:10:20 Hammer user.info kernel: LED Blink Module Unloaded
</pre>

==Source Code==
NOTE: this source makes reference to the HZ kernel value and also to "jiffies",<br>
for more information on these see the [[Kernel_Timer_Systems]] documentation
<pre>
/*
* ledblink.c - basic led blinking kernel module
*
* Copyright (c) 2008 TinCanTools
* David Anders <danders@amltd.com>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*
*/
#include <linux/module.h> /* Needed by all modules */
#include <linux/kernel.h> /* Needed for KERN_INFO */
#include <linux/timer.h> /* Needed for kernel timer */
#include <asm/arch/regs-gpio.h> /* Needed for GPIO defines */
#include <asm/io.h> /* Needed for s3c2410 functions */

static int blinkinterval = HZ / 2;
static struct timer_list blink_timer;

static void led_blink(unsigned long dummy)
{

/* the LED is active(on) when low(0) */

if (s3c2410_gpio_getpin(S3C2410_GPF0) == 0) /* check the current value of GPIO F0 */
s3c2410_gpio_setpin(S3C2410_GPF0, 1); /* turn LED off */

else
s3c2410_gpio_setpin(S3C2410_GPF0, 0); /* turn LED on */

mod_timer (&blink_timer, jiffies + blinkinterval); /* restart the timer */

}

int init_module(void)
{

s3c2410_gpio_cfgpin(S3C2410_GPF0, S3C2410_GPIO_OUTPUT); /* set the GPIO line F0 to an output */
s3c2410_gpio_setpin(S3C2410_GPF0, 1); /* make sure the LED starts in the off setting */

printk(KERN_INFO "LED Blink Module Loaded\n");

init_timer (&blink_timer);
blink_timer.function = led_blink;
mod_timer (&blink_timer, jiffies + blinkinterval);

/*
* A non 0 return means init_module failed; module can't be loaded.
*/
return 0;
}

void cleanup_module(void)
{
s3c2410_gpio_setpin(S3C2410_GPF0, 1); /* make sure the LED is off when exiting */

del_timer_sync(&blink_timer); /* sync and delete the timer before exiting */
printk(KERN_INFO "LED Blink Module Unloaded\n");
}

MODULE_LICENSE("GPL");

</pre>

[[Category:TCT-Hammer]]

Hammer LED Driver

2011-05-14T16:48:01Z

Jsujjava: Change to Category TCT-Hammer

==Software==
LED's connected to GPIO's can be accessed in several ways:

* [[Hammer LED Class Driver]]
* [[Hammer LED Driver Module]]
* [[Hammer LED Userspace App]]

==Hardware==
the most common way of operating a LED via a gpio is to use an active low configuration:

[[Image:led-example.jpg]]

[[Category:TCT-Hammer]]

Hammer LED Class Driver

2011-05-14T16:47:48Z

Jsujjava: Change to Category TCT-Hammer

== UserSpace Access ==

the LED onboard the hammer as well as the LED on the carrier board can be accessed from userspace via the sysfs interface. example interfaces are in /sys/devices/platform/s3c24xx_led.0/leds:led0/ and /sys/devices/platform/s3c24xx_led.1/leds:led1/. both directories include a file entry "brightness". to turn a LED on, echo a non zero value to the brightness file entry:
<pre>
echo 1 > /sys/devices/platform/s3c24xx_led.0/leds:led0/brightness
</pre>
to turn a LED off, echo a zero to the the brightness file entry:
<pre>
echo 0 > /sys/devices/platform/s3c24xx_led.0/leds:led0/brightness
</pre>

you can also check the current status of the LED by using cat on the brightness file entry:
<pre>
cat /sys/devices/platform/s3c24xx_led.0/leds:led0/brightness
</pre>

== Adding New LEDS ==

a new LED connected via a GPIO can be defined in the linux-2.6.xx/arch/arm/mach-s3c2410/mach-tct_hammer.c file. each LED will need to include some platform data and a platform device definition. Make sure the platform data and the platform device are above the platform declaration:

<pre>
static struct s3c24xx_led_platdata tct_hammer_pdata_led0 = {
.gpio = S3C2410_GPF0,
.flags = S3C24XX_LEDF_ACTLOW | S3C24XX_LEDF_TRISTATE,
.name = "led0",
.def_trigger = "timer",
};

static struct platform_device tct_hammer_led0 = {
.name = "s3c24xx_led",
.id = 0,
.dev = {
.platform_data = &tct_hammer_pdata_led0,
},
};

</pre>

Also include: '&tct_hammer_led0' in the platform declaration

<pre>
static struct platform_device *tct_hammer_devices[] __initdata = {
&tct_hammer_led0,
&s3c_device_adc,
&s3c_device_wdt,
&s3c_device_i2c0,
&s3c_device_usb,
&s3c_device_rtc,
&s3c_device_usbgadget,
&s3c_device_sdi,
#ifdef CONFIG_MTD_PARTITIONS
&tct_hammer_device_nor,
#endif
};
</pre>

Now you can reflash the Kernel.

this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.

== Nail Board LED's ==

<pre>
static struct s3c24xx_led_platdata tct_hammer_pdata_led1 = {
.gpio = S3C2410_GPH0,
.flags = S3C24XX_LEDF_ACTLOW | S3C24XX_LEDF_TRISTATE,
.name = "led1",
.def_trigger = "timer",
};

static struct s3c24xx_led_platdata tct_hammer_pdata_led2 = {
.gpio = S3C2410_GPH1,
.flags = S3C24XX_LEDF_ACTLOW | S3C24XX_LEDF_TRISTATE,
.name = "led2",
.def_trigger = "timer",
};

static struct platform_device tct_hammer_led1 = {
.name = "s3c24xx_led",
.id = 1,
.dev = {
.platform_data = &tct_hammer_pdata_led1,
},
};

static struct platform_device tct_hammer_led2 = {
.name = "s3c24xx_led",
.id = 2,
.dev = {
.platform_data = &tct_hammer_pdata_led2,
},
};
</pre>

you will also need to add some gpio setup in the machine init function:

<pre>
static void __init tct_hammer_init(void)
{

s3c2410_gpio_cfgpin(S3C2410_GPF0, S3C2410_GPIO_OUTPUT);
s3c2410_gpio_setpin(S3C2410_GPF0, 1);

/* add these lines to setup the leds on the nail board */
s3c2410_gpio_cfgpin(S3C2410_GPH0, S3C2410_GPIO_OUTPUT);
s3c2410_gpio_setpin(S3C2410_GPH0, 1);
s3c2410_gpio_cfgpin(S3C2410_GPH1, S3C2410_GPIO_OUTPUT);
s3c2410_gpio_setpin(S3C2410_GPH1, 1);

s3c2410_gpio_cfgpin(S3C2410_GPC12, S3C2410_GPIO_OUTPUT);
s3c2410_gpio_setpin(S3C2410_GPC12, 1);

/*uncomment these these to enable the second serial port */
/*
s3c2410_gpio_cfgpin(S3C2410_GPH6, S3C2410_GPH6_TXD0);
s3c2410_gpio_pullup(S3C2410_GPH6, 1);
s3c2410_gpio_cfgpin(S3C2410_GPH7, S3C2410_GPH7_RXD0);
s3c2410_gpio_pullup(S3C2410_GPH7, 1);
*/
#ifdef CONFIG_FB_S3C2410
s3c24xx_fb_set_platdata(&tct_hammer_lcd_info);
#endif
platform_add_devices(tct_hammer_devices, ARRAY_SIZE(tct_hammer_devices));
}

</pre>

in addition you will need to add the leds to the device list:

<pre>

static struct platform_device *tct_hammer_devices[] __initdata = {
#ifdef CONFIG_FB_S3C2410
&s3c_device_lcd,
#endif
&s3c_device_adc,
&s3c_device_wdt,
&s3c_device_i2c,
&s3c_device_usb,
&s3c_device_rtc,
&s3c_device_usbgadget,
&s3c_device_sdi,
&tct_hammer_led0,
/* add these two entries for the new LEDs */
&tct_hammer_led1,
&tct_hammer_led2,
&tct_hammer_beeper,
&tct_hammer_buttons,
#ifdef CONFIG_MTD_PARTITIONS
&tct_hammer_device_nor,
#endif
};

</pre>

[[Category:TCT-Hammer]]

Hammer LCD 8bit Color STN

2011-05-14T16:47:26Z

Jsujjava: Change to Category TCT-Hammer

This is a "HowTo" for the Panasonic EDMGRB8KJF ([[media:edmgrb8jf.pdf|Datasheet]]) available from [http://store.earthlcd.com/EDMGRB8KJF?sc=7&category=256 EarthLCD] to be used with the [[Hammer_Board|Hammer]] development module from [[TinCanTools]]

'''NOTE:''' This screen is an 8-bit STN screen, however in order to use it on the S3C2410A Hammer 12-bit STN must be used. The last 4 bits are simply masked off. If you have intentions of using this screen for frameworks such as Qt4 or others please first verify that they have 12-bit color support.

==Hardware==
{|border="3"
|+Matching Pinouts
!Pin Number||Hammer||Note||LCD||Pin Number
|-
|16||style="background:#FFFF40" |VM||style="background:#80FF80" |Display On/Off||style="background:#2099FF" |DISPON||16
|-
|17||style="background:#FFFF40" |VFRAME||style="background:#80FF80" |LCD Vertical sync||style="background:#2099FF" |FRM||20
|-
|18||style="background:#FFFF40" |VLINE||style="background:#80FF80" |LCD Horizontal sync||style="background:#2099FF" |LOAD||14
|-
|19||style="background:#FFFF40" |VCLK||style="background:#80FF80" |LCD pixel clock||style="background:#2099FF" |CP||12
|-
|21||style="background:#FFFF40" |LCD_VD0||style="background:#80FF80" |LCD data bit 0||style="background:#2099FF" |Data0||9
|-
|22||style="background:#FFFF40" |LCD_VD1||style="background:#80FF80" |LCD data bit 1||style="background:#2099FF" |Data1||8
|-
|23||style="background:#FFFF40" |LCD_VD2||style="background:#80FF80" |LCD data bit 2||style="background:#2099FF" |Data2||7
|-
|24||style="background:#FFFF40" |LCD_VD3||style="background:#80FF80" |LCD data bit 3||style="background:#2099FF" |Data3||6
|-
|25||style="background:#FFFF40" |LCD_VD4||style="background:#80FF80" |LCD data bit 4||style="background:#2099FF" |Data4||4
|-
|26||style="background:#FFFF40" |LCD_VD5||style="background:#80FF80" |LCD data bit 5||style="background:#2099FF" |Data5||3
|-
|27||style="background:#FFFF40" |LCD_VD6||style="background:#80FF80" |LCD data bit 6||style="background:#2099FF" |Data6||2
|-
|28||style="background:#FFFF40" |LCD_VD7||style="background:#80FF80" |LCD data bit 7||style="background:#2099FF" |Data7||1
|-
|| || ||style="background:#80FF80" |+3.3V||style="background:#2099FF" |VDD||10
|-
|| || ||style="background:#80FF80" |+3.3V||style="background:#2099FF" |VDD||11
|-
|| || ||style="background:#80FF80" |+3.3V||style="background:#2099FF" |VDD||13
|-
|| || ||style="background:#80FF80" |Ground||style="background:#2099FF" |VSS||5
|-
|| || ||style="background:#80FF80" |Ground||style="background:#2099FF" |VSS||15
|-
|| || ||style="background:#80FF80" |Ground||style="background:#2099FF" |VSS||17
|-
|| || ||style="background:#80FF80" |Ground||style="background:#2099FF" |VSS||19
|-
|| || ||style="background:#80FF80" |Contrast +1.95V (+-0.8V)||style="background:#2099FF" |VCON||18
|}

'''NOTE:''' VCON should be variable control to adjust contrast and the VDD should have separate power control, i.e. via a gpio
NOTE: 3.3V from the Hammer dev kit is not enough power and a seperate regulator will be required to power the device. Please make sure you also tie together the ground pins from the external regulator and the dev board.

'''NOTE:''' This display also requires a backlight inverter (see datasheet for requirements)
==Pictures==
[[File:tincantools-login.jpg]]<br/>
We have a login prompt!<br/>
[[File:mixer-display.jpg]]<br/>
Picture of LCD Display running a mixer console Ncurses GUI

==Linux Kernel 2.6.29.6 Build Notes==
In order to get this screen to work framebuffer support has to be built into your kernel.
cd hammer/source/linux-2.6.29.6
export ARCH=arm
export CROSS_COMPILE=arm-linux-uclibc-
make menuconfig

Device Drivers -> Graphics Support -> Support for frame buffer devices
Inside this sub menu add:
[*] Enable Video Mode Handling Helpers
<*> S3C2410 LCD framebuffer support

Under Device Drivers -> Graphics Support -> Console display driver support ADD
Framebuffer Console Support
'''NOTE''': It is also a good idea to go ahead and add the boot logo.

==Adding LCD to Machine File==
The next step is to add the display settings to your mach-tct_hammer.c file in ./arch/arm/s3c2410
If you have questions about this file please see the linux documentation ( I will try to make a patch for this at a later date)

Open up your mach-tct_hammer.c file as mentioned above and verify the following include headers exist
#include <asm/mach-types.h>
#include <mach/regs-lcd.h>
#include <mach/fb.h>
#include <mach/regs-gpio.h>
If they do not exist please add them.

Next add this in the upper section of the file

/* LCD/VGA controller */
#ifdef CONFIG_FB_S3C2410
static struct s3c2410fb_display __initdata tct_hammer_lcd_info = {
.width = 640,
.height = 480,

.type = S3C2410_LCDCON1_STN8,

.pixclock = 120000,
.xres = 640,
.yres = 480,
.bpp = 12,
.hsync_len = 48,

.left_margin = 4 << (4 + 3),
.right_margin = 8 << 3,
.upper_margin = 10,
.lower_margin = 10,

.lcdcon5 = 2
};
/* LCD/VGA controller */

static struct s3c2410fb_mach_info __initdata tct_hammer_fb_info = {

.displays = &tct_hammer_lcd_info,
.num_displays = 1,
.default_display = 0,

.gpccon = 0xaaaaa9aa,
.gpccon_mask = 0xffffffff,
.gpcup = 0x0000ffff,
.gpcup_mask = 0xffffffff,

.gpdcon = 0x00000000,
.gpdcon_mask = 0xffffffff,
.gpdup = 0x00000000,
.gpdup_mask = 0xffffffff,
.lpcsel = ((0xCE6) & ~7) | 1<<4,
};

#endif

These definitions are what notify the s3c2410fb driver how to configure itself in order to talk to the LCD display properly. We still have to tell the kernel to initialize these as well as configure the GPIO pins to run as the VD pins.

In the *tct_hammer_devices[] definition add
#ifdef CONFIG_FB_S3C2410
&s3c_device_lcd,
#endif
Finally in the tct_hammer_init function add the following lines to the top of the function:
#ifdef CONFIG_FB_S3C2410
// disable LCD_DISPON.
s3c2410_gpio_setpin(S3C2410_GPC4, 0);
s3c2410_gpio_cfgpin(S3C2410_GPC4, S3C2410_GPIO_OUTPUT);

// connect any frame buffer.
s3c24xx_fb_set_platdata(&tct_hammer_fb_info);
#endif

NOTE: TODO - Add information for modifying the s3c2410fb.c file as a setting needs changed to swap colors

Now build your kernel and install it on the device. The last thing you may have to do is configure your getty file in your rootfs to put a console on tty0 (this will include adding tty0 to your securetty list on some occasions)

[[Category:TCT-Hammer]]

Hammer LCD 4bit Grey Scale STN

2011-05-14T16:44:43Z

Jsujjava: Change to Category TCT-Hammer

The Hammer supprts an LCD interface which can be configured to drive various kinds of displays.
The following is how I wired up a 16 shade greyscale, 4 bit single scan, 320 x 240 LCD panel.

I used a Sharp LM32K10 display panel.

*[http://www.esskabel.de/Datenblaetter/LCD-Specs/Sharp/LM/LM32K10.pdf LM32K10 Datasheet]

[[Image:hammerlcd.jpg]]

[[Image:driver.jpg]]

The above schematic uses a 74AC244

The driver interface can be done with either:
*[[media:74ac244.pdf|74AC244]]
*[[media:74ac245.pdf |74AC245]]

The source of V- is left to the user, this panel requires about 7-10ma at -18-19VDC.

I used an *[http://www.datasheetarchive.com/NMA0515S-datasheet.html NMA0515S] with the V+ connection grounded, so its output is ~-30VDC at up to 33ma.

The following circuit drops the -33V to -18V for use by the LCD panel.

The transistor I used is a 2N3906 but any PNP device that can handle 100ma collector current will do.
[[Image:v-bias.jpg]]

The Hammer signon message displayed on the LM32K10 LCD panel.

[[Image:LM32K10.jpg]]

LCD's that can be used with the Hammer using the same interface:

*[http://www.esskabel.de/Datenblaetter/LCD-Specs/Sharp/LM/LM32010P.pdf LM32010P]
*[http://www.esskabel.de/Datenblaetter/LCD-Specs/Sharp/LM/LM32K101.PDF LM32K101]

Other LCD panels with built in controllers that could be used with the Hammer(These panels have an on-board controller and do not use the S3C2410's lcd controller):

*[http://www.allelectronics.com/cgi-bin/item/LCD-101/365/256_X_128_LCD_PANEL_.html Hyundai # HG25504 256x128]
*[http://www.allelectronics.com/cgi-bin/item/LCD-115/365/240_X_64_LCD_DISPLAY_.html Seiko #F2426 240x64]
*[http://www.bgmicro.com/index.asp?PageAction=VIEWPROD&ProdID=10816 AZ displays AGM1264F 128x64]
*[http://www.sparkfun.com/commerce/product_info.php?products_id=8568 XIAMEN OCULAR OPTICS GDM12864H 128x64]

[[Category:TCT-Hammer]]

Hammer I2C Driver

2011-05-14T16:44:22Z

Jsujjava: Change to Category TCT-Hammer

Start by entering the kernel config with the "make menuconfig" command, then choose the "Device Drivers" section
[[image:kernel1.jpg]]

use the up/down arrow keys to move to the "I2C Support" Section and use the space bar to select
[[image:kernel2.jpg]]

use the up/down arrow keys to move to the "I2C Device Interface" Section and use the space bar to select
[[image:kernel3.jpg]]

use the up/down arrow keys to move to the "I2C Hardware Bus support" Section and use the space bar to select
[[image:kernel4.jpg]]

use the up/down arrow keys to move to the "S3C2410 I2C Driver" Section and use the space bar to select
[[image:kernel5.jpg]]

tab to the "Exit" option and move back one screen<br>then use the up/down arrow keys to move to the "Miscellaneous I2C Chip Support" Section and use the space bar to select
[[image:kernel6.jpg]]

there are a number of supported base drivers to select
[[image:kernel7.jpg]]

i2c-* device files, usually found in the /dev directory on your system. They make it possible to have user-space programs use the I2C bus. Information on how to do this is contained in the file Documentation/i2c/dev-interface in the linux source tree.

[[Category:TCT-Hammer]]

Hammer How to use LCD

2011-05-14T16:43:03Z

Jsujjava: Change to Category TCT-Hammer

*[[Hammer LCD 4bit Grey Scale STN| 4-Bit Greyscale STN HowTo Page]]
*[[Hammer LCD 8bit Color STN| 8-Bit Color STN HowTo Page]]

[[Category:TCT-Hammer]]

Hammer How to USB FTDI

2011-05-14T16:42:41Z

Jsujjava: Change to Category TCT-Hammer

This page shows how to configure the FTDI serial adapter for use with the hammer.

==Configure the FTDI driver into the kernel==
cd linux-2.6.22
make menuconfig
Enable the FTDI Serial Converter Driver
Device Drivers --->
USB Support --->
USB Serial Converter Support --->
<M> USB FTDI Single Port Serial Driver (EXPERIMENTAL)
Exit, saving your changes
make
make modules_install INSTALL_MOD_PATH=../buildroot/project_build_arm_nofpu/Hammer/root/

This will compile the various kernel modules required and install them in the appropriate location in the root filesystem.

==Make sure that /dev/ttyUSB0 gets created==
Since the /dev entries are staticlaly defined, we need to ensure that /dev/ttyUSB0 gets created. Edit the
buildroot/target/device/Samsung/Hammer/device_table.txt file. Copy the /dev/ttyS line to create a /dev/ttyUSB line. You need to change the name (ttyS to ttyUSB), the major (4 to 188), and the minor (64 to 0).
/dev/ttyS c 666 0 0 4 64 0 1 4
/dev/ttyUSB c 666 0 0 188 0 0 1 4

==Make sure that the ftdi_sio.ko module gets loaded at boot time==
Edit the buildroot/project_build_arm_nofpu/Hammer/root/etc/inittab file and add a new entry after the rcS entry:
::sysinit:/etc/init.d/rcS
::sysinit:/sbin/modprobe ftdi_sio

==Recreate your rootfs image==
cd buildroot
rm binaries/Hammer/rootfs.arm_nofpu.ext2
make

==Compile a simple serial test program==
Compile [http://www.davehylands.com/hammer/sertest.c sertest.c] using the command line:
arm-linux-gcc -lpthreads -o sertest sertest.c

Transfer the sertest program to the hammer (I put it in /mnt/flash). You can use the rx command:
rx /mnt/flash/sertest
chmod +x /mnt/flash/sertest
and send the sertest program using X-Modem with your serial program. You can run sertest using the following command line:
/mnt/flash/sertest -p /dev/ttyUSB0

If you connect Tx to Rx on the FT232RL module, then you should see what you type.

[[Category:TCT-Hammer]]

Hammer Ethernet

2011-05-14T16:42:25Z

Jsujjava: Change to Category TCT-Hammer

Ethernet can be added to a Hammer Board using the following options:

* [[Enc28j60]] - SPI Interface [[Hammer_How_to_Enc28j60|HowTo for Hammer]]
* WIZ810MJ - SPI Interface [http://wiznet.co.kr/pro_iin_wiz810mj.htm Product Page]
* USB Ethernet - [[Hammer_How_to_USB_Ethernet|HowTo for Hammer]]

[[Category:TCT-Hammer]]

Hammer Buzzer Driver

2011-05-14T16:42:08Z

Jsujjava:

== UserSpace Access ==

the buzzer on the carrier board can be accessed from userspace via the sysfs interface. example interfaces are in the directory marked /sys/devices/platform/tct_hammer-beeper.0/input:input1. the directory include a file entry "beep" and "duration". to generate a beep echo a non zero value to the beep file entry:
<pre>
echo 4096 > /sys/devices/platform/tct_hammer-beeper.0/input\:input1/beep
</pre>
a tone will be generated for the length set in the duration file. to see what the current value is do:
<pre>
cat /sys/devices/platform/tct_hammer-beeper.0/input\:input1/duration
</pre>

the duration is measured in .01 seconds, i.e. a value of 100 is 1 second. if the value of duration is set for zero, the tone will be generated continuously until a zero value is echo'd to the beep entry:
<pre>
echo 0 > /sys/devices/platform/tct_hammer-beeper.0/input\:input1/duration
echo 4096 > /sys/devices/platform/tct_hammer-beeper.0/input\:input1/beep
(tone generated)
echo 0 > /sys/devices/platform/tct_hammer-beeper.0/input\:input1/beep
(tone stops)
</pre>

[[Category:TCT-Hammer]]

Hammer Button Driver

2011-05-14T16:41:54Z

Jsujjava: Change to Category TCT-Hammer

== UserSpace Access ==

the carrier board push button can be accessed via the sysfs interface as well as a shell script functionality. the sysfs entry for the push button can be found in the directory mark /sys/devices/platform/gpio-keys.0 . the driver also looks for a shell script in /sbin called pb0.sh. this shell script can be used to start user land applications. here is the provided example shell script:

<pre>
#!/bin/sh

if [ $1 = "down" ] ; then
if [ -x /mnt/flash/scripts/pb0.down ] ; then
/mnt/flash/scripts/pb0.down
else
current=`cat /sys/class/leds/led1/brightness`
if [ "${current}" = 0 ] ; then
echo 1 > /sys/class/leds/led1/brightness
else
echo 0 > /sys/class/leds/led1/brightness
fi
fi
else
if [ -x /mnt/flash/scripts/pb0.up ] ; then
/mnt/flash/scripts/pb0.up
fi
fi#
</pre>

== Adding New PushButtons ==

the gpio buttons are defined in the linux-2.6.xx/arch/arm/mach-s3c2410/mach-tct_hammer.c file. each button requires that the gpio be defined, a name, and key scan code associated with it. in addition standard platform data and platform device have to be defined.

<pre>
static struct gpio_keys_button gpio_keys_buttons[] = {
[0] = {
.code = 0x26,
.gpio = S3C2410_GPG3,
.active_low = 0,
.desc = "PB0",
},
};

static struct gpio_keys_platform_data gpio_keys_data = {
.buttons = gpio_keys_buttons,
.nbuttons = ARRAY_SIZE(gpio_keys_buttons),
};

static struct platform_device tct_hammer_buttons = {
.name = "gpio-keys",
.id = 0,
.dev = {
.platform_data = &gpio_keys_data,
},
};
</pre>

== PushButton Hardware ==

[[Image:pb-example.jpg]]

[[Category:TCT-Hammer]]

Hammer Board Example Kernel Drivers

2011-05-14T16:41:35Z

Jsujjava: Change to Category TCT-Hammer

* [[Hammer_LED_Driver|LEDS]]
* [[Hammer_Buzzer_Driver|Buzzer]]
* [[Hammer_Button_Driver|PushButton]]
* [[Hammer_I2C_Driver|I2C]]

[[Category:TCT-Hammer]]

Hammer Board Application Notes

2011-05-14T16:41:17Z

Jsujjava: Change to Category TCT-Hammer

This is where I would go looking for information on how to make use of the SIO, interrupt, and parallel I/O pins. For example, the pins must be configured for their function. How is that done? Obviously by writing a bit to an I/O port, but how is that done?

[[Category:TCT-Hammer]]

Hammer Bluetooth

2011-05-14T16:40:56Z

Jsujjava: Change to Category TCT-Hammer

BlueTooth can be used with the following options:

* UART BlueTooth - [http://www.sparkfun.com/commerce/categories.php?cPath=16_115 BlueTooth Uart Modules]
* USB BlueTooth - [http://www.qbik.ch/usb/devices/search_res.php?pattern=bluetooth Support Bluetooth Page]

Dongles that work:

* http://www.geeks.com/details.asp?invtid=ADPBTHPN&cat=NET

Dongles that don't work:

* http://www.geeks.com/details.asp?invtid=BLK-USBCYBERBLUE-BT&cpc=SCH
* http://www.geeks.com/details.asp?invtid=UBT3KH&cpc=SCH

This may change as linux-bluetooth evolves.

Most dongles based on CSR (Cambridge Silicon Radio) chipset work.

Dongles based on Broadcom bcm203x chipsets require firmware to be loaded by the driver.

Dongles based on Broadcom chipsets may work (someday).

[[Category:TCT-Hammer]]

Innovator Instructions

2011-05-13T17:55:12Z

Jsujjava: Add to Category Hardware Hacking

This page describes how to load Linux on the Innovator development board.
Unfortunately, this is not an easy process, since the pre-installed firmware
(iBoot from PSI) does not support reflashing the device with Linux.
You need to install another piece of firmware (rrload) and use that
to write the bootloader to flash, and to load Linux or write Linux
to flash.

Table Of Contents:

Here is a description of the steps necessary to bootstrap my TI Innovator board.

<hr />

Here's how I ([[User:Tim_Bird|Tim Bird]]) did it:

== Hardware Used ==
- Abatron BDI2000
- TI OMAP Deluxe Innovator development kit
- Linux host system (running [[Red Hat]] 7.3)

== Software and Configuration Files Used ==
- Abatron
- Abatron firmware image for ARM
- Abatron setup program
- innov925.cfg
- reg925t.def
- rrload
- setup
- rrload.com1
- toolchains
- Arm toolchains from Sony
- kernel
- celinux-031030.tar.bz2
- root filesystem
- [not documented yet]

== Terms ==
BOB = Break-Out-Board

== General Outline For Bootstrapping using Abatron JTAG and rrload ==
=== configure abatron ===
- install abatron firmware
- set network address for abatron
=== prepare target hardware and connections ===
- disassemble innovator, and install separate boards in break-out-board
- see instructions for Innovator Quick Start on PSI disk
- connections:
- host machine ethernet to hub (I configured as 192.168.1.1)
- abatron ethernet to hub (I configured as 192.168.1.2)
- BOB ethernet to hub (I configured as 192.168.1.3)
- Abatron jtag to multi-ICE connector on BOB
- use the 14-pin to 20-pin connector, labelled "BDI side" on one end and "ARM/[[XScale]]" on the other end
- attach this cable with "BDI side" in "Target A" on the Abatron and with "ARM/[[XScale]]" on J13
on the BOB
- set JP1 and JP2 on the BOB with jumpers on pins 1-2. This means put the jumpers on the
RIGHT side on each set of pins.
- connect dual serial cable between BOB and host machine
- connect DB9 connector to interface module serial port
- connect end of serial cable labeled COM1 to a null-modem (crossover cable)
- connect other end of null-modem cable to first serial port (ttyS0) on the linux host machine
=== prepare host software ===
- download and place files in /tftpboot
- innov925.cfg
- reg925t.def
- setup
- rrload.com1
- make sure tftpd is ready to run
- make sure minicom is configured to access /dev/ttyS0, at 115K N81
- in one window, run minicom to be listening to the serial output from the Innovator board
- in another window, be ready to run telnet to control the abatron
- you may want to add "192.168.1.2 abatron" to your /etc/hosts file
=== install rrload in user flash 0 ===
- make sure jumpers are set on BOB for access to user flash 0
- power up abatron by plugging in power cable at back
- start abatron by telnetting into it
- [hostpc]% telnet abatron
- start Innovator by flipping switch on interface module
- load and run setup
- [abatron prompt]>load setup
- [abatron prompt]>g
- load and run rrload.com1
- [abatron prompt]>load rrload.com1
- [abatron prompt]>g
- the rrload menu should appear in minicom
- save rrload to flash
- [rrload menu] E (for Erase component)
- [rrload menu] 1 (to erase the flash memory where the bootloader resides)
- [rrload menu] 0 (to return to the Main menu)
- [rrload menu] 2 (to store component to flash)
- [rrload menu] 1 (to store the bootloader)
- [rrload menu] 0 (to return to the Main menu)
- set configuration for rrload
- [need more detail]
- save configuration (bootloader params) to flash
- [rrload menu] E (for Erase component)
- [rrload menu] 2 (to erase the flash memory where the bootloader params resides)
- [rrload menu] 0 (to return to the Main menu)
- [rrload menu] 2 (to store component to flash)
- [rrload menu] 2 (to store the bootloader params)
- [rrload menu] 0 (to return to the Main menu)

=== use rrload to boot the kernel and root filesystem ===
[ need more detail]
==== build the kernel ====
Here are some commands I used to build the kernel:
- cd celinux-031030/
- <code>export PATH=$PATH:/usr/local/armv4tl-celf-linux/bin</code>
- cp arch/arm/def-configs/innovator .config
- make ARCH=arm CROSS_COMPILE=armv4tl-celf-linux- oldconfig
- make ARCH=arm CROSS_COMPILE=armv4tl-celf-linux- dep
- make ARCH=arm CROSS_COMPILE=armv4tl-celf-linux- zImage
==== prepare kernel for download ====
- /home/tbird/innovator/rrload/mkimage --LAddr 10c08000 --EAddr 10C08000 arch/arm/boot/compressed/vmlinux vmlinux.rr
- cp vmlinux.rr /tftpboot/
==== download kernel to board ====
- minicom (set to /dev/ttyS0)
- turn on development board, you should see the rrload menu
- choose option 3 (view/edit params) on the rrload menu
- choose option 3 (I/O load format)
- set value to "rrbin"
- choose option 4 (I/O load port)
- set value to "ser"
- choose option 0 (back to main menu)
- choose option 1 (load from I/O port)
- choose option 1 (load kernel)

On the host, as root copy the file to the serial port:
- cat /tftpboot/vmlinux.rr >/dev/ttyS0

On the client, wait for download to complete. Dots will appear
as the kernel is downloaded.
- choose option o (back to main menu)

==== download rootfs to board ====
[need more detail here]

==== boot the kernel ====
- choose option 4 (boot kernel)

== Important Notes ==
- I couldn't find documentation on JP1 and JP2. After trial-and-error, it was determined by
Takao Shinohara (of Sony) that pin 1 is on the RIGHT of these jumpers.

== Files ==
Here is a list of lots of relevant (or maybe not relevant) files:

Here are some files I used for bootstrapping:
- [[Media:innov925.cfg]]
- [[Media:reg925t.def]]
- Media:setup - could not upload file. Please see [http://tree.celinuxforum.org/CelfPubWiki/InnovatorInstructions?action=AttachFile&do=get&target=setup old wiki download]
- [[Media:rrload.com1]]

This is a file I got from TI describing how to build Linux for the Innovator and
bootstrap using a JTAG device and Code Composer Studio, from Windows:
- [[Media:Building_Linux_For_Innovator.pdf]]
- http://focus.ti.com/lit/an/swpa011/swpa011.pdf - above pdf on ti site
- http://focus.ti.com/lit/ug/spru667/spru667.pdf - Innovator Development Kit Manual
- http://focus.ti.com/docs/toolsw/folders/print/innovatorevmv1.html - product info
- [http://focus.ti.com/omap/docs/omapgenpage.tsp?navigationId=9305&templateId=5663&path=templatedata/cm/omaptools/data/innovator_kits innovator specs]

== Other support sites ==
- see http://muru.com/linux/omap/ for an unnofficial web site supporting Linux on Innovator
- see Linux for TI OMAP mail archives at: http://linux.omap.com/pipermail/linux-omap-open-source/
- to subscribe: http://linux.omap.com/mailman/listinfo/linux-omap-open-source
- TI page with lots of downloads and links to other resources is here:
http://focus.ti.com/docs/general/splashdsp.jhtml?&path=templatedata/cm/splashdsp/data/linux_com_portal
- The following page has a link to the 2.6 [[BitKeeper]] tree for TI OMAP:
http://focus.ti.com/docs/general/splashdsp.jhtml?&path=templatedata/cm/splashdsp/data/linux_com_resources
[[Category:Hardware Hacking]]

Memory Debuggers

2011-05-13T17:52:49Z

Jsujjava: Add Category Development Tools

Several tools exist for finding memory leaks or for reporting individual memory allocations
of a program. These tools help analyze memory usage patterns, detect unbalanced allocations and frees, report buffer over- and under-runs, etc.

=== mtrace ===
mtrace is a builtin part of glibc which allows detection of memory leaks caused by unbalanced malloc/free calls. To use it, the program is modified to call mtrace() and muntrace() to start and stop tracing of allocations. A log file is created, which can then be scanned by the 'mtrace' Perl script. The 'mtrace' program lists only unbalanced allocations. If source is available it can
show the source line where the problem occurred. mtrace can be used on both C and C++ programs.

See the [http://wikipedia.org/wiki/Mtrace mtrace wikipedia article] for more information.

=== memwatch ===
memwatch is a program that not only detects malloc and free errors but also reads and writes beyond the allocated space (buffer over and under-runs). To use it, you modify the source to include
the memwatch code, which provides replacements for malloc and free.

Some things that memwatch does not catch are writing to an address that has been freed and reading data from outside the allocated memory.

=== mpatrol ===
mpatrol appears to be like memwatch.

See http://mpatrol.sourceforge.net/

=== dmalloc ===
"The debug memory allocation or dmalloc library has been designed as a drop in replacement for the system's malloc, realloc, calloc, free and other memory management routines while providing powerful debugging facilities configurable at runtime. These facilities include such things as memory-leak tracking, fence-post write detection, file/line number reporting, and general logging of statistics."

This library can be used without modifying the existing program, and uses environment variables
to control it's operation and set of issues to log.

It's home page is at: http://dmalloc.com/

See Cal Erickson's article (link below, page 2) for information about using this system.

=== dbgmem ===
dbgmem looks like another dynamic library replacement tool, similar to dmalloc (but possibly having less features)

See http://dbgmem.sourceforge.net/

=== valgrind ===
valgrind does dynamic source code modification to instrument the program, and provides a number
of memory problem detection tools and profiling tools. Unfortunately, as of July 2010 it is
only available for x86 and ppc64 architecture platforms.

See [[Valgrind]]

=== Electric Fence ===
See [[Electric Fence]]

== Tutorials or Overviews ==
* [http://www.linuxjournal.com/article/6059 Memory Leak Detection in Embedded Systems] by Cal Erickson, Linux Journal, September 2002
** This article mentions mtrace, memwatch and dmalloc

[[Category:Development Tools]]

Hammer Uart2 Configuration

2011-05-13T17:52:00Z

Jsujjava: Add Category Hammer

Hammer LED Userspace App

2011-05-13T17:51:41Z

Jsujjava: Add Category Hammer

Hammer LED Driver Module

2011-05-13T17:51:17Z

Jsujjava: Add Category Hammer

Hammer LED Driver

2011-05-13T17:50:47Z

Jsujjava: Add Category Hammer

Hammer LED Class Driver

2011-05-13T17:50:27Z

Jsujjava: Add Category Hammer

Hammer LCD 8bit Color STN

2011-05-13T17:50:01Z

Jsujjava: Add Category Hammer

Hammer LCD 4bit Grey Scale STN

2011-05-13T17:49:38Z

Jsujjava: Add Category Hammer

Hammer I2C Driver

2011-05-13T17:48:19Z

Jsujjava: Add Category Hammer

Hammer How to use LCD

2011-05-13T15:34:01Z

Jsujjava: Add Category Hammer

*[[Hammer LCD 4bit Grey Scale STN| 4-Bit Greyscale STN HowTo Page]]
*[[Hammer LCD 8bit Color STN| 8-Bit Color STN HowTo Page]]

[[Category:Hammer]]

Hammer How to USB FTDI

2011-05-13T14:38:33Z

Jsujjava: Add Category Hammer

Hammer Ethernet

2011-05-13T13:14:22Z

Jsujjava: Add Category Hammer

Hammer Buzzer Driver

2011-05-13T13:13:37Z

Jsujjava: Add Category Hammer

Hammer Button Driver

2011-05-13T13:12:41Z

Jsujjava: Add Category Hammer

Android Events

2011-05-13T13:11:39Z

Jsujjava: Add Category Events

The only events I know of (as of Jan 2010) with Android content are:

== Google Events ==
* Google I/O - see the [http://en.wikipedia.org/wiki/Google_I/O Google I/O wikipedia entry]
** Google I/O for 2011 was in on May 10,11 in San Francisco
*** See [[Tims GoogleIO 2011 Notes]]
* [http://www.google.com/events/developerday Google Developer Days]
** Regional events with Google developers

== Linux events ==
* http://events.linuxfoundation.org/events/embedded-linux-conference/ Embedded Linux Conference
** See http://embeddedlinuxconference.com for an overview of multiple years
*** There were android talks especially at ELC Europe 2009 and 2010
*** See Matt Porter's talk and Nina Wilner's talk at [[ELC Europe 2009 Presentations]]
*** See Tim Bird's talk and the Android tutorial at [[ELC Europe 2010 Presentations]]

* Some CELF Japan Jamborees have technical content related to Android
** The following had Android presentations: [[Japan Technical Jamboree 31]], [[Japan Technical Jamboree 34]]

== Android Builders Summit ==
This is a new event (in 2011) for Android systems developers. This includes developers who are porting
Android to new hardware, working on the Android kernel or low-level infrastructure, or otherwise working
on Android itself (not on Android application development).

* [http://events.linuxfoundation.org/events/android-builders-summit/ ABS home page]
** [http://events.linuxfoundation.org/events/android-builders-summit/slides Presentation slides]

== Regional events ==
* [http://www.droidcon.co.uk/ Droidcon London 2010] - October 28,29, 2010, London
* [http://droidcon.be/ Droidcon Belgium] - next one = January 21, 2011, Brussels
* [http://www.android-group.jp/abc2011w/ Android Bazaar and Conference - Jan 9, 2011, Tokyo)

== General ==
* [http://www.andevcon.com/ Android Developer's Conference] - March 7-9, 2011
** This seems to be the first full-blown Android developer event, covering mostly application development, but also some system talks

== Other Conferences ==
* [http://www.gdconf.com/ Game Developer's conference] is starting to see Android participation
** See http://android-developers.blogspot.com/2010/01/android-at-2010-game-developers.html

[[Category:Android]]
[[Category:Events]]