/openbmc/linux/drivers/media/pci/bt8xx/ |
H A D | bttv-audio-hook.c | 60 /* Not much to do here */ in gvbctv3pci_audio() 162 /* Not much to do here */ in avermedia_tvphone_audio() 193 /* Not much to do here */ in avermedia_tv_stereo_audio() 231 /* Not much to do here */ in lt9415_audio() 264 /* Not much to do here */ in terratv_audio() 336 /* Not much to do here */ in pvbt878p9b_audio() 377 /* Not much to do here */ in fv2000s_audio() 413 /* Not much to do here */ in windvr_audio() 450 /* Not much to do here */ in adtvk503_audio()
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 261.out | 180 === Reject too much unknown extra data === 182 qemu-img: Could not open 'TEST_DIR/t.IMGFMT': Too much extra metadata in snapshot table entry 3 185 qemu-img: ERROR failed to read the snapshot table: Too much extra metadata in snapshot table entry 3 189 Discarding too much extra metadata in snapshot table entry 3 (65536 > 1024) 233 === Snapshot table too big with one entry with too much extra data === 237 qemu-img: Could not open 'TEST_DIR/t.IMGFMT': Too much extra metadata in snapshot table entry 505 240 qemu-img: ERROR failed to read the snapshot table: Too much extra metadata in snapshot table entry … 244 Discarding too much extra metadata in snapshot table entry 505 (116944 > 1024)
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | orc-unwinder.rst | 12 format of the ORC data is much simpler than DWARF, which in turn allows 13 the ORC unwinder to be much simpler and faster. 63 ORC debuginfo's advantage over DWARF itself is that it's much simpler. 66 much simpler, meaning fewer bugs, which is especially important for 69 The simpler debuginfo format also enables the unwinder to be much faster 114 annotations are needed than what DWARF would need, so they're much more
|
/openbmc/u-boot/include/configs/ |
H A D | tegra20-common.h | 28 * scriptaddr can be pretty much anywhere that doesn't conflict with something 31 * pxefile_addr_r can be pretty much anywhere that doesn't conflict with 76 * This parameter affects a TXFILLTUNING field that controls how much data is
|
H A D | tegra30-common.h | 24 * scriptaddr can be pretty much anywhere that doesn't conflict with something 27 * pxefile_addr_r can be pretty much anywhere that doesn't conflict with
|
H A D | tegra210-common.h | 23 * scriptaddr can be pretty much anywhere that doesn't conflict with something 26 * pxefile_addr_r can be pretty much anywhere that doesn't conflict with
|
H A D | tegra186-common.h | 26 * scriptaddr can be pretty much anywhere that doesn't conflict with something 29 * pxefile_addr_r can be pretty much anywhere that doesn't conflict with
|
H A D | tegra124-common.h | 29 * scriptaddr can be pretty much anywhere that doesn't conflict with something 32 * pxefile_addr_r can be pretty much anywhere that doesn't conflict with
|
H A D | tegra114-common.h | 27 * scriptaddr can be pretty much anywhere that doesn't conflict with something 30 * pxefile_addr_r can be pretty much anywhere that doesn't conflict with
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/plocate/ |
H A D | plocate_1.1.23.bb | 1 SUMMARY = "plocate, a much faster locate" 3 …s a locate(1) based on posting lists, completely replacing mlocate with a much faster (and smaller…
|
/openbmc/qemu/docs/system/ |
H A D | target-riscv.rst | 12 RISC-V hardware is much more widely varying than x86 hardware. RISC-V 29 Because RISC-V systems differ so much and in fundamental ways, typically 34 cares much less about the detail of the hardware.)
|
H A D | target-arm.rst | 15 Arm hardware is much more widely varying than x86 hardware. Arm CPUs 39 Because Arm systems differ so much and in fundamental ways, typically 44 cares much less about the detail of the hardware.)
|
/openbmc/linux/arch/arm64/kernel/ |
H A D | watchdog_hld.c | 10 * Arm CPUs in the market which are clocked much less than 5 GHz. On the other 11 * hand, we can't make it much higher as it would lead to a large hard-lockup
|
/openbmc/linux/include/linux/ |
H A D | timex.h | 90 * SHIFT_PLL is used as a dampening factor to define how much we 93 * much of the current value in time_offset we correct for each 100 * However this seems to increase convergence time much too long. 114 * SHIFT_FLL is used as a dampening factor to define how much we
|
H A D | zstd.h | 296 * @output: Destination buffer. `output->pos` is updated to indicate how much 298 * @input: Source buffer. `input->pos` is updated to indicate how much data 316 * @output: Destination buffer. `output->pos` is updated to indicate how much 331 * @output: Destination buffer. `output->pos` is updated to indicate how much 383 * @output: Destination buffer. `output.pos` is updated to indicate how much 385 * @input: Source buffer. `input.pos` is updated to indicate how much data was
|
/openbmc/openbmc/poky/meta/recipes-devtools/pseudo/ |
H A D | pseudo_git.bb | 24 # pseudo on 32bit systems is not much of use anyway and these features are not of much
|
/openbmc/linux/Documentation/process/ |
H A D | botching-up-ioctls.rst | 14 actually only used once interfaces. But the clear downside is that there's much 110 paths pretty much for free for graphics drivers. Also, be consistent with 160 an asynchronous event on a pollable file descriptor. It fits much better 208 it's much quicker to push a driver-private interface than engaging in 214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
|
/openbmc/linux/arch/mips/include/asm/ |
H A D | floppy.h | 42 * driver otherwise. It doesn't matter much for performance anyway, as most 47 * Actually this needs to be a bit more complicated since the so much different
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-nice-design.rst | 9 pestered us to make nice +19 tasks use up much less CPU time. 17 much stronger than they were before in 2.4 (and people were happy about 39 So that if someone wanted to really renice tasks, +19 would give a much
|
/openbmc/linux/rust/alloc/collections/ |
H A D | mod.rs | 73 reason = "Uncertain how much info should be exposed", 85 reason = "Uncertain how much info should be exposed", 113 reason = "Uncertain how much info should be exposed",
|
/openbmc/linux/Documentation/ |
H A D | subsystem-apis.rst | 8 from the point of view of a kernel developer. Much of the information here 63 **Fixme**: much more organizational work is needed here.
|
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/gthumb/gthumb/ |
H A D | 283c9483afd1215378c8b9871f51cd61770e53e7.patch | 16 additional code is not much worth it. Hence, use a simpler fix: in case 19 least as much as 'long', there is no precision/value loss.
|
/openbmc/linux/Documentation/powerpc/ |
H A D | kasan.txt | 48 this at run-time based on how much physical memory we have, but this requires 54 requires knowing how much contiguous physical memory a system has _at compile
|
/openbmc/linux/lib/zstd/common/ |
H A D | error_private.c | 29 … case PREFIX(frameParameter_windowTooLarge): return "Frame requires too much memory for decoding"; in ERR_getErrorString() 38 case PREFIX(tableLog_tooLarge): return "tableLog requires too much memory : unsupported"; in ERR_getErrorString()
|
/openbmc/linux/net/batman-adv/ |
H A D | bitarray.c | 60 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet() 72 /* received a much older packet. The other host either restarted in batadv_bit_get_packet()
|