Searched full:like (Results 1 – 25 of 3518) sorted by relevance
12345678910>>...141
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | libv4l-introduction.rst | 80 applications work with v4l2 devices. These functions work exactly like
123 Those functions operate just like the gcc function ``dup()`` and
131 operates like the :c:func:`open() <v4l2-open>` function.
135 operates like the :c:func:`close() <v4l2-close>` function.
139 operates like the libc ``dup()`` function, duplicating a file handler.
143 operates like the :c:func:`ioctl() <v4l2-ioctl>` function.
147 operates like the :c:func:`read() <v4l2-read>` function.
151 operates like the :c:func:`munmap() <v4l2-munmap>` function.
155 operates like the :c:func:`munmap() <v4l2-munmap>` function.
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 */
|
| /Linux-v5.4/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:
|
| /Linux-v5.4/Documentation/ioctl/ |
| 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
|
| /Linux-v5.4/Documentation/ |
| 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:
|
| /Linux-v5.4/drivers/mtd/ubi/ |
| D | Kconfig | 6 UBI is a software layer above MTD layer which admits use of LVM-like
8 flash chips like wear and bad blocks and provides some other useful
87 volume. This is handy to make MTD-oriented software (like JFFS2)
98 UBI driver will transparently handle things like bad eraseblocks and
101 practical for read-only file systems, like squashfs.
|
| /Linux-v5.4/Documentation/spi/ |
| D | spi-summary.rst | 28 Unlike serial busses like USB or SMBus, even low level protocols for
30 (except for commodities like SPI memory chips).
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
79 sensors and codecs, to memory, to peripherals like USB controllers
138 for those calls, including ones for common transaction types like writing
155 data to filesystems stored on SPI flash like DataFlash; and others might
219 like the physical address of the controller's first register and its IRQ.
228 So for example arch/.../mach-*/board-*.c files might have code like::
245 And SOC-specific utility code might look something like::
285 small handful.) That might look like::
[all …]
|
| /Linux-v5.4/Documentation/networking/device_drivers/ |
| D | sb1000.txt | 100 root to do this. It's better to use a utility like sudo to execute
101 frequently used commands like this with root permissions if possible. If you
103 driver message like this at the console:
115 11.) If you can't get site names (like www.yahoo.com) to resolve into
116 IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
118 If this doesn't help, try something like `ping -c 5 204.71.200.67' to
130 interface. It looks like I'm connected but I can't even ping any
189 and try setting the delay to something like 60 microseconds with:
191 it out. If it still doesn't work or you like playing with the driver, you may
|
| /Linux-v5.4/fs/fat/ |
| D | Kconfig | 10 files on them, i.e. MSDOS files will look and behave just like all
48 transparent, i.e. the MSDOS files look and behave just like all
93 like FAT to use. It should probably match the character set
98 instead if you would like to use UTF-8 encoded file names by default.
109 Set this if you would like to have "utf8" mount option set
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 64 If the driver needs to perform more complex initialization like getting and
73 like to be accessible to slave devices via generic API call
75 function like this::
83 could look like::
153 Here is what the ACPI namespace for a SPI slave might look like::
190 Note that this driver actually needs more information like page size of the
192 passing those. One idea is to return this in _DSM method like::
212 ACPI handle like::
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
322 a code like this::
[all …]
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | gadget.rst | 75 to hardware, through registers, fifos, dma, irqs, and the like. The
127 - networking subsystem (for network gadgets, like the CDC Ethernet
170 hardware-specific, any more than network protocols like X11, HTTP, or
223 Like the Linux-USB host side API, this API exposes the "chunky" nature
226 protocols, USB resembles synchronous protocols like HDLC (N bytes per
240 needs to handle some differences. Use the API like this:
288 enumeration until some higher level component (like a user mode daemon)
383 act like a net2280, a pxa25x, or an sa11x0 in terms of available
415 Pengutronix and Auerswald GmbH. This is like CDC Ethernet, but it runs
424 Familiar tools like GDB and pthreads can be used to develop and debug
[all …]
|
| /Linux-v5.4/Documentation/networking/ |
| D | cops.txt | 28 Use modprobe like this: /sbin/modprobe cops.o (IO #) (IRQ #)
37 Or in lilo.conf put something like this:
40 Then bring up the interface with ifconfig. It will look something like this:
48 You will need to configure atalkd with something like the following to make
|
| /Linux-v5.4/Documentation/isdn/ |
| D | gigaset.rst | 63 which provide access to additional device specific functions like SMS,
116 configuration file like /etc/modprobe.d/gigaset.conf for these.
157 querying parameters like field strengh and signal quality.
197 In this mode the device works like a modem connected to a serial port
220 flag_time=0. You can do this e.g. by adding a line like::
224 to an appropriate module configuration file, like::
230 section 3.2.) shows something like this when dialing::
255 or by adding a line like::
259 to an appropriate module configuration file, like::
334 by adding a line like::
[all …]
|
| /Linux-v5.4/Documentation/gpu/ |
| D | introduction.rst | 8 make use of DRM functions to make tasks like memory management,
64 have formal kerneldoc comments. Use normal C comments if you feel like a comment
83 Mostly the DRM subsystem works like any other kernel subsystem, see :ref:`the
96 After that point only bugfixes (like after the upstream merge window has closed
103 blackout period. As an example, drm-misc works like that.
|
| /Linux-v5.4/Documentation/sphinx/ |
| D | cdomain.py | 30 * Handle signatures of function-like macros well. Don't try to deduce
31 arguments types of function-like macros.
72 u"""Handles signatures of function-like macros.
75 function-like macro, the name of the macro is returned. Otherwise
99 # This is a function-like macro, it's arguments are typeless!
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-cros-ec-tunnel.txt | 5 the EC (like a battery and PMIC). To get access to those devices we need
8 The node for this device should be under a cros-ec node like google,cros-ec-spi
14 - google,remote-bus: The EC bus we'd like to talk to.
|
| /Linux-v5.4/include/linux/wimax/ |
| D | debug.h | 14 * debug action (like printing a message) if the current debug level
55 * The debug-levels.h file would look like:
111 * should be included like this:
169 * @f: printf-like format and arguments
173 * sure the printf-like formats and variables are always checked and
187 * CPP sintatic sugar to generate A_B like symbol names when one of
359 * @f: printf-like format and arguments
369 * @f: printf-like format and arguments
379 * @f: printf-like format and arguments
389 * @f: printf-like format and arguments
|
| /Linux-v5.4/Documentation/admin-guide/laptops/ |
| D | asus-laptop.rst | 15 events (like keyboards).
53 see some lines like this :
65 Hotkeys are also reported as input keys (like keyboards) you can check
82 kernel triggers like disk-activity or heartbeat.
179 like::
183 will usually do the trick ($arg is the 0000006n-like event passed to acpid).
191 Some models like the W1N have a LED display that can be used to display
239 - 0x5 like 0x1 or 0x4
|
| /Linux-v5.4/arch/s390/kernel/ |
| D | ftrace.c | 25 * The mcount code looks like this:
32 * The enabled ftrace code block looks like this:
44 * The disabled ftrace code block looks like this:
53 * like this:
55 * To enable ftrace the code gets patched like above and afterwards looks
56 * like this:
|
12345678910>>...141
