Home
last modified time | relevance | path

Searched full:knowing (Results 1 – 25 of 51) sorted by relevance

123

/Documentation/ABI/testing/
Ddebugfs-ec8 Knowing the EC GPE one can watch the amount of HW events related to
Dsysfs-bus-vfio-mdev72 Userspace applications interested in knowing the name of
85 Userspace applications interested in knowing the details of
Dsysfs-platform-dell-privacy-wmi44 consumed by various applications interested in knowing the Privacy
Dsysfs-bus-pci252 Userspace applications interested in knowing the
267 Userspace applications interested in knowing the
283 Userspace applications interested in knowing the
/Documentation/devicetree/bindings/mailbox/
Damlogic,meson-gxbb-mhu.yaml17 received data. However, there is no specified way of knowing if the sent
Darm,mhu.yaml16 However, there is no specified way of knowing if the sent data has been read
Darm,mhuv3.yaml69 knowing if, or when, the Receiver will act on the Transfer.
/Documentation/arch/powerpc/
Dkasan.txt54 requires knowing how much contiguous physical memory a system has _at compile
/Documentation/devicetree/bindings/gpio/
Dnxp,pcf8575.yaml18 input and reporting a low/high value, without knowing the last value written
/Documentation/arch/arm/
Dporting.rst10 The following symbol definitions rely on you knowing the translation that
/Documentation/driver-api/gpio/
Dintro.rst32 firmware knowing how they're used).
/Documentation/networking/
Dphy-link-topology.rst41 Knowing that some modules embed a PHY, the actual link is more like ::
/Documentation/core-api/
Dprintk-index.rst18 knowing what messages were updated in a particular kernel version and why.
Dmaple_tree.rst65 knowing one value within that range, or mtree_store() call with an entry of
/Documentation/arch/x86/
Dkernel-stacks.rst126 mark, knowing that it's part of the real backtrace.
/Documentation/usb/
Dgadget_multi.rst123 Knowing how MacOS is based on BSD and BSD is an Open Source it is
/Documentation/filesystems/xfs/
Dxfs-self-describing-metadata.rst104 Another key information point in forensic analysis is knowing who the metadata
106 and/or corrupted, and how long ago that it was last modified. Knowing the owner
/Documentation/admin-guide/media/
Dfaq.rst83 knowing how to tune into a single channel is enough for the
Dphilips.rst179 Some points worth knowing:
/Documentation/trace/
Ddebugging.rst61 It can be very useful in knowing what happened up to the point of the crash.
/Documentation/fb/
Dsstfb.rst186 - The 24/32 is not likely to work anytime soon, knowing that the
/Documentation/dev-tools/
Dtesting-overview.rst8 There are a number of different tools for testing the Linux kernel, so knowing
/Documentation/filesystems/bcachefs/
DCodingStyle.rst161 leads to overengineering. Knowing what's useful comes from many years of
/Documentation/hid/
Dhid-sensor.rst162 way to obfuscate the data being communicated by a sensor. Without knowing the
/Documentation/userspace-api/media/mediactl/
Drequest-api.rst29 with different configurations in advance, knowing that the configuration will be

123