Searched refs:compatibility (Results 1 – 25 of 80) sorted by relevance
1234
| /linux-2.4.37.9/Documentation/video4linux/bttv/ |
| D | README.quirks | 2 Below is what the bt878 data book says about the PCI bug compatibility
41 compatibility:
49 Thus, both the arbiter and the initiator contain 430FX compatibility
53 When EN_TBFX is enabled, the arbiter ensures that the two compatibility
74 compliant. To ensure compatibility when using PCs with these PCI
|
| D | Insmod-options | 14 triton1=0/1 for Triton1 (+others) compatibility
15 vsfx=0/1 yet another chipset bug compatibility bit
|
| /linux-2.4.37.9/Documentation/filesystems/devfs/ |
| D | ChangeLog | 20 other to set up compatibility symlinks)
140 - fix problem with SCSI disc compatibility names (sd{a,b,c,d,e,f})
812 - Fixed bugs: compatibility entries were not unregistered for:
822 - Fixed bugs: compatibility entries were not unregistered for:
1110 - Removed compatibility entries for sound devices
1112 - Removed compatibility entries for printer devices
1114 - Removed compatibility entries for video4linux devices
1116 - Removed compatibility entries for parallel port devices
1118 - Removed compatibility entries for frame buffer devices
1128 - Removed compatibility entries for SoundBlaster CD-ROMs
[all …]
|
| D | README | 104 enable devfs, the defaults are such that full compatibility is
310 compatibility issues which you would have with increasing major and
312 for details on maintaining compatibility with userspace.
585 compatibility symlinks for the old naming scheme. Don't change this
867 it to maintain compatibility entries. It is almost certain that you
868 will require this. Note that the kernel creates a compatibility entry
880 easier to install devfsd so that compatibility entries are created.
883 compatibility entries that devfsd creates.
906 If you don't run devfsd, or don't enable compatibility entry
910 be able to boot non-devfs kernels, you will need compatibility
[all …]
|
| /linux-2.4.37.9/arch/m68k/fpsp040/ |
| D | x_bsun.S | 6 | Copy the PC to FPIAR to maintain 881/882 compatibility
|
| D | x_ovfl.S | 16 | destination is not affected. For 68881 compatibility, the
|
| /linux-2.4.37.9/Documentation/ |
| D | highuid.txt | 20 - Decide whether or not to keep backwards compatibility with the system
27 compatibility syscalls, if the OS being emulated used 16-bit UIDs, or
|
| D | pci.txt | 146 For compatibility with device ordering in older kernels, you can also
236 There are several functions kept only for compatibility with old drivers
|
| /linux-2.4.37.9/drivers/message/fusion/ |
| D | Config.in | 30 # for backward compatibility with pre-linux-2.2.15 kernels.
|
| /linux-2.4.37.9/include/asm-alpha/ |
| D | hwrpb.h | 112 unsigned long compatibility; member
|
| /linux-2.4.37.9/Documentation/fb/ |
| D | clgenfb.txt | 84 * Add compatibility support. Now requires a 2.1.x, 2.2.x or 2.3.x kernel.
|
| D | matroxfb.txt | 37 has [as addon] compatibility code):
72 (0x100 = 256). You can also use value + 512 to achieve compatibility
97 Driver contains SVGALib compatibility code. It is turned on by choosing textual
325 Millennium I/II and SVGALib compatibility.
|
| /linux-2.4.37.9/Documentation/usb/ |
| D | uhci.txt | 43 + Easy migration to the new API, simplified by a compatibility API
52 1.3. Is there some compatibility to the old API?
56 these wrappers. For ISO there's no compatibility, because the old ISO-API
|
| D | error-codes.txt | 8 The USB_ST_* codes are deprecated and are only listed for compatibility;
|
| /linux-2.4.37.9/Documentation/cdrom/ |
| D | isp16 | 31 sjcd (in Sanyo/Panasonic compatibility mode) cdrom drivers
32 (probably with the optcd (in Sony compatibility mode) as well).
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | ext2.txt | 204 The compatibility feature mechanism used in ext2 is sophisticated.
206 unnecessarily sacrificing compatibility with older versions of the
207 filesystem code. The feature compatibility mechanism is not supported by
288 format and using a compatibility flag to signal the format change (at
289 the expense of some compatibility).
|
| /linux-2.4.37.9/Documentation/ia64/ |
| D | IRQ-redir.txt | 19 compatibility reasons with i386.
|
| /linux-2.4.37.9/Documentation/sound/ |
| D | README.awe | 144 Enables GUS compatibility mode if defined, reading GUS patches and
198 - Complete DOS/Win compatibility
|
| /linux-2.4.37.9/net/ipv4/netfilter/ |
| D | Config.in | 121 # Backwards compatibility modules: only if you don't build in the others.
|
| /linux-2.4.37.9/drivers/message/i2o/ |
| D | README | 101 compatibility problems
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | soundmodem.txt | 30 SoundBlaster or WSS compatibility mode. The driver does _NOT_ do this;
|
| /linux-2.4.37.9/Documentation/input/ |
| D | joystick-api.txt | 265 5. Backward compatibility
269 The driver offers backward compatibility, though. Here's a quick summary:
|
| /linux-2.4.37.9/Documentation/isdn/ |
| D | README.audio | 36 for compatibility only.
|
| /linux-2.4.37.9/drivers/isdn/ |
| D | Config.in | 43 bool ' Disable sending low layer compatibility' CONFIG_HISAX_NO_LLC
|
| /linux-2.4.37.9/Documentation/x86_64/ |
| D | boot-options.txt | 19 nomce (for compatibility with i386): same as mce=off
|
1234