/linux-3.4.99/drivers/scsi/ |
D | 53c700.scr | 181 CLEAR ACK 195 CLEAR ACK 199 CLEAR ACK 208 CLEAR ACK 212 CLEAR ACK 216 CLEAR ACK 220 CLEAR ACK 224 CLEAR ACK 232 CLEAR ACK 240 CLEAR ACK [all …]
|
D | 53c700_d.h_shipped | 238 CLEAR ACK 267 CLEAR ACK 280 CLEAR ACK 313 CLEAR ACK 326 CLEAR ACK 339 CLEAR ACK 352 CLEAR ACK 365 CLEAR ACK 382 CLEAR ACK 399 CLEAR ACK [all …]
|
/linux-3.4.99/Documentation/zh_CN/ |
D | stable_kernel_rules.txt | 46 - 如果补丁被接受到队列里,发送者会收到一个ACK回复,如果没有被接受,收 56 - 审查委员会有48小时的时间,用来决定给该补丁回复ACK还是NAK。 60 - 在审查周期结束的时候,那些得到ACK回应的补丁将会被加入到最新的稳定版
|
/linux-3.4.99/Documentation/ja_JP/ |
D | stable_kernel_rules.txt | 55 - 送信者はパッチがキューに受け付けられた際には ACK を、却下された場合 70 - レビュー委員会は 48時間の間に ACK か NAK を出す。 74 - レビューサイクルの最後に、ACK を受けたパッチは最新の -stable リリー
|
/linux-3.4.99/Documentation/input/ |
D | walkera0701.txt | 26 / O 4 3 O \ pin 3 (GND) LED ________________ 10 ACK 49 Driver use interrupt from parport ACK input bit to measure pulse length 80 (Warning, pulses on ACK are inverted by transistor, irq is raised up on sync
|
/linux-3.4.99/arch/arm/mach-at91/include/mach/ |
D | entry-macro.S | 25 streq \tmp, [\base, #AT91_AIC_EOICR] @ not going to be handled further, then ACK it now.
|
/linux-3.4.99/arch/mn10300/kernel/ |
D | smp-low.S | 66 movbu d2,(GxICR(FLUSH_CACHE_IPI)) # ACK the interrupt
|
D | mn10300-serial-low.S | 71 movbu d2,(e3) # ACK the interrupt 118 movbu d2,(e3) # ACK the interrupt
|
D | gdb-io-serial-low.S | 61 movbu d2,(XIRQxICR(GDBPORT_SERIAL_IRQ)) # ACK the interrupt
|
D | gdb-io-ttysm-low.S | 57 movbu d2,(GxICR(SCgRXIRQ)) # ACK the interrupt
|
/linux-3.4.99/drivers/usb/gadget/ |
D | goku_udc.c | 1547 #define ACK(irqbit) { \ macro 1598 ACK(INT_SUSPEND); in goku_irq() 1635 ACK(INT_USBRESET); in goku_irq() 1646 ACK(INT_SETUP); in goku_irq() 1651 ACK(INT_STATUSNAK|INT_ENDPOINT0); in goku_irq() 1661 ACK(INT_ENDPOINT0); in goku_irq() 1669 ACK(INT_MSTRDEND); in goku_irq() 1675 ACK(INT_MSTWREND); in goku_irq() 1681 ACK(INT_MSTWRTMOUT); in goku_irq() 1715 #undef ACK
|
/linux-3.4.99/Documentation/networking/ |
D | PLIP.txt | 141 D3->ACK 5 - 10 10 - 5 176 INIT -> ACK 16 - 10 204 That raises the ACK line, triggering an interrupt in the receiving 205 machine. The receiving machine disables interrupts and raises its own ACK
|
D | rxrpc.txt | 144 (*) Calls use ACK packets to handle reliability. Data packets are also 148 A hard-ACK indicates to the far side that all the data received to a point 149 has been received and processed; a soft-ACK indicates that the data has 151 not discard any transmittable packets until they've been hard-ACK'd. 153 (*) Reception of a reply data packet implicitly hard-ACK's all the data 157 received and the final hard-ACK on the last packet of the reply has 195 (*) ACK'ing is handled by the protocol driver automatically, including ping 234 the reply is transmitted with one or more sendmsgs, and then the final ACK 320 RXRPC_ACK -rt n/a Final ACK received 347 This is delivered to a server application to indicate that the final ACK [all …]
|
D | proc_net_tcp.txt | 34 | | | | | | (delayed ACK control data)
|
D | mac80211-injection.txt | 29 an ACK even if it is a unicast frame
|
D | ieee802154.txt | 49 comparation, automagic ACK handling, address matching, etc.
|
/linux-3.4.99/Documentation/scsi/ |
D | qlogicfas.txt | 71 that it gets a false ACK causing an extra byte to be inserted into the 73 termination (the ACK can be reflected), or by noise when the chips
|
/linux-3.4.99/drivers/media/dvb/bt8xx/ |
D | dst_common.h | 95 #define ACK 0xff macro
|
D | dst.c | 1103 if (reply != ACK) { in dst_get_device_id() 1252 if (reply != ACK) { in dst_command() 1423 if (reply != ACK) { in dst_write_tuna()
|
/linux-3.4.99/drivers/usb/serial/ |
D | garmin_gps.c | 115 #define ACK 0x06 macro 375 *ptr++ = ACK; in gsp_send_ack() 376 cksum += ACK; in gsp_send_ack() 541 if (data == ACK) { in gsp_receive() 542 ack_or_nak_seen = ACK; in gsp_receive()
|
/linux-3.4.99/Documentation/ |
D | stable_kernel_rules.txt | 57 - The sender will receive an ACK when the patch has been accepted into the 72 - The review committee has 48 hours in which to ACK or NAK the patch.
|
/linux-3.4.99/Documentation/pps/ |
D | pps.txt | 30 Carrier Detect pin) or to a parallel port (ACK-pin) or to a special 197 10 ACK * ------*
|
/linux-3.4.99/Documentation/spi/ |
D | butterfly | 66 IRQ = J402.PF4 = pin 10/S6,ACK
|
/linux-3.4.99/drivers/scsi/aic7xxx/ |
D | aic7xxx.seq | 1120 * it makes sense that the DMA circuitry doesn't ACK when 1445 * Wait for our ACK to go-away on it's own 1598 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ 1732 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ 1762 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ 1768 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ 1884 mov NONE,SCSIDATL; /* ACK Identify MSG */ 1961 * According to Adaptec's documentation, an ACK is not sent on input from 1967 * we send our ACK. 1977 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ [all …]
|
/linux-3.4.99/drivers/scsi/aic7xxx_old/ |
D | aic7xxx.seq | 798 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ 970 mov NONE,SCSIDATL; /* ACK Identify MSG */ 1018 mvi ARG_1 call inb_next; /* ACK the wide_residue and get */ 1044 * According to Adaptec's documentation, an ACK is not sent on input from 1050 * we send our ACK. 1058 mov NONE,SCSIDATL; /*dummy read from latch to ACK*/ 1073 mov NONE,SCSIDATL ret; /*dummy read from latch to ACK*/ 1102 * the DMA circuitry doesn't ACK when PHASEMIS is active). If we are
|