Home
last modified time | relevance | path

Searched refs:recognized (Results 1 – 25 of 43) sorted by relevance

12

/linux-3.4.99/arch/s390/include/asm/
Dsclp.h17 u8 recognized[SCLP_CHP_INFO_MASK_SIZE]; member
/linux-3.4.99/drivers/s390/char/
Dsclp_cmd.c722 u8 recognized[SCLP_CHP_INFO_MASK_SIZE]; member
759 memcpy(info->recognized, sccb->recognized, SCLP_CHP_INFO_MASK_SIZE); in sclp_chp_read_info()
/linux-3.4.99/Documentation/input/
Dappletouch.txt71 is not perfect. If finger movements are not recognized anymore, try reloading
Dmulti-touch-protocol.txt26 events. Only the ABS_MT events are recognized as part of a contact
333 in a finger packet must not be recognized as single-touch events.
Dxpad.txt62 If your dance pad is recognized by the driver but is using axes instead
/linux-3.4.99/Documentation/networking/
DDLINK.txt132 - The adapter is not recognized at boot, i.e. an Ethernet
150 o If the adapter _is_ recognized at boot but you get messages
/linux-3.4.99/Documentation/usb/
DCREDITS51 Systems recognized the importance of an up-to-date open
96 Being a recognized vendor and seller for all these devices,
/linux-3.4.99/arch/sh/kernel/
Dhead_64.S74 #error preprocessor flag CONFIG_CACHE_... not recognized!
/linux-3.4.99/Documentation/video4linux/bttv/
DPROBLEMS5 - The memory of some S3 cards is not recognized right:
/linux-3.4.99/Documentation/acpi/
Dmethod-customizing.txt19 "Device", "OperationRegion", are not recognized.
/linux-3.4.99/Documentation/misc-devices/
Dlis3lv02d78 If your laptop model is not recognized (cf "dmesg"), you can send an
/linux-3.4.99/Documentation/ABI/testing/
Dsysfs-driver-hid-roccat-kone92 ranging from 5 to 20 grams which are recognized by the mouse
/linux-3.4.99/fs/cifs/
DTODO97 1) existing symbolic links (Windows reparse points) are recognized but
/linux-3.4.99/Documentation/filesystems/
Dsysv-fs.txt20 - Only file systems with no filesystem name and no pack name are recognized.
/linux-3.4.99/Documentation/s390/
Dkvm.txt119 after the intercept exit was recognized.
Dcds.txt275 particular I/O request. If a pending device status was recognized,
358 status is recognized.
/linux-3.4.99/Documentation/video4linux/
Dw9968cf.txt170 At this point the pertinent devices should be recognized: "dmesg" can be used
213 recognized camera and use auto for the first one and for every
Dsn9c102.txt164 ports should be recognized. You can invoke "dmesg" to analyze kernel messages
187 recognized camera and use auto for the first one and for every
233 Every time a supported device is recognized, a write-only file named "green" is
Dzc0301.txt136 At this point the devices should be recognized. You can invoke "dmesg" to
/linux-3.4.99/Documentation/crypto/
Dapi-intro.txt105 on a recognized standard and/or have been subjected to appropriate
/linux-3.4.99/drivers/s390/cio/
Dchp.c596 if (!chp_test_bit(chp_info.recognized, bit)) in chp_info_get_status()
/linux-3.4.99/drivers/staging/wlags49_h2/
DREADME.ubuntu60 Now the card should be recognized. It should be able to configure
/linux-3.4.99/Documentation/arm/
DREADME13 an error if your compiler is a recognized offender.
/linux-3.4.99/Documentation/scsi/
Dibmmca.txt338 Integrated-, and MCA-adapters are automatically recognized. Unrecognizable
454 eight SCSI-subsystems can be recognized and announced to the upper-level
587 5) Magneto-Optical drives and medium-changers are also recognized, now.
793 3) Commandline-parameters are recognized again, even under Kernel 2.3.x or
1065 newer driver. I bet, it will be recognized correctly. Even multiple and
1066 different types of IBM SCSI-adapters should be recognized correctly, too.
1113 Q: My SCSI-adapter is not recognized by the driver, what can I do?
1114 A: Just force it to be recognized by kernel parameters. See section 5.1.
1168 was in such a case recognized as integrated SCSI-adapter or something
/linux-3.4.99/Documentation/power/
Duserland-swsusp.txt31 The ioctl() commands recognized by the device are:

12