Home
last modified time | relevance | path

Searched refs:OK (Results 1 – 25 of 84) sorted by relevance

1234

/linux-3.4.99/arch/powerpc/kernel/
Dprom_init_check.sh44 OK=0
48 OK=1
55 OK=1
58 OK=1
61 OK=1
64 OK=1
67 OK=1
70 OK=1
73 if [ $OK -eq 0 ]; then
/linux-3.4.99/drivers/usb/host/
Duhci-hub.c78 #define OK(x) len = (x); break macro
258 OK(4); /* hub power */ in uhci_hub_control()
311 OK(4); in uhci_hub_control()
317 OK(0); in uhci_hub_control()
329 OK(0); in uhci_hub_control()
338 OK(0); in uhci_hub_control()
341 OK(0); in uhci_hub_control()
356 OK(0); in uhci_hub_control()
359 OK(0); in uhci_hub_control()
382 OK(0); in uhci_hub_control()
[all …]
/linux-3.4.99/drivers/net/plip/
Dplip.c346 #define OK 0 macro
375 if ((r = (*f)(nl->dev, nl, snd, rcv)) != OK && in plip_bh()
376 (r = plip_bh_timeout_error(nl->dev, nl, snd, rcv, r)) != OK) { in plip_bh()
436 return OK; in plip_bh_timeout_error()
477 return OK; in plip_none()
526 return OK; in plip_receive()
613 return OK; in plip_receive_packet()
687 return OK; in plip_receive_packet()
693 return OK; in plip_receive_packet()
696 return OK; in plip_receive_packet()
[all …]
/linux-3.4.99/Documentation/isdn/
DINTERFACE.fax105 OK message will be sent.
109 0: output OK message (more pages follow)
112 ISDN_TTY_FAX_TRAIN_OK output of +FDCS and OK message (for receive mode).
118 OK message, switching to phase E.
/linux-3.4.99/Documentation/power/
Dvideo.txt105 Asus L2400D s3_mode (3)(***) (S1 also works OK)
107 Asus L3800C (Radeon M7) s3_bios (2) (S1 also works OK)
111 Compaq Armada E500 - P3-700 none (1) (S1 also works OK)
131 HP Omnibook 5150 none (1), (S1 also works OK)
165 Toshiba Satellite 4030CDT s3_mode (3) (S1 also works OK)
166 Toshiba Satellite 4080XCDT s3_mode (3) (S1 also works OK)
/linux-3.4.99/drivers/net/fddi/skfp/h/
Dsba_def.h67 #define OK 0x01 /* ??????? */ macro
/linux-3.4.99/drivers/isdn/hardware/eicon/
Dpc_maint.h68 #define OK 0xff macro
Dmessage.c738 (*command_function)(Id, plci, OK); in start_internal_command()
764 (*(plci->internal_command_queue[0]))(Id, plci, OK); in next_internal_command()
3914 if ((rc == OK) && a->FlowControlSkipTable[ch]) { in callback()
4154 if (rc != OK) in control_rc()
4165 if (rc != OK) in control_rc()
4175 if (rc != OK) Info = _WRONG_STATE; in control_rc()
4186 || (!nl_rc && (req == CALL_REQ) && (rc != OK))) in control_rc()
4235 if (rc != OK) in control_rc()
4271 if (rc != OK) in control_rc()
4294 if (rc == OK) /* command supported, wait for indication */ in control_rc()
[all …]
/linux-3.4.99/arch/s390/kvm/
DKconfig46 # OK, it's a little counter-intuitive to do this, but it puts it neatly under
/linux-3.4.99/drivers/staging/usbip/
Dusbip_protocol.txt110 4 | 4 | 0x00000000 | Status: 0 for OK
195 4 | 4 | 0x00000000 | Status: 0 for OK
199 | | | device, if the previous status field was OK (0),
/linux-3.4.99/drivers/staging/comedi/drivers/
Djr3_pci.c418 int result, more, pos, OK; in jr3_download_firmware() local
423 OK = 0; in jr3_download_firmware()
429 OK = 1; in jr3_download_firmware()
440 if (!OK) { in jr3_download_firmware()
/linux-3.4.99/Documentation/usb/
Dacm.txt126 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
127 device and try typing 'at'. If it responds with 'OK', then everything is
Dgadget_printer.txt107 Printer OK
130 To set error status to printer OK:
426 printf(" Printer OK\n");
/linux-3.4.99/arch/x86/kvm/
DKconfig82 # OK, it's a little counter-intuitive to do this, but it puts it neatly under
/linux-3.4.99/drivers/net/ethernet/sis/
Dsis900.h199 OK = 0x08000000, DSIZE = 0x00000FFF enumerator
/linux-3.4.99/Documentation/scsi/
Darcmsr_spec.txt9 ** (DRIVER DATA WRITE OK)
11 ** (DRIVER DATA READ OK)
13 ** (IOP331 DATA WRITE OK)
15 ** (IOP331 DATA READ OK)
/linux-3.4.99/Documentation/blockdev/
DREADME.DAC960337 /proc/rd/status returns "OK" when all DAC960 controllers in the system are
446 OK
449 returns "OK" indicating that there are no problems with any DAC960 controller
467 /proc/rd/status has changed from "OK" to "ALERT":
580 OK
618 OK
621 returns "OK" indicating that there are no problems with any DAC960 controller
643 /proc/rd/status has changed from "OK" to "ALERT":
722 OK
/linux-3.4.99/drivers/staging/frontier/
DREADME33 * It's theoretically OK on LEDs.
/linux-3.4.99/lib/raid6/
Dint.uc77 vv = (vv << 1) - (vv >> 7); /* Overflow on the top bit is OK */
/linux-3.4.99/Documentation/networking/
Dpktgen.txt33 Result: OK: max_before_softirq=10000
63 Result: OK: 13101142(c12220741+d880401) usec, 10000000 (60byte,0frags)
/linux-3.4.99/drivers/mtd/ubi/
DKconfig24 The default value should be OK for SLC NAND flashes, NOR flashes and
/linux-3.4.99/drivers/scsi/
Deata_generic.h74 #define OK 0 macro
/linux-3.4.99/Documentation/
Dinit.txt4 OK, so you've got this pretty unintuitive message (currently located
/linux-3.4.99/Documentation/networking/caif/
Dspi_porting.txt121 * called with the parameter assert set to true. It is OK
133 * to the CAIF SPI interface. It is OK to call this function
/linux-3.4.99/Documentation/serial/
Dn_gsm.txt37 and check that it's successful (should return OK) */

1234