Lines Matching refs:Boot
9 This directory contains the source code for U-Boot, a boot loader for
15 The development of U-Boot is closely related to Linux: some parts of
37 scattered throughout the U-Boot source identifying the people or
41 actual U-Boot source tree; however, it can be created dynamically
51 U-Boot, you should send a message to the U-Boot mailing list at
61 The U-Boot source code is maintained in the Git repository at
89 - create U-Boot project (http://sourceforge.net/projects/u-boot)
90 - current project page: see http://www.denx.de/wiki/U-Boot
96 The "official" name of this project is "Das U-Boot". The spelling
97 "U-Boot" shall be used in all written text (documentation, comments
100 This is the README file for the U-Boot project.
126 U-Boot v2009.11 - Release November 2009
127 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
128 U-Boot v2010.09-rc1 - Release candidate 1 for September 2010 release
150 /cmd U-Boot commands functions
156 /dts Contains Makefile for building internal U-Boot fdt.
166 /tools Tools to build S-Record or U-Boot images, etc.
187 U-Boot has added the Kbuild infrastructure used by the Linux kernel,
210 U-Boot can be built natively to run on a Linux host using the 'sandbox'
213 run some of U-Boot's tests.
222 SPL and U-Boot proper (i.e. they both follow the same rules).
275 CONFIG_SPL_STACK_R_ADDR. For non-SPL, U-Boot is relocated to run at the top of
286 - U-Boot is relocated to the top of memory and is now running from
295 - loads U-Boot or (in falcon mode) Linux
407 time of U-Boot entry and is required to be re-initialized.
534 XWAY SoCs for booting from NOR flash. The U-Boot image needs to
554 Support executing U-Boot in non-secure (NS) mode. Certain
561 U-Boot stores all clock information in Hz
565 "clocks_in_mhz" can be defined so that U-Boot
609 U-Boot can detect if an IDE device is present or not.
610 If not, and this new config option is activated, U-Boot
637 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
680 within "Boot Delay" after reset.
705 will not be available, and when U-Boot wants to execute the
712 If this variable is defined, U-Boot is linked against
719 If this variable is defined, U-Boot will use a device tree
725 U-Boot needs to get its device tree from somewhere. This can
729 If this variable is defined, U-Boot will embed a device tree
736 If this variable is defined, U-Boot will build a device tree
742 and in fact, U-Boot does this for you, creating a file called
748 If this variable is defined, U-Boot will use the device tree
805 When CONFIG_IO_TRACE is selected, U-Boot intercepts all I/O
1073 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
1301 If this option is set, then U-Boot will prevent the environment
1434 U-Boot will use this to determine if it is the destination of
1440 time is too long, U-Boot will retransmit requests. In order
1442 retransmissions, U-Boot's BOOTP client keeps a small cache of
1445 requests. Increasing this will allow U-Boot to accept offers
1553 fast while running U-Boot code, stop blinking as
1558 feature in U-Boot.
1566 to include the gpio_led driver in the U-Boot binary.
1867 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
1872 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
1969 If defined, this string will be added to the U-Boot
1974 U-Boot considers the values of the environment
2005 by U-Boot. Define CONFIG_PRAM to hold the number of
2035 normally accessible to U-Boot - e.g. some architectures
2112 U-Boot code. This is NOT an official, exported
2125 initialised so that it is available to U-Boot. This inhibits
2127 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL
2329 memory. U-Boot will then place the frame buffer at
2483 Partition on the MMC to load U-Boot from when the MMC is being
2497 Partition on the MMC to load U-Boot from when the MMC is being
2501 Filename to read to load U-Boot when reading from filesystem
2556 to read U-Boot
2562 Location in NAND to read U-Boot from
2565 Location in memory to load U-Boot to
2650 - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
2659 - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
2686 (end) of RAM and won't get "touched" at all by U-Boot. By
2722 embedded within the U-Boot image, or in a separate
2739 U-Boot relocates itself.
2816 instead of U-Boot software protection.
2941 may easily extract it and embed it in final U-Boot images.
2944 in U-Boot initialization (when we try to get the setting of for the
2946 U-Boot will hang.
2997 Display information about the board that U-Boot is running on
2998 when U-Boot starts up. The board function checkboard() is called
3007 Maximum size of the U-Boot image. When defined, the
3099 U-Boot uses the following memory types:
3159 Board can support master function for Boot from SRIO and PCIE
3249 controller) are omitted and/or U-Boot does not
3253 exception is when U-Boot is loaded (to RAM) by some
3264 that is executed before the actual U-Boot. E.g. when
3269 that is executed after the SPL and before the actual U-Boot.
3278 Generally U-Boot (and in particular the md command) uses
3280 U-Boot address as virtual addresses that need to be translated
3288 needed when U-Boot is running from Coreboot.
3300 This firmware often needs to be loaded during U-Boot booting, so macros
3344 This firmware often needs to be loaded during U-Boot booting, so macros
3355 This firmware often needs to be loaded during U-Boot booting.
3363 In order to achieve reproducible builds, timestamps used in the U-Boot build
3368 option for U-Boot or an environment variable in U-Boot.
3375 Building U-Boot has been tested in several native build environments
3380 which is extensively used to build and test U-Boot.
3401 U-Boot is intended to be simple to build. After installing the
3402 sources you must configure U-Boot for one specific board type. This
3420 - will configure for a TQM823L with U-Boot console on LCD
3425 Finally, type "make all", and you should get some working U-Boot
3434 this behavior and build U-Boot to some external directory:
3464 to port U-Boot to your hardware platform. To do this, follow these
3472 3. If you're porting U-Boot to a new CPU, then also create a new
3481 Testing of U-Boot Modifications, Ports to New Hardware, etc.:
3484 If you have modified U-Boot sources (for instance added a new board
3488 official or latest in the git repository) version of U-Boot sources.
3494 configure and build U-Boot for ALL supported system. Be warned, this
3499 See also "U-Boot Porting Guide" below.
3562 U-Boot supports user configuration using Environment Variables which
3582 bootargs - Boot arguments when booting an RTOS image
3647 device tree used by U-Boot when CONFIG_OF_CONTROL is
3665 address to use (U-Boot will still check that it
3666 does not overwrite the U-Boot stack and data).
3678 indication to U-Boot that all addresses are legal
3680 memory. In this case U-Boot will NOT COPY the
3710 ethrotate - When set to "no" U-Boot does not go through all
3727 unset, then it will be made silent if the U-Boot console
3806 the board). U-Boot refuses to delete or overwrite these variables
3812 ver - Contains the U-Boot version string as printed
3869 There are two different command line parsers available with U-Boot:
3911 Some boards come with redundant Ethernet interfaces; U-Boot supports
3951 U-Boot is capable of booting (and performing other auxiliary operations on)
3992 Although U-Boot should support any OS or standalone application
3994 U-Boot.
3996 U-Boot includes many features that so far have been part of some
4007 lots of low-level, hardware dependent stuff are done by U-Boot
4020 Porting Linux to U-Boot based systems:
4023 U-Boot cannot save you from doing all the necessary modifications to
4034 as your U-Boot configuration in CONFIG_SYS_IMMR.
4036 Note that U-Boot now has a driver model, a unified model for drivers.
4045 No specific requirements for U-Boot. Make sure you have some root
4052 With U-Boot, "normal" build targets like "zImage" or "bzImage" are
4055 U-Boot. Most older kernels also have support for a "pImage" target,
4068 CRC32 checksum etc. for use with U-Boot. This is what we are doing:
4082 * package compressed binary image for U-Boot:
4090 with U-Boot, either separated from the Linux kernel image, or
4100 contained in the header of an existing U-Boot image; this includes
4106 The second form (with "-d" option) is used to build a U-Boot image
4127 So a typical call to build a U-Boot image would read:
4168 Similar you can build U-Boot images from a 'ramdisk.image.gz' file
4195 To downloading a U-Boot image over the serial (console) interface,
4200 The 'objcopy' does not understand the information in the U-Boot
4240 Boot Linux:
4268 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
4314 Boot arguments: root=/dev/ram
4323 Boot Linux and pass a flat device tree:
4326 First, U-Boot must be compiled with the appropriate defines. See the section
4372 More About U-Boot Image Types:
4375 U-Boot supports the following image types:
4378 provided by U-Boot; it is expected that (if they behave
4379 well) you can continue to work in U-Boot after return from
4385 expect to re-enter U-Boot except by resetting the CPU.
4404 U-Boot or FPGA images) which usually will be programmed to
4408 U-Boot's command interpreter; this feature is especially
4409 useful when you configure U-Boot to use a real shell (hush)
4428 One of the features of U-Boot is that you can dynamically load and
4430 U-Boot like console I/O functions or interrupt services.
4438 application; it is automatically compiled when you build U-Boot.
4467 handler with the U-Boot code, can be found in 'examples/timer.c'.
4537 Starting at version 0.9.2, U-Boot supports NetBSD both as host
4538 (build U-Boot) and target system (boots NetBSD/mpc8xx).
4544 attempting to build U-Boot will fail because <machine/ansi.h> is
4554 and U-Boot include files.
4568 inner workings of U-Boot and make it easier to port it to custom
4575 The implementation of U-Boot is complicated by the fact that U-Boot
4587 U-Boot mailing list:
4589 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
4639 turned out that the implementation of U-Boot can be greatly
4660 (U-Boot also uses R12 as internal GOT pointer. r12
4664 ==> U-Boot will use R2 to hold a pointer to the global data
4670 average for all boards 752 bytes for the whole U-Boot image,
4685 ==> U-Boot will use R9 to hold a pointer to the global data
4692 ==> U-Boot will use gp to hold a pointer to the global data
4709 ==> U-Boot will use R10 to hold a pointer to the global data
4728 ==> U-Boot will use gp to hold a pointer to the global data
4733 U-Boot runs in system state and uses physical addresses, i.e. the
4741 U-Boot is installed in the first 128 kB of the first Flash bank (on
4744 to the upper end of DRAM. Immediately below the U-Boot code some
4778 In the reset configuration, U-Boot starts at the reset entry point
4781 To be able to re-map memory U-Boot then jumps to its link address.
4785 cache. After that, U-Boot initializes the CPU core, the caches and
4813 U-Boot Porting Guide:
4816 [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
4828 Pay consultant to port U-Boot;
4832 Download latest U-Boot source;
4837 email("Hi, I am new to U-Boot, how do I get started?");
4871 Send patch file to the U-Boot email list;
4890 All contributions to U-Boot should conform to the Linux kernel
4900 Please note that U-Boot is implemented in C (and to some small parts in
4918 Since the number of patches for U-Boot is growing, we need to
4922 Please see http://www.denx.de/wiki/U-Boot/Patches for details.
4951 the U-Boot mailing list, you will avoid most of the common problems
4959 directory of the U-Boot source tree (i. e. please make sure that