Searched refs:IDs (Results 1 – 25 of 59) sorted by relevance
123
| /linux-2.6.39/Documentation/usb/ |
| D | bulk-streams.txt | 33 allocate memory so the driver can use up to num_streams stream IDs. They must
35 IDs. This is to ensure that a UASP driver will be able to use the same stream
41 declares how many stream IDs it can support, and each bulk endpoint on a
42 SuperSpeed device will say how many stream IDs it can handle. Therefore,
43 drivers should be able to deal with being allocated less stream IDs than they
55 Picking new Stream IDs to use
64 driver supports secondary stream IDs.
77 All stream IDs will be deallocated when the driver releases the interface, to
|
| D | hiddev.txt | 155 use the relative IDs above to enumerate the valid IDs. The ioctl
|
| D | persist.txt | 81 same descriptors as before, including the Vendor and Product IDs, then
141 manufacturer, same IDs, and so on) there's an excellent chance the
|
| /linux-2.6.39/Documentation/namespaces/ |
| D | compatibility-list.txt | 18 1. Both the IPC and the PID namespaces provide IDs to address
28 2. Intentionally, two equal user IDs in different user namespaces
|
| /linux-2.6.39/arch/powerpc/include/asm/ |
| D | hydra.h | 32 u_int IDs; member
|
| /linux-2.6.39/Documentation/driver-model/ |
| D | binding.txt | 27 ID of the device must match one of the device IDs that the driver
28 supports. The format and semantics for comparing IDs is bus-specific.
31 a device against the IDs of a driver. The bus returns 1 if a match was
|
| D | bus.txt | 62 of device IDs of devices they support that reside in a bus-specific
67 comparing the device IDs the driver supports with the device ID of a
|
| D | porting.txt | 333 A driver typically contains a list of device IDs that it supports. The
334 bus driver compares these IDs to the IDs of devices registered with it.
335 The format of the device IDs, and the semantics for comparing them are
|
| D | driver.txt | 62 typically defines an array of device IDs that it supports. The format
63 of these structures and the semantics for comparing device IDs are
|
| /linux-2.6.39/Documentation/ |
| D | pnp.txt | 24 id - displays a list of support EISA IDs
141 1.) the protocol must use EISA IDs
161 - adds an EISA ID to the list of supported IDs for the specified device
190 Supported PnP card IDs can optionally be defined.
|
| D | svga.txt | 68 next section for a description of mode IDs).
99 3. Mode IDs
101 Because of the complexity of all the video stuff, the video mode IDs
241 flag, 0xffff and 0xfffe became aliases instead of real IDs.
|
| D | media-framework.txt | 135 IDs manually must ensure that all IDs are unique. IDs are not guaranteed to be
142 Unregistering an entity will not change the IDs of the other entities, and the
|
| D | stable_kernel_rules.txt | 15 - New device IDs and quirks are also accepted.
|
| /linux-2.6.39/Documentation/pcmcia/ |
| D | driver.txt | 8 New PCMCIA IDs may be added to a device driver pcmcia_device_id table at
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | udf.txt | 45 IDs on the disk, not just -1. The forget option causes all IDs to be written
|
| /linux-2.6.39/Documentation/networking/ |
| D | can.txt | 98 frames on different or the same CAN IDs. Several sockets listening on
104 CAN-IDs, frames, etc.
136 IDs, supporting several open file descriptors and (de)multiplexing
154 (can_id) is used for arbitration on the CAN-bus. Therefore the CAN-IDs
156 network the CAN-IDs are mapped to be sent by a specific ECU.
163 CAN-IDs from the same CAN network interface. The Socket CAN core
167 requests the (range of) CAN-IDs from the Socket CAN core that are
169 CAN-IDs can be done for specific CAN interfaces or for all(!) known
497 modules to subscribe needed CAN IDs (see chapter 3.1).
594 controllers support the filtering of CAN IDs or ranges of CAN IDs.
|
| /linux-2.6.39/include/linux/ |
| D | page_cgroup.h | 132 #error Not enough space left in pc->flags to store page_cgroup array IDs
|
| /linux-2.6.39/Documentation/w1/ |
| D | w1.netlink | 105 len is equal to number of IDs multiplied by 8]
108 w1_netlink_cmd->len = N * 8; where N is number of IDs in this message.
|
| /linux-2.6.39/Documentation/isdn/ |
| D | README.gigaset | 245 Call-IDs are numbers used to tag commands to, and responses from, the
248 mode"). Without Call-IDs (in Unimodem mode), only a very limited set of
253 connection to the base while Call-IDs are activated. As the Gigaset
|
| /linux-2.6.39/Documentation/RCU/ |
| D | arrayRCU.txt | 40 semaphore, message-queue, and shared-memory IDs to the data structure
|
| /linux-2.6.39/drivers/media/dvb/dvb-usb/ |
| D | Kconfig | 49 bool "Support faulty USB IDs"
52 Support for faulty USB IDs due to an invalid EEPROM on some Artec devices.
|
| /linux-2.6.39/Documentation/sound/alsa/ |
| D | hda_codec.txt | 38 needs to check the PCI subsystem IDs, so on. For non-PCI system, it
311 as a module parameter, and PCI subsystem IDs. If the matching entry
|
| /linux-2.6.39/Documentation/frv/ |
| D | features.txt | 270 (*) MMU Context IDs and Pinning
279 numbers, the kernel will pass context IDs from one task to another if
|
| /linux-2.6.39/Documentation/hwmon/ |
| D | smsc47b397 | 22 [1] And SMSC SCH5307-NS and SCH5317, which have different device IDs but are
|
| /linux-2.6.39/Documentation/infiniband/ |
| D | user_mad.txt | 94 Transaction IDs
|
123