<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://wiki.barebox.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://wiki.barebox.org/feed.php">
        <title>barebox</title>
        <description></description>
        <link>http://wiki.barebox.org/</link>
        <image rdf:resource="http://wiki.barebox.org/lib/images/favicon.ico" />
       <dc:date>2012-05-18T19:43:46+02:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=user:magic_variables&amp;rev=1334444333&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:iomem&amp;rev=1334434900&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:magicvar&amp;rev=1334434769&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=filesystems:ramfs&amp;rev=1334434129&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=filesystems:fat&amp;rev=1334433734&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=filesystems:tftp&amp;rev=1334433690&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:automount&amp;rev=1334433347&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:addpart&amp;rev=1334344051&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:bootm&amp;rev=1334343904&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:ping&amp;rev=1333535677&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=boards:phytec_phycore_i_mx31&amp;rev=1328015343&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:md&amp;rev=1328009971&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:timeout&amp;rev=1328009891&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=commands:memcpy&amp;rev=1323780832&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.barebox.org/doku.php?id=developer:driver_model&amp;rev=1320948412&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://wiki.barebox.org/lib/images/favicon.ico">
        <title>barebox</title>
        <link>http://wiki.barebox.org/</link>
        <url>http://wiki.barebox.org/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=user:magic_variables&amp;rev=1334444333&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-15T00:58:53+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>user:magic_variables</title>
        <link>http://wiki.barebox.org/doku.php?id=user:magic_variables&amp;rev=1334444333&amp;do=diff</link>
        <description>Some variables in barebox have special meanings. These are listed here. Other than these variables there are
device parameters. See here for more information on these.
Also see the magicvar command which gives an overview about the
magic variables that the current binary supports.</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:iomem&amp;rev=1334434900&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-14T22:21:40+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:iomem - created</title>
        <link>http://wiki.barebox.org/doku.php?id=commands:iomem&amp;rev=1334434900&amp;do=diff</link>
        <description>barebox supports dividing the iospsace into resources which can be requested by drivers. iomem gives an overview about these resources and their owners.

