| /linux-4.4.14/drivers/scsi/dpt/ |
| D | sys_info.h | 285 uCHAR something; member
319 uCHAR something; member
353 uCHAR something; member
387 uCHAR something; member
|
| /linux-4.4.14/arch/cris/ |
| D | Kconfig | 364 something else.
374 something else.
399 something else.
409 something else.
434 something else.
468 something else.
491 something else.
501 something else.
526 something else.
536 something else.
|
| /linux-4.4.14/Documentation/networking/ |
| D | cops.txt | 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
|
| D | tc-actions-env-rules.txt | 23 Post on netdev if something is unclear.
|
| D | 6pack.txt | 24 to experiment with something completely different from the known CSMA and
155 this is a problem of the 6pack driver or something else in the kernel.
|
| D | radiotap-headers.txt | 111 /* see if this argument is something we can use */
|
| D | generic-hdlc.txt | 35 Usually you want something like:
|
| D | eql.txt | 67 Unpack a recent kernel (something after 1.1.92) someplace convenient
228 make sure you have asyncmap set to something so that control
|
| D | README.sb1000 | 118 If this doesn't help, try something like `ping -c 5 204.71.200.67' to
189 and try setting the delay to something like 60 microseconds with:
|
| D | ieee802154.txt | 61 submits skb to qdisc), so if you need something from that cb later, you should
|
| D | decnet.txt | 38 start working. If you need something more complicated or are unsure how
91 or something similar, to /etc/sysconfig/network-scripts/ifcfg-eth0 or
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | callchain-overhead-calculation.txt | 25 /* do something */
29 /* do something */
44 recorded with callchains the output will show something like below
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-fpga-manager | 12 The intent is to provide enough detail that if something goes
13 wrong during FPGA programming (something that the driver can't
|
| D | sysfs-class-rc | 24 something like:
70 for the wakeup filter, something like:
|
| /linux-4.4.14/Documentation/usb/ |
| D | dwc3.txt | 4 Please pick something while reading :)
35 handed something to thread so we don't process event X prio Y
|
| D | authorization.txt | 64 checking if the class, type and protocol match something is the worse
66 to break it). If you need something secure, use crypto and Certificate
|
| D | rio.txt | 87 If you see something like:
95 If you see something like:
|
| D | gadget_serial.txt | 194 should show something like this:
226 should show something like this:
249 system log saying something like "Gadget Serial converter now
|
| D | hotplug.txt | 122 something like this:
|
| D | usbmon.txt | 81 This is where you do something that creates the traffic: plug in a flash key,
148 If they find something else, like a letter, they read the setup packet before
|
| D | gadget_hid.txt | 18 HID function descriptors you want to use - E.G. something
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | automount-support.txt | 14 Then from userspace, you can just do something like:
24 And then if you look in the mountpoint catalogue, you'll see something like:
82 If the mountpoint in question is in referenced by something other than
|
| D | befs.txt | 75 filesystem (experimental)", or something like that. Enable that option
|
| D | seq_file.txt | 44 sequence will continue until the user loses patience and finds something
45 better to do. The file is seekable, in that one can do something like the
144 code in the usual manner indicates that something went wrong; it will be
|
| D | gfs2-uevents.txt | 58 information about what the error is, which is something that needs to
|
| D | debugfs.txt | 34 clean it up at the end). A NULL return value indicates that something went
141 If you want to dump a block of registers (something that happens quite
|
| D | Locking | 159 dqio_sem) (unless an admin really wants to screw up something and
476 since this is something the userspace has to take care about.
480 not normally something one needs to worry about. Return values > 0 will be
578 (if you break something or notice that it is broken and do not fix it yourself
|
| D | tmpfs.txt | 21 as shared or something like that. Further on you can check the actual
|
| D | ramfs-rootfs-initramfs.txt | 16 Virtual Memory system needs the memory for something else. Similarly, data
318 something brand new. The kernel provides its own tools to create and
|
| D | btrfs.txt | 189 Force clearing and rebuilding of the disk space cache if something
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ieee802154/ |
| D | mrf24j40.txt | 7 - spi-max-frequency: maximal bus speed, should be set something under or equal
|
| /linux-4.4.14/arch/cris/boot/rescue/ |
| D | kimagerescue.S | 123 ;; check if we got something on the serial port
130 ;; got something - copy the byte and loop
|
| D | head_v10.S | 286 ;; check if we got something on the serial port
293 ;; got something - copy the byte and loop
|
| /linux-4.4.14/drivers/parport/ |
| D | TODO-parport | 13 bits when they have something to say. We should read out and deal
|
| /linux-4.4.14/Documentation/ |
| D | cpu-load.txt | 41 |_ something begins working |
42 |_ something goes to sleep
|
| D | circular-buffers.txt | 158 The producer will look something like this:
186 Note that wake_up() does not guarantee any sort of barrier unless something
199 The consumer will look something like this:
233 fact that we are writing to something that can be read concurrently,
|
| D | debugging-modules.txt | 12 of debugging module problems is something like this:
|
| D | kref.txt | 106 do something like:
125 something else or passing it off to something else, there is no reason
|
| D | bus-virt-phys-mapping.txt | 41 CPU sees a memory map something like this (this is from memory):
85 pointer from the kernel. So you can have something like this:
184 support both can do something like:
|
| D | basic_profiling.txt | 1 These instructions are deliberately very basic. If you want something clever,
|
| D | preempt-locking.txt | 27 something = tux[smp_processor_id()];
59 play while another task releases it. If you want to do something
|
| D | ManagementStyle | 124 something wrong with both projects, and the reason the people involved
193 second version in particular is a great way to either learn something
194 new about "xxx" or seem _extra_ managerial by pointing out something the
202 are doing something irreversible when you _do_ prod them in some
|
| D | ldm.txt | 57 When Linux boots, you will see something like:
|
| D | sparse.txt | 8 "__bitwise" is a type attribute, so you have to do something like this:
|
| D | mailbox.txt | 58 return; /* Or do something else here */
|
| D | serial-console.txt | 89 Programs that want to do something with the virtual console usually
|
| D | stable_api_nonsense.txt | 12 programs that were built on a pre 0.9something kernel that still work
182 proven type of development model must be doing something right :)
|
| D | CodingStyle | 60 something to hide:
306 NOTE! Again - there needs to be a _reason_ for this. If something is
368 shouldn't exceed 5-10, or you're doing something wrong. Re-think the
455 small comments to note or warn about something particularly clever (or
594 because they slept or did something else for a while.
771 something it would have done anyway.
|
| D | remoteproc.txt | 73 * something went wrong. handle it and leave.
250 do something (e.g. allocate a system resource). Sometimes a negotiation
|
| D | xz.txt | 115 kernel-related mailing lists, so if there's something I should know,
|
| D | pinctrl.txt | 444 On the bottom row at { A1, B1, C1, D1, E1, F1, G1, H1 } we have something
477 In this case the array could be something like: { spi0, i2c0, mmc0 }
577 group of pins would work something like this:
746 and similar functions. There are cases where you may be using something
897 to think that you need to come up with something really complex, that the
965 when going to sleep, it might imply that the pin is set into something the
1159 The result of grabbing this mapping from the device with something like
|
| D | HOWTO | 177 first, before asking something that has already been answered in the
524 proportional to the size of the patch, or something).
526 Small patches also make it very easy to debug when something goes
529 something).
|
| D | atomic_ops.txt | 113 you should use something like the following:
166 the compiler from doing this, write something like:
452 declaring the above to return "long" and just returning something like
|
| D | eisa.txt | 28 by the bus code. This can go from something as simple as reserving
|
| D | stable_kernel_rules.txt | 13 security issue, or some "oh, that's not good" issue. In short, something
|
| D | magic-number.txt | 39 something will change before 2.2.x. The entries are
|
| D | applying-patches.txt | 101 If patch encounters something that doesn't look quite right it has two
105 One example of something that's not 'quite right' that patch will attempt to
192 This will let you move from something like 2.6.12.2 to 2.6.12.3 in a single
|
| D | cpu-hotplug.txt | 181 the platform should have something like an attention button in PCI hotplug.
306 You can fail PREPARE notifiers if something doesn't work to prepare resources.
|
| D | DMA-API-HOWTO.txt | 126 something like __va(). [ EDIT: Update this when we integrate
212 The standard 32-bit addressing device would do something like this:
263 address you might do something like:
344 something like:
|
| D | vgaarbiter.txt | 76 poll : event if something changes on any card (not just the
|
| D | BUG-HUNTING | 143 because Linux snapshots will let you do this - something that you can't
|
| D | parport.txt | 74 kernel boot parameters to get the same effect. Add something like the
|
| D | module-signing.txt | 94 Setting this option to something other than its default of
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | design-patterns.txt | 102 The design pattern is the same for an hrtimer or something similar that will
110 standard C, which allows something similar to object oriented behaviours.
|
| D | devres.txt | 115 if (check something)
176 For example, you can do something like the following.
|
| D | overview.txt | 96 or something similar in the /lib/init/fstab file on Debian-based systems:
|
| D | driver.txt | 88 need to register with the bus using something like pci_driver_register.
|
| /linux-4.4.14/usr/ |
| D | Kconfig | 30 contains a directory. Setting this user ID (UID) to something
42 contains a directory. Setting this group ID (GID) to something
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | PROBLEMS | 37 Looks like XFree does something different when setting up the video memory?
56 screen mode. Maybe we need something faster than the PCI bus ...
|
| D | README.freeze | 6 might be something else ...
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-ismt | 33 something similar to the following:
|
| D | i2c-amd8111 | 16 If you see something like this:
|
| D | i2c-ocores | 26 E.G. something like:
|
| D | i2c-ali15x3 | 67 output of lspci will show something similar to the following:
79 ** then you must enable ACPI, the PMU, SMB, or something similar
|
| D | i2c-sis630 | 32 If you see something like this:
|
| D | i2c-nforce2 | 32 If your 'lspci -v' listing shows something like the following,
|
| D | i2c-sis96x | 24 The command "lspci" as root should produce something like these lines:
|
| D | i2c-i801 | 68 PCI devices. An output of lspci will show something similar to the
132 and you think there's something interesting on the SMBus (e.g. a
|
| /linux-4.4.14/Documentation/power/ |
| D | tricks.txt | 12 * use ext2. At least it has working fsck. [If something seems to go
|
| D | opp.txt | 190 /* do something when we can't satisfy the req */
208 implementation might choose to do something as follows:
224 choose to do something as follows:
|
| D | swsusp.txt | 15 * between suspend and resume, it may do something wrong. If you change
80 interrupt our programs so processes that are calculating something for a long
123 Q: Maybe I'm missing something, but why don't the regular I/O paths work?
333 A: Well, last messages on the screen are always useful. If something
|
| D | swsusp-dmcrypt.txt | 55 named "swapkey". /etc/fstab of your initrd contains something
|
| D | video.txt | 76 Now, if you pass acpi_sleep=something, and it does not work with your
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | log-writes.txt | 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
|
| D | persistent-data.txt | 74 There are plans to add more. For example, something with an
|
| D | verity.txt | 114 The tree looks something like:
|
| /linux-4.4.14/Documentation/i2c/ |
| D | i2c-protocol | 68 generates something like:
75 system memory into something that appears as a single transfer to the
|
| D | i2c-stub | 63 something like relayfs.
|
| D | fault-codes | 68 This rather vague error means something went wrong when
|
| D | slave-interface | 15 use a character device, be in-kernel only, or something completely different:
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-class-rfkill | 19 transmitter is forced off by something outside of
|
| /linux-4.4.14/net/unix/ |
| D | Kconfig | 13 an embedded system or something similar, you therefore definitely
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-fan.txt | 12 - alarm-gpios: This pin going active indicates something is wrong with
|
| /linux-4.4.14/arch/m68k/q40/ |
| D | README | 19 When something blocks interrupts (HD) it will lose some of them, so far
22 poll the floppy for this reason - something that can't be done in Linux.
54 preceded by the booter signature. This is a trace just in case something
|
| /linux-4.4.14/Documentation/sh/ |
| D | new-machine.txt | 113 might look something like:
138 * do something useful.
183 __IO_PREFIX to something sensible. A typical example would be:
192 this must be defined as something like:
261 Looking at the 'make help' output, you should now see something like:
|
| /linux-4.4.14/fs/hfsplus/ |
| D | Kconfig | 27 Linux. POSIX ACLs doesn't mean something under Mac OS X.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | 00-INDEX | 1 Index of files in Documentation/powerpc. If you think something about
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | GraphicsClient | 12 board supports MTD/JFFS, so you could also mount something on there.
31 something en masse, you should probably get the newer board.
|
| D | Assabet | 184 However Linux should display something like:
|
| /linux-4.4.14/Documentation/arm/sunxi/ |
| D | clocks.txt | 15 While the system is operational, you would see something like
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | vdso | 8 if you set CS on x86 to something strange, the vDSO functions are
|
| D | sysfs-class-rfkill | 54 The transmitter is forced off by something outside of
|
| /linux-4.4.14/Documentation/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 65 …WFReportParams -> StandAlone [ label="during handshake\lpeers do not agree\labout something essent…
|
| /linux-4.4.14/Documentation/fb/ |
| D | cirrusfb.txt | 7 { just a little something to get people going; contributors welcome! }
|
| D | cmap_xfbdev.txt | 22 *. X11 apps do something like the following when trying to use grayscale.
|
| D | 00-INDEX | 1 Index of files in Documentation/fb. If you think something about frame
|
| D | vesafb.txt | 73 "bad mode number" message if something goes wrong.
|
| D | sstfb.txt | 12 in progress, I feel uncomfortable with releasing tarballs of something
|
| /linux-4.4.14/drivers/eisa/ |
| D | Kconfig | 26 # Using EISA_VIRTUAL_ROOT on something other than an Alpha or
|
| /linux-4.4.14/Documentation/i2c/muxes/ |
| D | i2c-mux-gpio | 35 E.G. something like this for a MUX providing 4 bus segments
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | machine.txt | 55 The name field should be set to something that is usefully descriptive
|
| /linux-4.4.14/Documentation/vm/ |
| D | highmem.txt | 102 /* Do something to the contents of that page. */
150 page being 32-bytes that would end up being something in the order of 112G
|
| D | userfaultfd.txt | 7 memory page faults, something otherwise only the kernel code could do.
|
| D | pagemap.txt | 154 Using pagemap to do something useful:
|
| /linux-4.4.14/drivers/mmc/card/ |
| D | Kconfig | 43 (i.e. they can't do scatter-gather), something the kernel
|
| /linux-4.4.14/drivers/mtd/onenand/ |
| D | Kconfig | 19 flipped accidentally due to device wear or something else.
|
| /linux-4.4.14/tools/testing/selftests/futex/ |
| D | README | 56 Perhaps something like "wait-wake-1" "wait-wake-2" is adequate, leaving the
|
| /linux-4.4.14/drivers/iio/magnetometer/ |
| D | Kconfig | 96 (*) one of these is necessary to do something.
|
| /linux-4.4.14/Documentation/acpi/apei/ |
| D | einj.txt | 20 has an option to enable error injection. Look for something called WHEA
167 You should see something like this in dmesg:
|
| /linux-4.4.14/arch/blackfin/mach-common/ |
| D | interrupt.S | 180 # We are going to dump something out, so make sure we print IPEND properly
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | README | 9 don't know they need to tweak something, or because they don't
|
| /linux-4.4.14/Documentation/prctl/ |
| D | no_new_privs.txt | 50 fcap-using binaries; it will need to compromise something without the
|
| D | seccomp_filter.txt | 104 dependent value -- if resuming execution, set it to something
190 something like acpi_pm.
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | kirkwood-b3.dts | 102 * There is something on the bus at address 0x64.
|
| D | rk3288-veyron.dtsi | 253 * we just refer to vcc33_io every time something is
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig.txt | 155 names, so you have to know something close to what you are
212 names, so you have to know something close to what you are
|
| D | kbuild.txt | 12 by modprobe to not fail when trying to load something builtin.
|
| /linux-4.4.14/Documentation/fmc/ |
| D | fmc-chardev.txt | 11 bus-specific address but no associated name, or something like
|
| D | fmc-write-eeprom.txt | 8 Overwriting the EEPROM is not something you should do daily, and it is
|
| D | mezzanine.txt | 85 carriers will most likely offer something similar but not identical,
|
| /linux-4.4.14/Documentation/scsi/ |
| D | dc395x.txt | 98 Note: The GNU GPL says also something about warranty and liability.
|
| D | qlogicfas.txt | 45 command or something. It comes up faster if this is set to zero, and
|
| D | osst.txt | 67 add something like
108 Expect something like 1.8MB/s for the SC-x0 drives and 0.9MB/s for the DI-30.
|
| D | advansys.txt | 130 Increasing LOG_BUF_LEN in kernel/printk.c to something like
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | CMI8330 | 41 You should get something similar in syslog:
|
| D | SoundPro | 54 do something like the following (which *must* match the isapnp/BIOS
|
| D | README.modules | 29 Then, add to your /etc/modprobe.d/oss.conf something like:
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 8.Conclusion | 7 SubmittingDrivers are also something which all kernel developers should
|
| D | 6.Followthrough | 66 that you don't realize that something is fundamentally wrong or, perhaps,
198 On very rare occasion, you may see something completely different: another
|
| /linux-4.4.14/lib/raid6/ |
| D | int.uc | 27 /* Change this from BITS_PER_LONG if there is something better... */
|
| /linux-4.4.14/drivers/iio/gyro/ |
| D | Kconfig | 104 (*) one of these is necessary to do something.
|
| /linux-4.4.14/Documentation/spi/ |
| D | butterfly | 13 can come up with something fancier, providing ciruit protection to the
|
| /linux-4.4.14/drivers/iio/pressure/ |
| D | Kconfig | 112 (*) one of these is necessary to do something.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | driver.txt | 98 something like this sequence in its interrupt handler:
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
|
| /linux-4.4.14/Documentation/timers/ |
| D | timers-howto.txt | 65 it is something to be aware of.
|
| /linux-4.4.14/Documentation/mn10300/ |
| D | ABI.txt | 117 Normally the kernel uses something like:
|
| /linux-4.4.14/arch/x86/boot/ |
| D | header.S | 309 # in case something decided to "use" it
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | README.mm | 45 0xc0000000, to co-exist with the user-mode mapping. We will do something
107 be something like this:
|
| /linux-4.4.14/Documentation/input/ |
| D | joystick-api.txt | 154 /* do something interesting with processed events */
181 replace the read above with something like
|
| D | yealink.txt | 33 A: If you see something like:
|
| D | gameport-programming.txt | 35 space only when something really is using it. Disable it again in the
|
| D | ff.txt | 31 something goes wrong.
|
| /linux-4.4.14/drivers/usb/serial/ |
| D | oti6858.c | 96 u8 something; /* always equals 0x43 */ member
529 buf->something = 0x43; in oti6858_open()
|
| /linux-4.4.14/Documentation/RCU/ |
| D | NMI-RCU.txt | 53 for anyone attempting to do something similar on Alpha or on systems
|
| D | UP.txt | 113 lock must use something like spin_lock_irqsave() to
|
| /linux-4.4.14/Documentation/firmware_class/ |
| D | README | 55 image in fw_entry->{data,size}. If something went wrong
|
| /linux-4.4.14/drivers/media/usb/pwc/ |
| D | philips.txt | 77 something more than 4 is an absolute waste. This memory is only
189 If you want to trace something, look up the bit value(s) in the table
|
| /linux-4.4.14/Documentation/x86/ |
| D | exception-tables.txt | 40 was not swapped in, write protected or something similar. However,
152 The optimizer does a good job and gives us something we can actually
|
| /linux-4.4.14/Documentation/arm/ |
| D | Porting | 103 out of bounds memory accesses (eg, something writing off the end
|
| D | Interrupts | 101 "simple", or your own specific handler if you need to do something special.
|
| /linux-4.4.14/drivers/iio/accel/ |
| D | Kconfig | 75 (*) one of these is necessary to do something.
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-memory.txt | 74 something.
|
| /linux-4.4.14/drivers/net/wireless/b43/ |
| D | Kconfig | 10 Check "lspci" for something like
|
| /linux-4.4.14/Documentation/ia64/ |
| D | efirtc.txt | 36 expose this new way of representing time. Instead we use something very
|
| /linux-4.4.14/ |
| D | README | 5 kernel, and what to do if something goes wrong.
279 - Keep a backup kernel handy in case something goes wrong. This is
350 important: it tells something about why the kernel dumped code (in
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 12 or someone learns something from it.
626 into the wrong direction. Maybe something to investigate later. Could
648 in the result byte and then do something like
709 programmed in C. Of course it might be possible to squeeze something more
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex-design.txt | 29 is something called unbounded priority inversion. That is when the high
257 /* do something */
268 /* do something else */
278 /* do something again */
286 in func4 in the "do something again" area, we have a locking that follows:
613 There's also something special about a pending owner. That is a pending owner
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | omap_pm | 17 latency framework or something else;
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 20 something every GPU driver has to do on its own.
148 Especially if your reference clock is something really slow like the display
|
| /linux-4.4.14/arch/cris/arch-v32/kernel/ |
| D | head.S | 166 cmp.d 0x10000, $r0 ; Arbitrary, something above this code.
|
| /linux-4.4.14/tools/perf/config/ |
| D | utilities.mak | 28 # something that won't be converted, so that the
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace-design.txt | 35 running something like:
331 Every arch has an init callback function. If you need to do something early on
|
| D | tracepoint-analysis.txt | 60 to page allocation would look something like:
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | operations.txt | 52 Someone wanting to issue an operation should allocate something with this
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 439 is something of value in them, on the stack or elsewhere before making a
980 from this you should see something like
1003 we get something like
1018 If you get a crash which says something like
1228 d g to display the gprs, this should display something like
1513 You should see something like:
1740 You might now be thinking that the line above didn't work, something extra had
1786 you might see something like.
1833 In short it is far more useful than something like a crash log could ever hope
2059 You should see something like
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.txt | 181 by adding a module parameter. The conversion for this would be something like:
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-framework.txt | 237 i2c_get_clientdata(). For other busses something similar needs to be done.
565 Both functions return NULL if something went wrong.
570 The use of chipid is something that needs to be looked at more closely at a
632 - name: set to something descriptive and unique.
737 something.
1025 Several drivers need to do something when the first file handle is opened and
|
| D | v4l2-controls.txt | 18 All the rest is something that can be done centrally.
213 Note that if something fails, the function will return NULL or an error and
318 For all other types use ctrl->p_cur.p<something>. Basically the val
|
| D | README.pvrusb2 | 176 mmap()'ed buffers or something even more exotic.
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | isp.doc | 109 exception (vector #61), the operating system should execute something
|
| D | fpsp.doc | 101 (vector #11), the operating system should execute something similar to:
|
| D | TEST.DOC | 96 itest.sa data and execute something similar to:
|
| /linux-4.4.14/fs/jffs2/ |
| D | README.Locking | 27 time this happens are part of the new node, not just something that
|
| /linux-4.4.14/Documentation/networking/caif/ |
| D | spi_porting.txt | 131 * in something similar to this. The only thing you need to
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 285 you want to change something, go ahead, it probably won't hurt
339 You can install them by using ftp or something to copy them into the
479 something else, like host ptys.
668 you specify is the slave end of a tty/pty pair, something else must
734 consoles to something else:
1513 something as a source of input. So, the helper is used as a
2505 deadlocked on a semaphore or something similar. In this case, when
2593 o type 'att 1' to the ddd gdb and you will see something like
2680 At this point, you debug normally. When you insmod something, the
2681 expect magic will kick in and you'll see something like:
[all …]
|
| /linux-4.4.14/arch/cris/arch-v32/drivers/ |
| D | Kconfig | 49 if you do not need DMA to something else.
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | ppc-pv.txt | 107 of something. This is what we call "flags".
|
| /linux-4.4.14/Documentation/thermal/ |
| D | power_allocator.txt | 87 `thermal_zone_params` were being passed, then something like below
|
| /linux-4.4.14/Documentation/isdn/ |
| D | syncPPP.FAQ | 94 writes in the debug log something like:
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | zram.txt | 45 and, in general case, something like:
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 51 ok for the serial and parallel port, where you can do something
|
| /linux-4.4.14/Documentation/crypto/ |
| D | descore-readme.txt | 161 the table size. in fairness though he might be encoding something particular
313 S-box mapping order or something) into the right format for you.
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 180 subsystem state is something that's expected to happen frequently
309 the "cpuset" cgroup subsystem, the steps are something like:
402 Now you want to do something with this cgroup.
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 109 really force takeovers of sole proprietorships.) This was something
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | completion.txt | 16 msleep(1) loop to allow something else to proceed, you probably want to
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | cpu-drivers.txt | 272 /* Do something with pos */
|
| /linux-4.4.14/Documentation/hid/ |
| D | hiddev.txt | 18 The data flow for a HID event produced by a device is something like
|
| /linux-4.4.14/drivers/mtd/devices/ |
| D | Kconfig | 69 flipped accidentally due to device wear or something else.
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 186 Linux it will look something like this:
382 can look something like this:
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 92 # options do not appear when something else selects it. We need the two options
623 If something does not get converted properly, this option can be
|