| /linux-2.4.37.9/drivers/acpi/ |
| D | asus_acpi.c | 116 struct model_data *methods; //methods available on the laptop member
420 hotk->methods->name); in proc_read_info()
535 return sprintf(page, "%d\n", read_led(hotk, hotk->methods->mled_status, MLED_ON)); in proc_read_mled()
544 return write_led(buffer, count, hotk, hotk->methods->mt_mled, MLED_ON, 1); in proc_write_mled()
555 return sprintf(page, "%d\n", read_led(hotk, hotk->methods->wled_status, WLED_ON)); in proc_read_wled()
563 return write_led(buffer, count, hotk, hotk->methods->mt_wled, WLED_ON, 0); in proc_write_wled()
574 return sprintf(page, "%d\n", read_led(hotk, hotk->methods->tled_status, TLED_ON)); in proc_read_tled()
582 return write_led(buffer, count, hotk, hotk->methods->mt_tled, TLED_ON, 0); in proc_write_tled()
593 if (!read_acpi_int(NULL, hotk->methods->lcd_status, &lcd)) in get_lcd_state()
617 status = acpi_evaluate_object(NULL, hotk->methods->lcd_status, &input, &output); in get_lcd_state()
[all …]
|
| /linux-2.4.37.9/drivers/char/ftape/lowlevel/ |
| D | ftape-ctl.c | 105 static const wakeup_method methods[] = WAKEUP_METHODS; variable
273 for (method=no_wake_up; method < NR_ITEMS(methods); ++method) { in ftape_activate_drive()
293 methods[drive_type->wake_up].name); in ftape_activate_drive()
299 if (method >= NR_ITEMS(methods)) { in ftape_activate_drive()
411 methods[ft_drive_type.wake_up].name); in ftape_log_vendor_id()
435 methods[ft_drive_type.wake_up].name, in ftape_log_vendor_id()
436 methods[vendors[vendor_index].wake_up].name); in ftape_log_vendor_id()
|
| /linux-2.4.37.9/fs/intermezzo/ |
| D | Makefile | 10 kml_unpack.o methods.o presto.o psdev.o replicator.o super.o \
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | Locking | 1 The text below describes the locking rules for VFS-related methods.
80 but watch for other methods directly calling this one...
172 Note: currently almost all instances of address_space methods are
222 bad - as soon as we'll get disk_struct they will change (and methods will
263 ->open() locking is in-transit: big lock partially moved into the methods.
|
| D | vfs.txt | 190 All methods are called without any locks being held, unless otherwise
191 noted. This means that most methods can block safely. All methods are
229 describes the methods that can be performed on individual inodes.
263 Again, all methods are called without any locks being held, unless
284 If you wish to overload the dentry methods then you should
344 Again, all methods are called without any locks being held, unless
400 here. These methods may be set to NULL, as they are either optional or
|
| D | ext2.txt | 263 scheme but less reliable. Both methods are equally resolvable by their
|
| /linux-2.4.37.9/Documentation/arm/nwfpe/ |
| D | TODO | 24 method would be to use accurate table methods for these routines. I have
27 These methods are used in GLIBC for some of the transcendental functions.
|
| /linux-2.4.37.9/Documentation/isdn/ |
| D | README.concap | 125 protocol may not call any *dops methods after this. */
136 dummy methods here */
160 /* Control methods must be set to NULL by devices which do not
182 be accessed via *pops methods only*/
|
| D | README.sc | 73 versus between 16K and 64K. New methods for using the shared RAM
|
| /linux-2.4.37.9/Documentation/ |
| D | kmod.txt | 32 There are many user-land methods that will work (I prefer using /proc,
|
| D | cachetlb.txt | 28 invoke one of the following flush methods _after_ the page table
227 Next, you have two methods to solve the D-cache aliasing issue for all
|
| D | kernel-parameters.txt | 90 acpi_serialize [HW,ACPI] force serialization of AML methods
489 hardware access methods are allowed. Use this
|
| D | paride.txt | 11 host computer. While some devices (notably scanners) use ad-hoc methods
54 paride module which provides a registry and some common methods for
|
| D | stallion.txt | 64 There are two methods of configuring ISA, EISA and MCA boards into the drivers.
|
| /linux-2.4.37.9/Documentation/crypto/ |
| D | api-intro.txt | 90 methods may only be called from softirq and user contexts.
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | PLIP.txt | 112 PLIP uses several different data transfer methods. The first (and the
|
| D | 6pack.txt | 25 DAMA channel access methods.
|
| D | NAPI_HOWTO.txt | 120 ring. This happens only in close() and suspend() (when these methods
136 new methods introduce by NAPI
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | README.st | 12 one of the following three methods:
260 SCSI mode page 15. Note that some drives other methods for
|
| D | README.ibmmca | 580 work, because the methods have changed between 2.0.x and 2.1.x.
|
| /linux-2.4.37.9/Documentation/filesystems/devfs/ |
| D | ChangeLog | 340 - No longer set unnecessary methods
901 methods
1494 - Remove unnecessary tests in symlink methods
|
| D | README | 499 VFS (such as create() or mknod() inode methods). If driver information
|
| /linux-2.4.37.9/Documentation/s390/ |
| D | cds.txt | 30 functional layer was introduced that provides generic I/O access methods to
146 This methods implies that Linux/390 doesn't require to probe for free (not
163 different I/O methods, synchronous and asynchronous, and allows to specify
|
| /linux-2.4.37.9/drivers/char/ |
| D | README.epca | 41 or removed. There are two supported methods of doing this. The
|
| /linux-2.4.37.9/fs/hfs/ |
| D | ChangeLog | 2489 Supports 5 filename conversion methods.
|