| /linux-2.6.39/net/irda/ircomm/ |
| D | ircomm_event.c | 103 ret = self->issue.connect_request(self, skb, info); in ircomm_state_idle()
162 ret = self->issue.connect_response(self, skb); in ircomm_state_waitr()
166 ret = self->issue.disconnect_request(self, skb, info); in ircomm_state_waitr()
194 ret = self->issue.data_request(self, skb, 0); in ircomm_state_conn()
204 ret = self->issue.data_request(self, skb, skb->len); in ircomm_state_conn()
213 ret = self->issue.disconnect_request(self, skb, info); in ircomm_state_conn()
|
| D | ircomm_ttp.c | 104 self->issue.data_request = ircomm_ttp_data_request; in ircomm_open_tsap()
105 self->issue.connect_request = ircomm_ttp_connect_request; in ircomm_open_tsap()
106 self->issue.connect_response = ircomm_ttp_connect_response; in ircomm_open_tsap()
107 self->issue.disconnect_request = ircomm_ttp_disconnect_request; in ircomm_open_tsap()
|
| D | ircomm_lmp.c | 367 self->issue.data_request = ircomm_lmp_data_request; in ircomm_open_lsap()
368 self->issue.connect_request = ircomm_lmp_connect_request; in ircomm_open_lsap()
369 self->issue.connect_response = ircomm_lmp_connect_response; in ircomm_open_lsap()
370 self->issue.disconnect_request = ircomm_lmp_disconnect_request; in ircomm_open_lsap()
|
| /linux-2.6.39/Documentation/networking/ |
| D | ixgbevf.txt | 50 If an issue is identified with the released source code on the supported
52 to the issue to e1000-devel@lists.sf.net
|
| D | igbvf.txt | 78 If an issue is identified with the released source code on the supported
80 to the issue to e1000-devel@lists.sf.net
|
| D | igb.txt | 107 If an issue is identified with the released source code on the supported
109 to the issue to e1000-devel@lists.sf.net
|
| D | ixgb.txt | 347 cable assembly may resolve the issue.
355 the issue.
360 this situation occurs, using a different cable assembly may resolve the issue.
383 the available memory is heavily fragmented. This issue may be seen with PCI-X
431 If an issue is identified with the released source code on the supported
433 to the issue to e1000-devel@lists.sf.net
|
| /linux-2.6.39/drivers/staging/speakup/ |
| D | TODO | 11 The first issue has to do with the way speakup communicates with serial
34 Another issue seems to only happen on SMP systems. It seems
|
| /linux-2.6.39/arch/alpha/lib/ |
| D | strlen.S | 34 nop # helps dual issue last two insns
|
| D | strlen_user.S | 81 nop # dual issue next two on ev4 and ev5
|
| /linux-2.6.39/Documentation/timers/ |
| D | timer_stats.txt | 33 To activate a sample period issue:
36 To stop a sample period issue:
|
| /linux-2.6.39/arch/blackfin/mach-common/ |
| D | arch_checks.c | 55 # error You are using a part with anomaly 05000448, this issue causes random memory read/write fail…
|
| /linux-2.6.39/Documentation/arm/SA1100/ |
| D | Pangolin | 7 To compile for Pangolin, you must issue the following commands:
|
| D | Brutus | 6 To compile for Brutus, you must issue the following commands:
|
| /linux-2.6.39/net/rxrpc/ |
| D | rxkad.c | 830 time_t issue, now; in rxkad_decrypt_ticket() local
918 issue = le32_to_cpu(stamp); in rxkad_decrypt_ticket()
922 issue = be32_to_cpu(stamp); in rxkad_decrypt_ticket()
926 _debug("KIV ISSUE: %lx [%lx]", issue, now); in rxkad_decrypt_ticket()
929 if (issue > now) { in rxkad_decrypt_ticket()
935 if (issue < now - life) { in rxkad_decrypt_ticket()
941 *_expiry = issue + life; in rxkad_decrypt_ticket()
|
| /linux-2.6.39/Documentation/powerpc/ |
| D | qe_firmware.txt | 87 flexibility and save h/w traps If new features are activated or an issue is
134 | | RX INIT | command, the host must issue another special|
136 | | | following that re-issue the ATM RX INIT |
146 | | | must issue another command. |
157 | | command | INIT command, user must issue this command |
|
| /linux-2.6.39/include/net/irda/ |
| D | ircomm_core.h | 61 call_t issue; member
|
| D | irda_device.h | 111 struct dongle_reg *issue; /* Registration info */ member
|
| /linux-2.6.39/Documentation/usb/ |
| D | ehci.txt | 109 the EHCI controller can issue interrupts.
148 Bulk transfers are most often used where throughput is an issue. It's
167 onto one bus does not get you 60 MByte/sec. The issue appears to be
182 you issue a control or bulk request you can often expect to learn that
210 transfers are fully scheduled, so the main issue is likely to be how
|
| /linux-2.6.39/Documentation/ |
| D | stable_kernel_rules.txt | 13 security issue, or some "oh, that's not good" issue. In short, something
|
| /linux-2.6.39/drivers/staging/tm6000/ |
| D | README | 14 it is an overheat issue - is there a workaround that we could do?
|
| /linux-2.6.39/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 65 will re-issue those pending cmds again to FW after the OCR
77 OCR to finish, then issue the cmds to FW.
101 context value larger than 32bit value issue.
106 3. driver fixed the device update issue after get the AEN
192 … Unexpected interrupt occurs in HWR Linux driver, add the dumy readl pci flush will fix this issue.
258 issue. 2. Increased MFI_POLL_TIMEOUT_SECS to 60 seconds from
|
| /linux-2.6.39/drivers/scsi/arm/ |
| D | acornscsi.h | 318 Queue_t issue; /* issue queue */ member
|
| /linux-2.6.39/drivers/staging/zram/ |
| D | zram.txt | 35 data. So, for such a disk, you need to issue 'reset' (see below)
|
| /linux-2.6.39/Documentation/s390/ |
| D | 3270.txt | 163 above? Use the grep command to find out; for instance, issue
169 issue "ls -l /dev/3270/tty620". The output should start with the
177 If so, you must issue the command "DEF GRAF 620" from your VM
259 Have a command you issue frequently? Assign it to a PF or PA key! Use
|