Home
last modified time | relevance | path

Searched +full:boot +full:- +full:loader (Results 1 – 25 of 754) sorted by relevance

12345678910>>...31

/openbmc/linux/arch/arm/boot/dts/intel/axm/
H A Daxm5516-cpus.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * arch/arm/boot/dts/axm5516-cpus.dtsi
10 #address-cells = <1>;
11 #size-cells = <0>;
13 cpu-map {
74 compatible = "arm,cortex-a15";
76 clock-frequency = <1400000000>;
77 cpu-release-addr = <0>; // Fixed by the boot loader
82 compatible = "arm,cortex-a15";
84 clock-frequency = <1400000000>;
[all …]
/openbmc/u-boot/arch/arm/mach-omap2/
H A Dconfig.mk2 # Copyright (C) 2011, Texas Instruments, Incorporated - http://www.ti.com/
4 # SPDX-License-Identifier: GPL-2.0+
6 include $(srctree)/arch/arm/mach-omap2/config_secure.mk
9 ifeq ($(CONFIG_TI_SECURE_DEVICE),y) # Refer to README.ti-secure for more info
13 # u-boot-spl_HS_MLO
16 # u-boot-spl_HS_ULO
19 # u-boot-spl_HS_X-LOADER
21 ALL-y += u-boot-spl_HS_MLO
22 ALL-y += u-boot-spl_HS_ULO
23 ALL-y += u-boot-spl_HS_X-LOADER
[all …]
H A Dconfig_secure.mk1 # SPDX-License-Identifier: GPL-2.0+
3 # Copyright (C) 2016, Texas Instruments, Incorporated - http://www.ti.com/
6 ifneq ($(wildcard $(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh),)
8 cmd_mkomapsecimg = $(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh \
9 $(patsubst u-boot-spl_HS_%,%,$(@F)) $< $@ $(CONFIG_ISW_ENTRY_ADDR) \
12 cmd_mkomapsecimg = $(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh \
13 $(patsubst u-boot_HS_%,%,$(@F)) $< $@ $(CONFIG_ISW_ENTRY_ADDR) \
18 "$(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh not found." \
30 ifneq ($(wildcard $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh),)
31 cmd_omapsecureimg = $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh \
[all …]
/openbmc/openbmc/poky/meta/recipes-core/systemd/
H A Dsystemd-bootconf_1.00.bb3 SUMMARY = "Basic systemd-boot configuration files"
5 RPROVIDES:${PN} += "virtual-systemd-bootconf"
8 inherit systemd-boot-cfg
13 LABELS = "boot"
25 install -d ${D}/boot
26 install -d ${D}/boot/loader
27 install -d ${D}/boot/loader/entries
28 install loader.conf ${D}/boot/loader/
29 rm loader.conf
30 install *.conf ${D}/boot/loader/entries/
[all …]
/openbmc/openbmc/poky/scripts/lib/wic/plugins/source/
H A Dbootimg-efi.py4 # SPDX-License-Identifier: GPL-2.0-only
7 # This implements the 'bootimg-efi' source plugin class for 'wic'
31 Create EFI boot partition.
32 This plugin supports GRUB 2 and systemd-boot bootloaders.
35 name = 'bootimg-efi'
46 cp_cmd = "cp -v -p %s/%s %s" % (bootimg_dir, rd, hdddir)
55 cp_cmd = "cp -v -p %s/%s %s" % (bootimg_dir, dtb, hdddir)
62 Create loader-specific (grub-efi) config
88 grubefi_conf += "serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1\n"
89 grubefi_conf += "default=boot\n"
[all …]
H A Dbootimg-biosplusefi.py13 # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
16 # This implements the 'bootimg-biosplusefi' source plugin class for 'wic'
28 Create MBR + EFI boot partition
30 This plugin creates a boot partition that contains both
31 legacy BIOS and EFI content. It will be able to boot from both.
35 Note it is possible to create an image that can boot from both
37 --source bootimg-efi and another one with --source bootimg-pcbios.
42 what to boot. If you have such a BIOS, you need to manually remove the
48 Also, unlike "isoimage-isohybrid" that also does BIOS and EFI, this plugin
52 This plugin is made to put everything into a single /boot partition so it
[all …]
H A Disoimage-isohybrid.py4 # SPDX-License-Identifier: GPL-2.0-only
7 # This implements the 'isoimage-isohybrid' source plugin class for 'wic'
32 Legacy boot uses syslinux and EFI boot uses grub or gummiboot (not
38 part /boot --source isoimage-isohybrid --sourceparams="loader=grub-efi, \\
39 image_name= IsoImage" --ondisk cd --label LIVECD
40 bootloader --timeout=10 --append=" "
42 In --sourceparams "loader" specifies the bootloader used for booting in EFI
44 example above, wic creates an ISO image named IsoImage-cd.direct (default
45 extension added by direct imeger plugin) and a file named IsoImage-cd.iso
48 name = 'isoimage-isohybrid'
[all …]
/openbmc/u-boot/doc/device-tree-bindings/misc/
H A Dfs_loader.txt1 * File system firmware loader
4 --------------------
6 - compatible: should contain "u-boot,fs-loader"
7 - phandlepart: which block storage device and partition the image loading from,
9 32-bit array. For example phandlepart=<&mmc_0 1>, meaning use
11 - mdtpart: which partition of ubi the image loading from, this property is
13 - ubivol: which volume of ubi the image loading from, this property is required
22 fs_loader0: fs-loader@0 {
23 u-boot,dm-pre-reloc;
24 compatible = "u-boot,fs-loader";
[all …]
/openbmc/linux/Documentation/arch/arm/
H A Dbooting.rst9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
11 In order to boot ARM Linux, you require a boot loader, which is a small
12 program that runs before the main kernel. The boot loader is expected
16 Essentially, the boot loader should provide (as a minimum) the
28 ---------------------------
30 Existing boot loaders:
32 New boot loaders:
35 The boot loader is expected to find and initialise all RAM that the
39 the RAM in the machine, or any other method the boot loader designer
44 -----------------------------
[all …]
/openbmc/u-boot/doc/
H A DREADME.ti-secure1 README on how boot images are created for secure TI devices
4 Secure TI devices require a boot image that is authenticated by ROM
6 device is essentially useless. In order to create a valid boot image for
10 Information on the details on the complete boot image format can be obtained
11 from Texas Instruments. The tools used to generate boot images for secure
22 Booting of U-Boot SPL
25 When CONFIG_TI_SECURE_DEVICE is set, the U-Boot SPL build process
27 viable boot image. The build process will look for the environment
36 ${TI_SECURE_DEV_PKG}/scripts/create-boot-image.sh
38 This is called as part of the SPL/u-boot build process. As the secure
[all …]
/openbmc/u-boot/doc/driver-model/
H A Dfs_firmware_loader.txt3 # SPDX-License-Identifier: GPL-2.0
8 This is file system firmware loader for U-Boot framework, which has very close
10 to https://01.org/linuxgraphics/gfx-docs/drm/driver-api/firmware/index.html.
12 File system firmware loader can be used to load whatever(firmware, image,
17 To enable firmware loader, CONFIG_FS_LOADER need to be set at
20 Firmware Loader API core features
21 ---------------------------------
24 -------------------------------------------------------
26 firmware loading from to the firmware loader driver, those data could be
27 defined in fs-loader node as shown in below:
[all …]
/openbmc/qemu/docs/system/
H A Dguest-loader.rst4 Guest Loader
5 ------------
7 The guest loader is similar to the ``generic-loader`` although it is
10 hoops of firmware and boot-loaders.
12 The guest loader does two things:
14 - load blobs (kernels and initial ram disks) into memory
15 - sets platform FDT data so hypervisors can find and boot them
17 This is what is typically done by a boot-loader like grub using its
18 multi-boot capability. A typical example would look like:
20 .. parsed-literal::
[all …]
H A Dgeneric-loader.rst5 the COPYING file in the top-level directory.
7 Generic Loader
8 --------------
10 The 'loader' device allows the user to load multiple images or values into
15 The loader device allows memory values to be set from the command line. This
18 -device loader,addr=<addr>,data=<data>,data-len=<data-len> \
19 [,data-be=<data-be>][,cpu-num=<cpu-num>]
28 ``<data-len>``
32 ``<data-be>``
36 ``<cpu-num>``
[all …]
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dsystemd-boot.bbclass3 # SPDX-License-Identifier: MIT
5 # systemd-boot.bbclass - The "systemd-boot" is essentially the gummiboot merged into systemd.
9 # Set EFI_PROVIDER = "systemd-boot" to use systemd-boot on your live images instead of grub-efi
10 # (images built by image-live.bbclass)
12 do_bootimg[depends] += "${MLPREFIX}systemd-boot:do_deploy"
14 require conf/image-uefi.conf
16 inherit fs-uuid
21 # systemd-boot requires these paths for configuration files
23 install -d ${DEST}/loader
24 install -d ${DEST}/loader/entries
[all …]
/openbmc/u-boot/doc/device-tree-bindings/
H A Dchosen.txt2 ---------------
7 stdout-path property
8 --------------------
9 Device trees may specify the device to be used for boot console output
10 with a stdout-path property under /chosen.
13 -------
16 stdout-path = "/serial@f00:115200";
20 compatible = "vendor,some-uart";
25 tick-timer property
26 -------------------
[all …]
/openbmc/linux/Documentation/arch/x86/
H A Dboot.rst1 .. SPDX-License-Identifier: GPL-2.0
4 The Linux/x86 Boot Protocol
7 On the x86 platform, the Linux kernel uses a rather complicated boot
12 real-mode DOS as a mainstream operating system.
14 Currently, the following versions of the Linux/x86 boot protocol exist.
22 boot loader and the kernel. setup.S made relocatable,
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
31 safe for systems which use the EBDA from SMM or 32-bit
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
44 the boot command line.
[all …]
/openbmc/u-boot/board/hisilicon/poplar/
H A DREADME6 integrated quad-core 64-bit ARM Cortex A53 processor and high
8 set-top solution based on Linux or Android. Its high performance
13 CPU Quad-core ARM Cortex-A53 64 bit
14 DRAM DDR3/3L/4 SDRAM interface, maximum 32-bit data width 2 GB
16 CONSOLE USB-micro port for console support
19 JTAG 8-Pin JTAG
33 U-boot has a *strong* dependency with the l-loader and the arm trusted firmware
36 The boot sequence is:
37 l-loader --> arm_trusted_firmware --> u-boot
39 U-Boot needs to be aware of the BL31 runtime location and size to avoid writing
[all …]
/openbmc/u-boot/doc/uImage.FIT/
H A Dx86-fit-boot.txt5 ----------
10 binary which contains all sorts of parameters and a compressed self-extracting
11 binary for the kernel itself, often with a small built-in serial driver to
15 understanding is that an x86 CPU (even a really new one) starts up in a 16-bit
16 'real' mode where only 1MB of memory is visible, moves to 32-bit 'protected'
18 then to 64-bit 'long' mode if 64-bit execution is required.
20 Partly the self-extracting nature of Linux was introduced to cope with boot
21 loaders that were barely capable of loading anything. Even changing to 32-bit
25 Bit by bit more and more logic has been added to this post-boot pre-Linux
28 - Changing to 32-bit mode
[all …]
/openbmc/qemu/docs/system/arm/
H A Dxlnx-versal-virt.rst1 Xilinx Versal Virt (``xlnx-versal-virt``)
4 Xilinx Versal is a family of heterogeneous multi-core SoCs
10 https://www.xilinx.com/products/silicon-devices/acap/versal.html
22 - 2 ACPUs (ARM Cortex-A72)
26 - Interrupt controller (ARM GICv3)
27 - 2 UARTs (ARM PL011)
28 - An RTC (Versal built-in)
29 - 2 GEMs (Cadence MACB Ethernet MACs)
30 - 8 ADMA (Xilinx zDMA) channels
31 - 2 SD Controllers
[all …]
H A Daspeed.rst1 …-evb``, ``ast2600-evb``, ``ast2700-evb``, ``bletchley-bmc``, ``fuji-bmc``, ``fby35-bmc``, ``fp5280…
6 Aspeed SoC : the AST2400 integrating an ARM926EJ-S CPU (400MHz), the
8 with dual cores ARM Cortex-A7 CPUs (1.2GHz) and more recently the AST2700
9 with quad cores ARM Cortex-A35 64 bits CPUs (1.6GHz)
16 - ``palmetto-bmc`` OpenPOWER Palmetto POWER8 BMC
17 - ``quanta-q71l-bmc`` OpenBMC Quanta BMC
18 - ``supermicrox11-bmc`` Supermicro X11 BMC (ARM926EJ-S)
19 - ``supermicrox11spi-bmc`` Supermicro X11 SPI BMC (ARM1176)
23 - ``ast2500-evb`` Aspeed AST2500 Evaluation board
24 - ``romulus-bmc`` OpenPOWER Romulus POWER9 BMC
[all …]
/openbmc/u-boot/board/boundary/nitrogen6x/
H A DREADME.mx6qsabrelite1 U-Boot for the Freescale i.MX6q SabreLite board
4 This file contains information for the port of U-Boot to the Freescale
9 --------
11 To build U-Boot for the SabreLite board:
17 2. Boot from SD card
18 --------------------
20 The SabreLite boards boot from the SPI NOR flash. These boards need their SPI
21 to be reflashed with a small SD card loader to support boot from SD card. The
22 board will still boot from SPI NOR, but the loader will in turn request the
23 BootROM to load the U-Boot from SD card.
[all …]
/openbmc/linux/Documentation/admin-guide/
H A Defi-stub.rst2 The EFI Boot Stub
8 along with the EFI-specific entry point that the firmware loader
9 jumps to are collectively known as the "EFI boot stub", and live in
10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c,
12 arch/arm/boot/compressed/efi-header.S and
13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared
18 kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
19 and drivers/firmware/efi/libstub/arm64-stub.c.
21 By using the EFI boot stub it's possible to boot a Linux kernel
22 without the use of a conventional EFI boot loader, such as grub or
[all …]
/openbmc/linux/arch/riscv/boot/
H A DMakefile2 # arch/riscv/boot/Makefile
5 # architecture-specific flags and dependencies.
14 # Based on the ia64 and arm64 boot/Makefile.
19 OBJCOPYFLAGS_Image :=-O binary -R .note -R .note.gnu.build-id -R .comment -S
20 OBJCOPYFLAGS_loader.bin :=-O binary
21 OBJCOPYFLAGS_xipImage :=-O binary -R .note -R .note.gnu.build-id -R .comment -S
23 targets := Image Image.* loader loader.o loader.lds loader.bin
24 targets := Image Image.* loader loader.o loader.lds loader.bin xipImage
39 …@ (! [ -f vmlinux.relocs ] && echo "vmlinux.relocs can't be found, please remove vmlinux and try a…
50 $(obj)/loader.o: $(src)/loader.S $(obj)/Image
[all …]
/openbmc/openbmc/poky/meta/recipes-core/initrdscripts/files/
H A Dinit-install-efi-testfs.sh1 #!/bin/sh -e
11 # We need 200 Mb for the boot partition
22 if [ -e /sys/block/${device}/removable ]; then
61 rm -f /etc/udev/rules.d/automount.rules
62 rm -f /etc/udev/scripts/mount*
69 mkdir -p /tmp
72 disk_size=$(parted /dev/${device} unit mb print | grep '^Disk .*: .*MB' | cut -d" " -f 3 | sed -e "…
75 rootfs_size=$((disk_size-boot_size-testfs_size))
95 echo "Boot partition size: $boot_size MB ($bootfs)"
105 echo "Creating boot partition on $bootfs"
[all …]
/openbmc/u-boot/board/hisilicon/hikey/
H A DREADME4 HiKey is the first certified 96Boards Consumer Edition board. The board/SoC has: -
5 * HiSilicon Kirin 6220 eight-core ARM Cortex-A53 64-bit SoC running at 1.2GHz.
6 * ARM Mali 450-MP4 GPU
12 The HiKey schematic can be found here: -
13 https://github.com/96boards/documentation/blob/master/consumer/hikey/hikey620/hardware-docs/HiKey_s…
15 The SoC datasheet can be found here: -
16 …boards/documentation/blob/master/consumer/hikey/hikey620/hardware-docs/Hi6220V100_Multi-Mode_Appli…
18 Currently the u-boot port supports: -
24 The HiKey U-Boot port has been tested with l-loader, booting ATF, which then boots
25 U-Boot as the bl33.bin executable.
[all …]

12345678910>>...31