/linux-2.4.37.9/drivers/acpi/dispatcher/ |
D | dsmthdat.c | 90 ACPI_MOVE_32_TO_32 (&walk_state->arguments[i].name, in acpi_ds_method_data_init() 92 walk_state->arguments[i].name.integer |= (i << 24); in acpi_ds_method_data_init() 93 walk_state->arguments[i].descriptor = ACPI_DESC_TYPE_NAMED; in acpi_ds_method_data_init() 94 walk_state->arguments[i].type = ACPI_TYPE_ANY; in acpi_ds_method_data_init() 95 walk_state->arguments[i].flags = ANOBJ_END_OF_PEER_LIST | ANOBJ_METHOD_ARG; in acpi_ds_method_data_init() 153 if (walk_state->arguments[index].object) { in acpi_ds_method_data_delete_all() 155 index, walk_state->arguments[index].object)); in acpi_ds_method_data_delete_all() 159 acpi_ns_detach_object (&walk_state->arguments[index]); in acpi_ds_method_data_delete_all() 272 *node = &walk_state->arguments[index]; in acpi_ds_method_data_get_node()
|
/linux-2.4.37.9/drivers/acpi/ |
D | utils.c | 242 struct acpi_object_list *arguments, in acpi_evaluate_integer() argument 254 status = acpi_evaluate_object(handle, pathname, arguments, &buffer); in acpi_evaluate_integer() 278 acpi_object_list *arguments, 290 status = acpi_evaluate_object(handle, pathname, arguments, &buffer); 327 struct acpi_object_list *arguments, in acpi_evaluate_reference() argument 344 status = acpi_evaluate_object(handle, pathname, arguments, &buffer); in acpi_evaluate_reference()
|
/linux-2.4.37.9/arch/mips/kernel/ |
D | scall_o32.S | 40 lbu t3, sys_narg_table(v0) # number of arguments 43 subu t0, t3, 5 # 5 or more arguments? 164 PTR_LA t1, 3f # copy 1 to 2 arguments 318 lbu t4, sys_narg_table(a0) # number of arguments 329 addu t1, v0, 12 # 3 32-bit arguments 352 bnez t4, 1f # zero arguments?
|
/linux-2.4.37.9/arch/i386/math-emu/ |
D | README | 75 the reduced argument is accurate to more than 64 bits for arguments up 76 to a few pi, and accurate to more than 64 bits for most arguments, 77 even for arguments approaching 2^63. This is far superior to an 241 arguments greater than pi/4 can be thought of as being related to the 274 consequence, the accuracy of these functions for large arguments has 288 It is possible with some effort to find very large arguments which 298 For arguments close to critical angles (which occur at multiples of 300 arguments, the emulator is far more accurate. 311 number of randomly selected arguments in each case is about half a 318 result (which is 64 bits)) for about one per cent of all arguments [all …]
|
/linux-2.4.37.9/arch/alpha/lib/ |
D | callback_srm.S | 20 mov $20,$21 # Shift arguments right. 47 lda $25,2($31) # two integer arguments
|
/linux-2.4.37.9/include/acpi/ |
D | acpi_bus.h | 56 struct acpi_object_list *arguments, 62 struct acpi_object_list *arguments,
|
D | acstruct.h | 91 …struct acpi_namespace_node arguments[ACPI_METHOD_NUM_ARGS]; /* Control method argument… member
|
D | acdebug.h | 323 struct argument_info *arguments);
|
/linux-2.4.37.9/Documentation/sound/ |
D | Soundblaster | 8 The Sound Blaster module takes the following arguments 21 The following arguments are taken if ISAPnP support is compiled in
|
D | ultrasound | 7 The gus module takes the following arguments
|
D | mwave | 121 ro # Other kernel arguments go here. 134 to be dynamically deactivated via kernel arguments. Whatever you chose to
|
D | README.modules | 67 needs to pass the modules the necessary parameters as arguments, either
|
/linux-2.4.37.9/Documentation/ |
D | isapnp.txt | 72 used, where x is an integer value. Both vendor and device arguments 93 appropriate arguments for each card. 119 appropriate arguments for each matched device.
|
D | stallion.txt | 66 the driver configuration as module arguments. The other method is to modify 77 The simplest configuration for modules is to use the module load arguments 104 will also need to supply command line arguments to the "insmod" command 127 Up to 4 board configuration arguments can be specified on the load line.
|
D | binfmt_misc.txt | 74 If you want to pass special arguments to your interpreter, you can
|
/linux-2.4.37.9/arch/mips64/kernel/ |
D | scall_o32.S | 55 subu t0, t3, 5 # 5 or more arguments? 163 PTR_LA t1, 3f # copy 1 to 2 arguments 280 daddu t1, v0, 12 # 3 32-bit arguments 303 bnez t1, 1f # zero arguments?
|
/linux-2.4.37.9/arch/m68k/ifpsp060/ |
D | ilsp.doc | 91 add.l &0xc,%sp # clear arguments from stack 106 add.l &0xc,%sp # clear arguments from stack 124 addq.l &0x8,%sp # clear arguments from stack
|
/linux-2.4.37.9/Documentation/fb/ |
D | clgenfb.txt | 35 At the moment, there are two kernel command line arguments supported:
|
/linux-2.4.37.9/fs/ |
D | ChangeLog | 92 * namei.c (VFS_rename): New function. It gets the same arguments as 127 Added new function: vfs_unlink, with the same arguments as
|
/linux-2.4.37.9/arch/m68k/fpsp040/ |
D | slogn.S | 21 | situation. For those arguments, slognp1 takes approximately 22 | 210 cycles. For the less common arguments, the program will
|
/linux-2.4.37.9/drivers/acpi/utilities/ |
D | uteval.c | 81 string_desc = walk_state->arguments[0].object; in acpi_ut_osi_implementation()
|
/linux-2.4.37.9/drivers/scsi/ |
D | README.in2000 | 29 handling of command-line arguments when loaded as a module. 128 The default arguments (you get these when you don't give an 'in2000'
|
D | README.53c700 | 89 template and the new parameters as arguments. You should also call
|
/linux-2.4.37.9/Documentation/networking/ |
D | de4x5.txt | 154 Command line arguments are now allowed, similar to passing arguments
|
/linux-2.4.37.9/arch/ppc64/ |
D | config.in | 102 bool 'Default bootloader kernel arguments' CONFIG_CMDLINE_BOOL
|