From a3ffa97f40dc81f2d6b07ee964f2340fe0c1ba97 Mon Sep 17 00:00:00 2001 From: Sascha Hauer Date: Tue, 15 Dec 2009 09:11:09 +0100 Subject: rename U-Boot-v2 project to barebox This has been done with the following script: find -path ./.git -prune -o -type f -print0 | xargs -0 -r sed -i \ -e 's/u2boot/barebox/g' \ -e 's/U2Boot/barebox/g' \ -e 's/U-boot V2/barebox/g' \ -e 's/u-boot v2/barebox/g' \ -e 's/U-Boot V2/barebox/g' \ -e 's/U-Boot-v2/barebox/g' \ -e 's/U_BOOT/BAREBOX/g' \ -e 's/UBOOT/BAREBOX/g' \ -e 's/uboot/barebox/g' \ -e 's/u-boot/barebox/g' \ -e 's/u_boot/barebox/g' \ -e 's/U-Boot/barebox/g' \ -e 's/U-boot/barebox/g' \ -e 's/U-BOOT/barebox/g' find -path ./.git -prune -o \( -name "*u-boot*" -o -name "*uboot*" -o -name "*u_boot*" \) -print0 | \ xargs -0 -r rename 's/u[-_]?boot/barebox/' It needs some manual fixup following in the next patch Signed-off-by: Sascha Hauer --- README | 58 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 29 insertions(+), 29 deletions(-) (limited to 'README') diff --git a/README b/README index ef691b6574..e8a280fe33 100644 --- a/README +++ b/README @@ -1,8 +1,8 @@ -U2Boot +barebox ------ -This is u2boot, our proposal for a next generation of the famous U-Boot -bootloader. U-Boot offers an excellent choice as a bootloader for +This is barebox, our proposal for a next generation of the famous barebox +bootloader. barebox offers an excellent choice as a bootloader for today's embedded systems, seen from a user's point of view. Nevertheless, there are quite some design flaws which turned out over the last years and we think that they cannot be solved in a production @@ -12,7 +12,7 @@ about losing support for old boards. General features include: - A posix based file API - inside U-Boot the usual open/close/read/write/lseek functions are used. + inside barebox the usual open/close/read/write/lseek functions are used. This makes it familiar to everyone who has programmed under unix systems. - usual shell commands like ls/cd/mkdir/echo/cat,... @@ -46,12 +46,12 @@ General features include: the code. - simulation target - U-Boot can be compiled to run under Linux. While this is rather useless + barebox can be compiled to run under Linux. While this is rather useless in real world this is a great debugging and development aid. New features can be easily developped and tested on long train journeys and started under gdb. There is a console driver for linux which emulates a serial device and a tap based ethernet driver. Linux files can be mapped to - devices under U-Boot to emulate storage devices. + devices under barebox to emulate storage devices. - device parameter support Each device can have a unlimited number of parameters. They can be accessed @@ -64,7 +64,7 @@ General features include: - getopt There is a small getopt implementation. Some commands got really - complicated (both in code and in usage) due to the fact that U-Boot only + complicated (both in code and in usage) due to the fact that barebox only allowed positional parameters. - editor @@ -72,16 +72,16 @@ General features include: except the ones really needed: moving the cursor and typing characters. -Building U-Boot +Building barebox --------------- -U-Boot uses the Linux kernel's build system. It consists of two parts: +barebox uses the Linux kernel's build system. It consists of two parts: the makefile infrastructure (kbuild), plus a configuration system -(kconfig). So building U-Boot is very similar to building the Linux +(kconfig). So building barebox is very similar to building the Linux kernel. -For the examples below, we use the User Mode U-Boot implementation, which -is a port of U-Boot to the Linux userspace. This makes it possible to +For the examples below, we use the User Mode barebox implementation, which +is a port of barebox to the Linux userspace. This makes it possible to test drive the code without having real hardware. So for this test scenario, ARCH=sandbox is the valid architecture selection. This currently only works on ia32 hosts and partly on x86-64. @@ -89,7 +89,7 @@ only works on ia32 hosts and partly on x86-64. Selection of the architecture and the cross compiler can be done by using the environment variables ARCH and CROSS_COMPILE. -In order to configure the various aspects of U-Boot, start the U-Boot +In order to configure the various aspects of barebox, start the barebox configuration system: # make menuconfig @@ -100,44 +100,44 @@ finished (you can simulate this by using the standard demo config file with 'make sandbox_defconfig'), there is a .config file in the toplevel directory of the sourcode. -Once U-Boot is configured, we can start the compilation +Once barebox is configured, we can start the compilation # make -If everything goes well, the result is a file called uboot: +If everything goes well, the result is a file called barebox: - # ls -l uboot - -rwxr-xr-x 1 rsc ptx 114073 Jun 26 22:34 uboot + # ls -l barebox + -rwxr-xr-x 1 rsc ptx 114073 Jun 26 22:34 barebox -U-Boot usually needs an environment for storing the configuation data. +barebox usually needs an environment for storing the configuation data. You can generate an environment using the example environment contained in examples/environment: - # ./scripts/ubootenv -s -p 0x10000 examples/environment/ env.bin + # ./scripts/bareboxenv -s -p 0x10000 examples/environment/ env.bin To get some files to play with you can generate a cramfs image: # mkcramfs somedir/ cramfs.bin -The U-Boot image is a normal Linux executable, so it can be started +The barebox image is a normal Linux executable, so it can be started just like every other program: - # ./uboot -e env.bin -i cramfs.bin + # ./barebox -e env.bin -i cramfs.bin - U-Boot 2.0.0-trunk (Jun 26 2007 - 22:34:38) + barebox 2.0.0-trunk (Jun 26 2007 - 22:34:38) loading environment from /dev/env0 - uboot> / + barebox> / -Specifying -[ie] tells U-Boot to map the file as a device +Specifying -[ie] tells barebox to map the file as a device under /dev. Files given with '-e' will appear as /dev/env[n]. Files given with '-i' will appear as /dev/fd[n]. -If U-Boot finds a valid configuration sector on /dev/env0 it will +If barebox finds a valid configuration sector on /dev/env0 it will load it to /env. It then executes /env/init if it exists. If you have -loaded the example environment U-Boot will show you a menu asking for +loaded the example environment barebox will show you a menu asking for your settings. -If you have started U-Boot as root you will find a new tap device on your -host which you can configure using ifconfig. Once you configured U-Boots +If you have started barebox as root you will find a new tap device on your +host which you can configure using ifconfig. Once you configured bareboxs network settings accordingly you can do a ping or tftpboot. If you have mapped a cramfs image try mounting it with @@ -148,7 +148,7 @@ If you have mapped a cramfs image try mounting it with Memory can be examined as usual using md/mw commands. They both understand the -f option to tell the commands that they should work on the specified files instead of /dev/mem which holds the complete address space. -Note that if you call 'md /dev/fd0' (without -f) U-Boot will segfault on +Note that if you call 'md /dev/fd0' (without -f) barebox will segfault on the host, because it will interpret /dev/fd0 as a number. Directory layout -- cgit v1.2.3