| /linux-4.4.14/drivers/zorro/ |
| D | Kconfig | 5 bool "Zorro device name database"
8 By default, the kernel contains a database of all known Zorro device
10 user. This database increases the size of the kernel image by about
|
| /linux-4.4.14/scripts/ |
| D | kernel-doc-xml-ref | 34 my @database;
65 @database = @lines;
92 if ( grep( /^$_[0]$/, @database)) {
|
| D | spelling.txt | 331 detabase||database
|
| /linux-4.4.14/drivers/eisa/ |
| D | Kconfig | 41 bool "EISA device name database"
45 By default, the kernel contains a database of all known EISA
47 to the user. This database increases size of the kernel
|
| /linux-4.4.14/Documentation/fb/ |
| D | modedb.txt | 11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
85 to the global mode database whenever a new mode is released by display
123 with db/dbsize your non-standard video mode database, or NULL to use the
124 standard video mode database.
|
| D | 00-INDEX | 43 - info on the video mode database.
|
| D | ep93xx-fb.txt | 7 can use the standard Linux video mode database. In your board file:
|
| D | intel810.txt | 26 Formula, or a framebuffer specific database to set the video mode
|
| D | framebuffer.txt | 121 Fbset uses a video mode database stored in a configuration file, so you can
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-wusb_cbaf | 28 6. The CM looks it up its database.
35 matching CDID in its database), the device is
|
| /linux-4.4.14/net/dns_resolver/ |
| D | Kconfig | 15 cell's volume location database servers.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | afs.txt | 11 - The cell database.
162 The filesystem maintains an internal database of all the cells it knows and the
164 the system belongs is added to the database when modprobe is performed by the
173 No other cell database operations are available at this time.
|
| D | btrfs.txt | 54 Not well suited for large database workloads.
|
| D | ntfs.txt | 284 This would dump the LDM database found on /dev/hda which describes all of your
|
| /linux-4.4.14/fs/befs/ |
| D | Kconfig | 8 on files and directories, and database-like indices on selected
|
| /linux-4.4.14/Documentation/ |
| D | ldm.txt | 13 1MiB journalled database at the end of the physical disk. The size of
40 N.B. The missing 1MiB at the end of the disk is where the LDM database is
|
| D | module-signing.txt | 190 add those in also (e.g. from the UEFI key database).
|
| D | IPMI.txt | 13 standardized database for field-replaceable units (FRUs) and a watchdog
|
| /linux-4.4.14/net/xfrm/ |
| D | Kconfig | 34 bool "Transformation migrate database"
|
| /linux-4.4.14/net/wireless/ |
| D | Kconfig | 156 bool "use statically compiled regulatory rules database" if EXPERT
162 and includes code to query that database. This is an alternative
|
| /linux-4.4.14/Documentation/networking/ |
| D | regulatory.txt | 192 Statically compiled regulatory database
200 the wireless database information contained in net/wireless/db.txt is
|
| D | netlink_mmap.txt | 12 dump operations of f.i. the routing database.
|
| /linux-4.4.14/arch/sparc/kernel/ |
| D | pci_schizo.c | 1134 unsigned long i, tagbase, database; in schizo_pbm_iommu_init() local
1186 tagbase = SCHIZO_IOMMU_TAG, database = SCHIZO_IOMMU_DATA; in schizo_pbm_iommu_init()
1190 upa_writeq(0, pbm->pbm_regs + database + (i * 8UL)); in schizo_pbm_iommu_init()
|
| /linux-4.4.14/fs/reiserfs/ |
| D | Kconfig | 17 database and keyword search systems than block allocation based file
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 80 email to the maintainer to add it to the database. When reporting a new
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 565 specified address in the specified VLAN Id in the forwarding database
568 Note: VLAN ID 0 corresponds to the port private database, which, in the context
574 this port forwarding database
|
| /linux-4.4.14/arch/arm/tools/ |
| D | mach-types | 10 # To add an entry into this database, please see Documentation/arm/README,
16 # are merged into mainline or have been edited in the machine database
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | intel-pt.txt | 107 approach is available to export the data to a postgresql database. Refer to
109 call-graph-from-postgresql.py for an example of using the database.
|
| /linux-4.4.14/Documentation/usb/ |
| D | proc_usb_info.txt | 194 | description that often comes from the kernel's PCI ID database.
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig-language.txt | 4 The configuration database is a collection of configuration options
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 574 The kernel "devtype" is registered in the udev database
|
| /linux-4.4.14/Documentation/scsi/ |
| D | st.txt | 60 scans its database, and sets up the modes using the ioctls. Another
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 91 and a database), or
|
| /linux-4.4.14/Documentation/block/ |
| D | biodoc.txt | 242 This comes from some of the high-performance database/middleware
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 206 (*) An optional filesystem is available through which the key database can be
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.OSS | 1385 willing to maintain a database of supported cards (just like in XF86)?).
|
| /linux-4.4.14/ |
| D | CREDITS | 2886 D: Port of the database Postgres
|