Home
last modified time | relevance | path

Searched refs:structure (Results 1 – 25 of 74) sorted by relevance

123

/u-boot-v2022.01-rc1/doc/
A DREADME.asn15 and used as a description language for defining data structure in
12 data structure:
13 1) define data structure in a text file (*.asn1)
A DREADME.ubispl17 to load can contain. Used for sizing the scan data structure
22 structure
27 structure
31 scan data structure.
45 2k for the basic data structure
A DREADME.unaligned-memory-access.txt79 structure:
87 Let us assume that an instance of the above structure resides in memory
91 structure, i.e. address 0x10002, but that address is not evenly divisible
96 Therefore, for standard structure types you can always rely on the compiler
109 that you could reorder the fields in the structure in order to place fields
111 resident memory size of structure instances. The optimal layout of the
121 byte of padding at the end of the structure. This padding is added in order
125 structure type. This GCC-specific attribute tells the compiler never to
136 structure padding is of importance.
A DREADME.standalone8 'global_data' structure. The struct members for the jump table are
24 'global_data' structure: r2 on PowerPC, r9 on ARM, k0 on MIPS,
27 structure is passed as 'argv[-1]' pointer.
29 The application can access the 'global_data' structure in the same
A DREADME.Heterogeneous-SoCs44 Global structure updated for dsp cores and other components
70 3. Changes in MPC85xx_SYS_INFO Global structure
73 DSP cores and other device's components have been added in this structure.
A DREADME.udp8 a structure udp_ops (defined in include/net/udp.h) :
A DREADME.JFFS226 structure to find the start of a JFFS2 disk (called partition in the code)
A DREADME.armada-secureboot24 pertaining to the boot process. Furthermore, a eFuse structure (a
247 eFuse structure's values (this option is just needed for programming the eFuse
248 structure; production boot images may disable it).
274 ### Burn eFuse structure
277 | WARNING: Burning the eFuse structure is a irreversible |
286 the eFuse structure to the values needed for the used KAK digest, as well as
290 will write these values to the eFuse structure.
/u-boot-v2022.01-rc1/doc/develop/
A Dglobal_data.rst6 Globally required fields are held in the global data structure. A pointer to the
7 structure is available as symbol gd. The symbol is made available by the macro
51 Global data structure
A Dbloblist.rst10 a central structure. Each record of information is assigned a tag so that its
12 structure defined by the code that owns it.
34 created from a C structure which can beused to access its fields.
45 Single structure
A Dcommands.rst9 Commands are added to U-Boot by creating a new command structure.
11 U_BOOT_CMD_COMPLETE macro to fill in a struct cmd_tbl structure.
154 The structure created is named with a special prefix and placed by
/u-boot-v2022.01-rc1/board/freescale/m53017evb/
A DREADME35 - include/asm-m68k/fec.h FEC structure and definition
36 - include/asm-m68k/fsl_i2c.h I2C structure and definition
37 - include/asm-m68k/global_data.h Global data structure
44 - include/asm-m68k/ptrace.h Exception structure
47 - include/asm-m68k/timer.h Timer structure and definition
49 - include/asm-m68k/uart.h Uart structure and definition
50 - include/asm-m68k/u-boot.h U-Boot structure
/u-boot-v2022.01-rc1/include/linux/
A Dkernel.h283 #define check_member(structure, member, offset) _Static_assert( \ argument
284 offsetof(struct structure, member) == (offset), \
285 "`struct " #structure "` offset for `" #member "` is not " #offset)
/u-boot-v2022.01-rc1/doc/develop/devicetree/
A Dintro.rst33 - link in a UEFI hand-off block structure and put things in there
39 place it can go. It is a highly suitable data structure for just about anything
/u-boot-v2022.01-rc1/board/freescale/m5373evb/
A DREADME34 - include/asm-m68k/fec.h FEC structure and definition
35 - include/asm-m68k/fsl_i2c.h I2C structure and definition
36 - include/asm-m68k/global_data.h Global data structure
43 - include/asm-m68k/ptrace.h Exception structure
46 - include/asm-m68k/timer.h Timer structure and definition
48 - include/asm-m68k/uart.h Uart structure and definition
49 - include/asm-m68k/u-boot.h U-Boot structure
196 bdinfo - print Board Info structure
/u-boot-v2022.01-rc1/doc/device-tree-bindings/net/
A Dmdio.txt14 This example shows the structure used for the external MDIO bus on NXP LS1028A
A Dmdio-mux.txt1 The expected structure of an MDIO MUX device tree node is described here. This
28 Example structure, extracted from Linux bindings document:
A Dmdio-mux-reg.txt15 Example structure, used on Freescale LS1028A QDS board:
/u-boot-v2022.01-rc1/arch/x86/include/asm/arch-apollolake/acpi/
A Dglobalnvs.asl8 * NOTE: The layout of the GNVS structure below must match the layout in
/u-boot-v2022.01-rc1/arch/x86/include/asm/acpi/cros_ec/
A Demem.asl24 BTVR, 8, // Battery structure version
/u-boot-v2022.01-rc1/doc/uImage.FIT/
A Dsource_file_format.txt25 but the support is limited by simple format of the legacy uImage structure.
44 This document defines new uImage structure by providing FDT bindings for new
213 The 'configurations' node has has the following structure:
235 Each configuration has the following structure:
299 Normal kernel FIT image has data embedded within FIT structure. U-Boot image
306 structure and data to 512 byte, other values available for other align size.
/u-boot-v2022.01-rc1/doc/imx/clk/
A Dccf.txt31 * The "central" structure of this patch series is struct udevice and its
59 - Using it would change the original structure of the CCF code.
76 files have been introduced. The latter setups the CCF clock structure for
/u-boot-v2022.01-rc1/scripts/coccinelle/misc/
A Dbadty.cocci68 coccilib.org.print_todo(p[0], "WARNING sizeof argument should be pointer type, not structure type")
/u-boot-v2022.01-rc1/doc/device-tree-bindings/fpga/
A Daltera-socfpga-a10-fpga-mgr.txt30 For details of describing structure and contents of the FIT image,
/u-boot-v2022.01-rc1/doc/imx/habv4/
A Dintroduction_habv4.txt63 The CSF is a binary data structure interpreted by the HAB to guide
65 The CSF structure contains the commands, SRK table, signatures and
125 operations and should be present in the final image structure encapsulated
129 structure. The OTPMK is unique per device and can be accessed by CAAM only.

Completed in 45 milliseconds

123