Searched refs:structure (Results 1 – 25 of 118) sorted by relevance
12345
| /linux-2.4.37.9/arch/arm/nwfpe/ |
| D | ChangeLog | 12 - remove userRegisters pointer from this structure.
18 * The FPA11 structure is not a kernel-specific data structure.
21 FPA11 structure (size or position of elements contained
24 * Since 128-bit float requires the FPA11 structure to change
27 overflow the available space in the task structure.
36 * fpa11.c - Changes due to FPA11, FPREG structure alterations.
37 * fpa11_cpdo.c - Changes due to FPA11, FPREG structure alterations.
38 * fpa11_cpdt.c - Changes due to FPA11, FPREG structure alterations.
39 * fpa11_cprt.c - Changes due to FPA11, FPREG structure alterations.
40 * single_cpdo.c - Changes due to FPA11, FPREG structure alterations.
[all …]
|
| /linux-2.4.37.9/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 60 * 05-24-00 00.10.02 Added _MSG_IOC_INIT_REPLY structure.
62 * 06-12-00 01.00.02 Added _MSG_PORT_ENABLE_REPLY structure.
63 * Added _MSG_EVENT_ACK_REPLY structure.
64 * Added _MSG_FW_DOWNLOAD_REPLY structure.
65 * Added _MSG_TOOLBOX_REPLY structure.
66 * 06-30-00 01.00.03 Added MaxLanBuckets to _PORT_FACT_REPLY structure.
67 * 07-27-00 01.00.04 Added _EVENT_DATA structure definitions for _SCSI,
70 * _MSG_EVENT_ACK_REPLY structure to match specification.
82 * Added structure offset comments.
83 * 04-09-01 01.01.07 Added structure EVENT_DATA_EVENT_CHANGE.
[all …]
|
| /linux-2.4.37.9/Documentation/usb/ |
| D | hiddev.txt | 79 the value that it was changed to. Note that the structure is defined
98 hiddev_devinfo structure.
101 Gets a hiddev_devinfo structure which describes the device.
128 Fills in a hiddev_report_info structure for the user. The report is
137 filled into the returned hiddev_report_info structure.
141 hiddev_field_info structure. The user must fill in report_id and
142 report_type in this structure, as above. The field_index should also
147 Returns the usage_code in a hiddev_usage_ref structure, given that
149 field have already been filled into the structure.
152 Returns the value of a usage in a hiddev_usage_ref structure. The
|
| D | uhci.txt | 18 Correct, but its internal structure got more and more mixed up by the (still
87 2. Internal structure and mechanisms
93 2.1. Descriptor structure (QHs and TDs)
131 2.2. URB structure and linking to QH/TDs
|
| /linux-2.4.37.9/arch/ppc/boot/simple/ |
| D | head.S | 42 .long 0x62726f6d # structure ID - "brom"
44 .long 1 # structure version
|
| /linux-2.4.37.9/Documentation/sparc/ |
| D | sbus_drivers.txt | 17 structure called "struct sbus_dev". Likewise, each SBUS bus
20 fashion off of the bus structure.
22 The SBUS device structure contains enough information
25 used members of this structure, and their typical usage,
67 Each SBUS device structure contains an array of descriptors
81 Perhaps part of your driver software state structure looks like:
107 a start address and flags from the resource structure.
110 structure if driver gets physical address from some private place.
163 values as a memory mapped pointer to some structure
|
| /linux-2.4.37.9/Documentation/ |
| D | magic-number.txt | 2 add a magic number to a structure, you should also add it to this
7 numbers. This allows you to check at run time whether (a) a structure
8 has been clobbered, or (b) you've passed the wrong structure to a
15 the structure, like so:
|
| D | tty.txt | 15 discipline number and the ldisc structure. At the point of registration the
21 copy of the structure. You must not re-register over the top of the line
31 tty_ldisc structure in the ldisc table counts the number of lines using this
32 discipline. The reference count of the tty_ldisc structure within a tty
61 set_termios() - Called on termios structure changes. The caller
|
| D | scsi-generic.txt | 22 It is based in the sg_header interface structure.
24 an extended version of the sg_header interface structure.
26 It adds the sg_io_hdr interface structure.
|
| D | isapnp.txt | 150 structure. This structure contains all resources set to auto configuration
154 Once the device structure contains all requested resource values, the function
|
| D | dnotify.txt | 29 kernel know which signal to deliver, a siginfo structure will be passed to
30 the signal handler and the si_fd member of that structure will contain the
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | lapb-module.txt | 21 Probably the most important structure is the skbuff structure for holding
25 The two LAPB specific structures are the LAPB initialisation structure and
26 the LAPB parameter structure. These will be defined in a standard header
33 This structure is used only once, in the call to lapb_register (see below).
46 Each member of this structure corresponds to a function in the device driver
55 This structure is used with the lapb_getparms and lapb_setparms functions
200 module with lapb_register (see above) in the structure lapb_register_struct
|
| D | packet_mmap.txt | 109 this parameter must to have the following structure:
119 This structure is defined in /usr/include/linux/if_packet.h and establishes a
142 we will get the following buffer structure:
201 To understand the constraints of PACKET_MMAP, we have to see the structure
204 Currently, this structure is a dynamically allocated vector with kmalloc
293 Frame structure:
|
| /linux-2.4.37.9/arch/x86_64/boot/compressed/ |
| D | head.S | 71 subl $16,%esp # place for structure on the stack
74 pushl %eax # address of structure as first arg
|
| /linux-2.4.37.9/arch/i386/boot/compressed/ |
| D | head.S | 67 subl $16,%esp # place for structure on the stack
70 pushl %eax # address of structure as first arg
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | vfs.txt | 79 structure (this is the kernel-side implementation of file
80 descriptors). The freshly allocated file structure is initialised with
86 The file structure is placed into the file descriptor table for the
91 file structure, and then calling the required file structure method
109 need to do is call register_filesystem(). You pass a structure
151 struct super_block *sb: the superblock structure. This is partially
165 The most interesting member of the superblock structure that the
278 dentry. The "i_count" field in the inode structure should be
366 field in the inode structure. It then calls the open method
367 for the newly allocated file structure. You might think that
[all …]
|
| /linux-2.4.37.9/net/802/ |
| D | TODO | 3 1. Serialization of access to variables in the llc structure
12 the llc structure addressed by an incoming frame.
|
| /linux-2.4.37.9/drivers/char/ |
| D | ChangeLog | 151 (startup): Move the insertion of serial structure into the
176 async_struct structure. Only turn on DTR and RTS if the
204 structure. Put in more paranoid test for the 16750.
456 TTY_CLOSING flag so that we know that this tty structure
460 TTY_CLOSING is set on a tty structure; if so, something
482 structure in the async_struct structure, tqueue_hangup.
567 open file descriptors which point at the structure. If
574 session leader's task structure. When the session leader
628 * serial.c (block_til_ready): Use the correct termios structure to
631 Otherwise, use the currently active termios structure.
[all …]
|
| /linux-2.4.37.9/include/asm-sh/ |
| D | stat.h | 52 #error Must know endian to build stat64 structure!
|
| /linux-2.4.37.9/drivers/net/wan/8253x/ |
| D | sab8253xds.txt | 17 3. creating a file structure of the driver that aids understanding,
1042 The Makefile is a standard Linux kernel Makefile whose structure is
1335 network peer that uses the same serial Ethernet frame structure, it
2694 1. SAB_BOARD structure ^� driver specific
2696 2. SAB_CHIP structure ^� driver specific
2698 3. SAB_PORT structure ^� driver specific
2700 4. AURA_CIM structure ^� driver specific (actually specific to the
2710 SAB_PORT structure are used to track all the sk_buffs that are currently
2713 8. struct tty_struct ^� one per port, standard structure by which
2716 private data structure associated with each 8253x TTY, which on a given
[all …]
|
| /linux-2.4.37.9/Documentation/i2c/ |
| D | writing-clients | 19 The driver structure
22 Usually, you will implement a single driver structure, and instantiate
23 all clients from it. Remember, a driver structure contains general access
24 routines, a client structure specific information like the actual I2C
97 The client structure has a special `data' field that can point to any
98 structure at all. You can use this to keep client-specific data. You
102 An example structure is below.
126 Let's say we have a valid client structure. At some time, we will need
356 Remember, structure `addr_data' is defined by the macros explained above,
444 client structure, even though we cannot fill it completely yet.
[all …]
|
| D | functionality | 57 function callback `functionality', that gets an i2c_adapter structure
82 in the algorithm structure directly:
|
| /linux-2.4.37.9/Documentation/arm/ |
| D | Setup | 5 structure, otherwise known as 'struct param_struct' which is used
8 This structure is used to pass initialisation parameters from the
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | ChangeLog.ips | 6 6.11.07 - Make Logical Drive Info structure safe for DMA
38 4.80.20 - Set max_sectors in Scsi_Host structure ( if >= 2.4.7 kernel )
|
| /linux-2.4.37.9/arch/ia64/sn/fakeprom/ |
| D | README | 42 - builds the "ia64_bootparam" structure that is
43 passed to the kernel from SAL. This structure
|
12345