Home
last modified time | relevance | path

Searched refs:ordering (Results 1 – 22 of 22) sorted by relevance

/linux-2.4.37.9/Documentation/networking/
Dx25-iface.txt77 - With Linux 2.4.x (and above) SMP kernels, packet ordering is not
91 SMP re-ordering will not occur if the driver's interrupt handler is
Dppp_generic.txt14 ordering and combining received fragments
/linux-2.4.37.9/fs/sysv/
DINTRO29 * Byte ordering of "short" (16 bit entities) on disk:
36 * Byte ordering of "long" (32 bit entities) on disk:
/linux-2.4.37.9/Documentation/
Dscsi.txt22 will enforce the correct ordering of loading and unloading modules in
Dsvga.txt95 After scanning, the mode ordering is a bit different: the auto-detected SVGA
170 for more info on mode ordering). However, in very strange cases it's possible
Dtty.txt64 and ordering isn't predictable - FIXME
Dusing-newer-gcc.txt26 ordering, which itself depends on the declaration order of functions, module
Ddigiboard.txt57 cards are installed the ordering within the comma separated parameter
Dpci.txt146 For compatibility with device ordering in older kernels, you can also
DConfigure.help11076 re-ordering. This is often useful to simulate networks when
/linux-2.4.37.9/Documentation/usb/
Dw9968cf.txt336 1 = use RGB component ordering.
337 0 = use BGR component ordering.
/linux-2.4.37.9/Documentation/crypto/
Ddescore-readme.txt51 33us per encryption (options: 64k tables, FIPS standard bit ordering)
53 48us per encryption (options: 2k tables, FIPS standard bit ordering)
/linux-2.4.37.9/drivers/scsi/
DChangeLog.sym53c8xx96 that implement a weak memory ordering.
481 - The PCI memory read from SCRIPTS that should ensure ordering
483 device drivers regarding ordering are working so well. ;-)
DChangeLog.ncr53c8xx32 that implement a weak memory ordering.
381 - Add some barriers to enforce memory ordering for x86 and
DREADME.aic7xxx122 way to autodetect this ordering. So, we default to the most common
DREADME.ibmmca608 - reversed ordering of the drives (using the
613 - be consistent with the BIOS ordering of the drives. In the
DREADME.ncr53c8xx1834 byte ordering.
/linux-2.4.37.9/drivers/net/wan/8253x/
Dsab8253xfs.txt1288 and adapter units are ordered in reverse order to the ordering on the
1291 Multichannel units are ordered next, i.e., first. The ordering of
/linux-2.4.37.9/Documentation/isdn/
DREADME.HiSax127 cards are installed, the ordering within the comma separated parameter
/linux-2.4.37.9/drivers/scsi/aic7xxx_old/
DREADME.aic7xxx156 way to autodetect this ordering. So, we default to the most common
/linux-2.4.37.9/drivers/net/wireless/
Dairo.c542 u16 ordering; member
/linux-2.4.37.9/fs/hfs/
DChangeLog1843 the i386 and the "inverse big-endian" bit ordering that I thought