| /kernel/linux/linux-4.19/block/partitions/ |
| D | Kconfig | 8 Say Y here if you would like to use hard disks under Linux which
29 Say Y here if you would like to use hard disks under Linux which
42 Say Y here if you would like to use hard disks under Linux which
75 Say Y here if you would like to be able to read the hard disk
87 Say Y here if you would like to use hard disks under Linux which
94 Say Y here if you would like to use hard disks under Linux which
101 Say Y here if you would like to use hard disks under Linux which
108 Say Y here if you would like to be able to read the hard disk
116 Say Y here if you would like to use hard disks under Linux which
150 Like most systems, Solaris x86 uses its own hard disk partition
[all …]
|
| /kernel/linux/linux-5.10/block/partitions/ |
| D | Kconfig | 8 Say Y here if you would like to use hard disks under Linux which
29 Say Y here if you would like to use hard disks under Linux which
42 Say Y here if you would like to use hard disks under Linux which
75 Say Y here if you would like to be able to read the hard disk
87 Say Y here if you would like to use hard disks under Linux which
94 Say Y here if you would like to use hard disks under Linux which
101 Say Y here if you would like to use hard disks under Linux which
108 Say Y here if you would like to be able to read the hard disk
116 Say Y here if you would like to use hard disks under Linux which
150 Like most systems, Solaris x86 uses its own hard disk partition
[all …]
|
| /kernel/linux/linux-4.19/drivers/misc/lkdtm/ |
| D | refcount.c | 50 /* refcount_add() should behave just like refcount_inc() above. */
68 /* refcount_inc_not_zero() should behave just like refcount_inc() above. */
80 /* refcount_add_not_zero() should behave just like refcount_inc() above. */
164 * A refcount_dec_and_test() should act like refcount_dec() above when
179 * A refcount_sub_and_test() should act like refcount_dec_and_test()
237 * A refcount_add() should act like refcount_inc() above when starting
289 /* Should act like refcount_inc() above from saturated. */
300 /* Should act like refcount_inc() above from saturated. */
311 /* Should act like refcount_inc() above from saturated. */
323 /* Should act like refcount_inc() above from saturated. */
[all …]
|
| /kernel/linux/linux-5.10/drivers/misc/lkdtm/ |
| D | refcount.c | 42 /* refcount_add() should behave just like refcount_inc() above. */
60 /* refcount_inc_not_zero() should behave just like refcount_inc() above. */
72 /* refcount_add_not_zero() should behave just like refcount_inc() above. */
156 * A refcount_dec_and_test() should act like refcount_dec() above when
171 * A refcount_sub_and_test() should act like refcount_dec_and_test()
228 * A refcount_add() should act like refcount_inc() above when starting
280 /* Should act like refcount_inc() above from saturated. */
291 /* Should act like refcount_inc() above from saturated. */
302 /* Should act like refcount_inc() above from saturated. */
314 /* Should act like refcount_inc() above from saturated. */
[all …]
|
| /kernel/linux/linux-4.19/Documentation/kbuild/ |
| D | kconfig-macro-language.txt | 10 can write a makefile like follows:
20 and handles as if the source file were input like follows:
29 file like this:
49 Like in Make, a variable in Kconfig works as a macro variable. A macro
92 Like Make, Kconfig provides several built-in functions. Every function takes a
141 Kconfig adopts Make-like macro language, but the function call syntax is
144 A function call in Make looks like this:
152 to make "info" function print " hello", you can write like follows:
169 'call', like this:
236 Instead, you can do like follows so that any function call is statically
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
33 file like this::
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
96 Like Make, Kconfig provides several built-in functions. Every function takes a
145 Kconfig adopts Make-like macro language, but the function call syntax is
148 A function call in Make looks like this::
156 to make "info" function print " hello", you can write like follows::
173 'call', like this::
241 Instead, you can do like follows so that any function call is statically
|
| /kernel/linux/linux-4.19/drivers/usb/ |
| D | README | 16 controllers (in devices with Linux firmware, like printers or
17 cell phones); and hard-wired peripherals like Ethernet adapters.
40 image/ - This is for still image drivers, like scanners or
43 like keyboard, mice, touchscreens, tablets, etc.
44 ../media/ - This is for multimedia drivers, like video cameras,
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | libv4l-introduction.rst | 72 applications work with v4l2 devices. These functions work exactly like
113 Those functions operate just like the gcc function ``dup()`` and
121 operates like the :c:func:`open()` function.
125 operates like the :c:func:`close()` function.
129 operates like the libc ``dup()`` function, duplicating a file handler.
133 operates like the :c:func:`ioctl()` function.
137 operates like the :c:func:`read()` function.
141 operates like the :c:func:`munmap()` function.
145 operates like the :c:func:`munmap()` function.
|
| /kernel/linux/linux-5.10/scripts/mod/ |
| D | file2alias.c | 156 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
226 /* Returns the previous value, so it works like i++ or i-- */
387 /* Looks like: hid:bNvNpN */
405 /* Looks like: ieee1394:venNmoNspNverN */
429 /* Looks like: pci:vNdNsvNsdNbcNscNiN. */
472 /* looks like: "ccw:tNmNdtNdmN" */
495 /* looks like: "ap:tN" */
505 /* looks like: "css:tN" */
515 /* Looks like: "serio:tyNprNidNexN" */
534 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | asm-annotations.rst | 12 Some code like entries, trampolines, or boot code needs to be written in
21 Over time, the Linux kernel has adopted macros from various projects (like
42 annotated objects like this, tools can be run on them to generate more useful
75 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with
82 Checking tools like ``objtool`` should ensure such marked functions conform
84 debugging information (like *ORC data*) automatically.
92 this code needs hints like ``UNWIND_HINT_REGS`` provided by developers.
110 conventions -- global and local. Like in C, they both align the functions to
123 So in most cases, developers should write something like in the following
|
| D | atomic_t.txt | 64 (which implies -fwrapv) and defines signed overflow to behave like
73 With this we also conform to the C/C++ _Atomic behaviour and things like
174 Except of course when an operation has an explicit ordering like:
184 subsequent. Therefore a fully ordered primitive is like having an smp_mb()
193 ordering inherent to the op. These barriers act almost like a full smp_mb():
220 Further, while something like:
228 as well. Similarly, something like:
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | libv4l-introduction.rst | 73 applications work with v4l2 devices. These functions work exactly like
116 Those functions operate just like the gcc function ``dup()`` and
124 operates like the :c:func:`open() <v4l2-open>` function.
128 operates like the :c:func:`close() <v4l2-close>` function.
132 operates like the libc ``dup()`` function, duplicating a file handler.
136 operates like the :c:func:`ioctl() <v4l2-ioctl>` function.
140 operates like the :c:func:`read() <v4l2-read>` function.
144 operates like the :c:func:`munmap() <v4l2-munmap>` function.
148 operates like the :c:func:`munmap() <v4l2-munmap>` function.
|
| /kernel/linux/linux-5.10/Documentation/sound/designs/ |
| D | oss-emulation.rst | 29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
65 (NOTE: Some distributions have the device files like /dev/midi0 and
90 define like this:
97 device on the second card to /dev/adsp1, define like below:
125 This will lead to some problems for some applications like quake or
168 quake, send a command via echo like the following:
191 for OSS devices, define like the following:
209 and restore it like
271 file, /proc/asound/cardX/oss_mixer, which will be like the following
288 send the command like the following:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/sound/designs/ |
| D | oss-emulation.rst | 29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
65 (NOTE: Some distributions have the device files like /dev/midi0 and
90 define like this:
97 device on the second card to /dev/adsp1, define like below:
125 This will lead to some problems for some applications like quake or
168 quake, send a command via echo like the following:
191 for OSS devices, define like the following:
209 and restore it like
271 file, /proc/asound/cardX/oss_mixer, which will be like the following
288 send the command like the following:
[all …]
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| D | sound.h | 17 #define SND_DEV_DSP16 5 /* Like /dev/dsp but 16 bits/sample */
27 #define SND_DEV_ADSP 12 /* Like /dev/dsp (obsolete) */
28 #define SND_DEV_AMIDI 13 /* Like /dev/midi (obsolete) */
29 #define SND_DEV_ADMMIDI 14 /* Like /dev/dmmidi (onsolete) */
|
| D | if_vlan.h | 42 VLAN_NAME_TYPE_PLUS_VID, /* Name will look like: vlan0005 */
43 VLAN_NAME_TYPE_RAW_PLUS_VID, /* name will look like: eth1.0005 */
44 VLAN_NAME_TYPE_PLUS_VID_NO_PAD, /* Name will look like: vlan5 */
45 VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD, /* Name will look like: eth0.5 */
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | sound.h | 17 #define SND_DEV_DSP16 5 /* Like /dev/dsp but 16 bits/sample */
27 #define SND_DEV_ADSP 12 /* Like /dev/dsp (obsolete) */
28 #define SND_DEV_AMIDI 13 /* Like /dev/midi (obsolete) */
29 #define SND_DEV_ADMMIDI 14 /* Like /dev/dmmidi (onsolete) */
|
| D | if_vlan.h | 43 VLAN_NAME_TYPE_PLUS_VID, /* Name will look like: vlan0005 */
44 VLAN_NAME_TYPE_RAW_PLUS_VID, /* name will look like: eth1.0005 */
45 VLAN_NAME_TYPE_PLUS_VID_NO_PAD, /* Name will look like: vlan5 */
46 VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD, /* Name will look like: eth0.5 */
|
| /kernel/linux/linux-4.19/scripts/mod/ |
| D | file2alias.c | 136 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
206 /* Returns the previous value, so it works like i++ or i-- */
367 /* Looks like: hid:bNvNpN */
385 /* Looks like: ieee1394:venNmoNspNverN */
409 /* Looks like: pci:vNdNsvNsdNbcNscNiN. */
452 /* looks like: "ccw:tNmNdtNdmN" */
475 /* looks like: "ap:tN" */
485 /* looks like: "css:tN" */
495 /* Looks like: "serio:tyNprNidNexN" */
514 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | packing.rst | 51 1. Normally (no quirks), we would do it like this:
67 2. If QUIRK_MSB_ON_THE_RIGHT is set, we do it like this:
80 3. If QUIRK_LITTLE_ENDIAN is set, we do it like this:
94 like this:
104 5. If just QUIRK_LSW32_IS_FIRST is set, we do it like this:
118 6. If QUIRK_LSW32_IS_FIRST and QUIRK_MSB_ON_THE_RIGHT are set, we do it like
129 7. If QUIRK_LSW32_IS_FIRST and QUIRK_LITTLE_ENDIAN are set, it looks like
141 are set, it looks like this:
|
| /kernel/linux/linux-4.19/Documentation/spi/ |
| D | spi-summary | 27 Unlike serial busses like USB or SMBus, even low level protocols for
29 (except for commodities like SPI memory chips).
43 - Sometimes SPI is used to daisy-chain devices, like shift registers.
78 sensors and codecs, to memory, to peripherals like USB controllers
137 for those calls, including ones for common transaction types like writing
152 data to filesystems stored on SPI flash like DataFlash; and others might
215 like the physical address of the controller's first register and its IRQ.
224 So for example arch/.../mach-*/board-*.c files might have code like:
241 And SOC-specific utility code might look something like:
281 small handful.) That might look like:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 107 root to do this. It's better to use a utility like sudo to execute
108 frequently used commands like this with root permissions if possible. If you
110 driver message like this at the console::
123 11. If you can't get site names (like www.yahoo.com) to resolve into
124 IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
126 If this doesn't help, try something like ``ping -c 5 204.71.200.67`` to
137 interface. It looks like I'm connected but I can't even ping any
203 and try setting the delay to something like 60 microseconds with:
205 it out. If it still doesn't work or you like playing with the driver, you may
|
| /kernel/linux/linux-4.19/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 18 only cover technicalities and not the big-picture issues like what the command
19 submission ioctl exactly should look like. Learning these lessons is probably
30 the kernel has special types like __u32, __s64. Use them.
46 diminishes the checking tools like sparse can provide. The macro
116 killable. GPUs just die and your users won't like you more if you hang their
136 derived from different clock domains like your main system clock (provided
153 Especially if your reference clock is something really slow like the display
186 that the per-device modeset objects like connectors share a namespace with
214 per-device settings, or for child objects with fairly static lifetimes (like
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 19 only cover technicalities and not the big-picture issues like what the command
20 submission ioctl exactly should look like. Learning these lessons is probably
31 the kernel has special types like __u32, __s64. Use them.
47 diminishes the checking tools like sparse can provide. The macro
117 killable. GPUs just die and your users won't like you more if you hang their
137 derived from different clock domains like your main system clock (provided
154 Especially if your reference clock is something really slow like the display
187 that the per-device modeset objects like connectors share a namespace with
215 per-device settings, or for child objects with fairly static lifetimes (like
|
| /kernel/linux/linux-4.19/drivers/mtd/ubi/ |
| D | Kconfig | 5 UBI is a software layer above MTD layer which admits use of LVM-like
7 flash chips like wear and bad blocks and provides some other useful
86 volume. This is handy to make MTD-oriented software (like JFFS2)
97 UBI driver will transparently handle things like bad eraseblocks and
100 practical for read-only file systems, like squashfs.
|