/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/toradex/common/ |
A D | tdx-cfg-block.c | 387 if (it == 'y' || it == 'Y') { in get_cfgblock_interactive() 399 if (it == 'y' || it == 'Y') { in get_cfgblock_interactive() 411 if (it == 'y' || it == 'Y') { in get_cfgblock_interactive() 428 if (it == 'y' || it == 'Y') { in get_cfgblock_interactive() 450 if (it == 'y' || it == 'Y') { in get_cfgblock_interactive() 480 if (it == 'y' || it == 'Y') in get_cfgblock_interactive() 491 if (it == 'y' || it == 'Y') in get_cfgblock_interactive() 499 if (it == 'y' || it == 'Y') in get_cfgblock_interactive() 507 if (it == 'y' || it == 'Y') in get_cfgblock_interactive() 517 if (it == 'y' || it == 'Y') in get_cfgblock_interactive() [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/drivers/clk/aspeed/ |
A D | clk_ast2500.c | 231 struct ast2500_div_config it = { 0, 0, 0 }; in ast2500_calc_clock_config() local 241 for (; it.denum <= max_vals.denum; ++it.denum) { in ast2500_calc_clock_config() 242 for (it.post_div = 0; it.post_div <= max_vals.post_div; in ast2500_calc_clock_config() 243 ++it.post_div) { in ast2500_calc_clock_config() 244 it.num = (rate_khz * (it.post_div + 1) / input_rate_khz) in ast2500_calc_clock_config() 245 * (it.denum + 1); in ast2500_calc_clock_config() 246 if (it.num > max_vals.num) in ast2500_calc_clock_config() 250 * ((it.num + 1) / (it.denum + 1))) in ast2500_calc_clock_config() 251 / (it.post_div + 1); in ast2500_calc_clock_config() 259 *cfg = it; in ast2500_calc_clock_config()
|
/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
|
A D | minnowmax.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 17 else, as the one above does not seem to work, probably because it is not 23 Unzip it::
|
/u-boot/doc/ |
A D | README.bloblist | 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. 22 reading an SoC register. Reading the register may reset the value, so that it 33 change the length of a blob once it has been written. Each blob is normally 49 multiple blobs it does not seem useful to allow multiple bloblists. Of course 51 different memory areas due to fragmented memory, but it is simpler to just have 65 When a part of U-Boot is about to jump to the next part, it can 'finish' the 68 bloblist is in use, changes can be made which will affect the checksum, so it
|
A D | README.fdt-control | 11 make it possible for a single U-Boot binary to support multiple boards, 17 for three reasons. Firstly it is easy to use, being a simple text file. 18 It is extensible since it consists of nodes and properties in a nice 22 compiler checks the text file and converts it to a compact binary 27 and embedding it in your U-Boot image. This is useful since it allows 28 U-Boot to configure itself according to what it finds there. If you have 63 If you want to build your own dtc, it is kept here: 124 If CONFIG_OF_SEPARATE is defined, then it will be built and placed in 138 it and passes it to U-Boot. 140 If CONFIG_OF_HOSTFILE is defined, then it will be read from a file on [all …]
|
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.
|
A D | README.chromium-chainload | 10 placing this information in the U-Boot tree should make it easier to find for 13 Most of these platforms are supported by U-Boot natively, but it is risky to 14 replace the ROM unless you have a servo board and cable to restore it with. 58 used by U-Boot. This is because the Chromebook expects to pass it to the 59 kernel, and crashes if it is not present. 86 6. Start it up 132 fully relocatable, or expect it to hang. 178 7. Start it up 211 Used to make a backup of your firmware, or to replace it. 225 In addition, it has a very unusual design in that it does not do device init [all …]
|
/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/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/uefi/ |
A D | u-boot_on_efi.rst | 14 - You have EFI running on a board but U-Boot does not natively support it 19 requires it in order to provide support 36 memory and type 'help' but that is about it. 72 Trying it out 88 such as a USB stick. Then you can type something like this to start it:: 133 little x86-specific code involved - you can find most of it in 145 except that it has a lot of data attached to it. 152 The stub application is architecture-dependent. At present it has some 157 memory available to it and can operate as it pleases (but see the next 206 use case is not readily apparent, but it might be fun. [all …]
|
/u-boot/board/engicam/common/ |
A D | Kconfig | 8 Enable it in board Kconfig if it uses i.MX6 variant Engicam boards.
|
/u-boot/arch/arm/dts/ |
A D | zynqmp-p-a2197-00-revA.dts | 138 reg_vcc_fmc: tps544@7 { /* u80 - FIXME name - don't know what it does */ 146 reg_vcc_ram: tps544@8 { /* u83 - FIXME name - don't know what it does */ 150 reg_vcc_pslp: tps544@9 { /* u85 - FIXME name - don't know what it does */ 154 reg_vcc_psfp: tps544@a { /* u86 - FIXME name - don't know what it does */ 195 reg_vccaus: tps544@d { /* u88 - FIXME name - don't know what it does */ 203 reg_vcco_500: tps544@f { /* u93 - FIXME name - don't know what it does */ 207 reg_vcco_501: tps544@10 { /* u95 - FIXME name - don't know what it does */ 211 reg_vcco_502: tps544@11 { /* u97 - FIXME name - don't know what it does */ 215 reg_vcco_503: tps544@12 { /* u99 - FIXME name - don't know what it does */ 219 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";
|
A D | dra76x.dtsi | 4 * This program is free software; you can redistribute it and/or modify 5 * it under the terms of the GNU General Public License version 2 as
|
/u-boot/doc/uImage.FIT/ |
A D | beaglebone_vboot.txt | 52 8. Try it 72 # You can add -j10 if you have 10 CPUs to make it faster 86 use. In our case it is am335x-boneblack.dtb and it is built with the kernel. 173 with LZO to make it smaller. 187 gets access to that file they can sign kernels with it. Keep it secure. 245 You can also run fit_check_sign to check it: 301 'dev' and the '+' means that it verified. If it showed '-' that would be bad. 418 Now check it again: 450 with that, but it still needs to be signed, so it won't help. 497 for Linux. Put it into your machine and write U-Boot and the kernel to it. [all …]
|
A D | verified-boot.txt | 7 machine during the boot process to ensure that it is authorised and correct 15 A key point is that it is possible to field-upgrade the software on machines 17 been correctly signed, it is safe to read software from an updatable medium. 59 this key it checks the signature that it finds in the image. If it verifies 92 include hashes to verify images, so it is relatively straightforward to 96 a standard place. Then when a FIT is loaded it can be verified using that
|
/u-boot/lib/efi/ |
A D | Kconfig | 20 U-Boot to it. It allows only very basic functionality, such as a 36 other smaller amounts) and it can never be increased after that. 44 significant problem because it means that you must build a stub with 45 the correct type for EFI to load it correctly. If you are using 47 this may produce no error message - it just won't start!
|
/u-boot/board/bticino/mamoj/ |
A D | MAINTAINERS | 3 M: Raffaele RECALCATI <raffaele.recalcati@bticino.it> 4 M: Simone CIANNI <simone.cianni@bticino.it>
|
/u-boot/doc/develop/ |
A D | trace.rst | 21 which extracts useful information from it. The resulting trace output 30 way of trying out tracing before you use it on your actual board. To do 106 Finally run pytimechart to display it 137 it doesn't have a proper trace buffer. On many boards 175 that it captures most of the board init process, missing only the 185 collects the trace data and writes it somewhere. 192 that you mark this timer (and anything it calls) with 194 use it without causing an infinite loop. 277 here. To convert it into something useful, you can use proftool. 316 (it is common for tracing to add 10% to the time) [all …]
|