Home
last modified time | relevance | path

Searched refs:our (Results 1 – 150 of 150) sorted by relevance

/linux-4.4.14/drivers/net/ethernet/chelsio/
DKconfig29 For general information about Chelsio and our products, visit
30 our website at <http://www.chelsio.com>.
32 For customer support, please visit our customer support page at
56 For general information about Chelsio and our products, visit
57 our website at <http://www.chelsio.com>.
59 For customer support, please visit our customer support page at
76 For general information about Chelsio and our products, visit
77 our website at <http://www.chelsio.com>.
79 For customer support, please visit our customer support page at
117 For general information about Chelsio and our products, visit
[all …]
/linux-4.4.14/drivers/lguest/
DREADME18 - In which our potential hero is flown quickly over the landscape for a
27 - Whereby the Guest finds its voice and become useful, and our
31 - Where we trace back to the creation of the Guest, and thus begin our
36 Indeed, it is here that our hero is tested in the Bit of Despair.
39 - Where our understanding of the intertwined nature of Guests and Hosts
43 - Where our fully fledged hero grapples with the Great Question:
/linux-4.4.14/drivers/scsi/csiostor/
DKconfig10 For general information about Chelsio and our products, visit
11 our website at <http://www.chelsio.com>.
13 For customer support, please visit our customer support page at
/linux-4.4.14/drivers/infiniband/hw/cxgb4/
DKconfig9 For general information about Chelsio and our products, visit
10 our website at <http://www.chelsio.com>.
12 For customer support, please visit our customer support page at
/linux-4.4.14/drivers/infiniband/hw/cxgb3/
DKconfig9 For general information about Chelsio and our products, visit
10 our website at <http://www.chelsio.com>.
12 For customer support, please visit our customer support page at
/linux-4.4.14/arch/parisc/math-emu/
DREADME5 enough to update our copies with later changes from HP-UX -- it'll
6 make their 'diff' job easier if our code is relatively unmodified.
/linux-4.4.14/arch/alpha/lib/
Dstrrchr.S21 zapnot a1, 1, a1 # e0 : zero extend our test character
23 sll a1, 8, t5 # e0 : replicate our test character
79 addq t6, t0, v0 # .. e1 : add our aligned base ptr to the mix
Dstrchr.S24 andnot a0, 7, v0 # .. e1 : align our loop pointer
Dev67-strchr.S38 andnot a0, 7, v0 # E : align our loop pointer
/linux-4.4.14/Documentation/i2c/
Dupgrading-clients37 dev_err(dev, "failed to create our state\n");
161 as we are provided with the i2c_client in our example_probe. Instead we
173 And remove the change after our client is attached, as the driver no
190 dev_err(dev, "failed to create our state\n");
241 dev_err(dev, "failed to create our state\n");
Dslave-interface76 our own address and the write bit was detected. The data did not arrive yet, so
86 our own address and the read bit was detected. After returning, the bus driver
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Didle.fuc52 // set our "no interrupt has occurred during our execution" flag
/linux-4.4.14/fs/reiserfs/
DREADME97 Anatoly Pinchuk is a former member of our team who worked closely with
110 curious, because he never really understood the value of our project,
120 our group.
131 Chris Mason dived right into our code, and in just a few months produced
136 for our next major release.
154 anymore, and to dramatically increase our staffing. Ecila funded
DKconfig19 plugins consistent with our motto ``It takes more than a license to
38 latest benchmarks.:-) Use of this option allows our team to go all
/linux-4.4.14/drivers/gpu/drm/vc4/
DKconfig14 our display setup.
/linux-4.4.14/Documentation/fmc/
DFMC-and-SDB.txt2 FMC (FPGA Mezzanine Card) is the standard we use for our I/O devices,
5 In our I/O environments we need to write drivers for each mezzanine
82 changes on our drivers if that happens.
Dmezzanine.txt29 the `fmc.h' file - we hope other users will exploit our framework with
/linux-4.4.14/arch/arm/mach-shmobile/
Dheadsmp-scu.S36 bic r2, r2, r3 @ Clear bits of our CPU (Run Mode)
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-driver-tegra-fuse1 What: /sys/devices/*/<our-device>/fuse
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.seq130 * long as one of our data FIFOs is active.
150 * still be data in our FIFOs draining to the host. Complete
309 * tag set by the host so that our SCB dma engine
322 /* Increment our position in the QINFIFO. */
365 * our batching and round-robin selection scheme
502 * until we return to our idle loop), use a
570 * we are selecting with atn regardless of our packetized
573 * to our negotiation table entry for this selection will
624 * the point of selection until our idle
625 * loop determines that neither of our FIFOs
[all …]
Daic7xxx.seq53 * as well as for our selection to complete just in case the reselection wins
125 * the QINFIFO next pointer will not match our saved
422 /* Prevent our read from triggering another REQ */
430 * list. This is achieved by simply moving our "next" pointer into
456 * sending our identify messages.
840 * phase, our transfer location has almost certainly been
957 * allows us to update our notion of where we are
963 * call our idle loop until it is able to load
968 * our residual information is still correct from
1074 * Due to bayonette style S/G handling, our residual
[all …]
Daic7xxx.reg911 * without honoring our ATN
1388 * on top of the BIOS values, so we re-use those for our per-target
1558 * Base address of our shared data with the kernel driver in host
1682 mask HSCSIID 0x07 /* our SCSI ID */
1683 mask HWSCSIID 0x0f /* our SCSI ID if Wide Bus */
Daic79xx.reg96 * as the source and destination of any register accesses in our
165 * without honoring our ATN
3902 * Base address of our shared data with the kernel driver in host
4236 * The size of our sense buffers.
4241 * way we handle our scatter gather lists. The driver implements
/linux-4.4.14/Documentation/scheduler/
Dsched-domains.txt36 our CPU is on, starting from its base domain and going up the ->parent chain.
44 that group. If it manages to find such a runqueue, it locks both our initial
46 to our runqueue. The exact number of tasks amounts to an imbalance previously
/linux-4.4.14/arch/openrisc/
DTODO.openrisc4 that are due for investigation shortly, i.e. our TODO list:
/linux-4.4.14/Documentation/driver-model/
Ddesign-patterns.txt41 called. This is our state container for this instance of the device driver.
114 We can see here that we avoid having global pointers to our struct foo *
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt44 - our-claim-gpio: The GPIO that we use to claim the bus.
71 our-claim-gpio = <&gpf0 3 1>;
Di2c-cros-ec-tunnel.txt6 to tunnel our i2c commands through the EC.
/linux-4.4.14/Documentation/mic/
Dmic_overview.txt16 for applications. A key benefit of our solution is that it leverages
18 though in our case the virtio framework is used across a PCIe bus.
/linux-4.4.14/Documentation/scsi/
Daic79xx.txt119 - For pre-2.5.X kernels, carefully adjust our segment
121 - Cleanup channel display in our /proc output.
130 to reset our transceivers.
148 - Correct a race condition in our error recovery handler.
436 - Visit our Web site at http://www.adaptec.com/.
450 - Visit our Web site at http://www.adaptec.com/en-US/_common/world_index.
462 - Visit our web site at http://www.adaptec.co.jp/.
Daic7xxx.txt164 and our per-softc lock. This was only possible on RH9,
173 our performance.
333 - Visit our Web site at http://www.adaptec.com/.
347 - Visit our Web site at http://www.adaptec.com/en-US/_common/world_index.
359 - Visit our web site at http://www.adaptec.co.jp/.
DFlashPoint.txt20 development and provided technical support for our host adapters for several
21 years, and are pleased to now make our FlashPoint products available to this
DLICENSE.qla4xxx266 of preserving the free status of all derivatives of our free software and
DLICENSE.qla2xxx267 of preserving the free status of all derivatives of our free software and
DChangeLog.megaraid_sas235 4. Add the input parameter max_sectors to 1MB support to our GEN2 controller.
DChangeLog.lpfc638 (i.e. LOGO) before our FLOGI completes it should be LS_RJT'ed.
1273 when our reset is called.
1445 * Changed the way our pci_device_id structures are initialized
DChangeLog.sym53c8xx150 scsi dma buffer prior to queueing the command to our done
/linux-4.4.14/Documentation/acpi/
Dgpio-properties.txt42 typically this is the device itself (BTH in our case).
51 In our Bluetooth example the "reset-gpio" refers to the second GpioIo()
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt183 file. But first we want to find out what happened to our code in the
240 in our case the address of the label 1 is c017e7a5:
245 the fault, in our case the actual value is c0199ff5:
281 That's it, mostly. If you look at our example, you might ask why
Dkernel-stacks117 If the address does not fit into our expected frame pointer chain we
Dboot.txt979 In our example from above, we would do:
/linux-4.4.14/drivers/net/wireless/ath/carl9170/
DKconfig13 The firmware can be downloaded from our wiki here:
/linux-4.4.14/Documentation/arm/nwfpe/
DNOTES1 There seems to be a problem with exp(double) and our emulator. I haven't
/linux-4.4.14/Documentation/video4linux/
Dhauppauge-wintv-cx88-ir.txt20 Setup 4KHz sampling rate (roughly 2x oversampled; good enough for our RC5
DREADME.pvrusb2179 and USB core entry points are here. This is our "main".
/linux-4.4.14/arch/c6x/lib/
Ddivi.S27 ;; In our implementation, divu and remu are leaf functions,
Dremi.S27 ;; In our implementation, divu and remu are leaf functions,
Dremu.S27 ;; In our implementation, divu and remu are leaf functions,
Ddivu.S27 ;; In our implementation, divu and remu are leaf functions,
/linux-4.4.14/Documentation/video4linux/cx88/
Dhauppauge-wintv-cx88-ir.txt20 Setup 4KHz sampling rate (roughly 2x oversampled; good enough for our RC5
/linux-4.4.14/Documentation/networking/
Dskfp.txt108 If your problem is not listed here, please contact our
112 When contacting our technical support,
Dtcp.txt94 Frames are queued for output by tcp_write. We do our best to send the frames
Dcxgb.txt326 If you have problems with the software or hardware, please contact our
327 customer support team via email at support@chelsio.com or check our website
DLICENSE.qlcnic265 of preserving the free status of all derivatives of our free software and
DLICENSE.qlge265 of preserving the free status of all derivatives of our free software and
Dz8530drv.txt42 driver. If you want to run xNOS instead of our fine kernel AX.25
Dip-sysctl.txt1114 request we will check all our subnets that include the
1122 for primary IP addresses on all our subnets on the outgoing
1126 with the hope we will receive reply for our request and
Dbonding.txt498 Option specifying the rate in which we'll ask our link partner
1327 appropriate device driver modules. For our example above, you can do
2253 acting as a gateway. For our discussion, the important point is that
2281 host acting as a gateway. For our discussion, the important point is
/linux-4.4.14/arch/cris/arch-v10/
DREADME.mm185 PGDIR_SHIFT is the log2 of the amount of memory an entry in the PGD can map; in our
189 The pgd_t from our example will therefore be the 208'th (0xd0) entry in mm->pgd.
206 PAGE_SHIFT is the log2 of the size of a page; 13 in our case. PTRS_PER_PTE is
/linux-4.4.14/Documentation/spi/
Dep93xx_spi31 /* this is our GPIO line used for chip select */
/linux-4.4.14/Documentation/isdn/
DREADME.concap82 is provided) is outside our scope and might be different depending on
83 the encapsulation protocol used, e.g. for a ppp module using our service
177 struct net_device *net_dev; /* net device using our service */
DREADME.gigaset37 If you have another device that works with our driver, please let us know.
379 For help with general configuration problems not specific to our driver,
385 If you solved a problem with our drivers, wrote startup scripts for your
DREADME.sc12 our own option and without warranty. If you choose to assume all and
58 tool kit from our web site.
/linux-4.4.14/firmware/
DWHENCE48 drops binary dsp code images on our heads, but we don't get to see
131 Converted from Intel HEX files, used in our binary representation of ihex.
165 Compiled from original 8051 source into Intel HEX, used in our binary ihex form.
179 Converted from Intel HEX files, used in our binary representation of ihex.
220 Converted from Intel HEX files, used in our binary representation of ihex.
272 Converted from Intel HEX files, used in our binary representation of ihex.
/linux-4.4.14/Documentation/filesystems/
Djfs.txt52 "Mail list Subscribe" at our web page http://jfs.sourceforge.net/
Dpath-lookup.txt82 against our (parent, name) tuple.
92 point to perform the next step of our path walk against.
267 +---------------------+ At this point we have our destination dentry.
Dseq_file.txt85 which will start reading at that position. For our simple sequence example,
160 This structure will be needed to tie our iterator to the /proc file in
Ddirectory-locking9 For our purposes all operations fall in 5 classes:
Dxfs-self-describing-metadata.txt86 could be used, it is more than sufficient for our needs and has relatively
Dvfs.txt994 However, our vfsmount is pinned, and RCU held, so the dentries and
995 inodes won't disappear, neither will our sb or filesystem module.
/linux-4.4.14/Documentation/sh/
Dnew-machine.txt112 get_system_type() and platform_setup(). For our imaginary board, this
129 * If our hardware actually existed, we would do real
224 need to be listed). For our new board, this entry can look like:
/linux-4.4.14/arch/x86/
DMakefile_32.cpu67 # binutils from generating NOPL instructions against our will.
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-200215 * now supported by our character device. As a result,
99 * adjust our polling frequency to a much lower value,
100 * and thus to dramatically reduce our load on Linux,
/linux-4.4.14/Documentation/serial/
Dn_gsm.txt53 /* our modem defaults to a maximum size of 127 bytes */
Dmoxa-smartio483 possible. If all the possible solutions fail, please contact our technical
/linux-4.4.14/Documentation/x86/x86_64/
Dfake-numa-for-cpusets17 emulation setup of "numa=fake=4*512,". This will split our system memory into
/linux-4.4.14/Documentation/
Dhw_random.txt59 access to our RNG for use as a security feature. At this time,
Dmailbox.txt57 /* An ACK to our last sample sent */
Dhwspinlock.txt188 * we took the lock, do our thing now, but do NOT sleep
223 * we took the lock, do our thing now, but do NOT sleep
Dremoteproc.txt69 /* let's power on and boot our remote processor */
78 * our remote processor is now powered on... give it some work
Dkasan.txt144 From a high level, our approach to memory error detection is similar to that
Dkref.txt136 /* We are done with obj, so we pass our refcount off
Drpmsg.txt229 /* send a message on our channel */
DHOWTO478 - "This is for our Enterprise product line."
Dkmemcheck.txt323 collect_signal(). We continue our journey through the stack, to figure out
DSubmittingPatches589 idea was not posted in a public forum. That said, if we diligently credit our
Dpinctrl.txt57 this in our driver:
Dmemory-barriers.txt1394 therefore optimize the variable 'tmp' out of our previous example:
Ddevices.txt3352 in our notation). This removes the problem of exhausting the
/linux-4.4.14/Documentation/networking/caif/
DREADME23 TTY, we are installing our physical serial driver as a line discipline above
/linux-4.4.14/arch/x86/boot/
Dheader.S481 2: # Now %dx should point to the end of our stack space
/linux-4.4.14/Documentation/s390/
DDASD25 We performed our testing on 3380 and 3390 type disks of different
DDebugging390.txt235 On 390 our limitations & strengths make us slightly different.
237 of our 32 bit addresses, however, we use entirely separate address
329 0,1024,2048 & 3072 in this page as for our segment indexes.
330 On z/Architecture our page indexes are now 2k in size
343 our address space control registers.
390 & our devices have large buffers can survive interrupts being shut for
674 Hartmut ( our compiler developer ) also has been threatening to take out the
811 from cp mode ( in our case linux ).
1243 Ah now look at whats in sp+56 (sp+0x38) this is 8001B36A our saved r14 if
1244 you look above at our stackframe & also agrees with GPR14.
[all …]
Ds390dbf.txt643 &debug_test_format_fn, /* our own format function */
/linux-4.4.14/arch/arm/boot/dts/
Dexynos5250-snow-common.dtsi66 our-claim-gpio = <&gpf0 3 GPIO_ACTIVE_LOW>;
642 arb_our_claim: arb-our-claim {
/linux-4.4.14/Documentation/usb/
DWUSB-Design-overview.txt282 We reserve UWB bandwidth for our Wireless USB Cluster, create a Cluster
323 read descriptors and move our data.
356 immediately after to the DTI interface (yep, even the request). If our
401 context (wa_xfer) and submit it. When the xfer is done, our callback is
Drio.txt4 and scanner.c files to model our driver and this informative file.
Dgadget-testing.txt614 host: aplay -l # should list our USB Audio Gadget
640 host: aplay -l # should list our USB Audio Gadget
/linux-4.4.14/Documentation/virtual/kvm/devices/
Darm-vgic.txt78 fixed format for our implementation that fits with the model of a "GICv2
/linux-4.4.14/Documentation/sound/oss/
DAudioExcelDSP1682 driver, for MSS irq10 dma3 in our example.
/linux-4.4.14/Documentation/input/
Dinput-programming.txt136 again. To do that, we would add this to our example driver:
199 struct for each absolute axis your device has. If our button device had also
Djoystick-parport.txt12 and maybe even more. Like when a lightning kills you it is not our problem.
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-memory.txt119 interrupt mask 0x0048. If a bit is cleared in the mask, then we want our ISR to
/linux-4.4.14/Documentation/fpga/
Dfpga-mgr.txt11 The FPGA image data itself is very manufacturer specific, but for our purposes
/linux-4.4.14/drivers/net/ethernet/intel/
DKconfig117 Some of our devices contain thermal sensors, both external and internal.
210 our cards, via a hwmon sysfs interface.
/linux-4.4.14/net/ipv4/
Droute.c1474 u8 tos, struct net_device *dev, int our) in ip_route_input_mc() argument
1503 if (our) in ip_route_input_mc()
1976 int our = ip_check_mc_rcu(in_dev, daddr, saddr, in ip_route_input_noref() local
1978 if (our in ip_route_input_noref()
1986 tos, dev, our); in ip_route_input_noref()
/linux-4.4.14/arch/cris/boot/rescue/
Dhead_v10.S77 ;; That is not where we put our downloaded serial boot-code.
/linux-4.4.14/tools/perf/Documentation/
Dperf-script-python.txt73 Basically our task is to keep a per-syscall tally that gets updated
107 Once we have a perf.data file containing our data, we can use the -g
233 generate some results to print. To do that we need to have our
/linux-4.4.14/Documentation/acpi/apei/
Deinj.txt152 creativity in using this feature expands beyond our expectations).
/linux-4.4.14/Documentation/arm/
Dvlocks.txt37 /* signal our desire to vote */
/linux-4.4.14/Documentation/dmaengine/
Dprovider.txt32 memory copy operation, but our audio device could have a narrower FIFO
107 framework. In our case, that structure is dma_device.
/linux-4.4.14/Documentation/thermal/
Dcpu-cooling-api.txt112 In this simplified representation our model becomes:
/linux-4.4.14/Documentation/powerpc/
Dtransactional_memory.txt157 stack pointer will be back at the tbegin but our in memory stack won't be valid
/linux-4.4.14/Documentation/hwmon/
Dasc762162 address. One could use our flexible zone assignment to have a zone
/linux-4.4.14/Documentation/timers/
Dhrtimers.txt39 settimeofday or NTP time - further underlying our experience by
/linux-4.4.14/arch/sparc/kernel/
Dhead_32.S421 b no_sun4u_here ! AIEEE, a V9 sun4u... Get our BIG BROTHER kernel :))
Dhead_64.S266 stx %l3, [%sp + 2047 + 128 + 0x28] ! arg3: vaddr, our PC
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs-rdma.txt27 In our testing, we have obtained excellent performance results (full 10Gbit
/linux-4.4.14/Documentation/ia64/
Dmca.txt119 special code to cope with our inability to take any locks.
/linux-4.4.14/scripts/genksyms/
Dlex.lex.c_shipped759 /* Keep track of our location in the original source files. */
924 * consistency between YY_CURRENT_BUFFER and our
1910 /* Macros to append to our phrase collection list. */
Dparse.tab.c_shipped1545 /* Extend the stack our own way. */
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt201 On startup, we analyze the BTT flog to create our list of free blocks. We walk
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-kernel-api.txt172 our own internal ioctl call handling. This routine should return -ENOIOCTLCMD
/linux-4.4.14/Documentation/mtd/
Dnand_ecc.txt269 to write our code in such a way that we process data in 32 bit chunks.
391 If we look at e.g. rp14 and rp15 we see that we either xor our data with
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dentry.S303 ;; TODO: see the i386 version. The switch_to which calls resume in our version
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/sec/fuc/
Dg98.fuc0s99 // $r0 is always set to 0 in our code - this allows some space savings.
/linux-4.4.14/arch/arc/
DKconfig375 based on actual usage of FPU by a task. Thus our implemn does
/linux-4.4.14/Documentation/device-mapper/
Dthin-provisioning.txt37 dm-devel@redhat.com with details and we'll try our best to improve
/linux-4.4.14/Documentation/development-process/
D1.Intro109 join our community.
D5.Posting218 people who test our code and let us know when things do not work
D4.Coding209 many of those errors as possible before our code goes into the mainline
/linux-4.4.14/firmware/keyspan_pda/
Dkeyspan_pda.S121 ;;; our bit assignments
Dxircom_pgs.S121 ;;; our bit assignments
/linux-4.4.14/drivers/staging/rtl8192u/
Dcopying255 of preserving the free status of all derivatives of our free software and
/linux-4.4.14/Documentation/power/
Dswsusp.txt80 interrupt our programs so processes that are calculating something for a long
/linux-4.4.14/tools/usb/usbip/
DCOPYING255 of preserving the free status of all derivatives of our free software and
/linux-4.4.14/drivers/staging/rtl8192e/
Dlicense255 preserving the free status of all derivatives of our free software and
/linux-4.4.14/
DCOPYING271 of preserving the free status of all derivatives of our free software and
/linux-4.4.14/Documentation/kbuild/
Dkconfig-language.txt511 the deduced semantics matches our intended Kconfig design goals.
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex673 inserted some valid data-\cdrom.'' Thus, our proposal of the
709 even send in our own patches to the programs. The use of $O_NONBLOCK$
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dpfpsp.S964 # if our emulation, after re-doing the operation, decided that
2945 # from our 4-word stack frame. This means we must calculate the length
Dfpsp.S965 # if our emulation, after re-doing the operation, decided that
2946 # from our 4-word stack frame. This means we must calculate the length
/linux-4.4.14/scripts/dtc/
Ddtc-lexer.lex.c_shipped1255 * consistency between YY_CURRENT_BUFFER and our
Ddtc-parser.tab.c_shipped1326 /* Extend the stack our own way. */
/linux-4.4.14/Documentation/cgroups/
Dmemory.txt190 Note: we just account pages-on-LRU because our purpose is to control amount
Dcpusets.txt447 that would be beyond our understanding. So if each of two partially
/linux-4.4.14/scripts/kconfig/
Dzconf.lex.c_shipped1404 * consistency between YY_CURRENT_BUFFER and our
Dzconf.tab.c_shipped1548 /* Extend the stack our own way. */
/linux-4.4.14/drivers/tty/serial/
DKconfig271 generally being used as a console, we use our own output
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt4161 backtrace in and wait for our crack debugging team to fix the problem.