Home
last modified time | relevance | path

Searched refs:like (Results 1 – 200 of 996) sorted by relevance

12345

/linux-4.4.14/block/partitions/
DKconfig7 Say Y here if you would like to use hard disks under Linux which
28 Say Y here if you would like to use hard disks under Linux which
41 Say Y here if you would like to use hard disks under Linux which
74 Say Y here if you would like to be able to read the hard disk
86 Say Y here if you would like to use hard disks under Linux which
93 Say Y here if you would like to use hard disks under Linux which
100 Say Y here if you would like to use hard disks under Linux which
107 Say Y here if you would like to be able to read the hard disk
115 Say Y here if you would like to use hard disks under Linux which
167 Linux box via a removable medium like magneto-optical, ZIP or
[all …]
/linux-4.4.14/drivers/usb/
DREADME16 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-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-cros-ec-tunnel.txt5 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.
Di2c-s3c2410.txt9 (c) "samsung, s3c2440-hdmiphy-i2c", for s3c2440-like i2c used
11 (d) "samsung, exynos5440-i2c", for s3c2440-like i2c used
13 (e) "samsung, exynos5-sata-phy-i2c", for s3c2440-like i2c used as
/linux-4.4.14/fs/exofs/
DKconfig.ore4 # 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-4.4.14/Documentation/i2c/busses/
Di2c-sis63032 If you see something like this:
37 or like this:
42 or like this:
Di2c-piix446 Do 'lspci -v' and see whether it contains an entry like this:
52 identical (like many PCI devices, the PIIX4 incorporates a number of
62 option is 'force_addr=<IOPORT>'. This will not only enable the PIIX4 like
Di2c-amd811116 If you see something like this:
/linux-4.4.14/Documentation/laptops/
Dasus-laptop.txt12 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 ide-disk 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
Dsonypi.txt16 generate, like:
82 used in other Vaio models (like the FX series who does
106 mouse events, the other one which acts like a
137 mode (but without additional ACPI control, like processor
/linux-4.4.14/drivers/net/can/c_can/
DKconfig13 boards from ST Microelectronics (http://www.st.com) like the
15 boards like am335x, dm814x, dm813x and dm811x.
/linux-4.4.14/Documentation/networking/
Dcops.txt28 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
DREADME.sb1000100 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
Dmac80211-auth-assoc-deauth.txt21 like deauth/disassoc, without sending the
50 note over mac80211,driver: cleanup like for authenticate
Dnetdev-FAQ.txt8 anything found under net/ (i.e. core code like IPv6) and drivers/net
14 The netdev list is managed (like many other Linux mailing lists) through
20 Aside from subsystems like that mentioned above, all network-related Linux
87 A: Firstly, think whether you have a bug fix or new "next-like" content.
138 Should I request it via "stable@vger.kernel.org" like the references in
156 stable. Should I add a "Cc: stable@vger.kernel.org" like the references
181 it is requested that you make it look like this:
Dltpc.txt43 like me, you are simply connecting to your home Macintoshes and
98 treat the LocalTalk device like an ordinary Ethernet device, even if
99 that's what it looks like to Netatalk.
Darcnet.txt3 and cabling information if you're like many of us and didn't happen to get a
100 without patches, though, and also doesn't like several cards. Fixed
235 do something like this:
320 that are actually a lot like Ethernet packets, including the
322 Microsoft's NDIS ARCnet driver, like the one in WfWg and
359 only arc0 unless you have a good reason (like some other software, ie.
396 - talk to freedom via RFC1201 (arc0) protocol, because I like it
400 That's pretty easy to do. Set up insight like this:
403 route add freedom arc0 /* I would use the subnet here (like I said
411 And freedom gets configured like so:
[all …]
Dtproxy.txt4 This feature adds Linux 2.2-like transparent proxy support to current kernels.
55 add rules like this to the iptables ruleset above:
/linux-4.4.14/Documentation/fb/
Dcmap_xfbdev.txt22 *. 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
Darkfb.txt33 limitation). Unfortunately character attributes (like color) in text mode are
59 * acceleration support (8514-like 2D)
Dvesafb.txt8 of the BIOS, and use this as framebuffer device /dev/fb0, like the m68k
66 mode at the "vga=ask" prompt. For example if you like to use
84 another (accelerated) X-Server like XF86_SVGA might or might not work.
117 by comma, like this: "video=vesafb:ypan,invers"
Ddeferred_io.txt9 - userspace app like Xfbdev mmaps framebuffer
44 No changes needed. mmap the framebuffer like normal and just use it.
/linux-4.4.14/Documentation/mtd/
Dspi-nor.txt26 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-4.4.14/drivers/dma/bestcomm/
DKconfig13 optional for some drivers (like ATA), but required for
14 others (like FEC).
/linux-4.4.14/sound/oss/dmasound/
DKconfig7 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-4.4.14/drivers/mtd/ubi/
DKconfig5 UBI is a software layer above MTD layer which admits 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-4.4.14/Documentation/devicetree/bindings/arm/
Dvexpress-scc.txt10 (like silicon temperature sensors) and as interface to other subsystems
11 like platform configuration control and power management.
Dversatile-sysreg.txt5 platform functions like board detection and identification, software
/linux-4.4.14/Documentation/sound/alsa/
DOSS-Emulation.txt28 "alias sound-slot-0 snd-card-0" doesn't work any more like the old
63 (NOTE: Some distributions have the device files like /dev/midi0 and
86 define like this:
92 device on the second card to /dev/adsp1, define like below:
116 This will lead to some problems for some applications like quake or
152 quake, send a command via echo like the following:
173 for OSS devices, define like the following:
189 and restore it like
247 file, /proc/asound/cardX/oss_mixer, which will be like the following
263 send the command like the following:
DCMIPCI.txt65 "-MC" such like "CMI8738-MC6". You can check this name from
75 in alsa-lib. For example, you can play a WAV file with 6 channels like
80 channels as you like and set the format S16LE. For example, for playback
84 // or mmap if you like
113 For playback with aplay, you can run like below:
DHD-Audio.txt93 like:
155 you may see a message like below:
159 Meanwhile, in the earlier versions, you would see a message like:
214 first. A speaker output often requires more additional controls like
411 re-configure based on that state, run like below:
425 the codec parser will skip the features like auto-mute or mic
485 codec. This can work basically like the reconfiguration via sysfs in
488 A patch file is a plain text file which looks like below:
522 default pin-configurations just like `user_pin_configs` sysfs above.
530 0xdeadbeef is like below:
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/board/
Dfsl-board.txt83 Some Freescale boards like BSC9132QDS have on board FPGA connected on
100 Some Freescale boards like T1040RDB have an on board CPLD connected.
103 - compatible: Should be a board-specific string like "fsl,<board>-cpld"
/linux-4.4.14/Documentation/arm/
Dmem_alignment5 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
Dtcm.txt73 memory. Such a heap is great for things like saving
80 Functions to go into itcm can be tagged like this:
88 Variables to go into dtcm can be tagged like this:
91 Constants can be tagged like this:
/linux-4.4.14/Documentation/i2c/
Di2c-stub19 operations. This allows for continuous byte reads like those supported by
30 The typical use-case is like this:
63 something like relayfs.
Di2c-protocol42 They are just like the above transactions, but instead of a stop bit P
68 generates something like:
87 like SCCB require that. Normally, you really don't want to get interrupted
Dslave-eeprom-backend6 This is a proof-of-concept backend which acts like an EEPROM on the connected
Dwriting-clients25 provide. A client structure holds device-specific information like the
144 I2C device drivers using this binding model work just like any other
280 power state -- like putting a transceiver into a low power mode, or
282 appropriate callbacks for the dev_pm_ops of the driver (like suspend
285 These are standard driver model calls, and they work just like they
296 or reboots (including kexec) -- like turning something off -- use a
299 Again, this is a standard driver model call, working just like it
307 A generic ioctl-like function call back is supported. You will seldom
/linux-4.4.14/Documentation/isdn/
DREADME.gigaset56 which provide access to additional device specific functions like SMS,
100 configuration file like /etc/modprobe.d/gigaset.conf for these.
136 querying parameters like field strengh and signal quality.
181 for setting up that subsystem. Otherwise you can use some HOWTOs like
187 In this mode the device works like a modem connected to a serial port
210 flag_time=0. You can do this e.g. by adding a line like
214 to an appropriate module configuration file, like
219 section 3.2.) shows something like this when dialing:
237 or by adding a line like
239 to an appropriate module configuration file, like
[all …]
/linux-4.4.14/Documentation/acpi/
Denumeration.txt59 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 …]
Dgpio-properties.txt11 index, like the ASL example below shows:
80 question would look like this:
/linux-4.4.14/Documentation/power/
Dswsusp-dmcrypt.txt22 the key(s) from an external device like a pcmcia flash disk
32 it will always look like the following:
42 modify. For lilo the simplest setup looks like the following
56 like the following:
121 for init like "single" or "emergency" as boot parameters.
Ds2ram.txt30 - use a script like this:
41 like
78 correct date/time! It is therefore advisable to use a program like ntp-date
Dtricks.txt7 * go with minimal config, turn off drivers like USB, AGP you don't
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmfd.txt10 silicon) that handles analog drivers for things like audio amplifiers, LED
11 drivers, level shifters, PHY (physical interfaces to things like USB or
Datmel-smc.txt5 devices like FPGAs).
Dsun6i-prcm.txt4 (like clks and reset controllers).
/linux-4.4.14/Documentation/trace/
Devents-nmi.txt28 really hogging a lot of CPU time, like a millisecond at a time.
36 Your output would then look like:
/linux-4.4.14/drivers/gpu/drm/msm/
DNOTES18 But, HDMI/DSI/etc blocks seem like they can be shared across multiple
21 seems like we can do some clever tricks like use GPU to trigger
70 (ie. like DT super-node.. but I don't have any snapdragon hw yet that
/linux-4.4.14/Documentation/driver-model/
Dclass.txt7 A device class describes a type of device, like an audio or network
24 The device class structure looks like:
32 A typical device class definition would look like:
122 like this:
Ddevres.txt60 automatically released on driver detach. Implementation looks like
101 looks like the following.
164 like above are usually useful in midlayer driver (e.g. libata core
176 For example, you can do something like the following.
/linux-4.4.14/Documentation/gpio/
Ddrivers-on-gpio.txt54 drivers for the I2C devices on the bus like any other I2C bus driver.
59 and makes it possible to connect drivers for SPI devices on the bus like
65 the bus like any other W1 device.
83 NAND flash MTD subsystem and provides chip access and partition parsing like
86 Apart from this there are special GPIO drivers in subsystems like MMC/SD to
Ddriver.txt48 - optional debugfs dump method (showing extra state like pullup config)
66 (like PM runtime) in its gpio_chip implementation (.get/.set and direction
82 (like PM runtime) as part of its irq_chip implementation on -RT.
98 something like this sequence in its interrupt handler:
109 As result, spinlock_t or any sleepable APIs (like PM runtime) can't be used
129 The GPIO irqchip will then end up calling something like this sequence in
146 by the driver. The hallmark of this driver is to call something like
Dgpio.txt34 several dozen of them. Programmable logic devices (like FPGAs) can easily
35 provide GPIOs; multifunction chips like power managers, and audio codecs
63 On a given board each GPIO is used for one specific purpose like monitoring
/linux-4.4.14/sound/soc/blackfin/
DKconfig30 board connected to one of the Blackfin evaluation boards like the
40 board connected to one of the Blackfin evaluation boards like the
53 board connected to one of the Blackfin evaluation boards like the
66 board connected to one of the Blackfin evaluation boards like the
81 like the BF5XX-STAMP or BF5XX-EZKIT.
/linux-4.4.14/Documentation/video4linux/bttv/
DPROBLEMS10 Start up X11 like this: "XF86_S3 -probeonly" and write down where the
12 If it is different to the address found by bttv install bttv like this:
37 Looks like XFree does something different when setting up the video memory?
DCONTRIBUTORS21 like to be mentioned)
/linux-4.4.14/lib/
DKconfig.kasan49 This is a test module doing various nasty things like
51 kernel debugging features like kernel address sanitizer.
/linux-4.4.14/Documentation/hwmon/
Duserspace-tools4 Most mainboards have sensor chips to monitor system health (like temperatures,
37 like: gkrellm, ksensors, xsensors, wmtemp, wmsensors, wmgtemp, ksysguardd,
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-atlas7.txt7 For example, pinctrl might have properties like the following:
75 For example, pinctrl might have subnodes like the following:
Dfsl,imx-pinctrl.txt7 different PAD settings (like pull up, keeper, etc) the IOMUXC controls
29 the pad setting value like pull-up on this pin. And that's why fsl,pins entry
30 looks like <PIN_FUNC_ID CONFIG> in the example below.
Dfsl,imx53-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx51-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx35-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx6q-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx6dl-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx6sx-pinctrl.txt12 the pad setting value like pull-up on this pin. Please refer to i.MX6 SoloX
Dfsl,imx6sl-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx6ul-pinctrl.txt12 the pad setting value like pull-up on this pin. Please refer to i.MX6 UltraLite
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt18 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.
45 diminishes the checking tools like sparse can provide.
111 killable. GPUs just die and your users won't like you more if you hang their
131 derived from different clock domains like your main system clock (provided
148 Especially if your reference clock is something really slow like the display
181 that the per-device modeset objects like connectors share a namespace with
209 per-device settings, or for child objects with fairly static lifetimes (like
/linux-4.4.14/Documentation/spi/
Dspi-summary27 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
202 like the physical address of the controller's first register and its IRQ.
211 So for example arch/.../mach-*/board-*.c files might have code like:
228 And SOC-specific utility code might look something like:
268 small handful.) That might look like:
[all …]
/linux-4.4.14/Documentation/
Dbus-virt-phys-mapping.txt41 CPU sees a memory map something like this (this is from memory):
55 PPC, you can end up with a setup like this:
85 pointer from the kernel. So you can have something like this:
133 buffer), but can be things like a packet buffer in a network card etc.
144 For such memory, you can do things like
184 support both can do something like:
Dmen-chameleon-bus.txt38 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
39 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
42 per MCB device like PCIe based carriers with MSI or MSI-X support.
66 properties of the carrier device (like querying the IRQ number of a PCI
Dzorro.txt28 for the board with Zorro ID `ZORRO_PROD_xxx' looks like:
39 supports different types of boards, you can use a construct like:
Dmono.txt8 This will allow you to execute Mono-based .NET binaries just like any
39 # Some distributions, like Fedora Core, perform
Dpinctrl.txt103 like this, walking around the edge of the chip, which seems to be industry
127 some generic pinctrl_ops like this:
212 configuration in the pin controller ops like this:
295 instance like this:
347 numbers can be encoded in the range like this:
426 are chessboard-like, big ones have "holes" in some arrangement according to
428 pins you see some will be taken by things like a few VCC and GND to feed power
429 to the chip, and quite a few will be taken by large ports like an external
477 In this case the array could be something like: { spi0, i2c0, mmc0 }
518 like these:
[all …]
DCodingStyle131 ie a "while" in a do-statement or an "else" in an if-statement, like
183 somewhat like functions (and are usually used with parentheses in Linux,
243 and Pascal programmers, C programmers do not use cute names like
275 Please don't use things like "vps_t".
297 The reason we have them for things like pte_t etc. is that there
322 brain to become accustomed to the standard types like 'uint32_t',
371 and it gets confused. You know you're brilliant, but maybe you'd like
400 using GW-BASIC names like "err1:" and "err2:". Also don't name them after the
401 goto location like "err_kmalloc_failed:"
433 A common type of bug to be aware of it "one err bugs" which look like this:
[all …]
Datomic_ops.txt13 will fail. Something like the following should suffice:
113 you should use something like the following:
166 the compiler from doing this, write something like:
222 These behave just like atomic_{inc,dec}_return() except that an
224 This means that like atomic_{inc,dec}_return(), the memory barrier
297 For example, smp_mb__before_atomic() can be used like so:
386 sequence looks like this:
452 declaring the above to return "long" and just returning something like
462 like this occur as well.
464 These routines, like the atomic_t counter operations returning values,
[all …]
Ddebugging-via-ohci1394.txt20 locations such as buffers like the printk buffer or the process table.
36 buffer on to debug early boot problems in areas like ACPI where the system
38 available (notebooks) or too slow for extensive debug information (like ACPI).
116 If an driver is running on both machines you should see a line like
Dbinfmt_misc.txt17 To actually register a new binary type, you have to set up a string looking like
30 may contain hex-encoded characters like \x0a or \xA4. Note that you must
37 bits from matching by supplying a string like magic and as long as magic.
91 - enable support for em86 (like binfmt_em86, for Alpha AXP only):
DDMA-API-HOWTO.txt23 "resource_size_t". The kernel manages device resources like registers as
83 an interface like dma_map_single(), which sets up any required IOMMU
126 something like __va(). [ EDIT: Update this when we integrate
212 The standard 32-bit addressing device would do something like this:
242 the case would look like this:
263 address you might do something like:
344 something like:
428 or you can use the dma_pool API to do that. A dma_pool is like
431 like queue heads needing to be aligned on N byte boundaries.
433 Create a dma_pool like this:
[all …]
Dapplying-patches.txt40 names like "a/" and "b/").
48 So, if you applied a patch like this:
51 You can revert (undo) it like this:
57 This (as usual with Linux and other UNIX like operating systems) can be
67 Patch can also get the name of the file to use via the -i argument, like
72 uncompress it before applying it, then you can feed it to patch like this
79 gunzip or bunzip2 on the file -- like this:
97 Checking that the file looks like a valid patch file and checking the code
151 If you get a message like "Hunk #3 FAILED at 2387.", then it means that the
192 This will let you move from something like 2.6.12.2 to 2.6.12.3 in a single
[all …]
Dio-mapping.txt51 This works like io_mapping_map_atomic_wc except it allows
56 This works like io_mapping_unmap_atomic, except it is used
Ddebugging-modules.txt12 of debugging module problems is something like this:
DManagementStyle51 makes you look like you know what you're doing, so what a kernel manager
83 - admitting you were an idiot is harder than it looks. We all like to
123 That may sound like a failure, but it's usually a sign that there was
126 smelling like roses, and you avoided yet another decision that you could
163 like they get unfairly targeted. Make it inventive enough, and they
191 management responsibilities largely become ones of saying "Sounds like a
201 naturally gravitate back to what they are good at, so it's not like you
Dsparse.txt8 "__bitwise" is a type attribute, so you have to do something like this:
24 up looking just like integers to gcc.
/linux-4.4.14/net/l3mdev/
DKconfig10 drivers to support L3 master devices like VRF.
/linux-4.4.14/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.txt15 Old drivers define their own file_operations for actions like open(), write(),
134 A typical function-header change looks like:
157 have their own record-keeping for things like bootstatus and timeout using
176 watchdog_device like this:
181 by adding a module parameter. The conversion for this would be something like:
Dhpwdt.txt14 Watchdog functionality is enabled like any other common watchdog driver. That
39 on handling NMIs (like oprofile). Keeping hpwdt's priority at 0 (or LAST)
/linux-4.4.14/drivers/media/usb/siano/
DKconfig12 Choose if you would like to have Siano's support for USB interface
/linux-4.4.14/drivers/w1/masters/
DKconfig47 in HP iPAQ devices like h5xxx, h2200, and ASIC3-based like
/linux-4.4.14/Documentation/blockdev/
Dcpqarray.txt37 controllers, in EISA slots 1 and 2 you'd give it a boot argument like
42 If you were loading the driver as a module, you'd give load it like this:
/linux-4.4.14/Documentation/devicetree/bindings/nvmem/
Dnvmem.txt4 configuration data stored in NVMEMs like eeprom, efuses and so on.
22 information like offset and size in nvmem provider.
/linux-4.4.14/Documentation/devicetree/bindings/iio/humidity/
Ddht11.txt1 * DHT11 humidity/temperature sensor (and compatibles like DHT22)
/linux-4.4.14/drivers/pnp/isapnp/
DKconfig8 Say Y here if you would like support for ISA Plug and Play devices.
/linux-4.4.14/drivers/media/mmc/siano/
DKconfig13 Choose if you would like to have Siano's support for SDIO interface
/linux-4.4.14/drivers/gpu/drm/virtio/
DKconfig12 QEMU based VMMs (like KVM or Xen).
/linux-4.4.14/drivers/misc/eeprom/
DKconfig8 and compatible devices like FRAMs, SRAMs, ROMs etc. After you
11 ones like at24c64, 24lc02 or fm24c04:
16 Unless you like data loss puzzles, always be sure that any chip
/linux-4.4.14/Documentation/sound/oss/
Dmwave37 five for Linux, like this:
135 document, APM, it seems, MUST be off for setups like mine.
137 Now make sure C:\MWW\MWCONFIG.REF looks like this:
172 For some reason MPEG3 files, when played through mpg123, sound like they
DREADME.modules29 Then, add to your /etc/modprobe.d/oss.conf something like:
53 /lib/modules/<kernel-version>/misc. Mine looks like:
92 in /etc/modprobe.d/*.conf files like so:
Dbtaudio5 people start bugging me about this with questions, looks like I
69 like 44 kHz too.
/linux-4.4.14/Documentation/device-mapper/
Dlog-writes.txt41 Any REQ_DISCARD requests are treated like WRITE requests. Otherwise we would
47 If we logged DISCARD when it completed, the replay would look like this
77 we're fsck'ing something reasonable, you would do something like
99 Say you want to test fsync on your file system. You would do something like
Dverity.txt29 checked. It may be specified as a path, like /dev/sdaX, or a device number,
56 be the name of the algorithm, like "sha1".
87 booting from a known-good device (like a USB drive or CD).
114 The tree looks something like:
Dpersistent-data.txt14 we'd like to reduce the number.
75 array-like interface would see a lot of use.
/linux-4.4.14/Documentation/arm/SA1100/
DAssabet78 To initialize the non-volatile settings, like whether you want to use BOOTP or
112 Now the kernel can be retrieved from flash like this:
141 The result should look like:
184 However Linux should display something like:
204 Of course other filesystems than JFFS might be used, like cramfs for example.
261 (LCD doesn't like being blanked with
/linux-4.4.14/drivers/net/irda/
DKconfig28 To activate this driver you can start irattach like:
97 dongles you will have to start irattach like this:
108 ACTiSYS dongles you will have to start irattach like this:
119 dongles you will have to start irattach like this:
138 dongles you will have to start irattach like this:
151 MA600 dongle you will have to start irattach like this:
163 like this: "irattach -d girbil".
174 like this: "irattach -d mcp2120".
197 start irattach like this: "irattach -d act200l".
/linux-4.4.14/drivers/usb/serial/
DMakefile-keyspan_pda_fw2 # some rules to handle the quirks of the 'as31' assembler, like
/linux-4.4.14/Documentation/devicetree/bindings/arc/
Darchs-pct.txt4 CPU and cache events like cache misses and hits. Like conventional PCT there
Dpct.txt4 CPU and cache events like cache misses and hits. Like conventional PCT there
/linux-4.4.14/Documentation/dvb/
Dudev.txt4 This means that only the basic information like module loading parameters
32 like you know them. All real distributions out there scan the /etc/udev/rules.d
/linux-4.4.14/drivers/virtio/
DKconfig18 (like KVM or Xen).
37 life will be like in The Future.
/linux-4.4.14/Documentation/filesystems/
Dubifs.txt7 is completely different to any traditional file-system in Linux, like
41 limitations like wear and bad blocks (items 4 and 5 in the above list).
60 It does not need stuff like fsck.ext2. UBIFS automatically replays its
66 on the flash size, like in case of JFFS2. This is because UBIFS
Dseq_file.txt36 needing to worry about things like output buffers.
45 better to do. The file is seekable, in that one can do something like the
71 Iterators must be able to move to a specific position - like the file they
86 the start() function looks like:
182 Most code will simply use seq_printf(), which works pretty much like
191 The first two output a single character and a string, just like one would
192 expect. seq_escape() is like seq_puts(), except that any character in s
277 file_operations structure will look like:
Defivarfs.txt14 efivarfs is typically mounted like this,
Dhpfs.txt58 because kernel creates different files with names like bootsect.S and
72 why not use it for unix-specific info like file owner or access rights? This
78 something like 'chown luser file; chown root file' the file will contain
134 to handle some HPFS386 structures like access control list or extended perm
163 but vfs doesn't. Something like 'mv file FILE' won't work.
198 File names like "a .b" are marked as 'long' by OS/2 but chkdsk "corrects" it and
248 Directories have no longer archive attribute set (some programs don't like
Dautomount-support.txt14 Then from userspace, you can just do something like:
24 And then if you look in the mountpoint catalogue, you'll see something like:
/linux-4.4.14/Documentation/vm/
Dhighmem.txt57 and user maps. Some hardware (like some ARMs), however, have limited virtual
112 another you need to keep the kmap_atomic calls strictly nested, like:
155 data has to be accessed to traverse in TLB fills and the like. One
157 like NX and PAT.
Dpage_owner.txt25 page owner is disabled in default. So, if you'd like to use it, you need
32 done like as the kernel without page owner. These two unlikely branches
/linux-4.4.14/drivers/firmware/broadcom/
DKconfig7 NVRAM partition contains a text-like data representing name=value
/linux-4.4.14/Documentation/usb/
Dgadget_serial.txt82 like a serial device.
84 On the host-side system, the gadget serial device looks like a
142 The /dev/ttyGS0 line should work like most any other serial port.
194 should show something like this:
226 should show something like this:
240 to configure it to recognize the gadget serial device, like this:
249 system log saying something like "Gadget Serial converter now
Dhotplug.txt3 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
99 ... like USB_DEVICE with lo <= productversion <= hi
106 and their quirks, might have a MODULE_DEVICE_TABLE like this:
122 something like this:
Dmtouchusb.txt39 download, I persist in updating this driver since I would like to use the
53 generic functions like calibrations, resets, and vendor information can be
Drio.txt61 also like to thank Tri Nguyen <tmn_3022000@hotmail.com> who provided use
87 If you see something like:
95 If you see something like:
/linux-4.4.14/net/irda/ircomm/
DKconfig10 infrared link. Thus you should be able to use application like PPP,
/linux-4.4.14/Documentation/blackfin/
Dbfin-gpio-notes.txt57 Some drivers, like gpio-keys, need this behavior. Kernel only print out
58 warning messages like,
/linux-4.4.14/drivers/nvmem/
DKconfig5 Support for NVMEM(Non Volatile Memory) devices like EEPROM, EFUSES...
76 devices like VF5xx and VF6xx.
/linux-4.4.14/drivers/isdn/hysdn/
DKconfig14 Say Y here if you like to use Hypercope's CAPI 2.0 interface.
/linux-4.4.14/drivers/media/pci/pluto2/
DKconfig7 Support for PCI cards based on the Pluto2 FPGA like the Satelco
/linux-4.4.14/net/nfc/hci/
DKconfig8 HCI frames, like for example the NXP pn544.
/linux-4.4.14/net/irda/irlan/
DKconfig11 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-kernel-vmcoreinfo13 contains various information like struct size, symbol
Dsysfs-tty6 console devices, like 'tty1 ttyS0'.
17 device, like 'tty1'.
26 UART port in serial_core, that is bound to TTY like ttyS0.
Dsysfs-bus-iio-mpu60508 is a 3x3 unitary matrix. A typical mounting matrix would look like
Dsysfs-firmware-dmi-tables7 entry point contains general information, like SMBIOS
Ddebugfs-ec6 General information like which GPE is assigned to the EC and whether
Dsysfs-kernel-boot_params26 The whole boot_params directory structure is like below:
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dgpmc-nand.txt99 on various other factors also like;
109 (2) Device parameters like OOBSIZE.
131 probably use lower ecc-schemes like BCH8.
/linux-4.4.14/fs/fat/
DKconfig9 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
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt21 (like removing the whole kernel tree via a single network command).
46 system and put the data where it belongs (like the page or inode cache).
59 operations (like lookups or directory listings) between them according to IO priorities.
/linux-4.4.14/tools/build/Documentation/
DBuild.txt112 to make it easier to invoke build like:
129 It's possible to include special rule if needed (like we do for flex or bison
162 It's possible to build single object file by choice, like:
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Ddigicolor-usart.txt4 UART. USART also support synchronous serial protocols like SPI and I2S. Use
Dsirf-uart.txt27 On the board-specific dts, we can put rts-gpios and cts-gpios like
/linux-4.4.14/drivers/media/pci/dm1105/
DKconfig14 Support for cards based on the SDMC DM1105 PCI chip like
/linux-4.4.14/fs/ecryptfs/
DKconfig22 backends, like OpenSSL.
/linux-4.4.14/drivers/staging/rtl8723au/
DTODO3 ones have been removed, but things like channel > 14 still exist.
/linux-4.4.14/tools/perf/Documentation/
Dperf-data.txt22 like:
Dcallchain-overhead-calculation.txt21 Consider the following example; there are three functions like below.
44 recorded with callchains the output will show something like below
Dperf.txt17 range (0, 10). Use like:
Dperf-lock.txt27 'perf lock info' shows metadata like threads or addresses
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-arvo25 Description: When read, this file returns some info about the device like the
34 Description: The keyboard lets the user deactivate 5 certain keys like the
Dsysfs-driver-hid-roccat-kovaplus57 Description: When read, this file returns general data like firmware version.
94 profile_settings holds information like resolution, sensitivity
110 profile_settings holds information like resolution, sensitivity
Dsysfs-driver-hid-roccat-pyra43 Description: When read, this file returns general data like firmware version.
80 profile_settings holds information like resolution, sensitivity
96 profile_settings holds information like resolution, sensitivity
/linux-4.4.14/Documentation/sysctl/
DREADME29 only the sysctl options used in this file, I'd like to hear of
75 really like to hear about it :-)
Dnet.txt59 to queuing disciplines that work well without configuration like stochastic
61 queuing disciplines like Hierarchical Token Bucket or Deficit Round Robin
64 leaves. Virtual devices (like e.g. lo or veth) ignore this setting and instead
136 occur because of problems on the network like duplicate address or bad
293 preserved in order to be consistent with things like tcp_rmem.
/linux-4.4.14/net/bluetooth/
DKconfig19 technologies like IrDA. Bluetooth operates in personal area range
39 utilities like hciconfig and bluetoothd. These utilities and updates
/linux-4.4.14/arch/m68k/
DKconfig101 current kernel, and to start another kernel. It is like a reboot
102 but it is independent of the system firmware. And like a reboot
/linux-4.4.14/drivers/firewire/
DKconfig37 FireWire bus. SBP-2 devices include storage devices like
39 like scanners.
/linux-4.4.14/Documentation/target/
Dtcm_mod_builder.txt28 $FABRIC_MOD_name' parameters, and actually running the script looks like:
52 Would you like to add tcm_nab5000to drivers/target/Kbuild..? [yes,no]: yes
53 Would you like to add tcm_nab5000to drivers/target/Kconfig..? [yes,no]: yes
/linux-4.4.14/drivers/gpu/drm/vmwgfx/
DKconfig13 Choose this option if you would like to run 3D acceleration
/linux-4.4.14/Documentation/devicetree/bindings/arm/keystone/
Dkeystone.txt9 the form "ti,keystone-*". Generic devices like gic, arch_timers, ns16550
/linux-4.4.14/fs/
DKconfig.binfmt130 Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
139 binaries just like native Alpha binaries on your Alpha machine. For
153 formats into the kernel. You will like this especially when you use
154 programs that need an interpreter to run like Java, Python, .NET or
/linux-4.4.14/Documentation/serial/
Dserial-rs485.txt17 half-duplex hardware like an RS485 transceiver or any RS232-connected
18 half-duplex devices like some modems.
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt5 devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth.
10 another capabilities like L2 TLB or block-fetch buffers to minimize translation
/linux-4.4.14/Documentation/scsi/
Dosst.txt9 It won't address issues like "How do I compile a kernel?" or "How do I load
31 The osst is a new high-level SCSI driver, just like st, sr, sd and sg. It
34 are character devices with major no 206 and minor numbers like the /dev/stX
67 add something like
108 Expect something like 1.8MB/s for the SC-x0 drives and 0.9MB/s for the DI-30.
DNinjaSCSI.txt60 [5] Copy nsp_cs.ko to suitable place, like /lib/modules/<Kernel version>/pcmcia/ .
109 your computer, you encount some *BAD* error like disk crash.
/linux-4.4.14/drivers/net/wireless/rsi/
DKconfig13 Say Y, if you would like to enable debug support. This option
/linux-4.4.14/drivers/staging/rtl8188eu/
DTODO3 ones have been removed, but things like channel > 14 still exist.
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Ddmm.txt6 interleaving, optimizing transfer of 2D block objects, and provide MMU-like page
/linux-4.4.14/Documentation/scheduler/
Dsched-nice-design.txt16 understand it, the timeslice graph went like this (cheesy ASCII art
47 So for HZ=1000 we changed nice +19 to 5msecs, because that felt like the
70 Note that the 'inc' is relative to the current nice level. Tools like
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/
Demac.txt112 "ibm,mcmal-CHIP" where CHIP is the host ASIC (like
132 "ibm,zmii-CHIP" where CHIP is the host ASIC (like
141 "ibm,rgmii-CHIP" where CHIP is the host ASIC (like
/linux-4.4.14/drivers/media/dvb-core/
DKconfig26 of device (like demuxes and frontends) per adapter, but udev
/linux-4.4.14/drivers/gpu/drm/gma500/
DKconfig10 # GMA500 depends on ACPI_VIDEO when ACPI is enabled, just like i915
/linux-4.4.14/drivers/net/wimax/i2400m/
DKconfig16 Connection 2400 over USB (like any of the Intel Wireless
/linux-4.4.14/drivers/bcma/
DREADME5 AMBA standard fields like CID and PID.
/linux-4.4.14/fs/sysfs/
DKconfig17 delegating policy decisions, like persistently naming devices.
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Dautoidle.txt8 clock, it is always a derivative of some basic clock like a gate, divider,
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Drtc-palmas.txt11 - ti,backup-battery-chargeable: The Palmas series device like TPS65913 or
/linux-4.4.14/Documentation/cpuidle/
Ddriver.txt21 It can also support the dynamic changes (like battery <-> AC), by using
/linux-4.4.14/fs/befs/
DKconfig8 on files and directories, and database-like indices on selected
/linux-4.4.14/scripts/coccinelle/free/
Difnullfree.cocci56 msg = "WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recu…
/linux-4.4.14/net/hsr/
DKconfig16 instant fail-over network. Each HSR node in the ring acts like a
/linux-4.4.14/Documentation/block/
Dpr.txt7 these (like SCSI). Persistent Reservations allow restricting
99 This ioctl command works like IOC_PR_PREEMPT except that it also aborts
Dcmdline-partition.txt10 The format for the command line is just like mtdparts:
/linux-4.4.14/Documentation/devicetree/bindings/display/ti/
Dti,omap-dss.txt21 The encoder modules encode the received RGB pixel stream to a video output like
32 The video ports are used to describe the connections to external hardware, like
/linux-4.4.14/fs/reiserfs/
DKconfig27 If you like it, you can pay us to add new features to it that you
83 implemented by security modules like SELinux. This option
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei-client-bus.txt62 The driver init and exit routines for this device would look like:
103 And the driver's simplified probe routine would look like that:
/linux-4.4.14/arch/um/
DKconfig.um44 If you'd like to be able to work with files stored on the host,
53 the kernel, somewhat like the i386 SysRq interface. Since there is
/linux-4.4.14/Documentation/sh/
Dnew-machine.txt20 hierarchy looks like the following:
113 might look something like:
192 this must be defined as something like:
224 need to be listed). For our new board, this entry can look like:
261 Looking at the 'make help' output, you should now see something like:
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt117 that currently have no standard, like the FSL CPM.
290 otherwise like interrupt routing or a list of devices behind an I2C bus.
330 expected that a bootloader like uboot provides a bit more support,
415 boot for things like un-flattening the device-tree, allocating an
417 way to avoid overriding critical things like, on Open Firmware
474 need to be in that order) looks like this (addresses go from top to
546 of address and no possible sibling of the same name (like /memory or
559 which isn't only a virtual "container" for more nodes, like "/cpus"
587 you a idea of what a device-tree looks like. I have purposefully kept
589 order to give you a better idea of what the tree looks like in
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/x86/
Dce4100.txt6 Many of the "generic" devices like HPET or IO APIC have the ce4100
/linux-4.4.14/fs/nilfs2/
DKconfig9 consistency like conventional LFS, it achieves quick recovery after
/linux-4.4.14/arch/arm/boot/dts/
Domap-gpmc-smsc9221.dtsi4 * Compared to smsc911x, smsc9221 (and others like smsc9217
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dbrcm,bcm2835-cprman.txt11 clock generators, but a few (like the ARM or HDMI) will source from
/linux-4.4.14/scripts/coccinelle/api/alloc/
Dalloc_cast.cocci2 /// like kmalloc, kzalloc, kmem_cache_alloc, kmem_cache_zalloc etc.
/linux-4.4.14/Documentation/cpu-freq/
Dcore.txt33 policy changes (ex. thermal modules like ACPI) or of all
35 speed limits (like LCD drivers on ARM architecture). Additionally, the
/linux-4.4.14/Documentation/ABI/stable/
Dfirewire-cdev70 Receive various events. There are solicited events like
103 tools like jujuutils, fwhack, ...
/linux-4.4.14/drivers/memory/
DKconfig35 asynchronuous memory devices like ASRAM, NOR and NAND memory. A total
58 memory drives like NOR, NAND, OneNAND, SRAM.
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dti-phy.txt15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
/linux-4.4.14/lib/fonts/
DKconfig14 Say Y here if you would like to use fonts other than the default
101 big letters (like the letters used in the SPARC PROM). If the
/linux-4.4.14/Documentation/bus-devices/
Dti-gpmc.txt5 memory devices like
6 * Asynchronous SRAM like memories and application specific integrated

12345