/u-boot/doc/develop/ |
A D | designprinciples.rst | 9 Keep it Small 33 Keep it Fast 62 Keep it Simple 68 Keep it Portable 93 Keep it Configurable 110 Keep it Debuggable 139 Keep it Usable 156 U-Boot to be as simple as possible so porting it to and maintaining it on 165 Keep it Maintainable 174 Keep it Beautiful [all …]
|
A D | bloblist.rst | 11 owner can find it and update it. Each record is generally described by a C 12 structure defined by the code that owns it. 24 reading an SoC register. Reading the register may reset the value, so that it 35 change the length of a blob once it has been written. Each blob is normally 51 multiple blobs it does not seem useful to allow multiple bloblists. Of course 53 different memory areas due to fragmented memory, but it is simpler to just have 68 is controlled by `CONFIG_BLOBLIST_ADDR`. But in some cases it is preferable to 73 it is useful to expand the bloblist in U-Boot proper, since it may want to add 75 know anything about the bloblist format, just that it is convenient to use 83 When a part of U-Boot is about to jump to the next part, it can 'finish' the [all …]
|
A D | bootstd.rst | 126 and trying to boot it (-b). 428 bootflows, selecting one, obtaining information about it and booting it. 515 hunters as it goes. 555 checking it. In fact it sits in a loop doing that repeatedly until it finds 578 The maximum value for `method` is `num_methods - 1` so when it exceeds that, it 624 So when `iter_incr()` is called, it increments to the next one and returns it, 629 it indicates to the iterator what it should do when called. It can force moving 632 `BF_NO_MORE_PARTS` it knows that it should immediately move to the next bootdev. 633 When it sees `BF_NO_MORE_DEVICES` it knows that there is nothing more it can do 677 partition. If that works it tries to detect a file system. If that works then it [all …]
|
/u-boot/Licenses/ |
A D | ibm-pibs.txt | 3 copyrights to use it in any way he or she deems fit, including 4 copying it, modifying it, compiling it, and redistributing it either
|
A D | gpl-2.0.txt | 7 of this license document, but changing it is not allowed. 12 freedom to share and change it. By contrast, the GNU General Public 18 the GNU Lesser General Public License instead.) You can apply it to 25 if you want it, that you can change the software or use pieces of it 31 distribute copies of the software, or if you modify it. 67 that is to say, a work containing the Program or a portion of it, 80 source code as you receive it, in any medium, provided that you 91 of it, thus forming a work based on the Program, and copy and 104 when run, you must cause it, when started running for such 187 the Program or works based on it. [all …]
|
/u-boot/board/lego/ev3/ |
A D | README | 13 only and it takes care of low level configuration (PLL and DDR), we don't use 19 * If it is, try to load boot.scr from the first FAT partition 20 * If loading boot.scr was successful, run it 22 * If loading uEnv.txt was successful, import it 23 * If there is a uenvcmd variable (from uEnv.txt), run it 25 * If it was successful, try to load da850-lego-ev3.dtb 26 * If loading uImage was successful, boot it (DT is optional) 46 it on. You can also `run fwupdateboot` in the u-boot shell to reboot into this 50 If you are booting from the microSD card, it is enough to just write uboot.bin
|
/u-boot/arch/arm/dts/ |
A D | fsl-ls1028a-qds-9999-sch-24801-LBRW.dtsi | 16 * - if the QDS has had lane B rework, it is 1st port in slot 2, 17 * - otherwise it is 2nd port in slot 1. 19 * - if DIP SW5[1] = 0 it is 3rd port in slot 1, 20 * - otherwise it is 1st port in slot 3. 22 * - if DIP SW5[2-3] = 00b it is 4th port in slot 1, 23 * - if DIP SW5[2-3] = 01b it is 2nd port in slot 3, 24 * - if DIP SW5[2-3] = 11b it is 1st port in slot 4.
|
A D | zynqmp-p-a2197-00-revA.dts | 154 reg_vcc_fmc: tps544@7 { /* u80 - FIXME name - don't know what it does */ 162 reg_vcc_ram: tps544@8 { /* u83 - FIXME name - don't know what it does */ 166 reg_vcc_pslp: tps544@9 { /* u85 - FIXME name - don't know what it does */ 170 reg_vcc_psfp: tps544@a { /* u86 - FIXME name - don't know what it does */ 211 reg_vccaus: tps544@d { /* u88 - FIXME name - don't know what it does */ 219 reg_vcco_500: tps544@f { /* u93 - FIXME name - don't know what it does */ 223 reg_vcco_501: tps544@10 { /* u95 - FIXME name - don't know what it does */ 227 reg_vcco_502: tps544@11 { /* u97 - FIXME name - don't know what it does */ 231 reg_vcco_503: tps544@12 { /* u99 - FIXME name - don't know what it does */ 235 reg_vcc1v8: tps544@13 { /* u101 - FIXME name - don't know what it does */ [all …]
|
A D | sun50i-h5-libretech-all-h3-it.dts | 6 #include <sunxi-libretech-all-h3-it.dtsi> 10 compatible = "libretech,all-h3-it-h5", "allwinner,sun50i-h5";
|
/u-boot/drivers/clk/aspeed/ |
A D | clk_ast2500.c | 256 struct ast2500_div_config it = { 0, 0, 0 }; in ast2500_calc_clock_config() local 266 for (; it.denum <= max_vals.denum; ++it.denum) { in ast2500_calc_clock_config() 267 for (it.post_div = 0; it.post_div <= max_vals.post_div; in ast2500_calc_clock_config() 268 ++it.post_div) { in ast2500_calc_clock_config() 269 it.num = (rate_khz * (it.post_div + 1) / input_rate_khz) in ast2500_calc_clock_config() 270 * (it.denum + 1); in ast2500_calc_clock_config() 271 if (it.num > max_vals.num) in ast2500_calc_clock_config() 275 * ((it.num + 1) / (it.denum + 1))) in ast2500_calc_clock_config() 276 / (it.post_div + 1); in ast2500_calc_clock_config() 284 *cfg = it; in ast2500_calc_clock_config()
|
/u-boot/lib/efi/ |
A D | Kconfig | 21 U-Boot to it. It allows only very basic functionality, such as a 35 significant problem because it means that you must build a stub with 36 the correct type for EFI to load it correctly. If you are using 38 this may produce no error message - it just won't start! 53 significant problem because it means that you must build a stub with 54 the correct type for EFI to load it correctly. If you are using 56 this may produce no error message - it just won't start! 73 other smaller amounts) and it can never be increased after that.
|
/u-boot/board/synopsys/emsdp/ |
A D | README | 11 Since this board is based on FPGA it's possible to load and use different 18 - The first channel is used for serial debug port (which makes it possible 19 to use a serial connection on pretty much any host machine be it 29 - Also with help of this FTDI chip it is possible to reset entire 35 FAT file-system and uses it for keeping its environment in `uboot.env` 36 file. Note uboot.env is not just a text file but it is auto-generated 45 - This so-called "ROM" is a part of FPGA image and even though it 76 2. Though it is possible to load U-Boot as a simple Elf file via JTAG right 77 in "ROM" and start it from the debugger. One important note here we first
|
/u-boot/doc/board/intel/ |
A D | cherryhill.rst | 7 This uses Intel FSP for Braswell platform. Download it from Intel FSP website, 8 put the .fd file to the board directory and rename it to fsp.bin. 15 BIOS Table (VBT) is shipped. Put it to the board directory and rename it to 29 Register(s) > Register1 Value(Hex). This is is a one-time change. Once set, it
|
A D | bayleybay.rst | 7 This uses as FSP as with Crown Bay, except it is for the Atom E3800 series. 9 the time of writing). Put it in the corresponding board directory and rename 10 it to fsp.bin. 12 Obtain the VGA RAM (Vga.dat at the time of writing) and put it into the same
|
/u-boot/doc/ |
A D | README.generic-board | 47 initialisation is painful since it must be independently added in 10 58 5. While it is a bit of a tricky change, I believe it is worthwhile and 65 for a particular architecture. It also makes it easier to adopt Graeme's 66 initcall proposal when it is ready. 88 I think it is a good target for this series. On the other hand, x86 is 89 relatively small and simple, but different enough that it introduces a 98 #ifdefs to select fields for a particular SOC, so it is hard to 108 to pre-relocation init functions. I think this makes sense, but it can 109 be done as a separate change, and this series does not require it. 117 I have run-tested ARM on Tegra Seaboard only. To try it out, define [all …]
|
A D | README.watchdog | 5 including waiting for a character on a serial port. But it 9 new code, so it must be serviced, but the board would rather it 10 was off. And, it cannot always be turned off once on.
|
/u-boot/board/nvidia/nyan-big/ |
A D | README | 10 To build it, use the nyan-big config. 12 To boot it, connect a USB A-A cable from your computer to the back USB port. 18 The norrin config is close enough that it works well with Nyan.
|
/u-boot/doc/usage/fit/ |
A D | beaglebone_vboot.rst | 54 #. Try it 74 # You can add -j10 if you have 10 CPUs to make it faster 92 use. In our case it is am335x-boneblack.dtb and it is built with the kernel. 180 with LZO to make it smaller. 194 gets access to that file they can sign kernels with it. Keep it secure. 252 You can also run fit_check_sign to check it:: 308 'dev' and the '+' means that it verified. If it showed '-' that would be bad. 425 Now check it again:: 457 with that, but it still needs to be signed, so it won't help. 504 for Linux. Put it into your machine and write U-Boot and the kernel to it. [all …]
|
A D | verified-boot.rst | 10 machine during the boot process to ensure that it is authorised and correct 18 A key point is that it is possible to field-upgrade the software on machines 20 been correctly signed, it is safe to read software from an updatable medium. 63 this key it checks the signature that it finds in the image. If it verifies 98 include hashes to verify images, so it is relatively straightforward to 102 a standard place. Then when a FIT is loaded it can be verified using that
|
A D | index.rst | 7 images that it it reads and boots. Documentation about FIT is available at
|
/u-boot/board/engicam/common/ |
A D | Kconfig | 8 Enable it in board Kconfig if it uses i.MX6 variant Engicam boards.
|
/u-boot/tools/u_boot_pylib/ |
A D | LICENSE | 7 of this license document, but changing it is not allowed. 12 freedom to share and change it. By contrast, the GNU General Public 18 the GNU Lesser General Public License instead.) You can apply it to 25 if you want it, that you can change the software or use pieces of it 31 distribute copies of the software, or if you modify it. 67 that is to say, a work containing the Program or a portion of it, 80 source code as you receive it, in any medium, provided that you 91 of it, thus forming a work based on the Program, and copy and 104 when run, you must cause it, when started running for such 187 the Program or works based on it. [all …]
|
/u-boot/doc/chromium/ |
A D | chainload.rst | 13 placing this information in the U-Boot tree should make it easier to find for 16 Most of these platforms are supported by U-Boot natively, but it is risky to 17 replace the ROM unless you have a servo board and cable to restore it with. 64 used by U-Boot. This is because the Chromebook expects to pass it to the 65 kernel, and crashes if it is not present. 99 6. Start it up 145 fully relocatable, or expect it to hang. 196 7. Start it up 229 Used to make a backup of your firmware, or to replace it. 243 In addition, it has a very unusual design in that it does not do device init [all …]
|
/u-boot/doc/arch/ |
A D | arm64.rst | 16 1. U-Boot can run at any exception level it is entered in, it is 17 recommened to enter it in EL3 if U-Boot takes some responsibilities of a 21 entering the OS. For ARMv8-R it is recommened to enter at S-EL1, as for this 32 Since kernel version 4.2 Linux is more relaxed about the DT location, so it 42 of secondary processors to it and send event to wakeup secondary
|
/u-boot/doc/develop/devicetree/ |
A D | control.rst | 10 This feature aims to make it possible for a single U-Boot binary to support 19 the text file and converts it to a compact binary format, and a library 21 - It is extensible since it consists of nodes and properties in a nice 26 blob and embedding it in the U-Boot image. This is useful since it allows 27 U-Boot to configure itself according to what it finds there. If you have 56 If you want to build your own dtc, it is kept here:: 101 If CONFIG_OF_SEPARATE is defined, then it will be built and placed in 109 it and passes it to U-Boot. 111 If CONFIG_SANDBOX is defined, then it will be read from a file on 131 environment, for example (it will be ignored). After relocation, this [all …]
|