| /linux-2.4.37.9/net/rose/ |
| D | rose_subr.c | 192 *dptr++ = sk->protinfo.rose->diagnostic; in rose_write_internal()
520 void rose_disconnect(struct sock *sk, int reason, int cause, int diagnostic) in rose_disconnect() argument
533 if (diagnostic != -1) in rose_disconnect()
534 sk->protinfo.rose->diagnostic = diagnostic; in rose_disconnect()
|
| D | rose_route.c | 606 …uct rose_neigh *rose_get_neigh(rose_address *addr, unsigned char *cause, unsigned char *diagnostic) in rose_get_neigh() argument
626 *diagnostic = 0; in rose_get_neigh()
629 *diagnostic = 0; in rose_get_neigh()
773 unsigned char cause, diagnostic; in rose_route_frame() local
819 sk->protinfo.rose->diagnostic = 0; in rose_route_frame()
927 if ((new_neigh = rose_get_neigh(dest_addr, &cause, &diagnostic)) == NULL) { in rose_route_frame()
928 rose_transmit_clear_request(rose_neigh, lci, cause, diagnostic); in rose_route_frame()
|
| D | rose_link.c | 262 …_request(struct rose_neigh *neigh, unsigned int lci, unsigned char cause, unsigned char diagnostic) in rose_transmit_clear_request() argument
288 *dptr++ = diagnostic; in rose_transmit_clear_request()
|
| D | af_rose.c | 735 unsigned char cause, diagnostic; in rose_connect() local
772 …if ((sk->protinfo.rose->neighbour = rose_get_neigh(&addr->srose_addr, &cause, &diagnostic)) == NUL… in rose_connect()
1291 rose_cause.diagnostic = sk->protinfo.rose->diagnostic; in rose_ioctl()
1300 sk->protinfo.rose->diagnostic = rose_cause.diagnostic; in rose_ioctl()
|
| /linux-2.4.37.9/drivers/usb/ |
| D | aiptek.c | 399 int diagnostic; member
489 aiptek->diagnostic = in aiptek_irq()
522 aiptek->diagnostic = in aiptek_irq()
527 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_TOOL_DISALLOWED; in aiptek_irq()
643 aiptek->diagnostic = in aiptek_irq()
648 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_TOOL_DISALLOWED; in aiptek_irq()
856 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_NA; in aiptek_program_tablet()
1043 switch (aiptek->diagnostic) { in aiptek_procfs_read()
|
| /linux-2.4.37.9/net/x25/ |
| D | x25_subr.c | 321 unsigned char diagnostic) in x25_disconnect() argument
330 sk->protinfo.x25->causediag.diagnostic = diagnostic; in x25_disconnect()
|
| /linux-2.4.37.9/include/linux/ |
| D | x25.h | 109 unsigned char diagnostic; member
|
| D | rose.h | 73 unsigned char diagnostic; member
|
| /linux-2.4.37.9/include/net/ |
| D | rose.h | 127 unsigned char cause, diagnostic; member
|
| /linux-2.4.37.9/Documentation/s390/ |
| D | c7000.txt | 26 numbers will result in additional diagnostic messages.
|
| /linux-2.4.37.9/Documentation/usb/ |
| D | dc2xx.txt | 97 (or whatever name you used). Right now, gPhoto emits a diagnostic
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | cs89x0.txt | 457 Once the adapter has been installed and configured, the diagnostic option of
485 The diagnostic self-test checks the adapter's basic functionality as well as
532 on the same network. (Note: the diagnostic network test should not be run
597 diagnostic self-test. Normally, the ISA resource in conflict will fail the
|
| D | skfp.txt | 92 The adapter can be checked using the diagnostic program
|
| D | vortex.txt | 436 3) Download you card's diagnostic tool from Donald
|
| D | arcnet.txt | 140 sniffing), extra diagnostic information, etc. Unfortunately, there is no
|
| D | arcnet-hardware.txt | 715 Two diagnostic LEDs are visible on the rear bracket of the board.
942 Two diagnostic LEDs are visible on the rear bracket of the board.
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | ChangeLog | 219 NULL pointer panic on odd UDCs fixed, two bugs in diagnostic output
221 new memory allocation, extraneous diagnostic output suppressed,
|
| /linux-2.4.37.9/Documentation/ |
| D | Configure.help | 12615 extra diagnostic information.
|