/openbmc/linux/Documentation/devicetree/bindings/thermal/ |
H A D | thermal-zones.yaml | 35 max dT/dt, such that a device does not cross several trip boundaries
|
/openbmc/linux/Documentation/core-api/ |
H A D | asm-annotations.rst | 122 object files as the tools can trivially find exact function boundaries.
|
H A D | unaligned-memory-access.rst | 169 able to access memory on arbitrary boundaries, the reference to a[0] causes
|
H A D | dma-api-howto.rst | 399 like queue heads needing to be aligned on N byte boundaries. 412 must not cross 4KByte boundaries (but at that time it may be better to
|
/openbmc/linux/Documentation/filesystems/caching/ |
H A D | netfs-api.rst | 413 going to be written (it doesn't have to align to page boundaries necessarily, 414 but it does have to align to DIO boundaries on the backing filesystem). The
|
/openbmc/linux/Documentation/power/ |
H A D | userland-swsusp.rst | 122 - read()s across page boundaries are impossible (ie. if you read() 1/2 of
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | kickstart.rst | 142 says to start partitions on boundaries given x KBytes.
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | xfs.rst | 148 boundaries. This is only relevant to filesystems created 200 Data allocations will be rounded up to stripe width boundaries
|
/openbmc/u-boot/tools/binman/ |
H A D | README | 111 with device boundaries, such as the read-only/read-write separation in SPI 136 the boundaries between building input files (mkimage) and packaging then 751 requirments (alignment, spacing, device boundaries) and other required
|
/openbmc/linux/Documentation/networking/ |
H A D | kcm.rst | 78 A TCP stream must be parsed to determine message boundaries. Berkeley Packet
|
/openbmc/linux/Documentation/timers/ |
H A D | timekeeping.rst | 129 The sched_clock() function may wrap only on unsigned long long boundaries,
|
/openbmc/u-boot/doc/ |
H A D | README.unaligned-memory-access.txt | 163 able to access memory on arbitrary boundaries, the reference to a[0] causes
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | crop.rst | 92 capture boundaries and the driver may further adjust the requested size
|
H A D | control.rst | 221 - Emboss, the highlights and shadows replace light/dark boundaries
|
/openbmc/bmcweb/ |
H A D | DEVELOPING.md | 29 - All buffer boundaries must be checked before indexing or using values
|
/openbmc/linux/Documentation/filesystems/ |
H A D | nilfs2.rst | 252 To stride over segment boundaries, this sequence of files may be split
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 171.out | 299 checking boundaries
|
/openbmc/linux/Documentation/driver-api/media/ |
H A D | mc-core.rst | 30 not be confused with physical pins at chip boundaries.
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | gadget.rst | 225 packet boundaries are visible to drivers. Compared to RS-232 serial 232 protocols where packet boundaries (and "short packets") are not
|
/openbmc/qemu/docs/system/devices/ |
H A D | nvme.rst | 198 Set to ``on`` to allow reads to cross zone boundaries.
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | kfence.rst | 256 page boundaries selected at random. The pages to the left and right of the
|
/openbmc/linux/Documentation/process/ |
H A D | botching-up-ioctls.rst | 34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/uefi/files/n1sdp/ |
H A D | 0005-Platform-ARM-N1Sdp-NOR-flash-Dxe-Driver-for-N1Sdp.patch | 103 + // Ensure the Variable areas are aligned on block size boundaries. 1223 + // The write must not span block boundaries. 2323 + // The read must not span block boundaries.
|
/openbmc/linux/Documentation/driver-api/nvdimm/ |
H A D | nvdimm.rst | 458 A REGION, after resolving DPA aliasing and LABEL specified boundaries, surfaces
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-energy.rst | 94 cpuset configurations. Since the boundaries of exclusive cpusets do not
|