| /openbmc/linux/include/soc/arc/ |
| H A D | aux.h | 34 #define READ_BCR(reg, into) \ argument
38 if (sizeof(tmp) == sizeof(into)) { \
39 into = *((typeof(into) *)&tmp); \
46 #define WRITE_AUX(reg, into) \ argument
49 if (sizeof(tmp) == sizeof(into)) { \
50 tmp = (*(unsigned int *)&(into)); \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/fltk/fltk/ |
| H A D | fltk-native-link-libdl.patch | 15 0c1c3a771e dlfcn: Move dlopen into libc
16 add8d7ea01 dlfcn: Move dlvsym into libc
17 6dfc0207eb dlfcn: Move dlinfo into libc
18 492560a32e dlfcn: Move dladdr1 into libc
19 6a1ed32789 dlfcn: Move dlmopen into libc
20 77f876c0e3 dlfcn: Move dlsym into libc
21 602252b553 dlfcn: Move dladdr into libc
22 d8cce17d2a dlfcn: Move dlclose into libc
|
| /openbmc/qemu/rust/hw/char/pl011/src/ |
| H A D | device.rs | 206 self.receive_status_error_clear = c.to_be_bytes()[3].into(); in read()
209 return std::ops::ControlFlow::Continue(c.into()); in read()
211 Ok(RSR) => u8::from(self.receive_status_error_clear).into(), in read()
212 Ok(FR) => u16::from(self.flags).into(), in read()
213 Ok(FBRD) => self.fbrd.into(), in read()
214 Ok(ILPR) => self.ilpr.into(), in read()
215 Ok(IBRD) => self.ibrd.into(), in read()
216 Ok(LCR_H) => u16::from(self.line_control).into(), in read()
219 u16::from(self.control).into() in read()
221 Ok(FLS) => self.ifl.into(), in read()
[all …]
|
| H A D | lib.rs | 246 *self = 0.into(); in reset()
252 0.into() in default()
324 let mut ret: Self = 0.into(); in default()
391 *self = 0.into(); in reset()
397 0.into() in default()
538 *self = 0.into(); in reset()
546 let mut ret: Self = 0.into(); in default()
|
| /openbmc/linux/tools/testing/radix-tree/ |
| H A D | test.c | 121 unsigned long into; in item_gang_check_present() local
123 for (into = 0; into < nr; ) { in item_gang_check_present()
128 if (nr_to_find > (nr - into)) in item_gang_check_present()
129 nr_to_find = nr - into; in item_gang_check_present()
132 start + into, nr_to_find); in item_gang_check_present()
135 assert(items[i]->index == start + into + i); in item_gang_check_present()
136 into += hop; in item_gang_check_present()
147 unsigned long into = 0; in item_full_scan() local
154 while ((nfound = radix_tree_gang_lookup(root, (void **)items, into, in item_full_scan()
163 into = this_index; in item_full_scan()
|
| /openbmc/qemu/target/loongarch/ |
| H A D | trace-events | 5 kvm_failed_put_regs_core(const char *msg) "Failed to put core regs into KVM: %s"
7 kvm_failed_put_fpu(const char *msg) "Failed to put fpu into KVM: %s"
9 kvm_failed_put_mpstate(const char *msg) "Failed to put mp_state into KVM: %s"
11 kvm_failed_put_counter(const char *msg) "Failed to put counter into KVM: %s"
13 kvm_failed_put_cpucfg(const char *msg) "Failed to put cpucfg into KVM: %s"
|
| /openbmc/openbmc/meta-raspberrypi/classes/ |
| H A D | sdcard_image-rpi.bbclass | 65 # Additional files and/or directories to be copied into the vfat partition from the IMAGE_ROOTFS.
101 …AME}/* ::/ || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${BOOTFILES_DIR_NAME}/* into boot.img"
103 …${ARMSTUB} ::/ || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/armstubs/${ARMSTUB} into boot.img"
119 … ::${DEST_FILENAME} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${DEPLOY_FILE} into boot.img"
123 … ::${SDIMG_KERNELIMAGE} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/u-boot.bin into boot.img"
124 …MAGE}/boot.scr ::boot.scr || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/boot.scr into boot.img"
126 …mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${INITRAMFS_LINK_NAME}.bin into boot.img"
128 …NEL_IMAGETYPE} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE} into boot.img"
132 …mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${INITRAMFS_LINK_NAME}.bin into boot.img"
134 …G_KERNELIMAGE} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE} into boot.img"
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | idmappings.rst | 14 An idmapping is essentially a translation of a range of ids into another or the
37 idmapping is an order isomorphism from ``U`` into ``K``. So ``U`` and ``K`` are
50 dealing with subsets we can embed idmappings into each other, i.e. we can
126 of userspace ids into a range of kernel ids::
174 immediately translated into a kernel id according to the idmapping associated
212 then translate ``k11000`` into a userspace id in the second idmapping using the
215 /* Map the kernel id up into a userspace id in the second idmapping. */
221 /* Map the userspace id down into a kernel id in the second idmapping. */
224 /* Map the kernel id up into a userspace id in the first idmapping. */
233 into a kernel id according to the idmapping associated with the filesystem.
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-turris-mox-rwtm | 5 Description: (Read) Board version burned into eFuses of this Turris Mox board.
12 Description: (Read) MAC addresses burned into eFuses of this Turris Mox board.
20 as pair to the ECDSA private key burned into eFuses of this
29 during manufacturing and burned into eFuses. Can be 512 or 1024.
36 Description: (Read) Serial number burned into eFuses of this Turris Mox device.
|
| /openbmc/qemu/docs/ |
| H A D | pcie_pci_bridge.txt | 16 can be hot-plugged into appropriate root port (requires additional actions,
18 and supports devices hot-plug into the bridge itself
21 Hot-plug of legacy PCI devices into the bridge
89 - 2 PCIE-PCI bridges plugged into 2 different root ports;
90 - e1000 plugged into the first bridge.
92 - PCIE-PCI bridge, plugged into QEMU generic root port;
93 - 2 e1000 cards, one plugged into the cold-plugged PCIE-PCI bridge,
94 another plugged into the hot-plugged bridge.
98 The PCIE-PCI bridge can be hot-plugged only into pcie-root-port that
102 Windows 7 and older versions don't support hot-plug devices into the PCIE-PCI bridge.
[all …]
|
| H A D | pcie.txt | 26 and allows any PCI/PCI Express device to be plugged into any
28 Plugging a PCI device into a PCI Express slot might not always work and
30 Plugging a PCI Express device into a PCI slot will hide the Extended
34 PCI Express devices should be plugged only into PCI Express Root Ports and
67 2.1.1 To plug a device into pcie.0 as a Root Complex Integrated Endpoint use:
86 Prefer grouping PCI Express Root Ports into multi-function devices
92 Plug only PCI Express devices into PCI Express Ports.
114 2.2.1 Plugging a PCI Express device into a PCI Express Root Port:
121 2.2.3 Plugging a PCI Express device into a Switch:
135 Legacy PCI devices can be plugged into pcie.0 as Integrated Endpoints,
[all …]
|
| /openbmc/u-boot/arch/arm/cpu/armv7/ |
| H A D | cache_v7_asm.S | 28 mov r3, r0, lsr #23 @ move LoC into position
52 ARM( orr r11, r10, r4, lsl r5 ) @ factor way and cache number into r11
54 THUMB( orr r11, r10, r6 ) @ factor way and cache number into r11
55 ARM( orr r11, r11, r9, lsl r2 ) @ factor index number into r11
57 THUMB( orr r11, r11, r6 ) @ factor index number into r11
99 mov r3, r0, lsr #23 @ move LoC into position
122 ARM( orr r11, r10, r4, lsl r5 ) @ factor way and cache number into r11
124 THUMB( orr r11, r10, r6 ) @ factor way and cache number into r11
125 ARM( orr r11, r11, r9, lsl r2 ) @ factor index number into r11
127 THUMB( orr r11, r11, r6 ) @ factor index number into r11
|
| /openbmc/openbmc/meta-security/recipes-ids/suricata/files/ |
| H A D | CVE-2024-38535_pre.patch | 82 + name: "Host".as_bytes().to_vec().into(),
83 + value: "abc.com".as_bytes().to_vec().into(),
91 + name: "Host".as_bytes().to_vec().into(),
92 + value: "efg.net".as_bytes().to_vec().into(),
241 + assert_eq!(hd.name, ":method".as_bytes().to_vec().into());
242 + assert_eq!(hd.value, "GET".as_bytes().to_vec().into());
252 + assert_eq!(hd.name, "accept".as_bytes().to_vec().into());
253 + assert_eq!(hd.value, "*/*".as_bytes().to_vec().into());
263 + assert_eq!(hd.name, ":authority".as_bytes().to_vec().into());
264 + assert_eq!(hd.value, "localhost:3000".as_bytes().to_vec().into());
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | sleep-states.rst | 34 I/O devices into low-power states (possibly lower-power than available in the
58 I/O devices into low-power states, which is done for :ref:`suspend-to-idle
60 are suspended during transitions into this state. For this reason, it should
79 energy savings as everything in the system is put into a low-power state, except
80 for memory, which should be placed into the self-refresh mode to retain its
89 suspended and put into low-power states. In many cases, all peripheral buses
118 It takes three system state changes to put it into hibernation and two system
122 creates a snapshot image of memory to be written into persistent storage. Next,
123 the system goes into a state in which the snapshot image can be saved, the image
124 is written out and finally the system goes into the target low-power state in
[all …]
|
| /openbmc/linux/drivers/accessibility/speakup/ |
| H A D | Kconfig | 55 synthesizer. You can say y to build it into the kernel,
64 synthesizer. You can say y to build it into the kernel,
72 synthesizer. You can say y to build it into the kernel,
80 You can say y to build it into the kernel, or m to
88 synthesizer. You can say y to build it into the kernel,
97 synthesizer. You can say y to build it into the kernel,
106 (old) synthesizer. You can say y to build it into the
140 PC synthesizer. You can say y to build it into the
151 PC synthesizer. You can say y to build it into the
161 LT synthesizer. You can say y to build it into the
[all …]
|
| /openbmc/u-boot/board/wandboard/ |
| H A D | README | 20 Flashing U-Boot into the SD card
24 flashed into the SD card;
30 - Flash the u-boot.img image into the SD card:
34 - Insert the SD card into the slot located in the bottom of the board (same side
|
| /openbmc/linux/drivers/bluetooth/ |
| H A D | Kconfig | 35 Say Y here to compile support for Bluetooth USB devices into the
101 Say Y here to compile support for Bluetooth SDIO devices into the
116 Say Y here to compile support for Bluetooth UART devices into the
285 Say Y here to compile support for HCI BCM203x devices into the
297 Say Y here to compile support for HCI BCM4377 family devices into the
308 Say Y here to compile support for HCI BPA10x devices into the
321 Say Y here to compile support for HCI BFUSB devices into the
334 Say Y here to compile support for HCI DTL1 devices into the
348 Say Y here to compile support for HCI BT3C devices into the
361 Say Y here to compile support for HCI BlueCard devices into the
[all …]
|
| /openbmc/linux/arch/mips/include/asm/mach-ip27/ |
| H A D | kernel-entry-init.h | 36 li t0, 0x1c000 # Offset of text into node memory
37 dsll t1, NASID_SHFT # Shift text nasid into place
43 dsll t1, 6 # Get pfn into place
44 dsll t2, 6 # Get pfn into place
|
| /openbmc/u-boot/doc/ |
| H A D | README.falcon | 14 U-Boot is split into two parts: the SPL (Secondary Program Loader) and U-Boot
19 copies U-Boot image into the memory.
28 With Falcon Mode, this snapshot can be saved into persistent storage and SPL is
33 1. Boot the board into U-Boot.
34 After loading the desired legacy-format kernel image into memory (and DT as
39 2. Save the prepared snapshot into persistent media.
40 The address where to save it must be configured into board configuration
43 3. Boot the board into Falcon Mode. SPL will load the kernel and copy
116 or prepared FDT) from temporary storage in RAM into persistant storage
185 The parameters generated with this step can be saved into NAND at the offset
[all …]
|
| /openbmc/linux/Documentation/trace/ |
| H A D | histogram-design.rst | 158 If a map_entry is unused, meaning no key has yet hashed into it, its | |
451 into the tracing_map_elts' .vars[] array containing variable values. | | |
592 just the index into the var_ref_vals[] array that caches the values of | |
735 index into the tracing_map_elt.vars[] array of the actual variable
765 var.idx (into tracing_map_elt.vars[]): 0
822 var.idx (into tracing_map_elt.vars[]): 0
843 var.idx (into tracing_map_elt.vars[]): 0
845 var_ref_idx (into hist_data->var_refs[]): 0
868 them to generate a new wakeup_latency event into the trace stream.
903 next_pid into the wakeup_latency synthetic event invocation, which
[all …]
|
| /openbmc/linux/drivers/nfc/nfcmrvl/ |
| H A D | Kconfig | 21 into the kernel or say M to compile it as module.
33 into the kernel or say M to compile it as module.
44 into the kernel or say M to compile it as module.
55 into the kernel or say M to compile it as module.
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | trusted-services.md | 10 These files are automatically included into optee-os image accordingly to defined MACHINE_FEATURES.
14 To include TS SPs into optee-os image you need to add into MACHINE_FEATURES
31 …is required. If your platform doesn't include it already you can add `arm-ffa` into MACHINE_FEATUR…
52 Optionally for testing purposes you can add `packagegroup-ts-tests` into your image. It includes
58 See `ci/trusted-services.yml` for an example how to include them into an image.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fs_firmware_loader.txt | 13 and binary) from the storage device in file system format into target location
15 from the target location into FPGA.
81 Load firmware into a previously allocated buffer
92 address of buffer to load firmware into
98 offset of a file for start reading into buffer
105 The firmware is loaded directly into the buffer pointed to by buf
|
| /openbmc/linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 23 An XDP program can use these kfuncs to read the metadata into stack
25 consumers, an XDP program can store it into the metadata area carried
44 An XDP program can store individual metadata items into this ``data_meta``
53 program that redirects XDP frames into the ``AF_XDP`` socket (``XSK``) and
75 into the kernel. The kernel creates the ``skb`` out of the ``xdp_buff``
93 into devmaps and cpumaps.
99 in its ``skb``. If such a packet is later redirected into an ``XSK``,
|
| /openbmc/linux/Documentation/power/ |
| H A D | pci.rst | 31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
46 specific value into one of its standard configuration registers. The second
53 to put the device that sent it into the full-power state. However, the PCI Bus
92 programmed to go into it. The second one, D3cold, is the state that PCI devices
94 to program a PCI device to go into D3cold, although there may be a programmable
95 interface for putting the bus the device is on into a state in which Vcc is
111 programmatically put into D0. Thus the kernel can switch the device back and
[all …]
|