Searched refs:these (Results 1 – 25 of 1782) sorted by relevance
12345678910>>...72
| /linux-6.6.21/Documentation/admin-guide/ |
| D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
|
| /linux-6.6.21/fs/jffs2/ |
| D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /linux-6.6.21/Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /linux-6.6.21/drivers/scsi/arm/ |
| D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
40 Acorn system with one of these, say Y. If unsure, say N.
47 system with one of these, say Y, otherwise say N.
54 you have one of these, say Y. If unsure, say N.
65 Acorn system with one of these, say Y. If unsure, say N.
73 system with one of these, say Y. If unsure, say N.
|
| /linux-6.6.21/Documentation/virt/kvm/x86/ |
| D | errata.rst | 27 Clearing these bits in CPUID has no effect on the operation of the guest;
28 if these bits are set on hardware, the features will not be present on
31 **Workaround:** It is recommended to always set these bits in guest CPUID.
32 Note however that any software (e.g ``WIN87EM.DLL``) expecting these features
33 to be present likely predates these CPUID feature bits, and therefore
|
| /linux-6.6.21/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /linux-6.6.21/Documentation/trace/coresight/ |
| D | coresight-perf.rst | 40 If you see these above, then your system is tracing CoreSight data
94 minimum level of functionality is met. The scripts that launch these
105 CoreSight support or remove these binaries in order to not have these
123 multiple times and all these csv files will have more and more data
127 This means sometimes these tests fail as they don't capture all the
132 Be aware that some of these tests take quite a while to run, specifically
136 You can change where these csv logs are stored by setting the
156 You may wish to set these above environment variables if you wish to
|
| /linux-6.6.21/Documentation/userspace-api/media/v4l/ |
| D | vidioc-dbg-g-register.rst | 43 For driver debugging purposes these ioctls allow test applications to
50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
75 when a driver supports these ioctls it must also support
77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
83 We recommended the v4l2-dbg utility over calling these ioctls directly.
160 these ioctls.
|
| /linux-6.6.21/Documentation/arch/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
71 As the 'pdata' in the above examples indicates, these functions are
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
120 frequency. The OMAP PM interface contains functions for these
148 in these cases, the board file needs to do additional steps as follows:
|
| /linux-6.6.21/arch/mips/jazz/ |
| D | Kconfig | 8 kernel that runs on these, say Y here. For details about Linux on
19 kernel that runs on these, say Y here. For details about Linux on
29 kernel that runs on these, say Y here. For details about Linux on
|
| /linux-6.6.21/fs/nls/ |
| D | Kconfig | 46 codepage if you want to be able to read/write these filenames on
58 codepage if you want to be able to read/write these filenames on
70 codepage if you want to be able to read/write these filenames on
83 codepage if you want to be able to read/write these filenames on
99 codepage if you want to be able to read/write these filenames on
104 characters for these languages: Albanian, Croatian, Czech, English,
114 codepage if you want to be able to read/write these filenames on
125 codepage if you want to be able to read/write these filenames on
136 codepage if you want to be able to read/write these filenames on
147 codepage if you want to be able to read/write these filenames on
[all …]
|
| /linux-6.6.21/Documentation/admin-guide/perf/ |
| D | qcom_l3_pmu.rst | 6 Centriq SoCs. The L3 cache on these SOCs is composed of multiple slices, shared
12 options in sysfs, see /sys/devices/l3cache*. Given that these are uncore PMUs
25 Given that these are uncore PMUs the driver does not support sampling, therefore
|
| /linux-6.6.21/Documentation/admin-guide/sysctl/ |
| D | user.rst | 18 The primary purpose of these limits is to stop programs that
21 intention that the defaults of these limits are set high enough that
22 no program in normal operation should run into these limits.
36 Currently, these files are in /proc/sys/user:
|
| /linux-6.6.21/Documentation/arch/sh/ |
| D | register-banks.rst | 21 in mind when writing code that utilizes these banked registers, for obvious
22 reasons. Userspace is also not able to poke at the bank1 values, so these can
25 Presently the kernel uses several of these registers.
|
| /linux-6.6.21/Documentation/arch/x86/ |
| D | iommu.rst | 32 PS2 emulation. The regions of memory used for these devices are marked
34 regions will fail. Hence BIOS uses RMRR to specify these regions along with
35 devices that need to access these regions. OS is expected to setup
36 unity mappings for these regions for these devices to access these regions.
|
| /linux-6.6.21/Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
93 requesting these two separate cpu features to be enabled. The current KVM
95 these userspace flags are checked before enabling pointer authentication.
97 if support is added in the future to allow these two features to be
104 Additionally, when these vcpu feature flags are not set then KVM will
|
| /linux-6.6.21/Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
130 given even to these.) For example, loading a filesystem module via an
170 hole at the bottom of the stack to catch these overflows.
[all …]
|
| /linux-6.6.21/arch/m68k/ifpsp060/src/ |
| D | README-SRC | 9 You don't need to actually assemble these files in order to compile a
11 are sufficient and were generated from these source files by
|
| /linux-6.6.21/drivers/platform/x86/intel/atomisp2/ |
| D | Kconfig | 16 driver for these, so they do not work as a camera. Some of these
19 Some of these devices have a firmware issue where the LED gets turned
|
| /linux-6.6.21/fs/crypto/ |
| D | Kconfig | 28 # disable these generic implementations if corresponding optimized
29 # implementations will always be available too; for this reason, these are soft
30 # dependencies ('imply' rather than 'select'). Only disable these generic
|
| /linux-6.6.21/Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 51 these pins. One register is the output enable register
54 you can get/set the status if these pins. They can be used for input
57 Most grabber board vendors use these pins to control an external chip
65 line for your board. The important fields are these two::
76 (``BT848_GPIO_OUT_EN``) will be set as these pins must be driven by the
87 card installed, you might to check out if you can read these registers
|
| /linux-6.6.21/Documentation/hwmon/ |
| D | ucd9000.rst | 39 interrupts, cascading, or other system functions. Twelve of these pins offer PWM
40 functionality. Using these pins, the UCD90124 offers support for fan control,
47 functions. Twelve of these pins offer PWM functionality. Using these pins, the
60 functions. Ten of these pins offer PWM functionality. Using these pins, the
|
| /linux-6.6.21/scripts/ |
| D | checksyscalls.sh | 226 /* these can be expressed using other calls */
254 /* 64-bit ports never needed these, and new 32-bit ports can use statx */
|
| /linux-6.6.21/drivers/staging/ |
| D | Kconfig | 8 them. Please note that these drivers are under heavy
13 Using any of these drivers will taint your kernel which might
17 If you wish to work on these drivers, to help improve them, or
|
| /linux-6.6.21/Documentation/networking/ |
| D | sfp-phylink.rst | 133 Please note that some of these functions must be called under the
135 except if these are called from the driver suspend/resume paths.
165 For the most part, ``flags`` can be zero; these flags are passed to
172 The setup of fixed links should also be removed; these are handled
192 these functions. The old link update function for
199 in-band negotiation from completing, since these functions are called
229 For further information on these methods, please see the inline
265 otherwise. If a MAC is unable to provide these interrupts, then
273 as these will interfere with phylink's tracking of the link state,
|
12345678910>>...72