| /openbmc/linux/Documentation/maintainer/ |
| H A D | maintainer-entry-profile.rst | 59 wait for the next -rc. At a minimum:
|
| /openbmc/linux/arch/arm/boot/dts/st/ |
| H A D | ste-hrefv60plus.dtsi | 25 /* At 50 degrees take down the CPU frequency */
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-watchdog | 106 At alternate flash the 'access_cs0' sysfs node provides:
|
| H A D | ima_policy | 8 loaded into the run-time of this system. At runtime,
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | verifier.rst | 16 At the start of the program the register R1 contains a pointer to context
59 At the start R1 type is PTR_TO_CTX (a pointer to generic ``struct bpf_context``)
555 * At instruction #2 branching point is reached and state ``{ r0 == 0, r1 == 0, pc == 4 }``
558 * At instruction #4:
564 * At instruction #5 exit is reached and ``checkpoint[0]`` can now be processed
|
| /openbmc/linux/Documentation/driver-api/nvdimm/ |
| H A D | btt.rst | 22 device, and reserves a portion of the underlying storage for its metadata. At
177 the map for that external LBA to point to its new postmap ABA. At this point the
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | source_file_format.txt | 131 single component sub-image (like kernel, ramdisk, etc.). At least one
227 - configuration-sub-node-unit-name : At least one of the configuration
|
| /openbmc/u-boot/dts/ |
| H A D | Kconfig | 127 control. These will be packaged into a FIT. At run-time, U-boot
170 control in the SPL. These will be packaged into a FIT. At run-time,
|
| /openbmc/u-boot/doc/ |
| H A D | README.u-boot_on_efi | 169 The stub application is architecture-dependent. At present it has some
179 The payload can pass information to U-Boot in the form of EFI tables. At
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | unaligned-memory-access.rst | 79 At first, the concepts above may seem a little hard to relate to actual
110 At this point, it should be clear that accessing a single byte (u8 or char)
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | mca.rst | 106 At least that is what is supposed to happen. Alas there are broken
120 At least ia64 makes an attempt at recovering from hardware errors, but
|
| /openbmc/qemu/docs/interop/ |
| H A D | bitmaps.rst | 463 for any operation. At this point, the only valid operation on such bitmaps is
497 #. At a later point, issue incremental backups from ``bitmap0``.
499 At this point, the bitmap and drive backup would be correctly in sync, and
513 #. At a later point, issue incremental backups from ``bitmap0``.
1468 At the conclusion of the above example, ``drive0.inc0.qcow2`` is valid and
1596 At the conclusion of *this* example, both jobs have been aborted due to a
|
| /openbmc/linux/arch/m68k/fpsp040/ |
| H A D | x_unfl.S | 218 | At this point, a store to memory is pending
|
| /openbmc/linux/tools/perf/pmu-events/ |
| H A D | README | 89 At run time, perf determines the actual CPU it is running on, finds the
|
| /openbmc/linux/Documentation/target/ |
| H A D | tcm_mod_builder.rst | 57 At the end of tcm_mod_builder.py. the script will ask to add the following
|
| /openbmc/linux/Documentation/driver-api/virtio/ |
| H A D | virtio.rst | 126 At this point, the virtqueues will be allocated and configured by
|
| /openbmc/linux/Documentation/devicetree/bindings/cpu/ |
| H A D | cpu-capacity.txt | 47 representing CPU capacity expressed in normalized DMIPS/MHz. At boot time, the
|
| /openbmc/linux/Documentation/w1/ |
| H A D | w1-generic.rst | 39 and two byte address. At this step bus is reset and appropriate device
|
| /openbmc/linux/arch/arm/boot/dts/rockchip/ |
| H A D | rk3288-veyron-mickey.dts | 139 /* At very hot, don't let GPU go over 300 MHz */
|
| /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 | 1732 + At entry, *NumBytes contains the total size of the
1734 + At exit, *NumBytes contains the total number of
1769 + At entry, *NumBytes contains the total size of the
1771 + At exit, *NumBytes contains the total number of
2276 + At entry, *NumBytes contains the total size of the
2278 + At exit, *NumBytes contains the total number of
2366 + At entry, *NumBytes contains the total size of the
2368 + At exit, *NumBytes contains the total number of
|
| /openbmc/linux/arch/sh/lib/ |
| H A D | memcpy-sh4.S | 29 ! At the start of each iteration, r7 contains last long load
102 ! At the start of each iteration, r7 contains last long load
|
| /openbmc/qemu/docs/devel/ |
| H A D | reset.rst | 99 group which is being reset has had its *enter* phase executed. At this point
289 removed in the bus hierarchy. At the moment, it occurs only in the raspi
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-bwc.rst | 52 everything is good. At the same time we have a p(5)p(5) = 0.25% chance
58 At the same time, we can say that the worst case deadline miss, will be
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | gadget.rst | 244 found in Linux PDAs, and so on. At this point the device is logically
358 At this writing, a few of the current gadget drivers have been converted
378 At this writing, there are people at work on drivers in this framework
387 the assistance of tools such as GDB running with User Mode Linux. At
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | ras.rst | 171 At read, the *total width* bits code is converted back, using the same
194 On such mode, the same data is written to two memory modules. At read,
880 At the location ``/sys/devices/system/edac`` (sysfs) new edac_device devices
938 At the lowest directory level is the ``block`` directory. There can be 0, 1
1001 (QPI). At the driver, the term "socket" means one QPI. This is
1052 At driver init, all values are set to any.
|