example
iomem
0x00000000 - 0xfffffffe (size 0xffffffff) iomem
0x1000a000 - 0x1000afff (size 0x00001000) imx_serial0
0x1000e000 - 0x1000efff (size 0x00001000) imx_spi0
0x10021000 - 0x10021fff (size 0x00001000) imxfb0
0x10024500 - 0x100244ff (size 0x00000000) ehci0
0x10024540 - 0x1002453f (size 0x00000000) ehci0
0x1002b000 - 0x1002bfff (size 0x00…</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:magicvar&amp;rev=1334434769&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-14T22:19:29+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:magicvar - created</title>
        <link>http://wiki.barebox.org/doku.php?id=commands:magicvar&amp;rev=1334434769&amp;do=diff</link>
        <description>Several environment variables in barebox have a special meaning for some commands. The magivar command lists all special variables along with their meaning.</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=filesystems:ramfs&amp;rev=1334434129&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-14T22:08:49+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>filesystems:ramfs - created</title>
        <link>http://wiki.barebox.org/doku.php?id=filesystems:ramfs&amp;rev=1334434129&amp;do=diff</link>
        <description>ramfs is a simple malloc based filesystem. An instance of ramfs is mounted during startup on /. The filesystemtype passed to mount is 'ramfs'

example
mount none ramfs /somedir</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=filesystems:fat&amp;rev=1334433734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-14T22:02:14+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>filesystems:fat - [example] </title>
        <link>http://wiki.barebox.org/doku.php?id=filesystems:fat&amp;rev=1334433734&amp;do=diff</link>
        <description>barebox support the FAT filesystem including write support and long filenames. The filesystemtype passed to mount is 'fat'.

example
mount /dev/disk0.1 fat /mnt/fat
bootm /mnt/fat/uImage</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=filesystems:tftp&amp;rev=1334433690&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-14T22:01:30+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>filesystems:tftp - created</title>
        <link>http://wiki.barebox.org/doku.php?id=filesystems:tftp&amp;rev=1334433690&amp;do=diff</link>
        <description>barebox supports tftp as a regular filesystem with both read and write support. The filesystemtype passed to mount is 'tftp'. tftp does not support listing directories, so a mounted tftp directory will appear empty, nevertheless the files are there.</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:automount&amp;rev=1334433347&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-14T21:55:47+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:automount - created</title>
        <link>http://wiki.barebox.org/doku.php?id=commands:automount&amp;rev=1334433347&amp;do=diff</link>
        <description>Automatically mount a device when a path is first accessed


automount [OPTIONS] &lt;path&gt; &lt;cmd&gt;
 -l  list current automountpoints  -r  remove a mountpoint          

With the automount command barebox maintains a list of pathes and associated commands.
Whenever a path is first accessed the command is run. It's the commands responsibility
to make this path available.</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:addpart&amp;rev=1334344051&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-13T21:07:31+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:addpart</title>
        <link>http://wiki.barebox.org/doku.php?id=commands:addpart&amp;rev=1334344051&amp;do=diff</link>
        <description>Add partitions to a device or file.


addpart [OPTIONS] &lt;device&gt; &lt;part_desc&gt;

  -n        no prefix. Do not prepend the device name as prefix before the partition name   &lt;device&gt;  device being worked on     &lt;part_desc&gt;  size1[@offset1](name1)[ro],size2[@offset2](name2)[ro],...   

The size and the offset can be given in decimal (without any prefix) and in hex (prefixed with 0x).</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:bootm&amp;rev=1334343904&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-13T21:05:04+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:bootm</title>
        <link>http://wiki.barebox.org/doku.php?id=commands:bootm&amp;rev=1334343904&amp;do=diff</link>
        <description>Boot an application image. This has become the standard image starting mechanism and it can start uImages
aswell as zImages and barebox images.


bootm [OPTIONS] image
 -c  crc check uImage data  -r &lt;initrd&gt;  specify an initrd image  -L &lt;load addr&gt;  specify initrd load address  -a &lt;load addr&gt;  specify os load address  -e &lt;ofs&gt;  entry point to the image relative to start (0)  -o &lt;oftree&gt;  specify oftree  -v  verbose  -f  fallback 

The bootm command automatically detects the image type. This work…</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:ping&amp;rev=1333535677&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-04T12:34:37+02:00</dc:date>
        <dc:creator>Wolfram Sang</dc:creator>
        <title>commands:ping - Remove wrong fact. It resends a ping packet after 10 seconds. Code will be changed, soon, nonetheless.</title>
        <link>http://wiki.barebox.org/doku.php?id=commands:ping&amp;rev=1333535677&amp;do=diff</link>
        <description>ping HOST

HOST can be an IP address or a host name. If a host name is specified, barebox tries to resolve that host name and exits with a failure if not successful.</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=boards:phytec_phycore_i_mx31&amp;rev=1328015343&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-31T14:09:03+02:00</dc:date>
        <dc:creator>Jochen Frieling</dc:creator>
        <title>boards:phytec_phycore_i_mx31 - created</title>
        <link>http://wiki.barebox.org/doku.php?id=boards:phytec_phycore_i_mx31&amp;rev=1328015343&amp;do=diff</link>
        <description>The CPU module


&lt;http://www.phytec.eu/europe/products/modules-overview/phycore/produktdetails/p/phycore-imx31-2.html&gt;

This CPU card is based on a Freescale i.MX31 CPU. The card in configuration -0000REU is shipped with:


	*  128 MiB synchronous dynamic RAM (DDR type)
	*  64 MiB NAND flash
	*  32 MiB NOR flash
	*  512 kiB SRAM
	*  4kiB EEPROM
	*  MMU, FPU
	*  Serial, Ethernet, USB (OTG), I2C, SPI, MMC/SD/SDIO, PCMCIA/CF, RTC</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:md&amp;rev=1328009971&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-31T12:39:31+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:md - [Options:] </title>
        <link>http://wiki.barebox.org/doku.php?id=commands:md&amp;rev=1328009971&amp;do=diff</link>
        <description>md [OPTIONS] &lt;region&gt;

  -s &lt;file&gt;  display file (default: /dev/mem)     -b  output in bytes     -w  output in halfwords (16 bit)     -l  output in words (32 bit)   
Display (hexdump) a memory region.

Memory regions can be specified in two different forms: start+size or start-end, If &lt;start&gt; is ommitted it defaults to 0. If end is omitted it defaults to the end of the device, except for interactive commands like md and mw for which it defaults to 0x100. Sizes can be specified as decimal, or if …</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:timeout&amp;rev=1328009891&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-31T12:38:11+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:timeout - [Options:] </title>
        <link>http://wiki.barebox.org/doku.php?id=commands:timeout&amp;rev=1328009891&amp;do=diff</link>
        <description>timeout [OPTIONS] &lt;timeout&gt;

  -a  interrupt on any key     -c  interrupt on ctrl-c     -r  interrupt on return     -s  silent mode   
Wait &lt;timeout&gt; seconds for a timeout, return 1 on user intervention and 0 on timeout.

example
echo
echo -n &quot;Hit any key to stop autoboot: &quot;
timeout -a $autoboot_timeout
if [ $? != 0 ]; then
  echo &quot;autobooting aborted&quot;
  exit
fi</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=commands:memcpy&amp;rev=1323780832&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-13T13:53:52+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>commands:memcpy - [memcpy] </title>
        <link>http://wiki.barebox.org/doku.php?id=commands:memcpy&amp;rev=1323780832&amp;do=diff</link>
        <description>Copy to/from plain memory or files


memcpy [OPTIONS] &lt;src&gt; &lt;dst&gt; &lt;count&gt;
 -b, -w, -l   use byte, halfword, or word accesses   -s &lt;file&gt;    source file (default /dev/mem)   -d &lt;file&gt;    destination file (default /dev/mem) 

WIthout any options this command works like the standard memcpy C function. With the -s and -d options the source/destination file can
be overwritten. This makes it possible to copy a memory area to a file or a file to a memory area.</description>
    </item>
    <item rdf:about="http://wiki.barebox.org/doku.php?id=developer:driver_model&amp;rev=1320948412&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-11-10T19:06:52+02:00</dc:date>
        <dc:creator>Sascha Hauer</dc:creator>
        <title>developer:driver_model</title>
        <link>http://wiki.barebox.org/doku.php?id=developer:driver_model&amp;rev=1320948412&amp;do=diff</link>
        <description>We follow a rather simplistic driver model here. There is a struct device_d which
describes a particular device present in the system. A struct driver_d represents
a driver present in the system. Both structs find together via the members
'type' (int) and 'name' (char *). If both members match, the driver's probe
function is called with the struct device_d as argument. People familiar with
the Linux platform bus will recognize this behaviour and in fact many things were
stolen from there. Some s…</description>
    </item>
</rdf:RDF>

