Searched refs:variables (Results 1 – 25 of 53) sorted by relevance
123
/linux-2.4.37.9/Documentation/kbuild/ |
D | makefiles.txt | 16 5.1 Architecture-specific variables 17 5.2 Vmlinux build variables 25 7 Rules.make variables 32 7.7 Miscellaneous variables 33 8 New-style variables 34 8.1 New variables 126 The top Makefile exports the following variables: 130 These variables define the current kernel version. A few arch 189 variables. The top Makefile defines $(CORE_FILES), $(NETWORKS), 193 Note: there are more variables here than necessary. $(NETWORKS), [all …]
|
/linux-2.4.37.9/drivers/char/ |
D | ser_a2232fw.ax | 303 VARBASE 0 ; start variables at address $0000 304 PORTVAR 0 ; define variables for port 0 305 PORTVAR 1 ; define variables for port 1 306 PORTVAR 2 ; define variables for port 2 307 PORTVAR 3 ; define variables for port 3 308 PORTVAR 4 ; define variables for port 4 309 PORTVAR 5 ; define variables for port 5 310 PORTVAR 6 ; define variables for port 6 407 clr_loop sta 0,x ; clear zero page variables ;
|
/linux-2.4.37.9/arch/sh64/kernel/ |
D | head.S | 119 variables: label 177 _loada variables, GVDT 301 addi GVDT, fpu_in_use - variables, r31 /* Temporary */
|
/linux-2.4.37.9/Documentation/networking/ |
D | alias.txt | 50 ; local variables:
|
D | lapb-module.txt | 133 variables, the lapb_parms_struct is described above. The valid return values 143 variables, the lapb_parms_struct is described above. The values of t1timer,
|
D | 00-INDEX | 64 - /proc/sys/net/ipv4/* variables
|
/linux-2.4.37.9/net/802/ |
D | TODO | 3 1. Serialization of access to variables in the llc structure
|
/linux-2.4.37.9/scripts/ |
D | README.Menuconfig | 142 RECOMMEND that you make sure you do NOT have the shell variables 144 export those variables via /etc/profile. Some ncurses programs can 145 become confused when those variables (LINES & COLUMNS) don't reflect
|
/linux-2.4.37.9/arch/i386/math-emu/ |
D | README | 87 variables. The code which accesses user memory is confined to five 94 As from version 1.12 of the emulator, no static variables are used 265 later) for 'float' variables (24 bit precision numbers) when precision 266 control is set to 24, 53 or 64 bits, and for 'double' variables (53 269 variables when precision control is set to 64 bits).
|
/linux-2.4.37.9/Documentation/crypto/ |
D | descore-readme.txt | 179 for varying numbers of register variables. 219 (it appears that gcc can use ebx, esi and edi to hold register variables). 233 the en/decryption routines each use 6 necessary register variables, 235 if you don't have 4 register variables get a new machine. 247 do the arithmetic, so i assign these to explicit `m' register variables
|
/linux-2.4.37.9/Documentation/vm/ |
D | numa | 34 more variables like low_on_memory, nr_free_pages etc into the pg_data_t.
|
/linux-2.4.37.9/Documentation/cdrom/ |
D | cdu31a | 151 variables. 157 You can set the following variables in the driver:
|
/linux-2.4.37.9/Documentation/ |
D | kernel-docs.txt | 86 focus on lower details than its predecessor (files, variables...). 183 variables, network devices flags, transmit, receive, 267 Description: Kernel functions/structures/variables which changed 275 Description: Kernel functions/structures/variables which changed 360 the sources, describing directories, files, variables, data 669 and variables) and LSD can generate patches for you on the fly 686 Lots of cross references to variables and functions. You can see
|
D | spinlocks.txt | 93 to mostly read from the shared variables, the reader-writer locks 96 to change the variables it has to get an exclusive write lock. The
|
D | CodingStyle | 134 global variables are a must. To call a global function "foo" is a 137 GLOBAL variables (to be used only if you _really_ need them) need to 178 Another measure of the function is the number of local variables. They
|
/linux-2.4.37.9/Documentation/i2c/ |
D | functionality | 95 /* Define needed variables */
|
D | writing-clients | 16 tutorial, and `FOO_' for preprocessor variables. 245 /* Magic definition of all other variables and things */ 248 Note that you *have* to call the two defined variables `normal_i2c' and 303 These are automatically translated to insmod variables of the form 306 So we have a generic insmod variable `force', and chip-specific variables
|
/linux-2.4.37.9/arch/m68k/fpsp040/ |
D | fpsp.h | 15 | frame and any local variables needed by the FPSP package. 80 .set LOCAL_SIZE,192 | bytes needed for local variables
|
/linux-2.4.37.9/Documentation/parisc/ |
D | registers | 121 used to make references to global variables easier. r30 is
|
/linux-2.4.37.9/drivers/scsi/sym53c8xx_2/ |
D | ChangeLog.txt | 59 defined at compile time, as at least NetBSD uses variables
|
/linux-2.4.37.9/Documentation/usb/ |
D | hotplug.txt | 63 is the string "usb", and it passes these environment variables:
|
/linux-2.4.37.9/Documentation/mips/ |
D | time.README | 23 Two configs variables are introduced, CONFIG_OLD_TIME_C and CONFIG_NEW_TIME_C.
|
/linux-2.4.37.9/fs/cramfs/ |
D | README | 141 variables instead of #define'd constants. The gain is that people
|
/linux-2.4.37.9/drivers/scsi/ |
D | 53c700.scr | 23 ; operation. The particular variables pertaining to the commands are:
|
/linux-2.4.37.9/arch/x86_64/boot/ |
D | bootsect.S | 221 # These variables are addressed via %si register as it gives shorter code.
|
123