Searched refs:like (Results 1 – 25 of 1202) sorted by relevance
12345678910>>...49
| /Linux-v4.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
168 Linux box via a removable medium like magneto-optical, ZIP or
[all …]
|
| /Linux-v4.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,
|
| /Linux-v4.19/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-v4.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.
|
| /Linux-v4.19/Documentation/i2c/busses/ |
| D | i2c-sis630 | 32 If you see something like this:
37 or like this:
42 or like this:
|
| /Linux-v4.19/fs/exofs/ |
| D | Kconfig.ore | 4 # for every ORE user we do it like this. Any user should add itself here
6 # selected here, and we default to "ON". So in effect it is like been
|
| /Linux-v4.19/Documentation/laptops/ |
| D | asus-laptop.txt | 12 events (like keyboards).
49 see some lines like this :
61 Hotkeys are also reported as input keys (like keyboards) you can check
75 kernel triggers like disk-activity or heartbeat.
167 like:
171 will usually do the trick ($arg is the 0000006n-like event passed to acpid).
179 Some models like the W1N have a LED display that can be used to display
225 - 0x5 like 0x1 or 0x4
|
| /Linux-v4.19/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-v4.19/drivers/net/can/c_can/ |
| D | Kconfig | 13 boards from ST Microelectronics (http://www.st.com) like the
15 boards like am335x, dm814x, dm813x and dm811x.
|
| /Linux-v4.19/Documentation/fb/ |
| D | cmap_xfbdev.txt | 22 *. X11 apps do something like the following when trying to use grayscale.
32 There's also named equivalents like gray1..x provided you have an rgb.txt.
50 that the app wants to match to. The above code is doing what looks like a least
|
| /Linux-v4.19/drivers/dma/bestcomm/ |
| D | Kconfig | 13 optional for some drivers (like ATA), but required for
14 others (like FEC).
|
| /Linux-v4.19/sound/oss/dmasound/ |
| D | Kconfig | 7 Y to this question. This will provide a Sun-like /dev/audio,
21 Y to this question. This will provide a Sun-like /dev/audio,
35 Y to this question. This will provide a Sun-like /dev/audio,
|
| /Linux-v4.19/Documentation/mtd/ |
| D | spi-nor.txt | 26 Before this framework, the layer is like:
36 After this framework, the layer is like:
47 With the SPI NOR controller driver (Freescale QuadSPI), it looks like:
|
| /Linux-v4.19/Documentation/devicetree/bindings/powerpc/opal/ |
| D | sensor-groups.txt | 17 operations like clearing the min/max history of all
26 sensor groups like clearing min/max, enabling/disabling sensor
|
| /Linux-v4.19/drivers/net/dsa/b53/ |
| D | Kconfig | 27 Select to enable support for memory-mapped switches like the BCM63XX
35 Bridge Registers (SRAB) like it is found on the BCM53010
|
| /Linux-v4.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:
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
|
| /Linux-v4.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.
|
| /Linux-v4.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:
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | vexpress-scc.txt | 10 (like silicon temperature sensors) and as interface to other subsystems
11 like platform configuration control and power management.
|
| /Linux-v4.19/fs/fat/ |
| D | Kconfig | 9 files on them, i.e. MSDOS files will look and behave just like all
47 transparent, i.e. the MSDOS files look and behave just like all
92 like FAT to use. It should probably match the character set
97 instead if you would like to use UTF-8 encoded file names by default.
108 Set this if you would like to have "utf8" mount option set
|
| /Linux-v4.19/Documentation/isdn/ |
| D | README.gigaset | 57 which provide access to additional device specific functions like SMS,
101 configuration file like /etc/modprobe.d/gigaset.conf for these.
137 querying parameters like field strengh and signal quality.
182 for setting up that subsystem. Otherwise you can use some HOWTOs like
188 In this mode the device works like a modem connected to a serial port
211 flag_time=0. You can do this e.g. by adding a line like
215 to an appropriate module configuration file, like
220 section 3.2.) shows something like this when dialing:
238 or by adding a line like
240 to an appropriate module configuration file, like
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/board/ |
| D | fsl-board.txt | 82 Some Freescale boards like BSC9132QDS have on board FPGA connected on
99 Some Freescale boards like T1040RDB have an on board CPLD connected.
102 - compatible: Should be a board-specific string like "fsl,<board>-cpld"
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-stub | 19 operations. This allows for continuous byte reads like those supported by
30 The typical use-case is like this:
63 something like relayfs.
|
| /Linux-v4.19/Documentation/arm/ |
| D | mem_alignment | 5 doing so on some f***ed up ARM architectures like the EBSA110. However
6 this is not the case on many design I'm aware of, like all SA11x0 based
17 code), or even fixup the access by software like for kernel code. The later
|
| /Linux-v4.19/Documentation/acpi/ |
| D | enumeration.txt | 59 If the driver needs to perform more complex initialization like getting and
67 like to be accessible to slave devices via generic API call
69 function like this:
77 could look like:
146 Here is what the ACPI namespace for a SPI slave might look like:
183 Note that this driver actually needs more information like page size of the
185 passing those. One idea is to return this in _DSM method like:
205 ACPI handle like:
224 The slaves behind I2C bus controller only need to add the ACPI IDs like
313 a code like this:
[all …]
|
12345678910>>...49
