| /openbmc/libcper/specification/document/ |
| H A D | cper-json-specification.tex | 45 This document lays out a structure for representing UEFI CPER records, as described in UEFI Appendi…
56 This structure contains descriptions of the CPER log header, as well as the section descriptors and
57 section structures themselves within arrays, representing a full CPER log. This is the structure re…
59 % Parent structure (type 1) table.
61 header & object & A CPER header structure as defined in Section \ref{section:headerstructure}. \\
66 \jsontableend{Parent structure (type 1) field table.}
70 This structure contains a single section descriptor and section, representing a single section CPER…
71 This is the structure returned by \texttt{cper\_single\_section\_to\_ir(FILE* cper\_file)} as JSON …
73 % Parent structure (type 2) table.
78 \jsontableend{Parent structure (type 2) field table.}
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | var_funcs.py | 729 def nested_get(key_name, structure): argument
765 if type(structure) is list:
766 for entry in structure:
769 elif gp.is_dict(structure):
770 for key, value in structure.items():
778 def match_struct(structure, match_dict, regex=False): argument
816 struct_key_values = nested_get(match_key, structure)
838 def filter_struct(structure, filter_dict, regex=False, invert=False): argument
902 if type(structure) is list:
904 for element in structure:
[all …]
|
| /openbmc/u-boot/board/freescale/m52277evb/ |
| H A D | README | 32 - include/asm-m68k/crossbar.h CrossBar structure and definition
33 - include/asm-m68k/dspi.h DSPI structure and definition
34 - include/asm-m68k/edma.h eDMA structure and definition
35 - include/asm-m68k/flexbus.h FlexBus structure and definition
36 - include/asm-m68k/fsl_i2c.h I2C structure and definition
37 - include/asm-m68k/global_data.h Global data structure
41 - include/asm-m68k/lcd.h LCD structure and definition
45 - include/asm-m68k/ptrace.h Exception structure
47 - include/asm-m68k/ssi.h SSI structure and definition
49 - include/asm-m68k/timer.h Timer structure and definition
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 108.out | 12 Rebuilding refcount structure
34 Rebuilding refcount structure
67 Rebuilding refcount structure
84 Rebuilding refcount structure
100 Rebuilding refcount structure
120 Rebuilding refcount structure
142 Rebuilding refcount structure
183 Rebuilding refcount structure
|
| H A D | 286.out | 6 Output structure:
|
| H A D | 098.out | 35 Rebuilding refcount structure
49 Rebuilding refcount structure
|
| /openbmc/u-boot/doc/ |
| H A D | README.ubispl | 17 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
|
| H A D | README.bloblist | 10 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
|
| H A D | README.m54418twr | 35 - arch/m68k/include/asm/fec.h FEC structure and definition
36 - arch/m68k/include/asm/global_data.h Global data structure
43 - arch/m68k/include/asm/ptrace.h Exception structure
46 - arch/m68k/include/asm/timer.h Timer structure and definition
48 - arch/m68k/include/asm/uart.h Uart structure and definition
49 - arch/m68k/include/asm/u-boot.h u-boot structure
194 bdinfo - print Board Info structure
|
| H A D | README.unaligned-memory-access.txt | 79 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.
|
| H A D | README.standalone | 8 '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
|
| H A D | README.Heterogeneous-SoCs | 44 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.
|
| /openbmc/u-boot/board/freescale/m53017evb/ |
| H A D | README | 35 - 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
|
| /openbmc/u-boot/board/freescale/m547xevb/ |
| H A D | README | 41 - include/asm-m68k/fec.h FEC structure and definition
42 - include/asm-m68k/fsl_i2c.h I2C structure and definition
43 - include/asm-m68k/fsl_mcddmafec.h DMA FEC structure and definition
44 - include/asm-m68k/global_data.h Global data structure
51 - include/asm-m68k/ptrace.h Exception structure
54 - include/asm-m68k/timer.h Timer structure and definition
56 - include/asm-m68k/uart.h Uart structure and definition
57 - include/asm-m68k/u-boot.h U-Boot structure
217 bdinfo - print Board Info structure
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/lowpan-tools/lowpan-tools/ |
| H A D | 0001-addrdb-coord-config-parse.y-add-missing-time.h-inclu.patch | 9 The %union definition uses the time_t structure. In order to use this
10 structure, the <time.h> header has to be included. Otherwise, the build
|
| /openbmc/openpower-vpd-parser/docs/ |
| H A D | system-config-json.md | 3 ## TODO: Add description about structure of system config json
|
| H A D | backup-restore-config-json.md | 3 ## TODO: Add description about structure of backup and restore config json
|
| /openbmc/qemu/docs/ |
| H A D | image-fuzzer.txt | 27 Test images are generated from scratch and have valid inner structure with some
66 Each sublist can have one or two strings defining image structure elements.
177 3. Image template should describe a general structure invariant for all
183 6. Should generate the test image with the correct structure based on an image
190 for test case specification, e.g. group of tests for header structure,
220 specified via an action vector. Otherwise, knowledge about an image structure
231 Action vector is a sequence of structure elements retrieved from an image
234 Action pool is all available elements of an image structure that generated
236 Image template is a formal description of an image structure and relations
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | index.rst | 16 structure
|
| /openbmc/u-boot/include/ |
| H A D | common.h | 550 #define check_member(structure, member, offset) _Static_assert( \ argument
551 offsetof(struct structure, member) == offset, \
552 "`struct " #structure "` offset for `" #member "` is not " #offset)
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-frozenlist_1.6.0.bb | 1 SUMMARY = "A list-like structure which implements collections.abc.MutableSequence, and which can be…
|
| H A D | python3-portion_2.6.0.bb | 1 DESCRIPTION = "Python data structure and operations for intervals"
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-obtain.rst | 76 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
78 ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`"
105 :ref:`structure-core-script` environment
180 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
182 ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`"
259 The following figure shows the resulting directory structure after you
284 The following figure shows the resulting directory structure after you
292 The installed directory structure for the extensible SDK is quite
293 different than the installed structure for the standard SDK. The
298 Of note in the directory structure are an environment setup script for
|
| H A D | using.rst | 34 usage. You can see the directory structure in the
35 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
120 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
121 section for more details on the resulting directory structure of the installed
146 ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`"
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | of-plat.txt | 62 - The platform data is provided to drivers as a C structure. The driver
63 must use the same structure to access the data. Since a driver
185 structure is not available when device tree is used. It would make no sense
186 to use this structure if device tree were available, since the structure has
189 Therefore it is recommended that the of-platdata structure should be used
195 How to structure your driver
270 The of-platdata struct contents is copied from the C structure data to the
|