| /openbmc/linux/Documentation/driver-api/ |
| H A D | edac.rst | 18 The individual DRAM chips on a memory stick. These devices commonly
33 stick. Also called as "slot" on several datasheets.
48 just one memory stick when an error occurs, as the error correction code
75 * Single-Ranked stick
77 A Single-ranked stick has 1 chip-select row of memory. Motherboards
78 commonly drive two chip-select pins to a memory stick. A single-ranked
79 stick, will occupy only one of those rows. The other will be unused.
83 * Double-Ranked stick
85 A double-ranked stick has two chip-select rows which access different
88 * Double-sided stick
[all …]
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | dvb-usb-af9005-cardlist.rst | 15 * - Afatech DVB-T USB1.1 stick
17 * - Ansonic DVB-T USB1.1 stick
|
| H A D | dvb-usb-af9035-cardlist.rst | 41 * - EVOLVEO XtraTV stick
|
| /openbmc/qemu/hw/sparc64/ |
| H A D | sparc64.c | 118 cpu_timer_reset(env->stick); in main_cpu_reset()
156 CPUTimer *timer = env->stick; in stick_irq()
285 env->stick = cpu_timer_create("stick", cpu, stick_irq, in sparc64_cpu_devinit()
|
| /openbmc/linux/arch/sparc/include/asm/ |
| H A D | timer_64.h | 48 unsigned int stick[GET_TICK_NINSTR]; member
|
| /openbmc/linux/Documentation/input/ |
| H A D | gamepad.rst | 85 and one analog stick. It reports them as if it were a gamepad with only one
86 analog stick and two trigger buttons on the right side.
150 The left analog-stick is reported as ABS_X, ABS_Y. The right analog stick is
|
| /openbmc/u-boot/arch/x86/lib/ |
| H A D | elf_x86_64_efi.lds | 42 /* the EFI loader doesn't seem to like a .bss section, so we stick
|
| H A D | elf_ia32_efi.lds | 44 * stick it all into .data:
|
| /openbmc/u-boot/arch/arm/lib/ |
| H A D | elf_arm_efi.lds | 37 * stick it all into .data:
|
| H A D | elf_aarch64_efi.lds | 37 * stick it all into .data:
|
| /openbmc/u-boot/arch/riscv/lib/ |
| H A D | elf_riscv32_efi.lds | 39 * stick it all into .data:
|
| H A D | elf_riscv64_efi.lds | 39 * stick it all into .data:
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | pxrc.rst | 15 Many RC controllers is able to configure which stick goes to which channel.
|
| /openbmc/u-boot/arch/sandbox/dts/ |
| H A D | sandbox64.dts | 271 flash-stick {
287 flash-stick {
|
| H A D | test.dts | 654 flash-stick {
670 flash-stick@0 {
676 flash-stick@1 {
682 flash-stick@2 {
|
| H A D | sandbox.dts | 308 flash-stick {
324 flash-stick {
|
| /openbmc/linux/tools/testing/selftests/media_tests/ |
| H A D | regression_test.txt | 25 should stick around until this test exits.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lvm2/ |
| H A D | lvm2.inc | 36 # better to stick to configurations that were actually tested by
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | usb-info.txt | 341 for a hub and a flash stick. These are enough to create a pretend USB bus
359 flash-stick {
370 flash stick to emulate on one of its ports.
377 usb_emul [ + ] | `-- flash-stick
384 'flash-stick' is the emulation device, 'usb_mass_storage' is the real U-Boot
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | modifying-patches.rst | 8 exactly the same in your tree and the submitters'. If you stick strictly to
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | marvell-orion-net.txt | 15 For Orion SoCs we stick to the separation, although there each controller has
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-edac | 92 stick. For rank*/size, this is the size, in MB for one rank
93 of the DIMM memory stick. On single rank memories (1R), this
|
| /openbmc/linux/arch/arm/boot/dts/allwinner/ |
| H A D | sun5i-a10s-auxtek-t003.dts | 49 model = "Auxtek t003 A10s hdmi tv-stick";
|
| H A D | sun5i-a10s-r7-tv-dongle.dts | 50 model = "R7 A10s hdmi tv-stick";
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | sun5i-a10s-auxtek-t003.dts | 49 model = "Auxtek t003 A10s hdmi tv-stick";
|