Searched refs:transfers (Results 1 – 25 of 55) sorted by relevance
123
| /linux-2.4.37.9/Documentation/usb/ |
| D | ehci.txt | 53 and interrupt transfers, including requests to USB 1.1 devices through
61 transfers can't share much code with the code for high speed ISO transfers,
67 Transfers of all types can be queued. This means that control transfers
69 ones from another driver, and that interrupt transfers can use periods
81 transactions (interrupt and isochronous transfers). These place some
116 and bulk transfers. Shows each active qh and the qtds
120 and isochronous transfers. Doesn't show qtds.
129 can't, such as "high bandwidth" periodic (interrupt or ISO) transfers.
131 periodic transfers) use different encodings when operating at high speed.
148 Bulk transfers are most often used where throughput is an issue. It's
[all …]
|
| D | uhci.txt | 19 ongoing) efforts to get isochronous transfers (ISO) to work.
20 Since there is an increasing need for reliable ISO-transfers (especially
44 + Simple usage of ISO transfers
46 + ISO transfers allow variable length for each frame and striping
50 - Rewriting for ISO transfers needed
54 Yes, but only for control, bulk and interrupt transfers. We've implemented
63 Regarding to Thomas, ISO transfers now run stable with USB audio.
64 INT transfers (e.g. mouse driver) work fine, too.
78 should need URBification, if they use isochronous or interrupt transfers.
80 is fair queueing for BULK transfers. Since this would need (in principle)
[all …]
|
| D | URB.txt | 17 - Ongoing transfers for one URB (e.g. ISO) can simply be canceled with
21 has been successfully completed or canceled (INT transfers behave a bit
26 automatically submitted. This is especially useful for ISO transfers:
115 re-submission for INT transfers that are being continued.
131 - Too many queued ISO transfers (-EAGAIN)
141 The same applies to INT transfers, but here the seamless continuation is
192 1.8. How to do isochronous (ISO) transfers?
194 For ISO transfers you have to append the iso_packet_descriptor_t structure
218 1.9. How to start interrupt (INT) transfers?
220 INT transfers are currently implemented with different queues for intervals
|
| D | ohci.txt | 4 (ISO coming soon, Bulk, INT u. CTRL transfers enabled)
10 * v4.0 1999/08/18 removed all dummy eds, unlink unused eds, code cleanup, bulk transfers
16 * INT and CTRL transfers enabled, Bulk included but disabled, ISO needs completion
62 There is one basic command for all types of bus transfers (INT, BULK, ISO, CTRL):
78 queued transfers of an endpoint will return unsent. They will be marked with an error status.
80 e.g double-buffering for int transfers:
|
| D | proc_usb_info.txt | 59 control, bulk, or other kinds of USB transfers. The IOCTLs are
155 (millisecond) is in use. It reflects only periodic transfers, which
156 are the only transfers that reserve bandwidth. Control and bulk
157 transfers use all other bandwidth, including reserved bandwidth that
158 is not used for transfers (such as for short packets).
161 those transfers. For a low or full speed bus (loosely, "USB 1.1"),
263 | | | | |__Interval (max) between transfers
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | PLIP.txt | 119 ports. This allows byte-wide transfers and avoids reconstructing
120 nibbles into bytes, leading to much faster transfers.
126 printer "null" cable which transfers data four bits at a time using
159 ports. This allows byte-wide transfers, and avoids reconstructing
|
| /linux-2.4.37.9/drivers/scsi/sym53c8xx_2/ |
| D | Documentation.txt | 283 transfers. However, some flawed devices or mother boards will have
422 Synchronous transfers frequency (default answer: 80)
425 0 means "asynchronous data transfers".
443 - set synchronous negotiation speed to 10 Mega-transfers / second.
485 #factor = 9 Ultra-3 SCSI 80 Mega-transfers / second (Wide only)
486 #factor = 10 Ultra-2 SCSI 40 Mega-transfers / second
487 #factor = 11 Ultra-2 SCSI 33 Mega-transfers / second
488 #factor < 25 Ultra SCSI 20 Mega-transfers / second
523 burst:#x burst enabled (1<<#x burst transfers max)
524 #x is an integer value which is log base 2 of the burst transfers max.
[all …]
|
| /linux-2.4.37.9/Documentation/ |
| D | parport-lowlevel.txt | 92 Hardware assistance for EPP and/or ECP transfers may or may not be
159 transfers.
162 transfers, i.e. compat_write_block.
164 transfers.
166 transfers.
179 Similarly, hardware that is capable of assisting ECP transfers won't
1231 PARPORT_EPP_FAST Use fast transfers. Some chips provide 16-bit and
1260 PARPORT_EPP_FAST Use fast transfers. Some chips provide 16-bit and
1289 PARPORT_EPP_FAST Use fast transfers. Some chips provide 16-bit and
1320 PARPORT_EPP_FAST Use fast transfers. Some chips provide 16-bit and
|
| D | LVM-HOWTO | 79 vgcreate activates (transfers the metadata into the LVM driver in the kernel)
|
| D | hayes-esp.txt | 102 transfers of 32 bytes or less will always use PIO mode.
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | README.in2000 | 113 of the fifo, and (hopefully) faster data transfers. The
123 is being accessed, transfers usually go faster if disconnects
130 the driver to do adaptive disconnect, synchronous transfers, and a
|
| D | README.ncr53c8xx | 311 transfers. However, some flawed devices or mother boards will have
412 Elapsed time for data transfers
588 0 means "asynchronous data transfers".
641 - set synchronous negotiation speed to 10 Mega-transfers / second.
719 #factor = 10 Ultra-2 SCSI 40 Mega-transfers / second
720 #factor = 11 Ultra-2 SCSI 33 Mega-transfers / second
721 #factor < 25 Ultra SCSI 20 Mega-transfers / second
761 burst:#x burst enabled (1<<#x burst transfers max)
762 #x is an integer value which is log base 2 of the burst transfers max.
763 The NCR53C875 and NCR53C825A support up to 128 burst transfers (#x = 7).
[all …]
|
| D | README.aha152x | 24 SYNCHRONOUS enable synchronous transfers (0/1; default 1 [on])
92 enable synchronous transfers for first and second controller
|
| D | Config.in | 151 bool ' always negotiate synchronous transfers' CONFIG_SCSI_NCR53C7xx_sync
173 int ' synchronous transfers frequency in MHz' CONFIG_SCSI_NCR53C8XX_SYNC 20
|
| D | README.53c700 | 153 disable 8 byte bursting for DMA transfers.
|
| /linux-2.4.37.9/drivers/usb/gadget/ |
| D | Config.in | 34 # or any other controller that supports high speed transfers ...
|
| /linux-2.4.37.9/Documentation/video4linux/bttv/ |
| D | README.freeze | 44 Some hardware can't deal with PCI-PCI transfers (i.e. grabber => vga).
|
| /linux-2.4.37.9/drivers/message/i2o/ |
| D | README.ioctl | 220 Please note that SW transfers can take a long time.
262 Please note that SW transfers can take a long time.
|
| /linux-2.4.37.9/drivers/scsi/aic7xxx/ |
| D | aic7xxx.reg | 164 * SOFS (3:0) bits disables synchronous data transfers. Any offset value
165 * greater than 0 enables synchronous transfers.
192 * The aic7890/91 allow an offset of up to 127 transfers in both wide
1283 * control whether to enable Ultra transfers or not. During
|
| D | aic7xxx.seq | 603 * target transfers.
698 * so default to narrow transfers to avoid
840 * corrupted by the interveining, non-data, transfers. Ask
1200 * unable to handle direct transfers from
1404 * transfers from the sequencer. Force this to
1420 * transfers.
2254 * happen for SCSI transfers as the SCSI module
|
| /linux-2.4.37.9/drivers/ide/ |
| D | Config.in | 69 …dep_mbool ' Force (U)DMA burst transfers' CONFIG_PDC202XX_BURST $CONFIG_BLK_DEV_PDC202XX_…
|
| /linux-2.4.37.9/drivers/parport/ |
| D | ChangeLog | 138 want to use the FIFO for real data transfers.
263 BYTE mode reverse transfers (previously always went for NIBBLE
|
| /linux-2.4.37.9/Documentation/i2c/ |
| D | smbus-protocol | 164 PEC adds a CRC-8 error-checking byte to all transfers.
|
| /linux-2.4.37.9/arch/sparc64/ |
| D | config.in | 204 int 'synchronous transfers frequency in MHz' CONFIG_SCSI_NCR53C8XX_SYNC 10
|
| /linux-2.4.37.9/arch/m68k/ifpsp060/ |
| D | isp.doc | 180 data registers, and BEFORE the actual emulated transfers occur, the
|
123