| /linux-2.4.37.9/drivers/scsi/ |
| D | pci2000.c | 670 UCHAR *consistent; in Pci2000_Detect() local
707 consistent = pci_alloc_consistent (pdev, consistentLen, &consistentDma); in Pci2000_Detect()
708 if ( !consistent ) in Pci2000_Detect()
730 pci_free_consistent (pdev, consistentLen, consistent, consistentDma); in Pci2000_Detect()
748 padapter->dev[zz][z].scatGath = (PSCATGATH)consistent; in Pci2000_Detect()
750 consistent += 16 * sizeof (SCATGATH); in Pci2000_Detect()
752 padapter->dev[zz][z].cdb = (UCHAR *)consistent; in Pci2000_Detect()
754 consistent += MAX_COMMAND_SIZE; in Pci2000_Detect()
|
| D | 53c700.h | 47 if(!hostdata->consistent) \
50 if(!hostdata->consistent) \
53 if(!hostdata->consistent) \
235 __u32 consistent:1; member
|
| D | README.53c700 | 41 allocate consistent memory (should only be used if your architecture
42 has a mixture of consistent and inconsistent memory). Fully
43 consistent or fully inconsistent architectures should not define this.
69 consistent with the best operation of the chip (although some choose
|
| D | pci2220i.c | 2381 UCHAR *consistent; in GetRegs() local
2458 consistent = pci_alloc_consistent (pcidev, SECTORSXFER * BYTES_PER_SECTOR, &consistentDma); in GetRegs()
2460 consistent = pci_alloc_consistent (pcidev, ATAPI_TRANSFER, &consistentDma); in GetRegs()
2461 if ( !consistent ) in GetRegs()
2467 padapter->kBuffer = consistent; in GetRegs()
|
| D | 53c700.c | 252 hostdata->consistent = 1; in NCR_700_detect()
264 hostdata->consistent = 0; in NCR_700_detect()
366 if(hostdata->consistent) { in NCR_700_release()
|
| D | README.tmscsim | 45 The numbering scheme isn't consistent. The first versions went from 1.00 to
387 it's consistent with the BIOS' behaviour. Old DC390 drivers ignored the
|
| /linux-2.4.37.9/Documentation/sparc/ |
| D | sbus_drivers.txt | 182 Linux supports two styles of using SBUS DVMA: "consistent memory"
183 and "streaming DVMA". CPU view of consistent memory chunk is, well,
184 consistent with a view of a device. Think of it as an uncached memory.
205 In order to perform a consistent DVMA a driver does something
263 Lance driver abuses consistent mappings for data transfer.
|
| /linux-2.4.37.9/Documentation/ |
| D | DMA-mapping.txt | 212 Think of "consistent" as "synchronous" or "coherent".
215 to say, consistent DMA addresses given to the driver will always
218 Good examples of what to use consistent mappings for are:
231 consistent memory just as it may normal memory. Example:
264 To allocate and map large (PAGE_SIZE or so) consistent DMA regions,
286 The consistent DMA mapping interfaces, for non-NULL dev, will always
289 the upper 32-bits and thus perform DAC cycles, consistent allocation
293 In fact, as mentioned above, all consistent memory provided by the
404 Only streaming mappings specify a direction, consistent mappings
627 However, consistent mappings may in fact be used in conjunction with
[all …]
|
| D | unicode.txt | 66 However, since the set of symbols appear to be consistent throughout,
|
| D | digiboard.txt | 58 lists must be consistent, of course.
|
| D | svga.txt | 91 all consistent video modes supported by your BIOS will appear (plus maybe some
|
| D | IPMI.txt | 160 The upper layer of the interface provides the users with a consistent
|
| /linux-2.4.37.9/arch/arm/mm/ |
| D | Makefile | 23 obj-y += consistent.o fault-armv.o ioremap.o mm-armv.o
|
| /linux-2.4.37.9/fs/hfs/ |
| D | TODO | 14 2. An ioctl()-based interface is needed to provide a consistent way
|
| /linux-2.4.37.9/fs/affs/ |
| D | Changes | 115 more consistent. Changed a bad example in the
274 - Tried to make all types 'correct' and consistent.
|
| /linux-2.4.37.9/arch/arm/nwfpe/ |
| D | ChangeLog | 2 * Reformat all but softfloat files to get a consistent coding style.
|
| /linux-2.4.37.9/drivers/scsi/sym53c8xx_2/ |
| D | ChangeLog.txt | 142 consistent with what archs are expecting.
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | ntfs.txt | 157 which is consistent with Windows NT4. Using the show_sys_files mount
219 - Made character conversion to be always consistent. Previously we
|
| /linux-2.4.37.9/fs/ext2/ |
| D | CHANGES | 117 that the blocks and inodes bitmaps are consistent with the free
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | sis900.txt | 78 9. Names of variables were changed to be more consistent.
|
| /linux-2.4.37.9/fs/umsdos/ |
| D | specs | 268 * it tries /bin/sh /etc/rc. To be consistent with
|
| /linux-2.4.37.9/drivers/parport/ |
| D | ChangeLog | 460 looks consistent.
|
| /linux-2.4.37.9/Documentation/cdrom/ |
| D | cdrom-standard.tex | 114 {\em one\/} \linux\ \cdrom\ interface with consistent behavior for all
115 \cdrom\ devices. In addition, this also provides a consistent interface
144 For this reason, the \UCD\ was created to enforce consistent \cdrom\
|
| /linux-2.4.37.9/Documentation/crypto/ |
| D | descore-readme.txt | 145 by adding MORE statements to make the data movement more `consistent'
|
| /linux-2.4.37.9/drivers/net/e1000/ |
| D | LICENSE | 222 reliance on consistent application of that system; it is up to the
|