eLinux.org - User contributions [en]

Companies

2007-08-23T02:59:32Z

Chris: update atmark techno links

== Overview ==

This page provides information about companies that build and sell consumer electronics devices with Linux as their operating system. If you're looking for companies that build and sell Linux distributions for embedded devices or who provide services around embedded Linux, please see the [[Vendors]] page.

== A ==
[http://www.atmark-techno.com/en Atmark Techno]
* [http://www.atmark-techno.com/en/products/armadillo Armadillo Series]
* [http://www.atmark-techno.com/en/products/suzaku SUZAKU Series]

== M ==
[http://www.motorola.com/ Motorola] - [http://wikipedia.org/wiki/Motorola Wikipedia entry]

== N ==
[http://www.nokia.com/ Nokia] - [http://wikipedia.org/wiki/Nokia Wikipedia entry]
* [http://en.wikipedia.org/wiki/Nokia_N800 N800]
* [http://en.wikipedia.org/wiki/Nokia_770 N770]

[http://www.neurostechnology.com/ Neuros Technology] - [http://wikipedia.org/wiki/Neuros_Technology Wikipedia entry]
* [http://en.wikipedia.org/wiki/Neuros_Technology#Neuros_OSD Neuros OSD]

== P ==
[http://www.panasonic.com/ Panasonic] - [http://wikipedia.org/wiki/Panasonic Wikipedia entry]

== S ==
[http://www.sony.com/Sony Sony] - [http://wikipedia.org/wiki/Sony Wikipedia entry]
* too many products to list, see
** [http://www.sony.net/Products/Linux/Download/search.html Global Linux source code download site]
** [http://www.sony.com/linux US Linux source code download site]

[http://www.securecomputing.com Secure Computing] - [http://en.wikipedia.org/wiki/Secure_Computing Wikipedia entry]
* SnapGear family of products [http://www.snapgear.com homepage]

== T ==
[http://www.timesys.com TimeSys]
* [http://www.timesys.com/services LinuxLink]

[http://www.tvblob.com/?s=elinux Tvblob]
* [http://www.tvblob.com/?s=elinux vMAX]
* [http://www.tvblob.com/?s=elinux vTALK]
* [http://www.tvblob.com/?s=elinux vLINK]
* [http://www.tvblobbox.com/?s=elinux Tvblob BOX]

== Instructions for submitters ==
Please add company names in alphabetical order, and follow
the existing format. Make a link from your company
name to your main web site. If you have a wikipedia entry, please
link that as well. If you would like to, you may list a few
of your Linux-based products, but please don't go overboard.

[[Category:Companies]]

Products

2007-08-23T02:53:26Z

Chris: update armadillo-500 link

Here is a list of products which use embedded Linux.

Please see the [[Talk:Products|talk page]] for information about how we want to populate this page.

== Televisions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Televisions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Mobile Phones ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Mobile Phones using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
|- align="center"
| [http://www.accton.com/homepage/main3/product_range/23_CE/VM1188T.htm VM1188T]
| [http://www.accton.com Accton]
| 2006
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://www.cellon.com/products.jsp?id=18 C8000]
| [http://www.cellon.com/ Cellon]
| 2005
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS8901223473.html 3G Linux Ref Design]
| [http://www.catt.ac.cn/english/ Datang]
| 2004
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS4367004471.html E28 FMC phones]
| [http://www.e28.com/eng/ E28]
| 2006
| -
| -
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS5033717348.html E28 E2800]
| [http://www.e28.com/eng/ E28]
| 2003
| 32
| 32
| ARM9
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS2220873893.html E28 E2800+]
| [http://www.e28.com/eng/ E28]
| 2004
| 64
| 32
| ARM9 300MHz
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://www.g-tekgroup.com/products/pwg_500.asp PWG500]
| [http://www.g-tekgroup.com/ G-Tek]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://linuxdevices.com/articles/AT2559540724.html G500i]
| Grundig
| 2005
| 52 - User
| X
| OMAP850
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://www.haier.com/products/product.asp?proID=4948 N60]
| [http://www.haier.com Haier]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://www.imcosys.com/English/Smartphone/smartphone.html GPS Phone]
| [http://www.imcosys.com/ ImCoSys]
| 2006
| 64
| 64
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| [http://www.imcosys.com/English/Download/download.html SDK & Flash Image]
|-
|- align="center"
| [X]
| [X]
| X
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [X]
| [X]
| X
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|}
 

== Settop Boxes ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Settop Boxes using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Digital Video Recorders ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Digital Video Recorders using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Game Consoles ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Game Consoles using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| PlayStation 2
| Sony Computer Entertainment
| 2000
| 32MB
| unknown
| MIPS 64-bit R5900
| [http://en.wikipedia.org/wiki/PlayStation_2 PS2 wikipedia page], [http://playstation2-linux.com/ Playstation-linux community site]
| [http://blackrhino.xrhino.com/main.php?page=home Black Rhino Linux distribution site]
|- align="center"
| PlayStation 3
| Sony Computer Entertainment
| 2006
| 512 MB
| unknown
| CELL broadband engine
| [http://en.wikipedia.org/wiki/PlayStation_3 PS3 wikipedia page]
| [http://en.wikipedia.org/wiki/Linux_for_PlayStation_3 wikipedia PS3-linux page]
|-
|}
 

== Still and Video Cameras ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| HDR-UX1, HDR-SR1 video cameras
| Sony
| 2006
| ??
| ??
| ARM9
| [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=11035608 Sonystyle store listing]
| [http://www.sony.net/Products/Linux/Download/HDR-UX1_HDR-SR1.html Sony Linux Download area]
|-
|}

== Not Yet Categorized ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.linuxdevices.com/articles/AT4268573160.html HS210]
| [http://www.ericsson.com Ericsson]
| 2000
| 32
| 32
| StrongARM SA-1110
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| Armadillo-500
| [http://www.atmark-techno.com/en Atmark Techno]
| 2007
| 64
| 16
| i.MX31
| [http://www.atmark-techno.com/en/products/armadillo/a500 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser Armadillo Developer Site]
|-
|- align="center"
| Armadillo-300
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a300 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-300 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-9
| [http://www.atmark-techno.com/en Atmark Techno]
| 2004
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a9 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-9 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-240
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a240 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-240 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-230
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a230 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-230 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-220
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a220 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-220 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-210
| [http://www.atmark-techno.com/en Atmark Techno]
| 2005
| 32
| 4
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a210 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-210 Armadillo Developer Site]
|-
|}
 
--[[User:Bharatkapoor|Bharatkapoor]] 23:35, 5 December 2006 (EET)

[[Category:Products]]

Audio Video Graphics Spec 5fR2

2007-07-16T02:42:58Z

Chris:

Draft 0.3

== Introduction ==

Audio, video, and graphics processing is at the core of many CE products. The AVG requirements for CE devices are different than those for PCs/Servers, notably with respect to footprint, input devices, interlacing, streaming, etc.. Multiple graphics planes and video planes may be combined using, e.g., alpha blending and animation.

== Rationale ==

No single default/standard interfaces exist for AVG. Having a well defined, well supported interface for AVG devices will reduce fragmentation of solutions and encourage the CE community to develop solutions that apply to conforming interfaces, so that they can be deployed across a wider range of systems.

== Terminology ==

=== Acronyms and terms ===

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+ Acronyms and Terms
! style="background:#D0E0FF;"|'''Term'''
! style="background:#D0E0FF;"|'''Definition'''
|-
|ALSA||Advanced Linux Sound Architecture -- functional level audio API, now standard in 2.6 Linux kernels, replacing OSS.
|-
|API||Application Programmers Interface
|-
|ARIB||Association of Radio Industries and Businesses. Most relevant to AVG is the proposed graphics architecture proposed for High Definition TV Broadcast (the 5-plane model).
|-
|ATSC||Advanced Television Systems Committee. American standard body for digital television broadcasting.
|-
|Back-end Scaler||A Scaler which manipulates the graphics planes and data, but does not allow the host processor access to the (blended) end result, mainly for efficiency reasons.
|-
|CCIR 601||In 1982 CCIR 601 established a digital video standard, which uses the Y, Cr, Cb color space (often incorrectly referred to as YUV). Unlike YUV, Cr,Cb range [-0.5, -0.5]. A full conversion matrix is included below (*)
|-
|CE||Consumer Electronics: a class of devices used in the home or on the move. Includes DVD, DVR, PVR, PDA, TV, set-top box, cellular phones, etc.
|-
|DVB||Digital Video Broadcast: European standards body for digital television broadcasting.
|-
|DVD||Digital Versatile Disc: high capacity multimedia data storage medium.
|-
|DVR||Digital Video Recorder: a consumer electronic device.
|-
|FB,Framebuffer||Abstraction of video-out hardware with a low level (ioctl) API. Standard in >2.4 Linux kernel (see the /usr/src/linux/Documentation/fb kernel tree directory for more information).
|-
|Front-end Scaler||A Scaler which manipulates the graphics planes and data and allows the host processor access the (in-between and) end results.
|-
|HDTV||High Definition Television: provides a higher quality television broadcast, with progressive and interlaced ( 720p to 1080i ) video and support for 16:9 aspect (movie) ratio.
|-
|JPEG||Joint Photographic Experts Group: (lossy) still image compression standard.
|-
|MHP||Multimedia Home Platform: an API used together with MPEG-2 transmissions.
|-
|MIME||Multipurpose Internet Mail Extension: a standard for identifying the type of data contained in a file. MIME is an Internet protocol that allows sending binary files across the Internet as attachments to e-mail messages. This includes graphics, photos, sound, video files, and formatted text documents.
|-
|MP3||MPEG-1 Audio Layer 3: a popular audio compression standard.
|-
|MPEG-1/2/4||Moving Picture Experts Group: a compression standard for digital audio & video with varying levels of complexity and achievable compression ratios.
|-
|NTSC||National Television Systems Committee: American standard for analog television broadcasting.
|-
|PAL||Phase Alternating Line: American standard for analog television broadcasting.
|-
|PNG||Portable Network Graphics: (lossless) still image compression standard.
|-
|PVR||Personal Video Recorder: a consumer electronic device.
|-
|RGB[A]||Colorspace representation commonly used in computer graphics. It uses three orthogonal components -- Red, Green and Blue -- to represent colors in to human visible spectrum, e.g. by combining red and green as additive colors it can fool the eye into seeing "yellow" light. An optional A at the end denotes the presence of per-pixel alpha. See also CCIR 601.
|-
|Scaler||Graphics hardware accelerator which may scale and reformat (e.g. convert from YCC to RGB) graphics data and merge multiple independent graphics planes for final display.
|-
|V4L||Video for Linux: low level (ioctl) video input and overlay API, standard in 2.4. Originally designed for control of analog video capture and tuner cards, as well as parallel port and USB video cameras. Incorporated in many other higher level APIs such as DirectFB.
|-
|!V4L2||Video for Linux, second version, made to be more flexible and extensible. Added specifications for digital tuner control and capture.
|-
|YC''''''bCr[A]||Colorspace representation commonly used in analog and digital video broadcasts, and video compression technologies such as MPEG. It uses three orthogonal components, one for luminance (Y) and two for the color-difference signals (Cr,Cb). Since the eye is less sensitive to color than luminance, the color difference signals often get a smaller bandwidth allocated (or lower pixel resolution in the digital domain). An optional A at the end denotes the presence of per-pixel alpha. See also CCIR 601.
|-
|YIQ||Colorspace representation commonly used in North American TV broadcast and is similar to YUV (see definition of YUV). The relation with YUV is: I == 0.74 V - 0.27 U and Q == 0.48 V + 0.41 U
|-
|YUV||Colorspace representation commonly used in European TV broadcast. It is similar to YC''''''bCr and often meant to be the same (incorrectly) with U referring to Cb and V referring to Cr. With Y (luminance) defined as Y==0.299 R + 0.587 G + 0.114 B, by definition, U==B-Y, thus U represents colors from blue (U>0) to yellow (U<0). Likewise V==R-Y, thus V represents colors from magenta (V>0) to Cyan (blue green) (V<0).
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ RGB to YCbCr conversion matrix
|Y |||| 0.299 0.587 0.114||R
|-
|Cr||==|| 0.500 -0.419 -0.081||G
|-
|Cb||||-0.169 -0.331 0.500||B
|}

=== Compliance classifiers ===

Terminology conventions are adopted here as they are defined in IETF RFC 2119, "Key words for use in RFCs to Indicate Requirement Levels" (by S. Bradner, March 1997). A compliance classifier from the following set may be used:

;[M]ust, Required, Shall: This is the minimum set of requirements. The CELF based products are expected to comply with these requirements when expressed in unconditional form. A conditional requirement expressed in the form, "If X, then Y must be implemented", means that the requirement "Y" must be met when the conditional aspect "X" applies to a given implementation.

;[S]hould, Recommended: Recommended items are optional items that are strongly recommended for inclusion in CELF based products. The difference between "recommended" items and "optional" items, below, is one of priority. When considering features for inclusion in a product, recommended items should be included first.

;[O]ptional, May: Optional items are suggestions for features that will enhance the user experience or are offered as a less preferred choice relative to another recommended feature. If optional features are included, they should comply with the requirement to ensure interoperability with other implementations.

;E[X]pressly Forbidden: This term means that an item must not be incorporated in a CELF based product.

== Platforms ==

[O] Three target platforms are used or under consideration:
*Renesas SH4 host with SM501 graphics (See SzwgPlatform3)
*TI OMAP (See SzwgPlatform1)
*X86 generic with Matrox G450/550

For the first two, the [[System Size Spec]] page has a full description under "Definition - Platform".

== Audio Specification ==

[O] No additional Audio specifications have been defined. ALSA, defined in kernel 2.6, may be used. Further evaluation is required before it can be considered for recommendation (see work in progress). Future extensions relate to AV streaming and synchronization.

== Video-in/Capture Specification ==
[O] No additional Video input (capture) specifications have been defined. !V4L2, as defined in kernel 2.6, may be used.

[O] Proprietary solutions may also be used for video capture and digital tuners if
!V4L2 does not suffice.

[O] DirectFB may be used as a higher level API.

Note: Video output can be seen as an (interlaced) sub-set of graphics. See graphics specification below for more details.

== Video-out/Graphics Specification ==

[S] The standard Framebuffer is recommended for use in embedded CE devices.

[O] DirectFB may also be used in combination with the framebuffer.

Extensions to both are under consideration (see work in progress).

=== Graphics formats ===

[O] The framebuffer supports CLUT, RGB and RGBA packet data formats, but not YC''''''bCr[A].
Hardware capable of accelerating the display YC''''''bCr[A] packed data may develop
their own extensions to the framebuffer for now.

[O] Also, the DirectFB framework which supports these formats may be used.

=== Multi-plane support ===

[O] Graphics hardware capable of multiple planes may be implemented with a single or multiple
device drivers with one device per plane e.g. /dev/fb0, /dev/fb1,.../dev/fb5 for a 5 plane
capable device. Front-end based scalers are recommended to use the DirectFB framework.

[O] Back-end scalers may add ioctl's to their framebuffer drivers.

== Work in progress ==

Both DirectFB and the Framebuffer '''can''' be extended with YCbCr formats and multi-plane blending features commonly found in embedded CE devices. However, it is likely that only one of them will be supported in the future.

=== Framebuffer specification ===

==== YCbCr Format ====
===== Resolution Support =====

The recommended formats are:
*4:4:4 Equal number of samples of Y, Cb and Cr.
*4:2:2 Cb/Cr are subsampled by a factor of two horizontally.
*4:2:0 Cb/Cr are subsampled by a factor of two in both directions.
*4:1:1 Cb/Cr are subsampled by a factor of four horizontally (used in DV).

If any of these formats are used, the CCIR 601 standard must be used. It defines how the data is interleaved and the relative positions of the Cb/Cr samples in relation to the Y samples.

===== Memory representation =====

YCbCr may be stored in e.g a framebuffer in various ways:

*packed YC''''''bCrA 4:4:4 : 32-bit unit containing one pixel with alpha
*packed YC''''''bCr 4:2:2 : 16-bit unit, two successive units contain two horizontally adjacent pixels, no alpha
*planar YC''''''bCr[A] 4:2:2 : three [four] arrays, one for each component
*semi-planar YC''''''bCr 4:2:2 : two arrays, one with all Ys, one with Cb and Cr.
*planar YC''''''bCr[A] 4:2:0 : three [four] arrays, one for each component
*semi-planar YC''''''bCr 4:2:0 : two arrays, one with all Ys, one with U and Vs

Following CCIR601, only the packed formats are recommended, with the possible exception of a separate alpha plane in some cases (see ARIB [O6] proposal).

==== Font rendering ====
*freetype [O5]

==== Basic 2D acceleration ====

*lines (horz./vert. vs. anti-aliased lines)
*rectangles (fill and copy)
*pixmaps (bitblt, scaling)

==== Video format control ====

*resolution
*interlaced/progressive

==== Multi-plane support ====

*Each plane is represented by... [/dev/fb0, /dev/fb1,...]
*Additional API (ioctl) calls... [display order, placement, scaling,...]

==== DirectFB specification ====

[http://www.directfb.org/documentation/DirectFB_overview_V0.2.pdf DirectFB overview] [G2] provides a list of currently supported features, summarized below.

==== Important Terminology ====
;Surface:Memory region physically reserved for rendering pixels. Surfaces are used for regular rendering of pixels, sprites and so on.
;Sub-surface:Sub-region of surface. No physical memory allocated.
;Primary Surface:Visible screen in full screen mode.
;Layer:Each layer is different video memory. They are alpha-blended and displayed.
;Window/Windowstack:Each layer may have multiple window. Windowstack is a stack of windows. Each window has surface. Their locations and orders may be changed.

==== YCbCr Format ====
===== Resolution Support =====

Supported formats are:
*4:2:2 Cb/Cr are subsampled by a factor of two horizontally.
*4:2:0 Cb/Cr are subsampled by a factor of two in both directions.

===== Memory representation =====

*packed YCbCr 4:2:2 : 16-bit unit, two successive units contain two horizontally adjacent pixels, no alpha
*planar YCbCr 4:2:0 : three arrays, one for each component

===== Font rendering =====

*DirectFB bitmap font
*!TrueType (using !FreeType2)
*No bold or italics support other than by specifying a different typeface from the same font family. For example, 'Times New Roman Regular' and 'Times New Roman Italic' correspond to two different faces.

==== Basic 2D acceleration ====

*lines (anti-aliased)
*rectangles (fill and copy)
*triangle (fill and copy)
*pixmaps (bitblt, scaling)
*Per-pixel alpha blending (a.k.a. texture alpha)
*Per-plane alpha blending (a.k.a. alpha modulation)
*Colorizing (a.k.a. color modulation)
*Source and destination color keying

==== Video format control ====

*resolution
*interlaced/progressive support

==== Multi-plane support ====

* DirectFB layers (not surfaces) support the concept of planes.
* Layer API is provided through IDirectFBD''''''isplayLayer Interface.
* Opacity is available through IDirectFBD''''''isplayLayer::!SetOpacity.
* IDirectFBD''''''isplayLayer::!SetScreenLocation() controls scaling of the plane. Back-End Scaler(BES) is used, for instance for Matrox. It requires hardware support.
* Explicit Front-End Scaler(FES) is not available. Thus, stretched blit to the primary surface should be used.
* To execute a specific graphics operation (e.g. blitting of a surface), the DirectFB driver will access the memory mapped io ports of the graphics hardware to submit the command to the acceleration engine (actual hardware acceleration is done entirely from user space).

==== GFX Card Driver ====

* DirectFB abstracts the video driver through GFX driver.
* Graphic operation is executed through IDirectFBSurface interface. The interface calls appropriate callback routine in gfxcard driver(src/core/gfxcard.c). The callback routine decides whether the video device has hardware acceleration capability or not, and invokes appropriate functions.
* The following is the model used in the core gfxcard driver. Blit, !DrawLine,

DrawRect and similar operations are implemented in this way:

<pre>
void dfb_gfxcard_OPERATION()
{
bool hw == false;
lock();
/* check if acceleration is available, and then acquire */
if (hardware_accel_available(OPERATION) && hardware_accel_acquire(OPERATION)) {
hw == card->funcs.OPERATION();
}
/* if hardware acceleration is not available */
if (!hw) {
gAcquire();
gOPERATION();
gRelease();
}
unlock();
}
</pre>

==== DirectFb benchmarks ====
You can refer 'DirectFB' benchmark on various environment from Benchmark section of [[Evaluate Direct Fb Task Page]]

== References ==

G - Graphics/Video out:
1 Framebuffer
- http://www.kernel.org/ (1) KD26/fb
- http://linuxconsole.sourceforge.net/fbdev/HOWTO/
- http://www.tldp.org/HOWTO/Framebuffer-HOWTO.html
2 DirectFB (uses 1)
- http://www.directfb.org/
- http://www.directfb.org/documentation/DirectFB_overview_V0.2.pdf
3 NanoX
- http://www.microwindows.org/
4 SDL
- http://www.libsdl.org/
5 Gstreamer
- http://www.gstreamer.net/
6 OpenGL (OpenML)
- http://www.opengl.org/
- http://www.khronos.org/opengles/

V – Video in:
1 V4L[2]
- http://www.kernel.org/ (1) KD26/video4linux
- http://bytesex.org/v4l/
2 OpenML
- http://www.khronos.org/openml/
3 LinuxTV (DVB API)
- http://www.linuxtv.org

A – Audio in/out:
1 OSS
- http://www.kernel.org/ (1) KD26/sound/oss
- http://www.4front-tech.com/opensound.html
2 ALSA
- http://www.kernel.org/ (1) KD26/sound/alsa
- http://www.alsa-project.org
3 OpenAL
- http://www.openal.org/

U – Users of AVG:
1 V''''''ideoLan
- http://www.videolan.org
2 Freevo
- http://freevo.sourceforge.net
3 LinuxTV
- http://www.linuxtv.org/
4 MythTV
- http://www.mythtv.org/
5 DVR
- http://dvr.sourceforge.net/html/main.html
6 OpenPVR
- http://www.funktronics.ca/openpvr/
- http://sourceforge.net/projects/openpvr/

O – Other:
1 TV Linux Alliance
- http://www.tvlinuxalliance.com/
2 TV Anytime
- http://www.tv-anytime.org/
3 Digital Home Working Group
- http://www.dhwg.org/
4 B''''''ootSplash
- http://www.BootSplash.org/
5 F''''''reeType
- http://freetype.sourceforge.net/freetype2/
6 ARIB architecture
- http://www.arib.or.jp/english/html/overview/ov/std_b24.html

Note (1) - KD26 refers to the [http://www.kernel.org/pub/linux/kernel/v2.6/ Linux 2.6.X kernel] tree, which has a "Documentation" sub-directory.

== Remaining Issues ==
See Work in progress.

[[Category:MultiMedia]]

Companies

2007-07-16T02:39:30Z

Chris:

Squash Fs

2007-07-16T02:37:45Z

Chris:

== Description ==
"Squash FS" is the name of a compressed read-only filesystem for Linux. There are a number of such file systems available for Linux, including ROMFS, CRAMFS and SquashFS.

== Rationale ==
A compressed file system is interesting in embedded systems for reducing the overall size (in flash) of the Linux system. Squash FS is reported to have better compression capabilities than CRAMFS, which is a very popular

== Resources ==
=== Projects ===
The Squash fs home page is at: [http://squashfs.sourceforge.net/ Squash FS]

=== Specifications ===
There are no specifications on this technology.

== Downloads ==
=== Patch ===
*see the Squash fs [http://sourceforge.net/project/showfiles.php?group_id=63835 download page] for latest patches

=== Utility programs ===
The squashfs file release contains a README, the squashfs patch files, and the squashfs-tools directory (mksquashfs). Please see the INSTALL file for install instructions.

== How To Use ==
See the Squash FS Howto:
*[http://artemio.net/projects/linuxdoc/squashfs online version]
*[[Squash FS Howto]] page (copy of document in this wiki - may be out of date)

== Sample Results ==

Here are brief summaries for 2 large file systems, saved using a variety of file system types.

This information was provided by Phillip Lougher.

=== Ubuntu liveCD compression results ===

<pre>
ext3 uncompressed size 1.4 GB
ISO9660 uncompressed size 1.3 GB
Zisofs compressed size 589.81 MB
Cloop compressed size 471.89 MB
Squashfs2.0 compressed size 448.58 MB
Squashfs2.1 compressed size 448.58 MB
</pre>

=== Damn Small Linux liveCD compression results ===

<pre>
ext3 uncompressed size 126 MB
CRAMFS compressed size 52.19 MB
Squashfs2.0 compressed size 46.52 MB
Squashfs2.1 compressed size 46.52 MB
</pre>

=== File System Performance ===
There is performance data for these file systems on the page SquashFsComparisons.

=== lzma data comparison ===
Here is some information that was posted recently on the squashfsmailing list by Oleg Vdovikin:

<pre>
> # du -s target
> 7836 target
> # ls -l target.*
> -rw-r--r-- 1 root root 2842788 Aug 27 17:54 target.cramfs
> -rwx------ 1 root root 2449408 Jan 26 13:19 target.sqshfs
> -rwx------ 1 root root 2060288 Jan 26 13:21 target.lzmafs
>
> So, lzma for this filesystem gives 84% of original size. For bigger
> filesystem I've got 82%.
</pre>

= Future Work/Action Items =
Here is a list of things that could be worked on for this feature:
*there was a report in August, 2004 of problems with squashfs on PPC. see [http://sourceforge.net/forum/message.php?msg_id=2735613 here] (at bottom of page)
*there was a suggestion to use LZMA compression for version 3.0 of squashfs - see [http://sourceforge.net/forum/forum.php?thread_id=1113639&forum_id=215699 here]

== Notes on compression ==
<pre>
From: John Richard Moser <nigele...@comcast.net>
Date: Wed, 29 Sep 2004 18:20:11 +0200
Subject: Re: Compressed filesystems: Better compression?

Matti Aarnio wrote:
| Compression algorithms are a bit tough to be used in a random access
| smallish blocks environments. In long streams where you can use megabytes
| worth of buffer spaces there is no problem is achieving good performance.
| But do try to do that in an environment where your maximum block size
| is, say: 4 kB, and you have to start afresh at every block boundary.

Yes of course. I've seen the compressed page cache patch do this and
get fair peformance (10-20%), though on double size blocks (8KiB) it
manages almost twice as good (20-50%, averaged around 30% IIRC). Not
great, but not bad.

On compressed filesystems you can work with 64k or 128k blocks.
Somewhere around 32-64k is usually optimal; you're not going to see
great improvements using 1M blocks instead of 512k blocks.

| Whatever algorithms you use, there will always be data sequences that
| are of maximum entropy, and won't compress. Rather they will be
| presented in streams as is with a few bytes long wrappers around
| them.

Yes, an intelligent algorithm decides that if the underlying compression
algorithm used produces no results, it just marks the block as
uncompressed and stores it as such. ZLIB does this if the block gets
bigger. LZMA might not; but higher level intrinsics (block headers)
could handle that easy (as you said).
</pre>

[[Category:File Systems]]

Open Wrt

2007-07-16T02:31:27Z

Chris:

[[Open Wrt]] is a Linux distribution for embedded devices, especially wireless routers.

Instead of trying to create a single, static firmware, [[Open Wrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[Open Wrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[Category:Distributions]]

Mandatory Access Control Comparison

2007-07-16T02:28:56Z

Chris:

Table Of Contents:

This page has information about Mandatory Access Control (MAC) solutions, which is of interest to CE Linux Forum members,
because MAC provide strong access control for CE device which has rich resources to be managed.

== Comparison of MAC solution ==

||<#B0FFB0> '''_''' \
||<#B0FFB0> [http://www.lids.org/ LIDS] \
||<#B0FFB0> [http://tomoyo.sourceforge.jp/ TOMOYO] \
||<#B0FFB0> [http://rsbac.org/ RSBAC] \
||<#B0FFB0> [http://selinux.sourceforge.net/ SELinux] \
{|
|-
| bgcolor="#B0FFB0" | [http://en.opensuse.org/AppArmor App Armor]
|}

|| Security Model \
|| MAC(inode), TPE(1.2),TDE(1.2) \
|| MAC(path) \
|| MAC, RC, ACL, FF, UM, PM, DAZ, JAIL \
|| MAC(label), TE,RBAC,MLC,MCS \
{|
|-
| MAC(path)
|-
| Type
| LSM (2.6), patch (2.4)
| patch
| patch
| LSM
| LSM
|}

|| Current version (2.6) \
|| 2.2.2 for 2.6.14 (LSM) \
|| 1.1.3 for 2.6.11-17 \
|| 1.2.7 for 2.6.16 \
{|
|-
| in mainline
| 2.6.X (LSM)
|}

|| Current version (2.4) \
|| 1.2.2 for 2.4.30 \
|| 1.1.3 for 2.4.20 - 32 \
|| 1.2.7 for 2.4.32 \
{|
|-
| obsolete
| ?
|}

|| Policy learn mode \
|| /lids/lids.ini \
|| CCS=0 /root/security/profile0.txt || /etc/selinux/config \
|| rsbac_softmode \
{|
|-
|
|-
| disable option
| lids=0
|
|
| selinux=0
|
|-
| Policy location
| /etc/lids/
| /root/security/
|
| /etc/selinux
|
|-
| Distributions
|
|
| Hardened Gentoo
| Redhat, Fedora Core, Hardened Gentoo
| Open Suse
|-
| (by 3rd party)
| Fedora core, Debian
| Fedora core, Debian
| Debian
| Suse, Ubuntu
| Slackware
|}

== Benchmark ==
MEN WORKING

Hardware : Sharp Zaurus C860,
CPU :[[XScale]] 400MHz,
Memory : --MB,
OS : Openzaurus 3.5.4.1 + OPIE 1.2

=== Sizing ===

Kerenl 2.6.16 (linux-openzaurus-2.6.16-r40, Static build)
{|
|-
|
| Normal
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
|-
| Kernel size (Image)
| 2487744
| 2554880
| 2541808
| 2974224
| ?
|-
| Kernel size (zImage)
| 1181660
| 1205324
| 1207288
| 1351432
| ?
|-
| image size overhead
| 0
| 67136
| 54064
| 486480
| ?
|-
| policy size
| 0
|-
| memory consumption
| 0
|}

=== Lmbench ===

Processor, Process, Local communication latencies
{|
|-
|
| Normal
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
|-
| null call
| 0.46
| 0.46
| 0.46
|-
| null I/O
| 1.77
| 1.97 (11%)
| 1.77
|-
| stat
| 12.7
| 15.7 (24%)
| 12.8 (1%)
|-
| open/close
| 18.7
| 22.5 (20%)
| 59 (216%)
|-
| select TCP
| 91.3
| 91.6
| 91.3
|-
| sig inst
| 2.89
| 2.83 (-2%)
| 2.84 (-2%)
|-
| sig hndl
| 7.58
| 7.66 (1%)
| 9.25 (22%)
|-
| fork
| 3795
| 3808
| 3757 (-1%)
|-
| execve
| 13000
| 13000
| 15000 (15%)
|-
| sh
| 36000
| 37000 (3%)
| 41000 (14%)
|-
| ctxsw
| 175
| 186.3 (7%)
| 177.2
|-
| pipe
| 356.9
| 375.6 (5%)
| 358.1
|-
| AF_UNIX
| 674
| 718 (7%)
| 723 (7%)
|-
| UDP
| 747.5
| 776.3 (4%)
| 765.1 (2%)
|-
| RPC/UDP
| 969.1
| 1013 (5%)
| 1193 (23%)
|-
| TCP
| 957.3
| 1004 (5%)
| 964.6 (1%)
|-
| RPC/TCP
| 1332
| 1380 (4%)
| 1353 (2%)
|-
| TCP connect
| 2302
| 2379 (3%)
| 2357 (2%)
|-
| 0KB create
| 461
| 605.7 (31%)
| 669.8 (45%)
|-
| 0KB delete
| 232.5
| 267.1 (15%)
| 329.5 (42%)
|-
| 10KB create
| 5128.2
| 5234.6 (2%)
| 5235.6 (2%)
|-
| 10KB delete
| 298.8
| 349.8 (17%)
| 415.1 (39%)
|-
| Mmap latency
| -
| -
| -
|-
| Prot Fault
| 1.72
| 1.71
| 0.61 (-64%)
|-
| Page Fault
| 92
| 92
| 86 (-7%)
|}

=== Unixbench ===
{|
|-
|
| Normal
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
|-
| execl
| 89.3 lps
| 84.6
| 59.5
|-
| file read 1KB
| 53974.0 [[KBps]]
| 52176
| 53505
|-
| file write 1KB
| 328.0 [[KBps]]
| 321
| 376
|-
| file copy 1KB
| 288.0 [[KBps]]
| 199
| 311
|-
| file read 256B
| 34766.0 [[KBps]]
| 33831
| 34742
|-
| file write 256B
| 133.0 [[KBps]]
| 121
| 138
|-
| file copy 256B
| 126.0 [[KBps]]
| 121
| 121
|-
| file read 4KB
| 69148.0 [[KBps]]
| 67961
| 68851
|-
| file write 4KB
| 1417.0 [[KBps]]
| 1417
| 1333
|-
| file copy 4KB
| 1268.0 [[KBps]]
| 1237
| 1249
|-
| pipe
| 112917.5 lps
| 108924
| 112137
|-
| pipe switching
| 2655.4 lps
| 2559.6
| 2700
|-
| process creation
| 272.9 lps
| 367.8
| 276.4
|-
| system call
| 269446.2 lps
| 267748
| 268823.9
|-
| shell scripts (1)
| 82.2 lpm
| 77.6
| 58.6
|-
| shell scripts (8)
| 5.3 lpm
| 5.6
| 5.4
|-
| shell scripts (16)
| 2.0 lpm
| 0
| 2
|}

== Summary ==
{|
|-
|
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
| App Armor
|-
| build (kenrel) (easy:5 - 1:hard)
| 4
| 4
| 3
| 5
| ?
|-
| build (userland) (easy:5 - 1:hard)
| 4
| 4
| 3
| ?
| ?
|-
| image size
| 2%
| 2%
| 15%
| 3%
| ?
|-
| performance
|
|
|
|
| ?
|-
| policy lean mode (good:5 - 1:poor)
| 4
| 5
| ?
| 3
| ?
|-
| symlink
| by wrapper
| support(alias)
|
|
| ?
|-
| filesystem JFFS2
| ok
| ok
|
|
| ok?
|}

== Other resources ==

Access Control Comparison Table
http://gentoo-wiki.com/Access_Control_Comparison_Table

[[Category:Security]]

Security Terms

2007-07-16T02:28:03Z

Chris:

Asynchronous I/O::: I/O where control is returned to the calling program after the I/O process has started, but before the I/O is completed. The I/O transfer runs in parallel with respect to the processor work. The user program continues executing at the same time the I/O operation is executing.

Blocking I/O::: I/O where control is not returned to the calling program until all requested data is transferred. The I/O transfer runs serially with respect to the processor work.

; File system : : The methods and data structures that an operating system uses to keep track of files on a disk or partition; the way the files are organized on the disk. Also used about a partition or disk that is used to store the files or the type of the file system.

Linux Security Modules (LSM)::: A framework to support security systems as loadable Linux modules.

Non-blocking I/O::: I/O where control is returned to the calling program after the I/O process has started, but before the I/O is completed. The I/O transfer runs in parallel with respect to the processor work. The user program continues executing at the same time the I/O operation is executing.

Non-volatile storage::: (NVS, persistent storage, memory) A term describing a storage device whose contents are preserved when its power is off. Storage using magnetic media (e.g. magnetic disks, magnetic tape or bubble memory) is normally non-volatile by nature whereas semiconductor memories (static RAM and especially dynamic RAM) are normally volatile but can be made into non-volatile storage by having a (rechargeable) battery permanently connected.

RAM-based file system::: A file system built on RAM as the storage medium.

; Stack guarding : : A mechanism for protecting the system from buffer overrun ("stack smashing") attacks.

Synchronous I/O::: I/O where control is not returned to the calling program until all requested data is transferred. The I/O transfer runs serially with respect to the processor work.

[[Category:Security]]

Texas Instruments

2007-07-16T02:27:12Z

Chris:

Texas Instruments, Incorporated

headquarters in Dallas, TX USA

http://www.ti.com/

makers of graphing calculators

http://education.ti.com/

and OMAP processors

http://www.omap.com/

[[Category:Companies]]

Source Management Tools

2007-07-16T02:26:12Z

Chris:

Here are some different source management tools commonly used with Linux:

== Overview ==
* David Wheeler has an excellent breakdown of various SCM tools at: http://www.dwheeler.com/essays/scm.html
* IBM has an good overview of available tools at: http://www-128.ibm.com/developerworks/linux/library/l-vercon/
* There is a comparison of several different tools at: http://better-scm.berlios.de/comparison/comparison.html

== Patch Management Tools ==
* diff - to create patches
** use 'man diff' on your local system for information
* [http://wikipedia.org/wiki/Patch_%28Unix%29 patch] - to apply patches
** use 'man patch' on your local system for information
* [[Quilt]] is good for managing a group of patches relative to a single source base.
* diffstat reads a patch file (or standard input) and displays a histogram of the insertions, deletions, and modifications per-file. It is useful for reviewing large, complex patch files. It reads from one or more input files or from standard input. If an input filename ends with .bz2, .Z or .gz, diffstat will read the uncompressed data via a pipe from the corresponding program.
** diffstat is included in most Linux distributions
** [http://invisible-island.net/diffstat/diffstat.html diffstat home page]
** [http://www.die.net/doc/linux/man/man1/diffstat.1.html diffstat man page]
* [[Tim's patch management tools]] - diffinfo and friends - a more verbose diffstat, with splitting, joining and comparing of patches
* See also [[Diff And Patch Tricks]]

== GIT ==
GIT is the source code management tool used by many kernel developers.
* GIT project home page: http://git.or.cz/

[[Category:Development Tools]]

Nor vs Nand

2007-07-14T13:02:41Z

Chris:

There is a good introduction on the differences between NOR and NAND flash at:

http://www.commsdesign.com/design_corner/OEG20031022S0011

Samsung seems to be able to boot off of NAND flash.

[[Category:Flash Memory]]

Nor vs Nand

2007-07-14T13:02:31Z

Chris:

XC9500 XL

2007-07-14T13:02:05Z

Chris:

Xilinx CPLD
The XC9500XL family of [[CPLDs]] provide a high-performance, nonvolatile programmable logic solution comprising cost-optimized silicon, free design tools , and unparalleled support. High performance, low cost, and using the identical design environment as Xilinx [[FPGAs]], XC9500XL [[CPLDs]] provide everything you need for flexible, advanced logic system design.

* [[[Media:xc9500xl.pdf]] datasheet]
* [http://www.xilinx.com/products/silicon_solutions/cplds/xc9500_series/xc9500xl/ Xilinx XC5900XL Product Page]

[[Category:CPLDs]]

Using Jtager

2007-07-14T13:00:27Z

Chris:

== Using JTAGER with the Juicebox ==
=== Introduction ===
JTAGER has not been updated for a while but is a great program. It comes with support for the ARM7TDMI built in but only supports wiggler jtag hardware.

JTAGER is useful for debugging and downloading binary files to the JB. See [[JuiceBox Code Test]] for demo programs.

=== Install ===
Download the tarball from http://jtager.sourceforge.net/

Read the README file for install instructions (./configure && make && make install should do it)

=== Usage ===
This will take you through running the lcd_2 demo on your Juicebox using JTAGER. Note that I am using # for comments but this is not actually valid - it is just to clarify what the command is doing.

<pre>
#see available commands
JTAGER> help
*snip - see your output from this*

#halt the CPU
JTAGER> halt
Requesting HALT target ... [OK]
The target is halted in ARM mode.

#Verify the CPU
JTAGER> idcode
Device ID = 0x1F0F0F0F
bit[0] = 1, always be 1, required by IEEE Std 1149.1
Manufacturer (bit[11:1]): 0x787 - SAMSUNG
Part number (bit[27:12]): 0xF0F0
Version (bit[31:28]) : 0x1

#Copy the lcd_2 demo to memory (you have to hit enter twice)
#be sure to copy the BIN file and not the ELF file
JTAGER> memset --base=0x0c001000 --infile=hacking/juicebox/jb-code/lcd_2.bin
memset: Fill the memory block [0x0C001000, 0x0C0017EB] with the file "hacking/juicebox/jb-code/lcd_2.bin" ...
. [OK]
Total 2028 bytes are written.

#restart the proc at the correct entry point
JTAGER>JTAGER> restart 0x0c001000
Restarting the target processor at 0x0C001000
</pre>

That's it You should now be looking at the LCD demo starting with the text "Juicebox LCD Demo #2" on the screen.

=== What is going on here? ===
Read the lcd_2.dld file from the lcd_2 tarball - this gives a clue as to where to copy the BIN file.

<pre>
/* Memory Definitions */
MEMORY
{
RAM (rw) : ORIGIN = 0x0c001000, LENGTH = 0x00010000
SRAM (rw) : ORIGIN = 0x010001000, LENGTH = 0x1000

}
</pre>

The Juicebox memory (RAM) starts at 0x0c001000 - therefore that is where we copy the BIN to.

Now that you can copy binaries to your juicebox and run them it's time to start writing your own code. See [[JuiceBox Software Development]] for help.

[[Category:Development Tools]]

Open Embedded

2007-07-14T12:59:26Z

Chris:

Table Of Contents:

== Description ==
[[Open Embedded]] is the name of a project which seeks to provide embedded linux distributions, built from scratch.

=== Rationale ===
While the distribution used for most embedded systems has many custom elements, there are significant portions
of the software on consumer electronics products which could be standardized and utilized from the same source.

Open Embedded may represent the closest thing there is to a de-facto standard embedded distribution of Linux.

== Resources ==
=== Projects ===
http://www.openembedded.org/

=== Specifications ===
There are no CELF specifications related to Open Embedded.

== Downloads ==
=== Patch ===
- [Patch for 2.6.xx is *here* (often, the [[Patch Archive]])]

=== Utility programs ===
[other programs, user-space, test, etc. related to this technology]

== How To Use ==
See the Open Embedded wiki, at:
http://www.openembedded.org/cgi-bin/moin.cgi

== How to validate ==
[put references to test plans, scripts, methods, etc. here]

== Sample Results ==
=== Case Study 1 ===
=== Case Study 2 ===

== Future Work/Action Items ==
Here is a list of things that could be worked on for this feature:
-
I met with Phil Blundell and Tim Ansell at Linuxconf Australia and discussed
some possible ways the forum might sponsor Open Embedded.
Here are some ideas:
- create an installer, which automatically copes with weird distros
(I had problems getting OE installed, but then I use Mandrake)
- it should validate that all required packages are installed,
and if not present, install them
- OE has a somewhat long list of pre-requisites
- sponsor a conference/retreat of the core OE developers
- do nightly builds (and testing?) of various full-distro recipes
- do improvements to bitbake to solve the memory/performance
problems.
- need to identify if these are python issues (dependency graph
memory consumption seems to be)
- try to make bitbake less fragile
- have a way to freeze/sign a recipe collection for a known-good
distro?
- canonicalize workarounds to issues caused by autoconf badness
(inability to support cross-building)

Tim and Phil both said that contract money might not influence their
contribution levels (they are maxed out now). Changing their
focus with money might be detrimental (it might just take the fun
out of it.) So, outside contractors seems like the better way to
go for now.

[[Category:Development Tools]]

DaVinci U-boot 1.0

2007-07-14T12:58:48Z

Chris:

<Just a stub>

Most of what would be here is now quite well documented with the DVFlasher readme.

For those who do not know, DVFlasher is the program which allows uboot images to be installed on the DaVinci EVM's flash via a serial connection.

[[Category:Boot Loaders]]

M5900

2007-07-14T12:57:33Z

Chris:

[[Image:m5900.jpg]]
* http://www.amltd.com/m5900.asp
* Linux Kernel 2.6.16
* uClibc based root file system
* Samsung S3C2410
* 32mb ram
* 16mb Nor Flash
* 160x160 stn grey scale
* 55-key keyboard
* intergrated barcode scanner
* rs-232 interface
* usb slave interface
* 7.2v 2200mAh battery

[[Image:m5920.jpg]]

[[Category:Products]]

Qplus Target Builder

2007-07-14T12:56:27Z

Chris:

Table Of Contents:

== Description ==
Embedded Linux System Build Toolkit: Target Builder

Target Builder is a convenient system configuration tool for embedded linux system developer

== Resources ==
=== Projects ===

=== Specifications ===
* CELF patch included BSP
* Linux kernel/application/target configuration
* Deploy made root file system image
* Fine-grain control of system; file-list, compile options, and more...
* Kconfig based configuration system
** Automatic dependency checking
** Linux kernel 2.6.x support
* various deployment methods support
** CD installer, NFS, ETC
* Eclipse platform
** project wizard and management system
* Licensed by GPL
* Included CELF patches currently 2.6.9

=== Screen Shot ===

[[Image:timerresolution.jpg]]

== Downloads ==

'''[ftp://qplus.or.kr/pub/qplus/V2.0/qplus_dev_suite_2.0.2.iso Target builder & ESTO Develop Suite install CD image]'''

'''[ftp://qplus.or.kr/pub/qplus/V2.0/qplus_ce_epia_bsp_1.0.1.iso VIA epia board BSP install CD image]'''

'''[ftp://qplus.or.kr/pub/qplus/V2.0/qplus_esto_installation_guide_v2.0_050401.pdf Installation & user guide document(korean version)]'''

'''''[English guide document (comming soon)]'''''

== How To Document ==
We will document as soon as possible

=== How to make BSP ===

comming soon ;)

== Status ==
* Status: [implemented]

* Architecture Support:
*** i386: VIA epia board
*** ARM:
*** PPC:
*** MIPS:
*** SH:

=== VIA epia board BSP Package list ===

==== Kernel / Standard library ====
{|
|-
| align="center" | item
| align="center" | package
| align="center" | version
| align="center" | note
|-
| Kernel
| kernel
| 2.6.6-epia1
| real time patch, board support patch
|-
| Cross Tool Chain
| glibc
| 2.3.2
| .
|-
| gcc
| 3.2.2
| .
|-
| binutils
| 2.13.2.1
| .
|-
| Glibc
| 2.3.2
| .
|}

==== Utilities ====
{|
|-
| align="center" | item
| align="center" | package
| align="center" | version
| align="center" | note
|-
| bootloader
| lilo
| 21.4.4
| .
|-
| Shell
| busybox
| 0.60.5
| .
|-
| bash
| 2.4
| .
|-
| init
| initscripts
| 0.0.1
| inittab file and /etc/init.d scripts
|-
| libsn
| 0.5
| startup notification protocol
|-
| startup-notification
| 0.6
| startup notification protocol
|-
| moduleinittools
| 3.1
| .
|-
| config
| setup
| 2.4.7
| e.g. passwd, group, profile
|-
| login
| tinylogin
| 0.80
| addgroup, adduser, delgroup, deluser, login, su, sulogin
|-
| Archive
| tar
| 1.13.25
| .
|-
| unzip
| 5.50
| .
|-
| file
| bzip2
| 1.0.2
| .
|-
| fileutils
| 4.1
| .
|-
| device
| skellinux
| 0.0.1
| Device files for linux system
|-
| pciutils
| 2.1.8
| .
|-
| setserial
| 2.17
| .
|-
| telnet
| 0.17
| telnet client and server
|-
| ftp
| 0.17
| ftp client
|-
| iproute
| 2.4.7
| .
|-
| devfiles
| 0.0.1
| .
|-
| network
| rsync
| 2.4.6
| .
|-
| linc
| 1.0.1
| .
|-
| Daemon
| wuftp
| 2.7.0
| ftp server
|-
| tcpwrappers
| 7.6
| .
|-
| xinetd
| 2.1.8.9pre14
| .
|-
| nfs
| 0.3.3
| .
|-
| acpid
| 1.0.4
| .
|-
| Debugger
| stace
| 4.4.95
| .
|-
| targetagent
| 1.0
| .
|}

==== Graphic library / Window system ====
{|
|-
| item
| package
| version
| note
|-
| Graphic library
| glib
| 2.2.2
| .
|-
| gtk
| 2.2.2
| .
|-
| atk
| 1.2.4
| .
|-
| pango
| 1.2.5
| .
|-
| freetype
| 2.1.2
| .
|-
| fontconfig
| 2.2.2
| .
|-
| libjpeg
| 6b
| .
|-
| libpng
| 1.2.8
| .
|-
| libtiff
| 3.5.5
| .
|-
| ncurses
| 5.3
| .
|-
| cairo
| 0.2.0
| vector graphic library
|-
| gnome-mime-data
| 2.4.1
| .
|-
| gpe
| 0.9
| .
|-
| libgcrypt
| 1.2.1
| Cryptographic library
|-
| renderext
| 0.8
| .
|-
| xrender
| 0.8.3
| required for pango
|-
| xft
| 2.1.2
| required for pango
|-
| libpixman
| 0.1.2
| .
|-
| libgpg-error
| 1.0
| .
|-
| dbus
| 0.11.91
| .
|-
| Window system
| tinyX
| 4.2.0
| .
|-
| matchbox
| 0.9
| .
|-
| libmatchbox
| 1.6
| .
|-
| matchboxcommon
| 0.9.1
| .
|}

==== ETC libraries ====
{|
|-
| align="center" | item
| align="center" | package
| align="center" | version
| align="center" | note
|-
|
| expat
| 1.95.2
| C library for parsing XML
|-
| libcpp
| 6.1.2
| [[LIbstdc]]++ shared library
|-
| openssl
| 0.9.7a
| .
|-
| zlib
| 1.1.4
| .
|-
| libIDL
| 0.8.0
| for firefox
|-
| libtermcap
| 2.0.8
| .
|-
| libmimedir
| 1.2.1
| FR2425 parsing library
|-
| gmp
| 4.1.4
| GNU MP Bignum library
|-
| openbex
| 1.0.1
| Object exchange protocol
|-
| readline
| 4.3
| .
|-
| sqlite
| 2.8.16
| .
|}

==== Web browser and Media player ====
{|
|-
| align="center" | item
| align="center" | package
| align="center" | version
| align="center" | note
|-
| .
| firefox
| 1.0.1
| .
|-
| .
| mplayer
| 1.0
| .
|}

== Future Work/Action Items ==

- BSP authoring tool
- to provide fast and easy BSP developing environment
- support various architectures and boards
- Xscale, SH, OMAP, ETC
- more powerful packaging system
- support remote upgrade
- expand provided packages
- Packaging various CELF [[WGs]] products
- ulibc support

== Q&A ==
any question? ;)

[[Category:Development Tools]]

Pixter Multimedia Expansion Slot

2007-07-14T12:50:52Z

Chris:

<pre>

* indicates verified by software and hardware
+ indicates verified by hardware only

</pre>

{|
|-
| *1
| A0
| *2
| D0
|-
| *3
| A1
| *4
| D1
|-
| *5
| A2
| *6
| D2
|-
| *7
| A3
| *8
| D3
|-
| *9
| A4
| *10
| D4
|-
| *11
| A5
| *12
| D5
|-
| *13
| A6
| *14
| D6
|-
| *15
| A7
| *16
| D7
|-
| *17
| A8
| *18
| D8
|-
| *19
| A9
| *20
| D9
|-
| *21
| A10
| *22
| D10
|-
| *23
| A11
| *24
| D11
|-
| *25
| A12
| *26
| D12
|-
| *27
| A13
| *28
| D13
|-
| *29
| A14
| *30
| D14
|-
| *31
| A15
| *32
| D15
|-
| *33
| A16
| *34
| PA5
|-
| *35
| A17
| *36
| PA4
|-
| *37
| A18
| +38
| nCS2
|-
| *39
| A19
| +40
| nCS3
|-
| *41
| A20
| *42
| nOE
|-
| *43
| A21
| *44
| nWE
|-
| *45
| A22
| *46
| Vdd
|-
| *47
| A23
| *48
| PA0/INT3/UARTTX2
|-
| +49
| PA3
| *50
| PA1/INT2/UARTRX2
|-
| *51
| PB6/UARTRX1/INT0
| +52
| PA2
|-
| *53
| PB7/UARTTX1/INT1
| 54
| ????
|-
| *55
| PB0/nDACK/nUARTCTSO
| *56
| Vss
|-
| *57
| PB1/DREQ/nUARTRTS0
| *58
| Vdd
|-
| *59
| Vss
| 60
| ????
|}

* PB6 and PB7 buttons are connected to PG0 and PG1 GPIO's
* PB8 seems to be connected to PH7 GPIO

[[Category:Pixter]]

Pixter Multimedia Expansion Cartridge

2007-07-14T12:50:45Z

Chris:

Here's a quick and dirty table describing a pixter multimedia game cartridge that didnt use [[Chip On Board]] technology. Hopefully I (or someone else) will clean it up later.

[[Image:pixtercart-composite.jpg]]

-=- NET/FUNCTION LIST FOR PIXTER MULTIMEDIA GAME CARTRIDGE -=-

'''NAND MEMORY ('rom'): Matrix Memory 11247-01'''
http://www.matrixsemi.com/products-and-applications/documents/DS0043DMTSOPR1.11_062405.pdf
Note that the PDF is a different part number. It was chosen because its the same product line and likely has the same pin interface. This is the same IC used in the [[JuiceBox]].

{|
|-
| net1
| net2
| function
| flash function
| wiki pin
|-
| crt:2
| rom:20
| DATA0
| IO1
| 30
|-
| crt:4
| rom:21
| DATA1
| IO2
| 29
|-
| crt:6
| rom:22
| DATA2
| IO3
| 28
|-
| crt:8
| rom:23
| DATA3
| IO4
| 27
|-
| crt:10
| rom:27
| DATA4
| IO5
| 26
|-
| crt:12
| rom:28
| DATA5
| IO6
| 25
|-
| crt:14
| rom:29
| DATA6
| IO7
| 24
|-
| crt:16
| rom:30
| DATA7
| IO8
| 23
|}

'''Logic: Hitachi 74HC32D ('H32') quad 2-input OR gate'''

(I cheated and used a local copy of a Fairchild Semi DM74LS32 pdf)

{|
|-
| net1
| net2
| function
| flash function
| wiki pin
|-
| crt:40
| H32:1
| 1a
| nOE
| 10
|-
| crt:40
| H32:4
| 2a
| nOE
| 10
|-
| crt:42
| H32:2
| 1b
| nCS3
| 11
|-
| crt:44
| H32:5
| 2b
| nCS2
| 12
|-
| H32:3
| rom:5
| 1y
| RE#
| [internal net]
|-
| H32:6
| rom:14
| 2y
| WE#
| [internal net]
|}

'''More rom / misc lines'''

{|
|-
| net1
| net2
| function
| flash function
| wiki pin
|-
| crt:51
| rom:12
| -
| CLE
| *
|-
| crt:53
| rom:13
| -
| ALE
| *
|-
| crt:56
| crt:58
| -
| -
| *
|-
| crt:57
| rom:3
| -
| R/B#
| *
|-
| crt:58
| crt:56
| vcc
| -
| *
|-
| crt:59
| GND
| GND
| -
| *
|}

''* I'm honestly confused about these; [[prpplague]] pinned the [[Pixter Expansion Slot]] without any knowledge for pin1 from the hardware, and had to guess pin numbers.''

Keys:
* crt Cartridge port on the pixter MM (numbered odd pins on front; even pints on back as determined by cart PCB)
* rom ROM pin (u-shaped numbering pattern as normal for DIP ic's)
* H32 7432 pin (u-shaped numbering pattern as normal for DIP IC's)`

<hr />

[[Category:Pixter]]

Pixter Multimedia Developer Board

2007-07-14T12:50:36Z

Chris:

[[Image:devboard.jpg]]

[[Category:Pixter]]

Pixter Multimedia

2007-07-14T12:50:30Z

Chris:

[[Image:pixter-mm.jpg]]

Items of interest inside the device:
* Sharp [[LH79524]] CPU
* Two IC42S16100-7T SDRAM [[ICs]] (2MB each, 4MB total) [[http://www.issi.com/pdf/42S16100.pdf datasheet]]
* TLV320DAC26 audio [[http://www-s.ti.com/sc/ds/tlv320dac26.pdf datasheet]]
* OTP flash [[Chip On Board]] IC
* SPI eeprom [[Chip On Board]] IC (still collecting information on this)
* Audio [[Chip On Board]] IC which connects to the DAC26's microphone input (still collecting information on this)
* Well-labeled [[PixterMultimediaLCD]] port
* 4-wire touch-screen
* Silkcreen above largest [[Chip On Board]] reads "PT1543A-BGA-42FC 2005/04/30 REC 4.2B"
* [[Pixter Multimedia Expansion Slot]]
* [[Pixter Multimedia Expansion Cartridge]]
* [[Pixter Multimedia Developer Board]]
* [[PixterMultimediaJTAG]]

PCB Pads:

Primary side:
* TXD0, RXD0 these are incorrectly label on the pcb, they are actually UARTTXD1 and UARTRXD1
* CTS0, RTS0 (apparently extended to cartridge port)
* L16 (nCS0 PM0)
* A4 (PH5/ETHERTX1 I/O General Purpose I/O Signals -- Port H5; multiplexed with Ethernet Transmit Channel 1)

USB Pins:
* A16 USBDN I/O USB Data Negative (Differential Pair output, single ended and Differential pair input)
* A15 USBDP I/O USB Data Positive (Differential Pair output, single ended and Differential pair input)

Secondary side:
* Test1
* Vss
* Test2
* CS1 bridge (SMT pads for 0-ohm resistor with a line between them) opposite the big CoB blob
* M4 (PB4/SSPRX/I2SRXD/UARTRX0/UARTIRRX0) Port B4; multiplexed with SSP Data In, I2S Data In, UART0 Serial Data In, and UART0 Infrared Data In
* 1V8 (most likely 1.8v for the cpu core)

<hr />

[[Category:Pixter]]

Pixter Expansion Slot

2007-07-14T12:50:12Z

Chris:

The Pixter expansion slot is a 60 pin double sided card edge connector. the pads are .035" wide, with a .015" gap between pads, and a total of .050" center-to-center of the pads. the pcb is .047" thick which is a somewhat non-standard thickness. most pcb board houses with manufactor either .031 or .062 for their express and reduced cost production. there are a few production houses that will do the .047 for no additional cost, but only do them on a specific day of the week. Pin 60 is tied to the control(on/off) line of the S-1131 ( [[Media:PixterChipList/S1131.pdf]] ) voltage regulator which allows the external cart to power the unit on and off. By using a [[Pixter Dev Cart]], all the following pins can be used to develop projects:

{|
|-
| 1
| A0
| 2
| D0
|-
| 3
| A1
| 4
| D1
|-
| 5
| A2
| 6
| D2
|-
| 7
| A3
| 8
| D3
|-
| 9
| A4
| 10
| D4
|-
| 11
| A5
| 12
| D5
|-
| 13
| A6
| 14
| D6
|-
| 15
| A7
| 16
| D7
|-
| 17
| A8
| 18
| D8
|-
| 19
| A9
| 20
| D9
|-
| 21
| A10
| 22
| D10
|-
| 23
| A11
| 24
| D11
|-
| 25
| A12
| 26
| D12
|-
| 27
| A13
| 28
| D13
|-
| 29
| A14
| 30
| D14
|-
| 31
| A15
| 32
| D15
|-
| 33
| A16
| 34
| PE1/UARTTX2
|-
| 35
| A17
| 36
| PE0/UARTRX2
|-
| 37
| A18
| 38
| nCS2
|-
| 39
| A19
| 40
| nCS3
|-
| 41
| A20
| 42
| nOE
|-
| 43
| A21
| 44
| nWE
|-
| 45
| A22
| 46
| Vdd
|-
| 47
| A23
| 48
| PE4/SSPTX
|-
| 49
| PD2/INT2
| 50
| PE3/UARTTX0
|-
| 51
| PD4/INT4/UARTRX1
| 52
| PF6
|-
| 53
| PD3/INT3/UARTTX1
| 54
| PF4
|-
| 55
| PD5/INT5/DACK
| 56
| Vss
|-
| 57
| PD6/INT6/DREQ
| 58
| Vdd
|-
| 59
| Vss
| 60
| power control
|}

<hr />

[[Category:Pixter]]

Category:Pixter

2007-07-14T12:49:09Z

Chris:

The Pixter is like a personal digital assistant (PDA) for kids. But instead of storing boring appointments and phone numbers, they get to draw, do puzzles, and learn a little, too.

Pixter Dev Cart

2007-07-14T12:48:39Z

Chris:

a breakout board designed to provide access to all of the signals on the [[Pixter Expansion Slot]]. the headers are on .1" spacing to allow for use of off-the-shelf prototyping boards and parts.

(shown in double size to make viewing easier, red is the top layer , and blue is the bottom layer)
[[Image:pixterdevcart.jpg]]

[[Category:Pixter]]

Pixter Dev Board

2007-07-14T12:48:31Z

Chris:

This is a Pixter taken apart and placed on a board for development. Currently this includes just the basics of touchscreen interface, power, calibrate button(GPIO), audio (PWM), and [[JTAG]]. On the todolist will be a duplication of the i/o pins (using a [[Pixter Dev Cart]]) available on the [[Pixter Expansion Slot]] which will give rise to the addition of items such as [[Pixter MMC|mmc interface]], 10baseT nic, and rs-232 interfaces.

[[Image:pixdev.jpg]]

the opposite side of the main pixter board has a pair of solder pads which appear to be for a 0 ohm resistor. the pads have a pcb trace between the pads. this pad pair is stenciled "NCS0", which is the chip select for the onboard ROM. by cutting the trace between the pads the onboard ROM can be disabled. might be possible to find an unused or duplicate pin on the [[Pixter Expansion Slot]] that can be replaced with the NCS0 line.

there are several other unidentified three pad areas with traces between two of the pads:

P100
P101
P102
P103

as well as one single pair marked "option"

[[Category:Pixter]]

Pixter Chip List

2007-07-14T12:48:22Z

Chris:

The Pixter main board consists of the following chips:

[[Image:mainboard.jpg]]

* [[LH75411| Sharp Blue Streak LH75411]]
* Seiko S-1131 Low Dropout CMOS Voltage Regulator [[Media:S1131.pdf]]
* Cypress CY62127 64K x 16 Static RAM [[Media:CY62127.pdf]]
* SL386D Low Voltage Audio Power AMP [[Media:SL386D.pdf]]
* MC34063 Step-Up/Step-Down Inverting Switch Regulator [[Media:MC34063A-D.pdf]]
* LM324 Quad Operational Amplifier [[Media:LM324.pdf]]
* [[Chip On Board]] Audio IC
* [[Chip On Board]] ROM

LCD is a VDS VG-T161658 no info

some of the cartridges are also known to use:
* SST 39VF400A 256K x 16-Bit Multi-Purpose Flash chip [[Media:SST39VF400.pdf]]

<hr />

[[Category:Pixter]]

Pixter Camera

2007-07-14T12:48:11Z

Chris:

The Pixter Camera is an add on cartridge for the Pixter , this is probably the best cart to use for development since the cart is screwed together (others have the plastic cases bonded together making it difficult to open without damaging the case), has almost all the pins for the external connector used, and has plenty of room for a custom pcb. the main camera board also includes a ccd imager board, plus two Cypress CY62127 64K x 16 Static RAM chips ( [[Media:PixterChipList/CY62127.pdf]] ) and two SST 39VF400A 256K x 16-Bit Multi-Purpose Flash chips ( [[Media:PixterChipList/SST39VF400.pdf]] ).

retail cost for the pixter camera is around $30.00

[[Image:pixtercamera.jpg]]

[[Category:Pixter]]

PixterMultimediaLCD

2007-07-14T12:48:00Z

Chris:

* Custom Sharp LQ038B3DD01
* 3.8" square
* TFT
* 160 x 160
* 8-Bit, 256 colors
* single panel
* 4-wire bonded touch screen

{|
|-
| Register
| Value
|-
| 0xFFFF4000
| 0x0A080824
|-
| 0xFFFF4004
| 0x0505009F
|-
| 0xFFFF4008
| 0x00A13000
|-
| 0xFFFF401C
| 0x00000827
|}

* [http://www.sharpsma.com/Page.aspx/americas/en/part/LQ030B7DD01/ Similiar Sharp LCD 320x320]
* [[[Media:lq030b7dd01.pdf]] LQ030B7DD01 Datasheet]

major difference between the the LQ030B7DD01 and the LQ038B3DD01 is the that the lq038 is a 3.8" and the lq030 is a 3.0" , the only other obvious difference is the resolution, the LQ030B7DD01 is 320x320 , and the LQ038B3DD01 is 160x160. from the numbering i can only assume that sharp uses the B7 and B3 to indicate the resultion.

if anyone has a document describing the numbering scheme Sharp uses for their lcds please post

LQ-XXX-ABCDEF

XXX is the screen size in inches
examples:
{|
|-
| 030
| 3.0"
|-
| 031
| 3.1"
|-
| 035
| 3.5"
|-
| 036
| 3.6"
|-
| 038
| 3.8"
|-
| 039
| 3.9"
|}

A is the screen format

{|
|-
| B
| Square
|-
| Q
| Quarter VGA
|-
| V
| VGA
|-
| S
| SVGA
|-
| X
| XGA
|-
| T
| 16:9
|}

(sloppy edit)

Breakthrough jbevren managed to switch the lcd into 16bpp mode and upload a raster image to the lcd. The lcd seems to be pretty good qualty too.
http://jbevren.net/pixter/

More documentation next week :)

[[Category:Pixter]]

PixterMultimediaJTAG

2007-07-14T12:47:49Z

Chris:

JTAG Pins:
* D2 nTRST I JTAG Test Reset Input
* P4 TMS I JTAG Test Mode Select Input
* T3 TCK I JTAG Test Clock Input
* T1 TDI I JTAG Test Serial Data Input
* P3 TDO O JTAG Test Data Serial Output
* TEST1 ARM ICE debug mode

* to place the LH79524 into ARM ICE debug mode you will need to connect test1 via a 4.7K Ohm resistor to ground

[[Image:pixter-mm-jtag.jpg]]

[[Category:Pixter]]

Pixter

2007-07-14T12:47:14Z

Chris:

(picture from [[http://www.amazon.com/exec/obidos/tg/detail/-/B0000AL9XS/102-9169933-0758560?v=glance&s=toys&n=507846&vi=pictures&img=14#more-pictures amazon]] where you can [[http://www.amazon.com/exec/obidos/tg/detail/-/B0000AL9XS/qid=1104437061/sr=2-3/ref=sr_2_3/104-3795122-0638312 order]] it for $79.99)
[[Image:Pixter.jpg]]

[[Image:internals.jpg]]

The Pixter is like a personal digital assistant (PDA) for kids. But instead of storing boring appointments and phone numbers, they get to draw, do puzzles, and learn a little, too. The Pixter is about the size of a small book, and has a pretty solid weight to it. It's made out of brightly colored and durable plastic. The main action of this toy is drawing with an attached stylus. The Color Pixter offers much better graphics then the black and white version, which comes in handy with activities like Paint-by-Numbers and Connect-the-Dots. You can draw a picture free form, or you can use one of the starter backgrounds. There are tool buttons, like on a PDA, that give you access to fun stamps, special effects, and the eraser button. You can also save your creation in the Pixter's memory. There are some boppy tunes playing along with all this creative activity, but luckily for parents, there's also a jack for headphones and a volume adjuster. The [[Pixter Expansion Slot]] on top of the Pixter accepts ROM-based expansion cards that contain additional software and games. Requires 4 'AA' batteries. (Not included.)

The [[LH75411]] controller was developed to be a perfect fit to the Pixter's hardware and memory needs. Based on a 70-MHz [[ARM7TDMI]] core, the chip includes color LCD controller circuitry; a 10-bit, eight-channel A/D converter, an integral touchscreen controller; and the usual assortment of counter/timers, programmed I/O pins and SRAM. Pivotal to the design were the the 32 kbytes of SRAM, which make it possible to execute the Pixter's algorithms locally, and outputs that can be configured to implement a 12-bit pulse-width-modulated audio output. The addition of an inexpensive external capacitor gave the Pixter the functionality of a moderate-quality audio D/A converter.

There are several projects in the works to make an external cartridge to boot a small [[EmbeddedOS]].
conversaion on hacking the Pixter can be found on irc.freenode.net #pixterdev and #elinux

* [[Pixter Chip List]]
* [[Pixter Expansion Slot]]
* [[RMS100]] - similar hardware
* [[Pixter Dev Board]]
* [[PixterMMC]]
* [[Pixter Camera]]
* [[Pixter Dev Cart]]

<hr />

[[Category:Pixter]]

Category:Linux Tiny

2007-07-14T12:45:15Z

Chris:

The linux-tiny patchset is a series of patches against the 2.6 mainline Linux kernel to reduce its memory and disk footprint, as well as to add features to aid working on small systems.

Linux Tiny

2007-07-14T12:44:39Z

Chris:

== Introduction ==
The linux-tiny patchset is a series of patches against the 2.6 mainline Linux kernel to reduce its memory
and disk footprint, as well as to add features to aid working on small systems. Target users are
developers of embedded system and users of small or legacy machines such as 386s and handhelds.

== Resources ==
* Project home page: [http://www.selenic.com/tiny-about/ Linux Tiny]
* Project mailing list: [http://selenic.com/mailman/listinfo/linux-tiny Mailing List]
* A Linux Weekly News article about the project is at: [http://lwn.net/Articles/63516/ LWN Article]
* [[Image:Alert.gif]] - [http://tree.celinuxforum.org/CelfPubWiki/TechConference2005Docs?action=AttachFile&do=get&target=linux-tiny.pdf Linux-tiny Presentation] by Matt Mackall, delivered at CELF's Technical Conference in 2005.

== 2.6.16.19 Downloads ==
Linux-tiny seems not to have been maintained after kernel version 2.6.14. I've made my own broken-out patch set for 2.6.16.19.

See:
* [[Media:2.6.16.19-tiny1-broken-out.tar.bz2|2.6.16.19-tiny1-broken-out]]
* and some porting notes: [[Media:linuxtinyNOTES.txt|notes]]

== Original Announcements and e-mail ==
The original (Dec 11, 2003) announcement about the patchset, to the kernel mailing list, is available here:
* [http://lwn.net/Articles/62858/ Announcement]

Here are some other announcements from Matt Mackall to LKML:
*[http://www.ussg.iu.edu/hypermail/linux/kernel/0312.3/0454.html 2.6.0-tiny1 Dec 27, 2003]
*[http://www.ussg.iu.edu/hypermail/linux/kernel/0401.0/0403.html 2.6.1-rc1-tin1 Jan 2, 2004]
*[http://www.ussg.iu.edu/hypermail/linux/kernel/0401.0/1256.html 2.6.1-rc1-tiny2 Jan 6, 2004]

Recent discussion thread on lkml is summarized at: [http://kt.zork.net/kernel-traffic/latest.html#6 LKML Thread Summary]
The thread is available at [http://www.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=19Kuz-872-3%40gated-at.bofh.it&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D19Kuz-872-3%2540gated-at.bofh.it here]

Note that currently, the smallest kernel that is reported in this thread is 197K compressed.

== Download ==
=== Last release ===
A recent Linux-tiny patchset release is available here: [[Media:tiny-quilt-2.6.22-rc7-1.tar.gz]]

=== Installation Instructions ===
To apply the above patches, you need the referenced kernel (2.6.22-rc7) and quilt.
Follow these steps:
* wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.21.tar.bz2
* tar -xjf linux-2.6.21.tar.bz2
* wget http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.22-rc7.bz2
* bunzip2 patch-2.6.22-rc7.bz2
* wget http://elinux.org/images/6/6d/Tiny-quilt-2.6.22-rc7-1.tar.gz
* cd linux-2.6.21
* patch -p1 <../patch-2.6.22-rc7
* tar -xzf ../Tiny-quilt-2.6.22-rc7-1.tar.gz
* quilt push -a

=== Auxiliary tools ===
Here is a short shell script for making a tiny-quilt release: [[Media:release-tiny]]

=== Older releases ===
An older Linux-tiny patchset can be downloaded from: [http://selenic.com/tiny/ Linux Tiny Patchset]

== Test Project and Results ==
The CELF System Size working group has worked extensively with the Linux-tiny patch set. There is a script to produce a report of size reductions for the individual patches
in the patchset, and results from various vendors about their use of Linux-tiny. See [[Linux Tiny Test Project]]

There are some miscellaneous usage notes at: [[Linux Tiny Notes]]

[[Category: Linux Tiny]]

Linux Tiny Kernel Size Script

2007-07-14T12:44:29Z

Chris:

== Script ==
Linux Tiny Test Project's Step1 script updated as on 21 Mar 2005:

[[Image:linux_tiny_step1_210305.sh]]

Readme file for usage of linux_tiny_step1_210305.sh script:

[[Image:README.txt]]

Linux Tiny Test Project's Step1 script updated as on 09 Mar 2005:

[[Image:linux_tiny_step1_090305.sh]]

Readme file for usage of linux_tiny_step1_090305.sh script:

[[Image:README.txt]]

Example:

Sample INPUTDIR for 'linux_tiny_step1_090305.sh' script:

[[Image:indir_090305.tar]]

The above tar file contain the following files:

#indir/README
#indir/varlist
#indir/baseline_config

Sample RESULTDIR generated by 'linux_tiny_step1_090305.sh' script:

[[Image:results_090305.tar]]

The above tar file contain the following files:

#res/size_results
#res/CONFIG_MODULES.config.patch
#res/CONFIG_KMOD.config.patch

Note: The celinux-040503 release kernel soruce tree used for the above sample testing.

#[[Image:minutes.Mvista.txt]]

[[Category: Linux Tiny]]

Linux Tiny Notes

2007-07-14T12:44:21Z

Chris:

Here are some miscellaneous notes on using Linux tiny. I wrote this up really quickly while I was
integrating Linux-tiny into a 2.6.11 kernel and doing some size testing.

I'm providing these raw notes so that others might benefit from my experience.

== Patch Notes ==
Here are some notes on individual linux-tiny sub-patches:

== devlist.patch ==
* replaces device allocation code, don't know size impact, is NOT conditional
** maybe should add, but don't know - looks dangerous

== core-small.patch - CONFIG_CORE_SMALL ==
Add CONFIG_CORE_SMALL Kconfig option

=== CONFIG_CORE_SMALL patches ===
These are hash table and data structure static size adjustments
* pid-max.patch
* user-hash.patch
* futex-queues.patch
* tvec_bases.patch
* con_buf.patch

== config-net-small.patch ==
Add CONFIG_NET_SMALL Kconfig option

=== CONFIG_NET_SMALL patches ===
These tune some net-related data sizes
* cache_defer_hash.patch
* unix_socket_table.patch
* inet_protos.patch
* flow-cache-small.patch

== Miscellanoues patches ==
* small-8023.patch - what does this do?
* tg3-oops.patch - what does this do?

== *inline patches ==
* just make big routines not inline (unconditionally)
** Seems pretty safe to me.

== 06-crypto-sleep.patch ==
* looks scary - not immediately obvious from patch how it saves size.

== # measurement bits ==
Looks like very harmless stuff to instrument kernel for mem debugging, and
give tools for parsing stuff.

* kmalloc-accounting.patch - keep track of kmallocs
* audit-bootmem - print out all bootmem allocations
* bloat-o-meter.patch - provides bloat-o-meter program to compare two kernel binary images
**This script shows the size difference on a symbol-by-symbol basis between two binaries (sorted by the amount of difference)

* deprecate-inline.patch - mark inlines as deprecated so compiler emits warnings
**Note that it provides count-inlines program to parse compiler output and report size of inlines.
* func-size.patch - use information about inlines to calculate function sizes (script is very similar to count-inlines program)

== kill-printk.patch ==
* is single biggest reducer of kernel size, doesn't seem to work with serial console!!
** CONFIG_PRINTK

== nobug.patch ==
Allow elimination of BUG code, which expands with file and line strings.
There are 1776 BUG() references in the 2.6.11 kernel. There are 1930 BUG_ON(xxx) references in the kernel.
* uses CONFIG_BUG

== nopanic.patch ==
too dangerous to turn off panic, not used.

== no-elf-core.patch ==
Allow disabling of ELF core dumps
* CONFIG_ELF_CORE

== no-kcore.patch ==
Allow disabling of /proc/kcore, is x86-specific
* uses CONFIG_PROC_KCORE

== no-aio.patch ==
Allow disabling of Posix async IO
* uses CONFIG_AIO

== no-xattr.patch ==
Allow disabling of xattr syscalls
* uses CONFIG_XATTR

== fslock.patch ==
Allow disabling of file locking syscalls
* uses CONFIG_FILE_LOCKING

== direct-io-core.patch ==
Allow disabling of direct IO support
* uses CONFIG_DIRECTIO

== Changes in number of in-kernel items ==
=== max-swapfiles.patch ===
Make number of swapfiles configurable (default=32) (shift=5 => 32 files, shift=0 => 1 file)
* uses CONFIG_MAX_SWAPFILES_SHIFT

=== ldiscs.patch ===
Make number of tty line disciplines configurable (default=16)
* uses CONFIG_NR_LDISCS

=== max_user_rt_prio.patch ===
Make number of schedule slots configurable (default=100)
* uses CONFIG_MAX_USER_RT_PRIO

== change-hz.patch ==
It's not obvious how this changes the size of the kernel, and it appears to be x86 only

= Notes on building and size reductions from various configs =
Notes on OSK builds:
* first, did 'quilt pop pm/deferred-resume-test.patch', then built to get vmlinux.baseline
<pre> text data bss dec filename
2107356 333344 113680 2554380 vmlinux.baseline
</pre>

* did 'quilt push -a', then built to get vmlinux.patched
<pre> bloat-o-meter vmlinux.baseline vmlinux.patched = +2920/-8884
text data bss dec filename
2101372 333888 113648 2548908 vmlinux.patched
</pre>

* configured all parameters at minimums, then built
** couldn't finish linking, and got the following errors:
*** undefined reference to add_preferred_console
*** undefined reference to generic_setxattr and generic_getxattr
*** undefined reference to printk
* configured printk and xattrs back on, then built to get vmlinux.try1

<pre> bloat-o-meter vmlinux.patches vmlinux.try1 = +4520/-350490
text data bss dec filename
1734504 90616 89036 1914156 vmlinux.try1
</pre>

Panic trying to mount rootfs via nfs
* tried to isolate nfs problem:
** configured with AIO, file locks and direct IO on - same problem
** configured with 5 swap files, 8 tty line disciplines, and 100 mat rt levels - same problem
** went back to working config - diffed and noticed NFS_FS was off
*** NFS_FS requires FILE_LOCKING

== Table of Config options ==
Here is a table showing default value and value recommended for size savings.

Note that I couldn't use CONFIG_PRINTK, CONFIG_XATTR or CONFIG_FILE_LOCKING in my setup.

{| border="1" cellpadding="5" cellspacing="0" align="center"
! style="background:#ffcc00;"|'''CONFIG option'''
! style="background:#ffcc00;"|'''description'''
! style="background:#ffcc00;"|'''default'''
! style="background:#ffcc00;"|'''small'''
|-
|CONFIG_CORE_SMALL ||tune some kernel data sizes ||N ||Y
|-
|CONFIG_NET_SMALL ||tune some net-related data sizes ||N ||Y
|-
|CONFIG_KMALLOC_ACCOUNTING||turn on kmalloc accounting ||N ||Y - for measurement
|-
|CONFIG_AUDIT_BOOTMEM ||print out all bootmem allocations ||N ||Y - for measurement
|-
|CONFIG_DEPRECATE_INLINES||cause compiler to emit info about inlines ||N ||Y - for measurement
|-
|CONFIG_PRINTK ||allow disable of printk code and message data ||Y ||N
|-
|CONFIG_BUG ||allow elimination of BUG (and BUG_ON??) code ||Y ||N
|-
|CONFIG_ELF_CORE ||allow disabling of ELF core dumps ||Y ||N
|-
|CONFIG_PROC_KCORE ||allow disabling of /proc/kcore ||Y ||N
|-
|CONFIG_AIO ||allow disabling of async IO syscalls ||Y ||N
|-
|CONFIG_XATTR ||allow disabling of xattr syscalls ||Y ||N
|-
|CONFIG_FILE_LOCKING ||allow disabling of file locking syscalls ||Y ||N
|-
|CONFIG_DIRECTIO ||allow disabling of direct IO support ||Y ||N
|-
|CONFIG_MAX_SWAPFILES_SHIFT||number of swapfiles ||5 ||0
|-
|CONFIG_NR_LDISCS ||number of tty line disciplines ||16 ||2?
|-
|CONFIG_MAX_USER_RT_PRIO||number of RT priority levels (schedule slots)||100 ||5?
|-
|style="background:#ffcc00;"|Other config options ||These are not in Linux-tiny, but help with size||default||small
|-
|CONFIG_KALLSYMS ||load all symbols for debugging/kksymoops ||Y ||N
|-
|CONFIG_SHMEM ||allow use of shmem filesystem ||Y ||N
|}

== Some results ==

This was for a quick check of Linux-tiny on an OSK board.

{| border="1" cellpadding="5" cellspacing="0" align="center"
! style="background:#ffcc00;"|'''section'''
! style="background:#ffcc00;"|'''vmlinux.baseline'''
! style="background:#ffcc00;"|'''vmlinux.try3'''
! style="background:#ffcc00;"|'''delta'''
! style="background:#ffcc00;"|'''percent'''
|-
|| text|| 2107356|| 2057276|| -50080||-2%
|-
|| data|| 333344|| 100988|| -232356||-69%
|-
|| bss|| 113680|| 92784|| -20896||-18%
|-
|total|| 2554380|| 2251048|| -303332||-11%
|}

== Program for producing report (Download) ==
*[[Image:size-delta|size delta]]

== Miscellaneous test notes ==
* kernel would not link with CONFIG_PRINTK=n
** undefined reference to add_preferred_console
** undefined reference to printk
* kernel would not link with CONFIG_XATTR=n
** undefined reference to generic_setxattr and generic_getxattr
* kernel would not mount root fs (NFS) with CONFIG_FILE_LOCKING=n

== Config changes ==
<pre>
[tbird@crest osk]$ diff config.baseline config.try3
--- config.baseline 2005-05-23 17:31:57.000000000 -0700
+++ config.try3 2005-05-23 17:31:40.000000000 -0700
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11.10-alp
-# Mon May 23 16:49:43 2005
+# Mon May 23 17:27:14 2005
#
CONFIG_ARM=y
CONFIG_MMU=y
@@ -34,34 +34,33 @@
CONFIG_FASTBOOT=y
# CONFIG_RTC_NO_SYNC is not set
CONFIG_PRESET_LPJ=0
-# CONFIG_EMBEDDED is not set
-CONFIG_KALLSYMS=y
-CONFIG_KALLSYMS_ALL=y
-CONFIG_KALLSYMS_EXTRA_PASS=y
+CONFIG_EMBEDDED=y
+# CONFIG_KALLSYMS is not set
# CONFIG_KMALLOC_ACCOUNTING is not set
# CONFIG_AUDIT_BOOTMEM is not set
CONFIG_PRINTK=y
-CONFIG_ELF_CORE=y
-# CONFIG_CORE_SMALL is not set
-# CONFIG_NET_SMALL is not set
-CONFIG_FUTEX=y
-CONFIG_EPOLL=y
-CONFIG_AIO=y
+# CONFIG_ELF_CORE is not set
+CONFIG_CORE_SMALL=y
+CONFIG_NET_SMALL=y
+# CONFIG_FUTEX is not set
+# CONFIG_EPOLL is not set
+# CONFIG_AIO is not set
CONFIG_XATTR=y
CONFIG_FILE_LOCKING=y
-CONFIG_DIRECTIO=y
+# CONFIG_DIRECTIO is not set
+# CONFIG_UID16 is not set
# CONFIG_MEASURE_INLINES is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
-CONFIG_SHMEM=y
+# CONFIG_SHMEM is not set
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_CFLAGS is not set
-CONFIG_MAX_SWAPFILES_SHIFT=5
-CONFIG_NR_LDISCS=16
-CONFIG_MAX_USER_RT_PRIO=100
-# CONFIG_TINY_SHMEM is not set
+CONFIG_MAX_SWAPFILES_SHIFT=0
+CONFIG_NR_LDISCS=2
+CONFIG_MAX_USER_RT_PRIO=5
+CONFIG_TINY_SHMEM=y

#
# Loadable module support
@@ -435,6 +434,7 @@
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
+# CONFIG_SERIO_LIBPS2 is not set
# CONFIG_SERIO_RAW is not set

#
@@ -912,7 +912,7 @@
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_BUG=y
-CONFIG_DEBUG_BUGVERBOSE=y
+# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_FS is not set
CONFIG_FRAME_POINTER=y
</pre>

== Series file ==
Please note that I didn't try all the patches. I only integrated and used 37 of the broken-out patches. You can see this from the series file I used, which follows:

<pre>
####################################
# start of linux tiny patches
# key:
# ## = patches Tim commented out
# # = patches commented out in original 2.6.11-tiny broken out series file

##tiny/tiny-extraversion.patch
#
# stuff already in -mm
#
##tiny/kgdb-ga.patch
##tiny/kgdboe-netpoll.patch
tiny/use-funit-at-a-time.patch
##tiny/devlist.patch
#
# tiny stuff
#
# core
tiny/core-small.patch
tiny/pid-max.patch
tiny/user-hash.patch
tiny/futex-queues.patch
tiny/tvec_bases.patch
tiny/con_buf.patch
# net
tiny/config-net-small.patch
tiny/cache_defer_hash.patch
tiny/unix_socket_table.patch
tiny/inet_protos.patch
tiny/flow-cache-small.patch
#
# Unconditional bits
#
##tiny/small-8023.patch
##tiny/tg3-oops.patch
tiny/namei-inlines.patch
tiny/buffer-inlines.patch
tiny/fs_open-inlines.patch
tiny/inode-inlines.patch
tiny/ext2namei-inlines.patch
tiny/fslocks-inline.patch
##tiny/06-crypto-sleep.patch
#
# build options
#
tiny/tiny-cflags.patch
#
# measurement bits
#
tiny/kmalloc-accounting.patch
tiny/audit-bootmem.patch
tiny/bloat-o-meter.patch
tiny/deprecate-inline.patch
tiny/func-size.patch
#
# trimmed debugging support
#
##tiny/no-doublefault.patch
tiny/kill-printk.patch
##tiny/tiny-panic.patch
tiny/nobug.patch
##tiny/nopanic.patch
tiny/no-elf-core.patch
tiny/no-kcore.patch
#
# trimmed code
#
# TRB - 5/19 - haven't looked at these yet
##tiny/tiny-crc.patch
##tiny/threadinfo-ool.patch
##tiny/semaphore-inline.patch
##tiny/slob.patch
##tiny/slob-accounting.patch
##tiny/mempool-shrink.patch
#tiny/sysfs-backingstore.patch
##tiny/no-translations.patch
#tiny/tinyvt.patch
#
# trimmed apis
#
# TRB - 5/19 - haven't looked at ## ones yet
##tiny/ptrace.patch
##tiny/remove-vm86.patch
##tiny/sysenter.patch
tiny/no-aio.patch
tiny/no-xattr.patch
tiny/fslock.patch
tiny/direct-io-core.patch
tiny/uid16.patch
#tiny/posix-timers.patch
##tiny/ethtool.patch
##tiny/inetpeer.patch
##tiny/net-filter.patch
##tiny/dev_mcast.patch
#tiny/rtnetlink.patch
##tiny/igmp.patch
##tiny/binfmt-script.patch
##tiny/elf-no-aout.patch
#
# trimmed constants
#
tiny/max-swapfiles.patch
tiny/ldiscs.patch
tiny/max_user_rt_prio.patch
##tiny/change-hz.patch
#
# trimmed hw support
#
# TRB - 5/19 - haven't looked at ## ones yet
#tiny/small-nomodedb.patch
##tiny/ide-hwif.patch
##tiny/sbf.patch
##tiny/serial-pci.patch
##tiny/dmi_blacklist.patch
##tiny/pci-quirks.patch
##tiny/tsc.patch
##tiny/cpu-support.patch
##tiny/mtrr.patch
#
# inflate cleanups
#
# TRB - 5/19 - haven't looked at ## ones yet
##tiny/inflate-noinline.patch
##tiny/inflate-formatting.patch
##tiny/inflate-legacy.patch
##tiny/inflate-input.patch
##tiny/inflate-iostate.patch
##tiny/inflate-huft.patch
##tiny/inflate-crc.patch
##tiny/inflate-killglobals.patch
##tiny/inflate-initramfs.patch
##tiny/inflate-initrd.patch
##tiny/inflate-i386.patch
##tiny/inflate-arm.patch
##tiny/inflate-x86_64.patch
#
# unsorted
#
# TRB - 5/19 - haven't looked at ## ones yet
##tiny/inflate-roll-crc.patch
##tiny/netpoll-timeout.patch
##tiny/movsl-mask.patch
#tiny/rolled-md4.patch
#tiny/kill-ext3-md4.patch

# end of linux tiny patches
####################################
</pre>

[[Category: Linux Tiny]]

Linux Tiny Test Project

2007-07-14T12:44:09Z

Chris:

== Description ==
This is a project to implement an automated test framework for finding the
specific sub-patches or configuration options (in the total set of
Linux tiny sub-patches) which yeild the biggest size improvements.

The main motivation for this is the (overwhelming) number of sub-patches
in the linux-tiny patchset. In order to avoid doing a manual test of
each sub-patch, this framework was conceived as a method of isolate
the most important sub-patches of the patchset, in order to focus our
attention on those.

The basic idea is that an automated script will run which will test
each configuration option provided by the Linux-tiny patchset. For
each one, the script will measure the reduction in size of the
Linux kernel that results from turning that option on. From this,
a list of the 'top-10' configuration options will be made. Subsequently,
patches to support those top-10 configuration options will be ported and
analyzed on non-x86 processor platforms.

This will give us a starting point to determine the most beneficial
parts of the linux-tiny patchset.

[[Image:Alert.gif]] ''It is recognized that some parts of Linux-tiny are tools for
size evaluation. Some parts affect dynamic memory size, rather than
the static size from the kernel compilation. While the technique
described here is crude and ignores these parts, it's at least
a starting point for evaluating and analyzing Linux-tiny.''

== Linux-tiny specific core member ==
* Classified by Name
** Chihiro Morita(Mitsubishi) / Step 3
** Richard Griffiths(intel) / Step 1 and 2
** M Ranga Swami Reddy(sankhya) / Step 1
** Keijiro Yano(Toshiba) / Step 3
** Masahiro Fukuda(NEC Electronics) / Step 2
** Shuduo Sang(Monta Vista) / Step 1 , 2 and 3
* Classified by Steps
**Step 1 Richard Griffiths(intel), M Ranga Swami Reddy(sankhya),ShuduoSang(MontaVista)
**Step 2 Richard Griffiths(intel), Masahiro Fukuda(NEC Electronics), ShuduoSang(MontaVista)
**Step 3 Chihiro Morita(Mitsubishi), Keijiro Yano(Toshiba), ShuduoSang(MontaVista)

== Step1 ==
Scope and objective
*Step1 is to develop automated testing (config-->build-->capture size) framework on PC/Linux platform.
Specification on the framework(tentative)
*given the following directory structure:
:<code>input/...</code> = input directory = environment var INPUT_DIR
::has <code>baseline_config</code> file
:<code>linux-2.6.8.1/...</code> = kernel source directory = environment var KERN_SRC
:<code>results/...</code> = output directory = environment var RESULT_DIR
*variable iteration:
:for CONFIG_VAR in `cat $(INPUT_DIR)/varlist`; do <loop body here> ; done
*Automated flow control for the following operation assuming individual CONFIG vars are given by Step2.
*#copy baseline_config to .config
*#*<code>cp ../$(INPUT_DIR)/baseline_config .config</code>
*#turn on that variable in the .config file
*#*may need to strip current definition of CONFIG_FOO from .config file)
*#*<code>echo "CONFIG_FOO=y" >>.config</code>
*#make sure configuration is consistent (turn on dependent configuration options)
*#*yes <code>''</code> | make oldconfig
*#save a diff between .config and baseline_config
*#*<code>diff -u $RESULT_DIR/baseline_config .config *#*>../$(RESULT_DIR)/$(CONFIG_VAR).config.patch </code>
*#build kernel image
*#make vmlinux
*#save results
*#*echo $(CONFIG_VAR) >>../$(RESULT_DIR)/size_results
*#*size vmlinux >>../$(RESULT_DIR)/size_results
*#*(sub-system size measurements from linux-tiny presentation by Matt Mackall)
*#*<code>echo ==================================== >>../$(RESULT_DIR)/size_results</code>
*#cleanup for next loop iteration, if necessary
*#*<code>make clean</code> (is this needed?)
*#repeat

== Step2 ==
* pre-requisite (manual tasks):
#build a list of individual CONFIG vars to test
#create a baseline_config file
#kernel source for your platform
#provide environment to run automated script, consisting of:
*directories mentioned above: {{{input, results, <linux kernel source}}}
*environment variables for script: {{{INPUT_DIR, RESULT_DIR, KERN_SRC}}}
*environment variables for kernel building: {{{ARCH, CROSS_COMPILE, PATH}}}
#measure size of kernel compiled with baseline_config
#if the build is cleaned out between every compile, it may be desirable to have ccache installed - see http://ccache.samba.org/
* step2 script [[Image:tiny-step2script.tgz|tiny-step2script]]
* result {{pdf|linux-tiny-size-result.pdf|linux-tiny-size-result}}

== Rationale ==
[This feature is important because ...]

== Resources ==
=== Projects ===
* see the [[Linux Tiny]] page

=== Specifications ===
None

== Downloads ==
=== Patch ===
*See [[Patch Archive]]

=== Utility programs ===
[other programs, user-space, test, etc. related to this technology]

[[Linux Tiny Kernel Size Script]]

== How To Use ==

== Sample Results ==

[Examples of use with measurement of the effects.]

== Case Study 1 ==
On RBTX4938 board (MIPS architecture):
*{{pdf|linux-tiny_size_mips.pdf|linux-tiny_size_mips}}

[[Image:linux-tiny_size_mips.png]]

== Case Study 2 ==

= Future Work/Action Items =
Here is a list of things that could be worked on for this feature: ??

[[Category: Linux Tiny]]

Products

2007-07-14T12:39:59Z

Chris: add Armadillo-2[1234]0

Here is a list of products which use embedded Linux.

Please see the [[Talk:Products|talk page]] for information about how we want to populate this page.

== Televisions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Televisions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Mobile Phones ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Mobile Phones using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
|- align="center"
| [http://www.accton.com/homepage/main3/product_range/23_CE/VM1188T.htm VM1188T]
| [http://www.accton.com Accton]
| 2006
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://www.cellon.com/products.jsp?id=18 C8000]
| [http://www.cellon.com/ Cellon]
| 2005
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS8901223473.html 3G Linux Ref Design]
| [http://www.catt.ac.cn/english/ Datang]
| 2004
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS4367004471.html E28 FMC phones]
| [http://www.e28.com/eng/ E28]
| 2006
| -
| -
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS5033717348.html E28 E2800]
| [http://www.e28.com/eng/ E28]
| 2003
| 32
| 32
| ARM9
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS2220873893.html E28 E2800+]
| [http://www.e28.com/eng/ E28]
| 2004
| 64
| 32
| ARM9 300MHz
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://www.g-tekgroup.com/products/pwg_500.asp PWG500]
| [http://www.g-tekgroup.com/ G-Tek]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://linuxdevices.com/articles/AT2559540724.html G500i]
| Grundig
| 2005
| 52 - User
| X
| OMAP850
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://www.haier.com/products/product.asp?proID=4948 N60]
| [http://www.haier.com Haier]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://www.imcosys.com/English/Smartphone/smartphone.html GPS Phone]
| [http://www.imcosys.com/ ImCoSys]
| 2006
| 64
| 64
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| [http://www.imcosys.com/English/Download/download.html SDK & Flash Image]
|-
|- align="center"
| [X]
| [X]
| X
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [X]
| [X]
| X
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|}
 

== Settop Boxes ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Settop Boxes using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Digital Video Recorders ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Digital Video Recorders using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Game Consoles ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Game Consoles using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| PlayStation 2
| Sony Computer Entertainment
| 2000
| 32MB
| unknown
| MIPS 64-bit R5900
| [http://en.wikipedia.org/wiki/PlayStation_2 PS2 wikipedia page], [http://playstation2-linux.com/ Playstation-linux community site]
| [http://blackrhino.xrhino.com/main.php?page=home Black Rhino Linux distribution site]
|- align="center"
| PlayStation 3
| Sony Computer Entertainment
| 2006
| 512 MB
| unknown
| CELL broadband engine
| [http://en.wikipedia.org/wiki/PlayStation_3 PS3 wikipedia page]
| [http://en.wikipedia.org/wiki/Linux_for_PlayStation_3 wikipedia PS3-linux page]
|-
|}
 

== Still and Video Cameras ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| HDR-UX1, HDR-SR1 video cameras
| Sony
| 2006
| ??
| ??
| ARM9
| [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=11035608 Sonystyle store listing]
| [http://www.sony.net/Products/Linux/Download/HDR-UX1_HDR-SR1.html Sony Linux Download area]
|-
|}

== Not Yet Categorized ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.linuxdevices.com/articles/AT4268573160.html HS210]
| [http://www.ericsson.com Ericsson]
| 2000
| 32
| 32
| StrongARM SA-1110
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| Armadillo-500
| [http://www.atmark-techno.com/en Atmark Techno]
| 2007
| 64
| 16
| i.MX31
| [http://www.atmark-techno.com/products/armadillo/a500 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser Armadillo Developer Site]
|-
|- align="center"
| Armadillo-300
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a300 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-300 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-9
| [http://www.atmark-techno.com/en Atmark Techno]
| 2004
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a9 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-9 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-240
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a240 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-240 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-230
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a230 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-230 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-220
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 32
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a220 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-220 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-210
| [http://www.atmark-techno.com/en Atmark Techno]
| 2005
| 32
| 4
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a210 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-210 Armadillo Developer Site]
|-
|}
 
--[[User:Bharatkapoor|Bharatkapoor]] 23:35, 5 December 2006 (EET)

[[Category:Products]]

Products

2007-07-14T12:35:37Z

Chris: add Armadillo-9

Here is a list of products which use embedded Linux.

Please see the [[Talk:Products|talk page]] for information about how we want to populate this page.

== Televisions ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Televisions using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Mobile Phones ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Mobile Phones using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:150px" | Download Area
|- align="center"
| [http://www.accton.com/homepage/main3/product_range/23_CE/VM1188T.htm VM1188T]
| [http://www.accton.com Accton]
| 2006
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://www.cellon.com/products.jsp?id=18 C8000]
| [http://www.cellon.com/ Cellon]
| 2005
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS8901223473.html 3G Linux Ref Design]
| [http://www.catt.ac.cn/english/ Datang]
| 2004
| -
| -
| -
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS4367004471.html E28 FMC phones]
| [http://www.e28.com/eng/ E28]
| 2006
| -
| -
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS5033717348.html E28 E2800]
| [http://www.e28.com/eng/ E28]
| 2003
| 32
| 32
| ARM9
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://linuxdevices.com/news/NS2220873893.html E28 E2800+]
| [http://www.e28.com/eng/ E28]
| 2004
| 64
| 32
| ARM9 300MHz
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| -
|-
|- align="center"
| [http://www.g-tekgroup.com/products/pwg_500.asp PWG500]
| [http://www.g-tekgroup.com/ G-Tek]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://linuxdevices.com/articles/AT2559540724.html G500i]
| Grundig
| 2005
| 52 - User
| X
| OMAP850
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://www.haier.com/products/product.asp?proID=4948 N60]
| [http://www.haier.com Haier]
| 2006
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [http://www.imcosys.com/English/Smartphone/smartphone.html GPS Phone]
| [http://www.imcosys.com/ ImCoSys]
| 2006
| 64
| 64
| OMAP 730
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| [http://www.imcosys.com/English/Download/download.html SDK & Flash Image]
|-
|- align="center"
| [X]
| [X]
| X
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| [X]
| [X]
| X
| X
| X
| X
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|}
 

== Settop Boxes ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Settop Boxes using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Digital Video Recorders ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Digital Video Recorders using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| X
| X
| X
| X
| X
| X
| X
|-
|}
 

== Game Consoles ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Game Consoles using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| PlayStation 2
| Sony Computer Entertainment
| 2000
| 32MB
| unknown
| MIPS 64-bit R5900
| [http://en.wikipedia.org/wiki/PlayStation_2 PS2 wikipedia page], [http://playstation2-linux.com/ Playstation-linux community site]
| [http://blackrhino.xrhino.com/main.php?page=home Black Rhino Linux distribution site]
|- align="center"
| PlayStation 3
| Sony Computer Entertainment
| 2006
| 512 MB
| unknown
| CELL broadband engine
| [http://en.wikipedia.org/wiki/PlayStation_3 PS3 wikipedia page]
| [http://en.wikipedia.org/wiki/Linux_for_PlayStation_3 wikipedia PS3-linux page]
|-
|}
 

== Still and Video Cameras ==
{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source or Notes
! style="width:250px" | Download Area
|- align="center"
| HDR-UX1, HDR-SR1 video cameras
| Sony
| 2006
| ??
| ??
| ARM9
| [http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&productId=11035608 Sonystyle store listing]
| [http://www.sony.net/Products/Linux/Download/HDR-UX1_HDR-SR1.html Sony Linux Download area]
|-
|}

== Not Yet Categorized ==

{| border="1" cellspacing="0" cellpadding="5"
|+'''Not Yet Categorized devices using Embedded Linux'''
|- style="background:#CCCCCC"
! style="width:100px" | Product Name
! Company Name
! Year Introduced
! RAM MB
! Flash MB
! Processor
! style="width:150px" | Source
! style="width:250px" | Download Area
|- align="center"
| [http://www.linuxdevices.com/articles/AT4268573160.html HS210]
| [http://www.ericsson.com Ericsson]
| 2000
| 32
| 32
| StrongARM SA-1110
| [http://www.linuxdevices.com/articles/AT9423084269.html LinuxDevices]
| X
|-
|- align="center"
| Armadillo-500
| [http://www.atmark-techno.com/en Atmark Techno]
| 2007
| 64
| 16
| i.MX31
| [http://www.atmark-techno.com/products/armadillo/a500 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser Armadillo Developer Site]
|-
|- align="center"
| Armadillo-300
| [http://www.atmark-techno.com/en Atmark Techno]
| 2006
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a300 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-300 Armadillo Developer Site]
|-
|- align="center"
| Armadillo-9
| [http://www.atmark-techno.com/en Atmark Techno]
| 2004
| 64
| 8
| ARM9 200MHz
| [http://www.atmark-techno.com/en/products/armadillo/a9 Company Site]
| [http://armadillo.atmark-techno.com/filebrowser/armadillo-9 Armadillo Developer Site]
|-
|}
 
--[[User:Bharatkapoor|Bharatkapoor]] 23:35, 5 December 2006 (EET)

[[Category:Products]]

Security Working Group

2007-07-14T10:50:30Z

Chris:

== Security Working Group ==

This page will collect information about the activities of the security working group.

== Security Working Group Charter ==
The security working group will work to improve the security capabilities of the Linux operating system to address the range of security requirements for consumer electronics devices.

The working group will establish security requirements for consumer electronics devices and evaluate the suitability of candidate architectures and implementations to satisfy those requirements

== Scope ==
* Data preservation despite kernel bugs
* Protection from malicious attacks
* Protection from stack overrun attacks
* Preservation of program code integrity
* Network security Interfaces to security hardware
* Investigate kernel interface to support security services

== Organization ==

The working group is chaired by Stephen Johnson. You can contact him directly at steve@research.panasonic.com.

== Technical information ==

For technical activities please see the [[Security Resources]] page.

[[Category:Security]]

Do Printk

2007-07-14T10:46:59Z

Chris:

== Description ==
This page describes the "DO_PRINTK" feature. This is a small tweak on the already-supported
printk configuration option in the kernel, which allows a developer to configure whether the
kernel will be compiled with or without printk messages.

This feature allows you to turn off printk messages, while preserving the printk function
itself. Then, you can turn on the printk messages from an individual file, or set of files.
This allows you greater granularity of control over the printk messages that are compiled
into the kernel.

=== Rationale ===
Control over the printk messages in the kernel is important because the kernel messages
comprise a substantial portion of the overall kernel size (ranging from 5 to 10% of overall
kernel image size.)

The kernel (as of this writing, version 2.6.17) already supports an option to turn off all
printk messages. However, sometimes this is too much. Sometimes, an embedded developer
may want to see a few printk messages from specific files or routines, while still not
enabling every single printk message in the kernel. The DO_PRINTK feature provides
this fine-grained control.

== Downloads ==
=== Patch ===
Patch for 2.6.17.4 is here: [[Media:do-printk.patch]] (3KB)

== How To Use ==
To use DO_PRINTK, perform the following steps:

* Apply the patch
* Configure your kernel with CONFIG_PRINTK_FUNC=y and CONFIG_PRINTK=n
** These options appear under "General Setup", "Configure standard kernel features (for small systems)" in 'make menuconfig'
<pre><nowiki>
General Setup --->
[*] Configure standard kernel features (for small systems) --->
[*] Enable printk function in the kernel
[ ] Enable support for printk messages
</nowiki></pre>
** With CONFIG_PRINTK=n, the compiler will by default omit (compile away) the calls to printk in all files
* Select the individual files you would like to still emit printk messages from
** Add "#define DO_PRINTK" to the files where you wish printk messages to be preserved
*** Make sure this definition appears '''before''' any <code>#include</code> lines in the file.
** Alternatively, add -DDO_PRINTK to the compiler flags for files you wish to preserve printks in.
*** (see below for details)
* Compile the kernel
* (optionally) Examine the kernel size, and rejoice at your size savings
* Install the kernel

=== Ways to force printks to be preserved ===
There are actually several ways to get DO_PRINTK defined for a particular file:

# add to the top of the file a line consisting of:
<pre>
#define DO_PRINTK
</pre>
#* this must appear before any <code>#include</code> lines for the file
#* this definition will override the CONFIG_PRINTK=n directive, and allow printks in the file to work normally
# add an option to CFLAGS to the Makefile which controls the building of the file(s) you want to affect
#* To affect an individual file, add -DDO_PRINTK for the CFLAGS for that file:
#* For example, in the Makefile that compiles foo.c , add the line:
<pre>CFLAGS_foo.o += -DDO_PRINTK</pre>
#* To affect all the files in a directory, set EXTRA_CFLAGS, like so:

<pre>EXTRA_CFLAGS += -DDO_PRINTK</pre>

<hr />

== Sample Results ==

Examples of use with measurement of the effects.

=== Case Study 1 ===

On an x86 machine, using kernel.org 2.6.17.4 kernel, I got the results below, using the DO_PRINTK feature in combination with the PRINTK configuration option.

Here is the key for the following tables:

{|
|-
| kernel
| CONFIG_PRINTK_FUNC
| CONFIG_PRINTK
| DO_PRINTK used with files...
| Notes
|-
| func.yes-printk.yes-do.na/vmlinux
| yes
| yes
| not applicable
| This is a pretty regularly-configured kernel (used for baseline in first set of comparisons)
|-
| func.yes-printk.no-do.none/vmlinux
| yes
| no
| none
| Turn off all messages, but leave printk function in place
|-
| func.no-printk.na-do.na/vmlinux
| no
| not applicable
| not applicable
| Turn off all messages and remove printk function
|-
| func.yes-printk.no-do.init.star/vmlinux
| yes
| no
| init/*.c
| Turn off most messages, preserve messages from files in 'init' source directory
|-
| func.yes-printk.no-do.init.main.c/vmlinux
| yes
| no
| init/main.c
| Turn off most messages, preserve messages from init/main.c
|}

==== Summary of image size results ====
Kernel sizes (sorted by decreasing size):

{|
|-
| text
| data
| bss
| dec
| hex
| filename
|-
| 2621433
| 564958
| 137072
| 3323463
| 32b647
| func.yes-printk.yes-do.na/vmlinux (a.k.a. baseline)
|-
| 2376317
| 564958
| 137072
| 3078347
| 2ef8cb
| func.yes-printk.no-do.init.star/vmlinux
|-
| 2375508
| 564958
| 137072
| 3077538
| 2ef5a2
| func.yes-printk.no-do.init.main.c/vmlinux
|-
| 2374733
| 564958
| 137072
| 3076763
| 2ef29b
| func.yes-printk.no-do.none/vmlinux (a.k.a. printk-off baseline)
|-
| 2371463
| 564514
| 120688
| 3056665
| 2ea419
| func.no-printk.na-do.na/vmlinux
|}

==== Image size results compared to baseline ====

The following tables show the image sizes of various kernels compared with a baseline
kernel. The baseline kernel has a fairly normally i386 configuration, with
CONFIG_PRINTK_FUNC=y and CONFIG_PRINTK=y.

Size delta results:

{|
|-
| section
| baseline/vmlinux
| func.no-printk.na-do.na/vmlinux
| change
| percent
|-
| text
| 2621433
| 2371463
| -249970
| -9%
|-
| data
| 564958
| 564514
| -444
| 0%
|-
| bss
| 137072
| 120688
| -16384
| -11%
|-
| total
| 3323463
| 3056665
| -266798
| bgcolor="#B0FFB0" | -8% *
|-
| bgcolor="#B0FFB0" | * Full size reduction using printk elimination is 266K or 8% of vmlinux
|}

<hr />
Size delta results:
{|
|-
| section
| baseline/vmlinux
| func.yes-printk.no-do.init.main.c/vmlinux
| change
| percent
|-
| text
| 2621433
| 2375508
| -245925
| -9%
|-
| data
| 564958
| 564958
| 0
| 0%
|-
| bss
| 137072
| 137072
| 0
| 0%
|-
| total
| 3323463
| 3077538
| -245925
| -7%
|}

<hr />
Size delta results:
{|
|-
| section
| baseline/vmlinux
| func.yes-printk.no-do.init.star/vmlinux
| change
| percent
|-
| text
| 2621433
| 2376317
| -245116
| -9%
|-
| data
| 564958
| 564958
| 0
| 0%
|-
| bss
| 137072
| 137072
| 0
| 0%
|-
| total
| 3323463
| 3078347
| -245116
| -7%
|}

<hr />
Size delta results:
{|
|-
| section
| baseline/vmlinux
| func.yes-printk.no-do.none/vmlinux
| change
| percent
|-
| text
| 2621433
| 2374733
| -246700
| -9%
|-
| data
| 564958
| 564958
| 0
| 0%
|-
| bss
| 137072
| 137072
| 0
| 0%
|-
| total
| 3323463
| 3076763
| -246700
| -7%
|}

<hr />

==== Image size results compared to 'printk-off' baseline ====
The following tables show the image sizes of various kernels compared with a baseline
kernel. The baseline kernel has 'printk-off' configuration, with
CONFIG_PRINTK_FUNC=y and CONFIG_PRINTK=n.

Size delta results:
{|
|-
| section
| func.yes-printk.no-do.none/vmlinux
| func.no-printk.na-do.na/vmlinux
| change
| percent
|-
| text
| 2374733
| 2371463
| bgcolor="#FFB0B0" | -3270 *
| 0%
|-
| data
| 564958
| 564514
| bgcolor="#FFB0B0" | -444 *
| 0%
|-
| bss
| 137072
| 120688
| bgcolor="#FFB0B0" | -16384 *
| -11%
|-
| total
| 3076763
| 3056665
| bgcolor="#FFB0B0" | -20098 *
| 0%
|-
| bgcolor="#FFB0B0" | * Size of printk function alone is about 3.6k in image and 20k in static memory
|}

<hr />
Size delta results:
{|
|-
| section
| func.yes-printk.no-do.none/vmlinux
| func.yes-printk.no-do.init.main.c/vmlinux
| change
| percent
|-
| text
| 2374733
| 2375508
| bgcolor="#FFFFB0" | 775 *
| 0%
|-
| data
| 564958
| 564958
| 0
| 0%
|-
| bss
| 137072
| 137072
| 0
| 0%
|-
| total
| 3076763
| 3077538
| 775
| 0%
|-
| bgcolor="#FFFFB0" | * Size of printk messages from a single C file (init/main.c in this case) was 775 bytes. Obviously, this is heavily dependent on the number of printk calls and the size of the messages in that file.
|}

<hr />
Size delta results:
{|
|-
| section
| func.yes-printk.no-do.none/vmlinux
| func.yes-printk.no-do.init.star/vmlinux
| change
| percent
|-
| text
| 2374733
| 2376317
| 1584
| 0%
|-
| data
| 564958
| 564958
| 0
| 0%
|-
| bss
| 137072
| 137072
| 0
| 0%
|-
| total
| 3076763
| 3078347
| 1584
| 0%
|}

<hr />
Size delta results:
{|
|-
| section
| func.yes-printk.no-do.none/vmlinux
| func.yes-printk.yes-do.na/vmlinux
| change
| percent
|-
| text
| 2374733
| 2621433
| 246700
| 10%
|-
| data
| 564958
| 564958
| 0
| 0%
|-
| bss
| 137072
| 137072
| 0
| 0%
|-
| total
| 3076763
| 3323463
| 246700
| 8%
|}

<hr />

=== Case Study 2 ===
[need to post PPC and MIPS results here also]

== Status ==
* Status: tested on multiple platforms
* Architecture Support:
(for each arch, one of: unknown, patches apply, compiles, runs, works, accepted)
** i386: works
** ARM: compiles, not run-tested yet
** PPC: works
** MIPS: works
** SH: unknown

== Future Work/Action Items ==
Here is a list of things that could be worked on for this feature:
- nothing right now

[[Category:Printk]]

Toolbox

2007-07-14T10:45:05Z

Chris:

This page has information about developing Embedded Linux, including links to toolchains, debuggers and other development tools. Also, it has links to pages with debugging tips.

= Development Tools =

== Toolchains ==
A tool chain is basically defined as a compiler, linker and C library (I.e. GCC, binutils & glibc/uClibc). Optionally, a tool chain may contain a debugger and C++ compiler. Quite often, the tool chain used for embedded devices is a cross toolchain: All the programs (like GCC) run on a PC but produce binary code to run on a different architecture (e.g. ARM). This is called cross compilation and is assumed to be what you want to do. It is possible to compile natively, running gcc on your target. However, unless you have an x86 target, you need a tool chain on your device, which eats up your flash and will also take much longer to compile things than your far more powerful PC. Before going down the route of obtaining a toolchain, it's worth checking to see if one is included with your target's Board Support Package (BSP), if you have one.

=== Note about C libraries ===
Realistically, there are two options for the C Library: [http://en.wikipedia.org/wiki/Uclibc uClibc] & [http://en.wikipedia.org/wiki/Glibc glibc]. GLibc is what your PC is probably using. It's a bit of a brute, very powerful but a bit bloated. If flash space and memory footprint is an issue, using uClibc is likely to be the better option. However, the space advantages gained using uClibc are becoming less important as the price of memory & flash continues to drop. There are a few "gotcha"s when using uClibc. At time of writing(uClibc 0.9.28), locales are a bit ropey and the new Application Binary Interface (ABI) for ARM architectures (EABI) introduced with GCC 4.1.1 requires patches to be applied. This situation is likely to get better quickly as uClibc is under heavy development.

=== Available Toolchains ===
Creating a cross development toolchain from sources can be a real pain. There are version dependency issues, patches required to make something work etc. etc. Check out the [http://kegel.com/crosstool/crosstool-0.43/buildlogs/ build matrix] for crosstool and look at all the red "failed" entries. Fortunately, there are several groups of people who have done all the hard work for you, producing scripts to create a toolchain or releases of binary toolchains.

==== Buildroot ====
Buildroot is a complete build system based on the Linux Kernel configuration system and supports a wide range of target architectures. It generates root file system images ready to be written to flash. In addition to having a huge number of packages which can be compiled into the image, it also generates a cross toolchain to build those packages from source. Even if you don't want to use buildroot for your root filesystem, it is a useful tool for generating a toolchain. It should be noted however that it only supports uClibc. If you want to use glibc, you'll need something else. Link: [http://buildroot.uclibc.org/ Buildroot homepage]

==== Scratchbox ====
Scratchbox provides toolchains for ARM and x86 target architectures (with PowerPC, MIPS and CRIS in experimental stages). Both uClibc & glibc are supported. Scratchbox simplifies cross compiling software which is built using GNU autotools - Code tests performed by configure are run in an emulator or even on the actual target. The toolchains scratchbox ships with are based on gcc 3.3 and as such are quite old, but stable and well tested. It should be pointed out that scripts to build custom toolchains are also provided with scratchbox allowing more recent gcc versions to be used. Link: [http://www.scratchbox.org/ Scratchbox]

==== Crossdev (Gentoo) ====
Crossdev is specific to developers using Gentoo for their development PCs. It is a script which generates a cross toolchain using the portage build scripts for gcc etc. There are numerous architectures which are supported and both uClibc and glibc toolchains can be built. Link: [http://gentoo-wiki.com/HOWTO_Cross_Compile Gentoo Cross-Compile HOWTO]

==== Crosstool ====
Crosstool is a script which downloads source tar-balls and builds simple gcc/glibc cross toolchains. There is a build matrix which shows which versions of gcc/glibc work together with various architectures ([http://kegel.com/crosstool/crosstool-0.43/buildlogs/ link]). The inclusion of this matrix makes it easy to select which versions of gcc/glibc should be used to generate a toolchain for a particular architecture. Link: [http://kegel.com/crosstool/ Crosstool]

==== Code Sourcery ====
Code Sourcery is a commercial company which develops cross development tools for numerous architectures. Code Sourcery provides a "lite" version for their ARM, Coldfire & Power PC architecture development tools which is freely available. The toolchains are usually very up-to-date. Link: [http://www.codesourcery.com/ Code Sourcery]

==== Crossdev/tsrpm (Timesys) ====
Crossdev is a project sponsored by Timesys, completely unrelated to the Gentoo cross toolchain generation system. The projects main focus is on a tool called tsrpm which is used to build cross development toolchains and generate cross-compiled software packages. Currently only x86 and select PowerPC architectures are supported. Link: [https://crossdev.timesys.com/ Crossdev]

* FIXTHIS - need link for debuggers (DDD, gdb, kgdb, etc.)eclipse
* FIXTHIS - need link for IDEs (eclipse, etc.)

== Tracers and Profilers ==
* see [[Kernel Trace Systems]]

== Benchmarks ==
* see [[Benchmark Programs]]

== Source Management Tools ==
There are a number of tools for managing patches, which are useful for different tasks.
There's now a whole page devoted to this. See [[Source Management Tools]]

For some simple tools for managing patches, see [[Diff And Patch Tricks]]

= Debugging Tips =
* See the [[Kernel Debugging Tips]] page

[[Category:Development Tools]]

DHT-Walnut Usefull Projects

2007-07-14T10:41:04Z

Chris:

[http://www.musicpd.org/ mpd] server

Following in the footsteps of [http://devices.natetrue.com/musicap/ Nate True], I turned a DHT-Walnut + parts into a server to play my music collection. It grabs the data via nfs from an NSLU2, and is controlled via various [http://www.musicpd.org/clients.shtml mpc-like] clients from my desktops.

[[Image:mpdserver.jpg]]

After the above was running flawlessly for a day, somehow the usb audio device got fried. May have been a ground loop in the stereo. I had gotten used to having music playing. so I dug out an old PCI sound card (CS4280 based) and compiled the drivers and plugged it in. GIGO... seems like [[IBM4xx]] DMA support needs to be turned on in the kernel to make it work. Things are fine now with a few extra ground wires, just to be sure.

[[[Media:config.gz]] 2.6.16-pre3 configuration]

[[Image:mpdserver1.jpg]]

[[Category:DHT-Walnut]]

DHT-Walnut U Boot

2007-07-14T10:41:00Z

Chris:

== U-Boot 1.1.4 ==

Information on U-Boot can be found at [http://u-boot.sourceforge.net/]

The source for U-Boot 1.1.4 is downloadable from ftp://ftp.denx.de/pub/u-boot/u-boot-1.1.4.tar.bz2

Here is a patch that makes it work on the DHT-Walnut: [http://www.farnsworth.org/linuxppc/u-boot-dht-walnut-df2.patch u-boot-dht-walnut-df2.patch].

A binary that can be copied to the DHT-Walnut flash at 0xfffc0000 is available here: [http://www.farnsworth.org/linuxppc/u-boot-1.1.4-df2.bin u-boot-1.1.4-df2.bin]

Changes since u-boot-1.1.4-df1.bin:
* A default ethaddr is now set: de:ad:be:ef:00:00
* The ethaddr can be changed as often as you like. Use: ''setenv ethaddr be:ef:be:ef:be:ef ; saveenv''
* Only the first two memory banks of a DIMM are used. This allows us to use (half of) double-sided DIMMS.

Some things to note when changing from ppcboot to U-Boot:
* Default baudrate is 115200.
* Occupies flash addresses 0xfffc0000-0xffffffff (256MB).
* Maintains two copies of environment data, primary copy at 0xfffb0000, backup copy at 0xfffa0000.

== Installing U-Boot 1.1.4 on the DHT Walnut ==
* Boot the board and bring it to the ppcboot (or U-Boot) console prompt.

* Download the new bootloader [[[Media:u-boot-1.1.4-df2.bin]] u-boot-1.1.4-df2.bin] into RAM:
** Using Kermit (you'll need a terminal emulator that supports the kermit file transfer mode):

=> ''loadb 800000 115200''

<pre>## Switch baudrate to 115200 bps and press ENTER ...
## Ready for binary (kermit) download ...
## Start Addr = 0x00800000
## Switch baudrate to 9600 bps and press ESC ...
</pre>

** or tftpboot (requires a tftp server and setting the environment variables ethaddr, ipaddr and serverip)

=> ''tftpboot 800000 u-boot-1.1.4-df2.bin''

<pre>Using ppc_4xx_eth0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.44
Filename 'u-boot.bin'.
Load address: 0x800000
Loading: ####################################################
done
Bytes transferred = 262144 (40000 hex)
</pre>

* Verify that the download was received correctly (crc should be 0xd3cef189):

=> ''crc 800000 40000''

<pre>CRC32 for 00800000 ... 0083ffff ==> d3cef189
</pre>

* Unprotect the last 4 sectors:

=> ''protect off fffc0000 ffffffff''

<pre>Un-Protected 4 sectors
</pre>

'''From this point on, do *not* power down the board, and type *very* carefully.
This is the critical section.'''

* Erase the last four sectors:

=> ''erase fffc0000 ffffffff''

<pre>Erase Flash from 0xfffc0000 to 0xffffffff
Erasing sector fffc0000
.Erasing sector fffd0000
.Erasing sector fffe0000
.Erasing sector ffff0000
. done
Erased 4 sectors</pre>

* Copy the new bootloader into flash:

=> ''cp.b 800000 fffc0000 40000''

<pre>Copy to Flash... done
</pre>

* Verify that the image is correct (crc of u-boot-1.1.4-df2.bin is 0xd3cef189).

=> ''crc fffc0000 40000''

<pre>CRC32 for fffc0000 ... ffffffff ==> d3cef189
</pre>

'''End of critical section. Congratulations'''
* Reset the board and see that the new version booted
*** Don't forget to change your baud rate to 115200

=> ''reset''

<pre>
U-Boot 1.1.4 (Feb 16 2006 - 17:15:06)

CPU: AMCC PowerPC 405GP Rev. E at 266.640 MHz (PLB=66, OPB=33, EBC=33 MHz)
Internal PCI arbiter enabled, PCI async ext clock used
16 kB I-Cache 8 kB D-Cache
Board: DHT Walnut
I2C: ready
DRAM: 128 MB
FLASH: 512 kB
PCI: Bus Dev VenId DevId Class Int
00 04 105a 0d30 0101 1d
In: serial
Out: serial
Err: serial
Net: ppc_4xx_eth0
IDE: Bus 0: OK
Device 0: not available
Device 1: not available
BEDBUG:ready
</pre>

You will see a message like : *** Warning - bad CRC, using default environment
That's normal. It will go away after you issue a ''saveenv'' command.

This bootloader works well with the 2.6 Linux kernel available [wiki:DHT-Walnut2.6LinuxKernel here].

Please let me know of any success or issues you encounter. [mailto:dale-elinux@farnsworth.org dale-elinux@farnsworth.org]

[[Category:DHT-Walnut]]

DHT-Walnut Known Working Hardware

2007-07-14T10:40:48Z

Chris:

This page lists all hardware that is known to work (and not to work) with the DHT Walnut board. Some PCI cards that don't work, may have kernel/driver compilation issues. Here is a kernel that works with the drivers listed below.

[[[Media:kernel]] 2.6.16-pre-3 kernel]

== Known To Work ==
=== Video ===
* Matrox Millenium II (framebuffer console for kernel 2.4 & 2.6)
* ATI Rage XL (atyfb driver with mods for kernel 2.6.16-pre3)
=== USB Cards ===
* Best Buy 2-port USB2.0 card (NEC D720101GJ) -- NOTE: Some kernel trees has no console mapping for the Walnut target, so while USB works, keyboard only works in X.
* [[Compu Geeks]] 2 & 5 port USB2.0 cards (NEC D720101GJ--(NOTE: Kernel 2.6.16-pre3 and later seem to handle the console mapping ok, and both usb keyboards & mice (some) work ok. )--
=== SCSI Adapters ===
* Adaptec 2930CU is recognized by the [[AIC7xxx]] driver
=== Sound Cards ===
* No Name CS4280/4297A PCI uses cs46xx driver, needs [[IBM4xx]] DMA support turned on in the kernel config.
* Creative Labs [[En Soniq]] es1370 uses ens1370 driver, needs [[IBM4xx]] DMA support turned on in the kernel config.
[[[Media:sound.tar.gz]] Drivers]

=== IDE ===
* SYBA [[Compact Flash]] to IDE adapter (available [http://www.newegg.com/Product/Product.asp?Item=N82E16822998003 HERE])
=== USB Serial Adapters ===
* FTDI USB-Serial adapter chipset (ftdi_sio driver as module, kernel 2.6.15.4)
== Known Not To Work ==
=== Video ===
* most "standard" PCI video cards
* many of these cards need their hardware initialized by the BIOS which the DHT doesn't have.
=== Sound Cards ===
* Aureal Votrex2 using au88x0 driver, built from either the latest ALSA sources or from those in kernel 2.6.16. The driver loads and appears to initialize without errors, but causes a kernel oops when an application tries to use it.

[[Category:DHT-Walnut]]

DHT-Walnut Jtag Bootloader Installation

2007-07-14T10:40:42Z

Chris:

== Recovering a bricked DHT Walnut board ==

Using OCD Commander, a JTAG adapter, and [[GPSFan]]'s ram resident ppcboot, it is possible to reprogram the flash. In short, use OCD Commander to turn on the sdram, download the ram targeted ppcboot, and install a new bootloader.

You'll need a macro file [http://elinux.org/wiki/DHT-Walnut?action=AttachFile&do=get&target=recovery_config.mac recovery_config.mac] and the ppcboot image [[[Media:ppcboot_ram.s19]] ppcboot_ram.s19].

There's also an experimental ram-resident version of u-boot-1.1.4 [[[Media:u-boot-ram.s19]] u-boot-ram.s19] that can be downloaded to 0x400000. Source diffs against the current version from CVS, incorporating the patches from both [[GPSFan]] and dfarnsworth: [[[Media:u-boot-ram.patch]] u-boot-ram.patch]. Expect to see much more output at boot, as this version has debug output turned on. (Other changes include setting the entry point in the linker script, output files renamed to u-boot.s19 and u-boot.elf, sdram config disabled, added debug info on code relocation, and a modified default environment.)

* Start OCD Commander, connect to the board, reset, and halt.

>''reset''
* The CPU should be ready to fetch the first instruction:

>''cpu''

<pre> PC: FFFFFFFC CR: 00000000 MSR: 00000000 LR: 01FD327C
B -524028
</pre>

* Configure the system:

>''recovery_config'' (Or hit the macro button and navigate to the recovery_config.mac file.)

<pre>
>endian big
BIG Endian set for WORD and DASM commands
>dcr 0x086 = 0x0400D038 ; 0x086: PLB0_BEAR R PLB Bus Error Address Register
>dcr 0x0A0 = 0x03000000 ; 0x0A0: POB0_BESR0 R/Clear PLB to OPB Bus Error Status Register 0
>dcr 0x0B1 = 0x0000102E ; 0x0B1: CPC0_CR0 R/W Chip Control Register 0
>dcr 0x010 = 0x30
>dcr 0x11 = 0x20880000 ; offset 0x30: SDRAM0_RTR R/W Refresh Timer Register
>dcr 0x010 = 0x40
>dcr 0x11 = 0x00046001 ; offset 0x40: SDRAM0_B0CR R/W Memory Bank 0 Configuration Register
>dcr 0x010 = 0x48
>dcr 0x11 = 0x01046001 ; offset 0x48: SDRAM0_B2CR R/W Memory Bank 2 Configuration Register
>dcr 0x010 = 0x80
>dcr 0x11 = 0x010A801A ; offset 0x80: SDRAM0_TR R/W SDRAM Timing Register 1
>dcr 0x010 = 0x20
>dcr 0x11 = 0x80800000 ; offset 0x20: SDRAM0_CFG R/W Memory Controller Options 1
>dcr 0x012 = 0x00
>dcr 0x13 = 0xFFF18000 ; offset 0x00: EBC0_B0CR R/W Peripheral Bank 0 Configuration Register
>dcr 0x012 = 0x01
>dcr 0x13 = 0xF0018000 ; offset 0x01: EBC0_B1CR R/W Peripheral Bank 1 Configuration Register
>dcr 0x012 = 0x02
>dcr 0x13 = 0xF0118000 ; offset 0x02: EBC0_B2CR R/W Peripheral Bank 2 Configuration Register
>dcr 0x012 = 0x03
>dcr 0x13 = 0xF0218000 ; offset 0x03: EBC0_B3CR R/W Peripheral Bank 3 Configuration Register
>dcr 0x012 = 0x04
>dcr 0x13 = 0x400DA000 ; offset 0x04: EBC0_B4CR R/W Peripheral Bank 4 Configuration Register
>dcr 0x012 = 0x07
>dcr 0x13 = 0xF0318000 ; offset 0x07: EBC0_B7CR R/W Peripheral Bank 7 Configuration Register
>dcr 0x012 = 0x10
>dcr 0x13 = 0x9B015480 ; offset 0x10: EBC0_B0AP R/W Peripheral Bank 0 Access Parameters
>dcr 0x012 = 0x11
>dcr 0x13 = 0x02815480 ; offset 0x11: EBC0_B1AP R/W Peripheral Bank 1 Access Parameters
>dcr 0x012 = 0x12
>dcr 0x13 = 0x04815A80 ; offset 0x12: EBC0_B2AP R/W Peripheral Bank 2 Access Parameters
>dcr 0x012 = 0x13
>dcr 0x13 = 0x01815280 ; offset 0x13: EBC0_B3AP R/W Peripheral Bank 3 Access Parameters
>dcr 0x012 = 0x14
>dcr 0x13 = 0x03800480 ; offset 0x14: EBC0_B4AP R/W Peripheral Bank 4 Access Parameters
>dcr 0x012 = 0x17
>dcr 0x13 = 0x01815280 ; offset 0x17: EBC0_B7AP R/W Peripheral Bank 7 Access Parameters
>word 0xEF400000 = 0x00000080 ; 0xEF400000: PCIL0_PMM0LA R/W PMM 0 Local Address
>word 0xEF400004 = 0x010000E0 ; 0xEF400004: PCIL0_PMM0MA R/W PMM 0 Mask/Attribute
>word 0xEF400008 = 0x00000080 ; 0xEF400008: PCIL0_PMM0PCILA R/W PMM 0 PCI Low Address
>word 0xEF400014 = 0x010000E0 ; 0xEF400014: PCIL0_PMM1MA R/W PMM 1 Mask/Attribute
>spr 0x009 = 0x00000000 ; CTR Count Register 9 0x009 0x120 Read/Write
>spr 0x3FB = 0x80000001 ; ICCR Instruction Cache Cachability Register 1019 0x3FB 0x37F Read/Write
>spr 0x3DB = 0x0001568B ; PIT Programmable Interval Timer 987 0x3DB 0x37E Read/Write
>spr 0x3B9 = 0x00000000 ; SGR Storage Guarded Register 953 0x3B9 0x33D Read/Write
>spr 0x3DA = 0x04400000 ; TCR Timer Control Register 986 0x3DA 0x35E Read/Write
</pre>

* Download the ppcboot image to ram:

>''down''

<pre>E:\src\ppc\ppcboot\ppcboot_ram.s19: downloaded 163100 bytes in 0 minutes, 22.785 seconds
PC set to starting address 0x00400000
</pre>

* Jump to the startup (which isn't the same as the download address):
>''go 0x400100''

At this point, you should have a running ppcboot v1.1.6. Install a new flash resident bootloader using the bootloader update procedure [wiki:DHT-WalnutInstallingTheUpdatedBootloader Installing the Updated Bootloader]

[[Category:DHT-Walnut]]

DHT-Walnut Installing The Updated Bootloader

2007-07-14T10:40:35Z

Chris:

== Installing a New Bootloader ==
Quick notes on updating from stock ppcboot v1.1.2 to [[GPSFan]]'s ppcboot v1.1.6.1

* Boot the board and bring it to the ppcboot console prompt.
* Check current flash configuration:

=> ''flinfo''

<pre>Bank # 1: AMD AM29F040 (512 Kbit, uniform sector size)
Size: 512 KB in 8 Sectors
Sector Start Addresses:
FFF80000 RO FFF90000 RO FFFA0000 RO FFFB0000 FFFC0000
FFFD0000 FFFE0000 FFFF0000 </pre>

Note that the bottom three sectors, containing the existing 1.1.2 bootloader, are protected.
We also want to protect the last sector, which contains the initial jump instruction, so:

=> ''protect on ffff0000 ffffffff''

<pre>Protected 1 sectors
</pre>

* Zero out a section of ram before the download:

=> ''mw.b 400000 0 30000''
* Now download the new bootloader [http://elinux.org/wiki/DHT-Walnut?action=AttachFile&do=get&target=ppcboot1.1.6.1.bin ppcboot1.1.6.1.bin] into ram (you'll need a terminal emulator that supports the kermit file transfer mode):

=> ''loadb 400000 115200''

<pre>## Switch baudrate to 115200 bps and press ENTER ...
## Ready for binary (kermit) download ...
## Start Addr = 0x00400000
## Switch baudrate to 9600 bps and press ESC ...
</pre>

* Verify that the download was received correctly (crc should be 0x083fb0a3):

=> ''crc 400000 30000''

<pre>CRC32 for 00400000 ... 0042ffff ==> 083fb0a3
</pre>

* Erase the three spare sectors, which we'll use to backup the 1.1.2 bootloader:

=> ''erase fffc0000 fffeffff''

<pre>Erase Flash from 0xfffc0000 to 0xfffeffff
Erasing sector fffc0000
.Erasing sector fffd0000
.Erasing sector fffe0000
. done
Erased 3 sectors</pre>

* (Optional: erase the 0xfffb0000 sector, which will be used for non-volatile environment storage.)

=> ''erase fffb0000 fffbffff''

<pre>Erase Flash from 0xfffb0000 to 0xfffbffff
Erasing sector fffb0000
. done
Erased 1 sectors</pre>

* Check that sectors 0xfffc0000 to 0xfffe0000 are erased, and sector 0xffff0000 is protected:

=> ''flinfo''

<pre>Bank # 1: AMD AM29F040 (512 Kbit, uniform sector size)
Size: 512 KB in 8 Sectors
Sector Start Addresses:
FFF80000 RO FFF90000 RO FFFA0000 RO FFFB0000 E FFFC0000 E
FFFD0000 E FFFE0000 E FFFF0000 RO </pre>

* Now we're ready to backup the 1.1.2 bootloader. Copy three sectors from 0xfff80000 to 0xfffc0000:

=> ''cp.b fff80000 fffc0000 30000''

<pre>Copy to Flash... done
</pre>

* Easy enough, right? Compare just to be sure it went ok:

=> ''cmp.b fff80000 fffc0000 30000''

<pre>Total of 196608 bytes were the same
</pre>

* Now we're ready to modify the bootsectors. We'll turn off protection, erase the three bottom sectors, and copy the new 1.1.6.1 bootloader from ram.

* Unprotect the bottom three sectors:
=> ''protect off fff80000 fffaffff''

<pre>Un-Protected 3 sectors
</pre>

'''From this point on, do *not* power down the board. This is the critical section.'''
* Erase the bottom three sectors with the original 1.1.2 bootloader:

=> ''erase fff80000 fffaffff''

<pre>Erase Flash from 0xfff80000 to 0xfffaffff
Erasing sector fff80000
.Erasing sector fff90000
.Erasing sector fffa0000
. done
Erased 3 sectors</pre>

* Copy the new bootloader into flash:
=> ''cp.b 400000 fff80000 30000''

<pre>Copy to Flash... done
</pre>

* Verify the copy:
=> ''cmp.b 400000 fff80000 30000''

<pre>Total of 196608 bytes were the same
</pre>

* Verify that the image is correct (crc of ppcboot1.1.6.1.bin is 0x083fb0a3).
=> ''crc fff80000 30000''

<pre>CRC32 for fff80000 ... fffaffff ==> 083fb0a3
</pre>

'''End of critical section. Congratulations''''

* We've finished modifying flash, so turn the write protection back on:
=> ''protect on fff80000 fffaffff''

<pre>Protected 3 sectors
</pre>

* Reset the board and see that the new version booted

=> ''reset''

<pre>
PPCBoot 1.1.6 (Feb 5 2006 - 21:38:51)

CPU: IBM PowerPC 405GP Rev. E at 266.640 MHz (PLB=66, OPB=33, EBC=33 MHz)
PCI async ext clock used, internal PCI arbiter enabled
16 kB I-Cache 8 kB D-Cache
</pre>

To sum up, you'll end up executing these commands:

=> ''protect on ffff0000 ffffffff''

=> ''mw.b 400000 0 30000''

=> ''loadb 400000 115200''

=> ''crc 400000 30000''

=> ''erase fffc0000 fffeffff''

=> ''cp.b fff80000 fffc0000 30000''

=> ''cmp.b fff80000 fffc0000 30000''

=> ''protect off fff80000 fffaffff''

=> ''erase fff80000 fffaffff''

=> ''cp.b 400000 fff80000 30000''

=> ''cmp.b 400000 fff80000 30000''

=> ''crc fff80000 30000''

=> ''protect on fff80000 fffaffff''

[[Category:DHT-Walnut]]

DHT-Walnut GPIO

2007-07-14T10:40:00Z

Chris:

== Warning ==
The GPIO registers are quite fickle things. Not only are they for the Media LED and J5 header, they also manage the [[IRQs]] and Peripheral Chip selects. Hitting a wrong bit in Linux will cause problems, kernel panics, total lockups, bad things, 'plagues of locusts', you get the idea. When using the [[PPC405 _gpio]] driver below(or the 405_ocp_gpio driver in DENX [[Linux PPC]] 2.4, use a mask of 0xFFC00000, that way you don't manage to hit something you really don't want to.

== Playing with the Media LED ==
The Media LED on the DHT-Walnut is wired to the processor by the GPIO pins. However its behind a 74VHC14 Schmitt Inverter. So you have to send it low in order to turn it on. This top section only covers the Media LED and the U-Boot/[[PPCBoot]] ROM Monitor.

=== Memory Locations ===
0xef600700 is the memory location of the GPIO output register. It's 4 bytes wide. It turns on and off the GPIO pins on the PPC405GP.

0xef600704 is the location of the Tri-State register. Also 4 bytes wide. Controls if the GPIO pin is active when high.

0xef600718 is the location of the Open Drain register. Also 4 bytes wide. Controls if the GPIO pin is an open drain or active output.

0xef60071c is the location of the GPIO Input register. Also 4 bytes wide. The state of each pin is reflected in the correspondig value in this register. (synchronized with [[OPBClk]])

=== Playing with the LED ===
By having all the bits in the Tri-State register high and the Output register all low, The pins are driven low. Because the Media LED is behind the inverter it glows when low. Setting it high in the Output register will turn it off.

=== Example using U-Boot 1.1.4 ===
Setting the Tri-State Register to drive all usable [[GPIOs]].
<pre>=> nm 0xef600704
ef600704: 00000000 ? ffc00000
ef600704: ffc00000 ?</pre>
The LED should be lit now as its pin is driven low.

Turning the LED on and off with the Output Register
<pre>=> nm 0xef600700
ef600700: 00000000 ? 20000000 //LED should be off.
ef600700: 20000000 ? 00000000 //LED goes on.
ef600700: 00000000 ?</pre>

=== The J5 Header ===
The J5 header located to the left of the RAM slot actually has 9 GPIO pins wired to it. [[GPIOs]] 1 to 9 to be exact. That header also has the Power and Media [[LEDs]] wired to it, so using the first 2 pins will look awkward if your bit-banging to say a SD/MMC card or LCD display. The J5 header has the following layout. As things are developed they will be added.

[[[Media:gpio-J5.jpg]]]
=== Linux and the [[GPIOs]] ===
==== Module for 2.6.16 ====
Using a module from a Monta Vista 2.4 kernel, I did the slight editing so that it will compile with 2.6.16. I have made a patch file that can be applied to a vanilla 2.6.16(possibly any 2.6) kernel. You can also use Ken's 2.6.16-pre3 config on the [wiki:DHT-WalnutUsefullProjects DHT-WalnutUsefullProjects] page as a base config.

Also included is a small bit of test code to show how to operate the gpio driver.

Module patch and test code here: [[[Media:ppc405_gpio.tar.gz]] ppc405_gpio.tar.gz] (Version 1) '''(Version 2 will be up once I clean some little problems out of the test code, possibly tonight)'''

Any errors or things you want to see, don't hesitate to let me know. I'll be slowly adding little things to the module as helpers.

Once you have your module installed and modprobe/insmoded, just run 'make' to built the test app. If you don't have a /dev/ entry yet just 'make dev' and it'll do it for you. [[Dev FS]] isn't supported yet, I'm working on that now.

[[Category:DHT-Walnut]]

DHT-Walnut Booting From Hdd

2007-07-14T10:39:54Z

Chris:

'''Work In Progress'''

ppcboot provides only basic functionality to access Hard disks: you can print the partition table and read and write blocks (addressed by absolute block number), but there is no support to create new partitions or to read files from any type of filesystem. The current version of ppcboot-1.1.6 has a problem with writing to hdd, however, once the Linux kernel is loaded and the userland initialized, the hdd can be accesses normally through PIO and DMA modes. This may or may-not be fixed in the future.

Update: disk write seems to work well in [wiki:DHT-Walnut-U-Boot U-Boot 1.1.4]. The information on this page applies to U-Boot as well as ppcboot.

As usual, you can get some information about the available IDE commands using the help command in ppcboot:

<pre> => help ide
ide reset - reset IDE controller
ide info - show available IDE devices
ide device [dev] - show or set current device
ide part [dev] - print partition table of one or all IDE devices
ide read addr blk# cnt
ide write addr blk# cnt - read/write `cnt' blocks starting at block `blk#'
to/from memory address `addr' </pre>

You may create the needed partitions by tftpbooting Linux and an appropriate userland, then use fdisk to partition the disk. Then reboot back to ppcboot.

ppcboot can be configured for DOS and [[Mac OS]]? type partition tables. Since ppcboot cannot read files from a filesystem you should create one (or more) small partitions (maybe 1 or 2 MB) if you want to boot from the "disk". (The size of these partitions will depend on how large your kernel and userland images are)

For example on a 128 MB [[Compact Flash]] card we could create the following partiton table under Linux:

<pre> # fdisk /dev/hde
hde: hde1 hde2 hde3 hde4

Command (m for help): p

Disk /dev/hde: 8 heads, 32 sectors, 978 cylinders
Units = cylinders of 256 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hde1 1 17 2160 83 Linux
/dev/hde2 18 34 2176 83 Linux
/dev/hde3 35 803 98432 83 Linux
/dev/hde4 804 978 22400 82 Linux swap

Command (m for help): q

# mkswap /dev/hde4
Setting up swapspace version 1, size = 22933504 bytes </pre>

Here we have two small boot partitions (/dev/hde1 and /dev/hde2, 2 MB each), one big partition to hold a filesystem (/dev/hde3, 99 MB), and a swap partition (/dev/hde4, 22 MB). We also initialized /dev/hde4 as swap space.

ppcboot will recognize this partition table as follows:

<pre> => ide part

Partition Map for IDE device 0 -- Partition Type: DOS

Partition Start Sector Num Sectors Type
1 32 4320 83
2 4352 4352 83
3 8704 196864 83
4 205568 44800 82 </pre>

An easy way to load the Linux kernel into the first partition is to boot all the way back to Linux, mount an nfs partition to retrieve the kernel and userland images. then use dd to put them onto the hdd:

* mount -t nfs -0 nolock xxx:yyy:zzz:aaa:/ /mnt
* cd /mnt
* cd /tftpboot
* dd if=kernel.img of=/dev/hde1
* dd if=userland.img of=/dev/hde2

To boot from a disk you can use the diskboot command:

<pre> => help diskboot
diskboot loadAddr dev:part </pre>

The diskboot command expects a load address in RAM, and a combination of device and partition numbers, separated by a colon. It then reads the image from disk and stores it in memory. We can now boot it using the bootm command [to automatically boot the image define the ppcboot environment autostart with the value =yes=].

<pre> => diskboot 400000 0:1
ide_read dev 0 start 0, blocks 1 buffer at 3F9F8C0
## Valid DOS partition found ##

Loading from IDE device 0, partition 1: Name: hda1
Type: PPCBoot
First Block: 63, # of blocks: 8001, Block Size: 512
ide_read dev 0 start 3F, blocks 1 buffer at 400000
Image Name: DHT Kernel
Created: 2006-02-05 19:37:25 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1085059 Bytes = 1059 kB = 1 MB
Load Address: 00000000
Entry Point: 00000000
ide_read dev 0 start 40, blocks 847 buffer at 400200

=> diskboot c00000 0:2
ide_read dev 0 start 0, blocks 1 buffer at 3F9F8C0
## Valid DOS partition found ##

Loading from IDE device 0, partition 2: Name: hda2
Type: PPCBoot
First Block: 8064, # of blocks: 8064, Block Size: 512
ide_read dev 0 start 1F80, blocks 1 buffer at C00000
Image Name: Ramdisk Image
Created: 2006-02-05 20:24:43 UTC
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 765638 Bytes = 747 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
ide_read dev 0 start 1F81, blocks 5D7 buffer at C00200

=> bootm 400000 c00000
## Booting image at 00400000 ...
Image Name: DHT Kernel
Created: 2006-02-05 19:37:25 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1085059 Bytes = 1059 kB = 1 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00c00000 ...
Image Name: Ramdisk Image
Created: 2006-02-05 20:24:43 UTC
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 765638 Bytes = 747 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
... </pre>

<pre> => setenv bootargs root=/dev/ram0
=> setenv autostart yes
=> disk 400000 0:1 \;\ diskboot c00000 0:2 \;\ bootm 400000 c00000

=> bootd
ide_read dev 0 start 0, blocks 1 buffer at 3F9F518
## Valid DOS partition found ##

Loading from IDE device 0, partition 1: Name: hda1
Type: PPCBoot
First Block: 63, # of blocks: 8001, Block Size: 512
ide_read dev 0 start 3F, blocks 1 buffer at 400000
Image Name: DHT Kernel
Created: 2006-02-05 19:37:25 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1085059 Bytes = 1059 kB = 1 MB
Load Address: 00000000
Entry Point: 00000000
ide_read dev 0 start 40, blocks 847 buffer at 400200
ide_read dev 0 start 0, blocks 1 buffer at 3F9F518
## Valid DOS partition found ##

Loading from IDE device 0, partition 2: Name: hda2
Type: PPCBoot
First Block: 8064, # of blocks: 8064, Block Size: 512
ide_read dev 0 start 1F80, blocks 1 buffer at C00000
Image Name: Ramdisk Image
Created: 2006-02-05 20:24:43 UTC
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 765638 Bytes = 747 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
ide_read dev 0 start 1F81, blocks 5D7 buffer at C00200
## Booting image at 00400000 ...
Image Name: DHT Kernel
Created: 2006-02-05 19:37:25 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1085059 Bytes = 1059 kB = 1 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00c00000 ...
Image Name: Ramdisk Image
Created: 2006-02-05 20:24:43 UTC
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 765638 Bytes = 747 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Ramdisk to 03ee4000, end 03f9eec6 ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:mapin_ram done
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
setup_arch: ocp_early_init
arch: exit
arch: exit 2

Welcome to the DHS local environment.

uclibc login:

</pre>

The above procedure puts the userland image from the second partition into a ramdisk. If you would like the userland to be an ext2/3/rieser/xfs partition on the hdd do the following:

** put the kernel and small userland onto the first and second partitions as above
** boot as above from the hdd to the ramdisk userland
** bring up the network and NFS mount a remote filesystem
** mkfs.ext2/3/reiser/xfs /def/hde3
** mount the resulting partition somewhere convienent
** populate that partition with the appropriate files
** sync, and unmount all mounted filesystems
** reboot to ppcboot
** change bootargs to "bootargs root=/def/hde3"
** bootd to try out the new root, if it works ok, reboot back to ppcboot, change the bootargs again and saveenv
** bootd and enjoy your new system.

This page was modified from and mostly lifted from:
[http://www.denx.de/wiki/view/DULG/UsingPCCard]

[[Category:DHT-Walnut]]

DHT-Walnut Boot Via Tftp

2007-07-14T10:39:44Z

Chris:

It's relative easy if:
* You have a tftp server setup
* Have a kernel Image and Userland Image in the /tftpboot/ directory on your server

** =>tftpboot 400000 [[Working Kernel Image]]
** < kernel image loads >
** =>tftpboot c00000 [[Working Userland Image]]
** < userland image loads >
** bootm 400000 c00000
** < kernel boots and loads userland image >

[[Category:DHT-Walnut]]

DHT-Walnut Add J10

2007-07-14T10:39:36Z

Chris:

Just suck or wick the solder out of the holes and solder it in...

[[Image:j10a.jpg]]

[[Category:DHT-Walnut]]

DHT-Walnut 2.6 Linux Kernel

2007-07-14T10:39:27Z

Chris:

== Linux Kernel v2.6.15 ==

Here is a 2.6.15 kernel, built from unmodified source code found [http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.15.4.bz2 here].
* [http://www.farnsworth.org/linuxppc/uImage.2.6.15.4-walnut-df4 uImage.2.6.15.4-walnut-df4]
* [http://www.farnsworth.org/linuxppc/config.2.6.15.4-walnut-df4 config.2.6.15.4-walnut-df4]

(this latest image adds CONFIG_MATH_EMULATION, CONFIG_I2C, CONFIG_CRAMFS, CONFIG_DEVFS_FS, and CONFIG_PACKET)

This kernel works with ppcboot 1.1.6 or the U-Boot bootloader available [wiki:DHT-Walnut-U-Boot here].

The following things have been tested and all seem to work:
* 10/100 Ethernet port
* IDE with drives on /dev/hda and /dev/hdb
* Firewire with the PCI card sold with the DHT-Walnut. I tested a Firewire DVD-writer.
* USB with an PCI OHCI adapter
* Console on Matrox video FB using a USB keyboard
* NFS root filesystem
* standalone system with root=/dev/hda1 and matrox fb console with usb keyboard.

All the on-board hardware seems to be supported by the vanilla 2.6.15 kernel.

Note: To set the Linux console baud rate to 115200, add "console=ttyS0,115200" to the U-Boot bootargs environment variable.

Please let me know of any success or issues you encounter. [mailto:dale-elinux@farnsworth.org dale-elinux@farnsworth.org].

[[Category:DHT-Walnut]]