Home
last modified time | relevance | path

Searched refs:what (Results 1 – 25 of 246) sorted by relevance

12345678910

/linux-2.4.37.9/drivers/usb/storage/
Ddebug.c51 char *what = NULL; in usb_stor_show_command() local
54 case TEST_UNIT_READY: what = "TEST_UNIT_READY"; break; in usb_stor_show_command()
55 case REZERO_UNIT: what = "REZERO_UNIT"; break; in usb_stor_show_command()
56 case REQUEST_SENSE: what = "REQUEST_SENSE"; break; in usb_stor_show_command()
57 case FORMAT_UNIT: what = "FORMAT_UNIT"; break; in usb_stor_show_command()
58 case READ_BLOCK_LIMITS: what = "READ_BLOCK_LIMITS"; break; in usb_stor_show_command()
59 case REASSIGN_BLOCKS: what = "REASSIGN_BLOCKS"; break; in usb_stor_show_command()
60 case READ_6: what = "READ_6"; break; in usb_stor_show_command()
61 case WRITE_6: what = "WRITE_6"; break; in usb_stor_show_command()
62 case SEEK_6: what = "SEEK_6"; break; in usb_stor_show_command()
[all …]
/linux-2.4.37.9/drivers/usb/
Dmicrotek.c233 char *what = NULL; in mts_show_command() local
236 case TEST_UNIT_READY: what = "TEST_UNIT_READY"; break; in mts_show_command()
237 case REZERO_UNIT: what = "REZERO_UNIT"; break; in mts_show_command()
238 case REQUEST_SENSE: what = "REQUEST_SENSE"; break; in mts_show_command()
239 case FORMAT_UNIT: what = "FORMAT_UNIT"; break; in mts_show_command()
240 case READ_BLOCK_LIMITS: what = "READ_BLOCK_LIMITS"; break; in mts_show_command()
241 case REASSIGN_BLOCKS: what = "REASSIGN_BLOCKS"; break; in mts_show_command()
242 case READ_6: what = "READ_6"; break; in mts_show_command()
243 case WRITE_6: what = "WRITE_6"; break; in mts_show_command()
244 case SEEK_6: what = "SEEK_6"; break; in mts_show_command()
[all …]
/linux-2.4.37.9/scripts/
Dcheckhelp.pl18 $what=$3;
21 @found = grep (/$what$/, @options);
23 next if $nohelp{$what};
24 print "$name\n$what\n No help for $what\n\n";
25 $nohelp{$what}=1;
/linux-2.4.37.9/drivers/isdn/
Disdn_audio.c515 char what; in isdn_audio_eval_dtmf() local
534 what = ' '; in isdn_audio_eval_dtmf()
562 what = dtmf_matrix[grp[LOGRP]][grp[HIGRP]]; in isdn_audio_eval_dtmf()
564 s->last = what; /* min. 1 non-DTMF between DTMF */ in isdn_audio_eval_dtmf()
566 what = '.'; in isdn_audio_eval_dtmf()
569 what = '.'; in isdn_audio_eval_dtmf()
571 if ((what != s->last) && (what != ' ') && (what != '.')) { in isdn_audio_eval_dtmf()
572 printk(KERN_DEBUG "dtmf: tt='%c'\n", what); in isdn_audio_eval_dtmf()
575 *p = what; in isdn_audio_eval_dtmf()
598 s->last = what; in isdn_audio_eval_dtmf()
[all …]
/linux-2.4.37.9/arch/arm/kernel/
Dplx90x0.c130 char *what; in plx90x0_init() local
147 what = "PCI9060"; in plx90x0_init()
150 what = "PCI9060ES"; in plx90x0_init()
153 what = "PCI9060SD"; /* uhuhh.. */ in plx90x0_init()
156 what = "PCI9080"; in plx90x0_init()
164 printk("PCI: PLX Technology %s host bridge found.\n", what); in plx90x0_init()
/linux-2.4.37.9/drivers/ide/
Dide-timing.h189 …e_timing_merge(struct ide_timing *a, struct ide_timing *b, struct ide_timing *m, unsigned int what) in ide_timing_merge() argument
191 if (what & IDE_TIMING_SETUP ) m->setup = MAX(a->setup, b->setup); in ide_timing_merge()
192 if (what & IDE_TIMING_ACT8B ) m->act8b = MAX(a->act8b, b->act8b); in ide_timing_merge()
193 if (what & IDE_TIMING_REC8B ) m->rec8b = MAX(a->rec8b, b->rec8b); in ide_timing_merge()
194 if (what & IDE_TIMING_CYC8B ) m->cyc8b = MAX(a->cyc8b, b->cyc8b); in ide_timing_merge()
195 if (what & IDE_TIMING_ACTIVE ) m->active = MAX(a->active, b->active); in ide_timing_merge()
196 if (what & IDE_TIMING_RECOVER) m->recover = MAX(a->recover, b->recover); in ide_timing_merge()
197 if (what & IDE_TIMING_CYCLE ) m->cycle = MAX(a->cycle, b->cycle); in ide_timing_merge()
198 if (what & IDE_TIMING_UDMA ) m->udma = MAX(a->udma, b->udma); in ide_timing_merge()
/linux-2.4.37.9/include/asm-ppc/
Dmediabay.h21 int check_media_bay(struct device_node *which_bay, int what);
22 int check_media_bay_by_base(unsigned long base, int what);
/linux-2.4.37.9/Documentation/i2c/
Ddev-interface6 examine /proc/bus/i2c to see what number corresponds to which adapter.
33 /* ERROR HANDLING; you can check errno to see what went wrong */
37 When you have opened the device, you must specify with what device
41 /* ERROR HANDLING; you can check errno to see what went wrong */
133 what happened. The 'write' transactions return 0 on success; the
141 want to know what happens behind the screens.
/linux-2.4.37.9/Documentation/isdn/
D00-INDEX8 - general info on what you need and what to do for Linux ISDN.
/linux-2.4.37.9/lib/zlib_inflate/
Dinffast.c16 #define exop word.what.Exop
17 #define bits word.what.Bits
Dinftrees.h24 } what; member
/linux-2.4.37.9/Documentation/networking/
Ddecnet.txt16 CONFIG_PROC_FS (to see what's going on)
72 There is a list of what the other files under /proc/sys/net/decnet/ do
78 pages for details on what the various options do) or through the iproute2
99 Here is a quick guide of what to look for in order to know if your DECnet
132 you can do to help me work out exactly what it is that is wrong. Useful
166 documentation above and beyond what was previously publicly available.
Dpktgen.txt32 'minimum' MAC is what you set with srcmac.
34 'minimum' MAC is what you set with dstmac.
/linux-2.4.37.9/Documentation/
Dwatchdog-api.txt115 available to ask what the device can do:
124 options a flags describing what the device supports
126 the options field can have the following bits set, and describes what
207 Here I have tried to summarize what the different drivers support and
237 what should happen on a timeout, the string "int" or anything
277 Has a module parameter "action" that controls what happens
290 [FIXME -- I'm unable to tell what the timeout is]
334 [FIXME -- I'm unable to tell what the timeout is]
Dlaptop-mode.txt28 So what does the laptop mode patch do? It attempts to fully utilize the
49 know why or what causes it. The laptop mode patch has a little helper for
51 the kernel message buffer about what process caused the io. Be very careful
Dnfsroot.txt26 you want to use nfsroot, and if yes what kind of auto configuration
36 LILO or a network boot program) it has to be told what root fs device
91 RARP and BOOTP (depending on what has been enabled during kernel confi-
92 guration, and if both what protocol answer got in first).
96 pends on what has been enabled during kernel configuration
143 depend on what facilities are available:
Doops-tracing.txt12 the person responsible for the code relevant to what you were doing.
85 and do a replace of spaces to "\x" - that's what I do, as I'm too lazy
93 and then you get a better idea of what happens than with the gdb
97 sources (and general knowledge of what it _should_ do), the assembly
104 Essentially, you just look at what doesn't match (in this case it was the
105 "Code" disassembly that didn't match with what the compiler generated).
/linux-2.4.37.9/drivers/scsi/
DREADME.aic7xxx195 fast to see. By using this option, you can write down what the errors
200 is a debugging aid used to see exactly what state the card is in
210 card's sequencer are indeed what they are suppossed to be. Again,
246 I'm probably going to be telling you what to set this to anyway :)
251 what the variable should be. It depends entirely on how the chipset
257 setting was 0, then that's what it would be after the reset, but if
278 then you next need to figure out what your settings should be.
284 they are listed, and also record what the machine is detecting as
294 DEVCONFIG values for each controller, then figure out what the
309 Now that you know what the correct setting was for each controller,
[all …]
/linux-2.4.37.9/drivers/scsi/aic7xxx_old/
DREADME.aic7xxx229 fast to see. By using this option, you can write down what the errors
234 is a debugging aid used to see exactly what state the card is in
244 card's sequencer are indeed what they are suppossed to be. Again,
280 I'm probably going to be telling you what to set this to anyway :)
285 what the variable should be. It depends entirely on how the chipset
291 setting was 0, then that's what it would be after the reset, but if
312 then you next need to figure out what your settings should be.
318 they are listed, and also record what the machine is detecting as
328 DEVCONFIG values for each controller, then figure out what the
343 Now that you know what the correct setting was for each controller,
[all …]
/linux-2.4.37.9/fs/reiserfs/
Dprints.c156 static char * is_there_reiserfs_struct (char * fmt, int * what, int * skip) in is_there_reiserfs_struct() argument
166 *what = k[1]; in is_there_reiserfs_struct()
198 int i, j, what, skip; in prepare_error_buf() local
202 while( (k = is_there_reiserfs_struct( fmt1, &what, &skip )) != NULL ) in prepare_error_buf()
211 switch (what) { in prepare_error_buf()
Ddir.c34 #define store_ih(where,what) copy_item_head (where, what) argument
/linux-2.4.37.9/Documentation/fb/
Dtridentfb.txt30 look at the driver output to see what it says when initializing.
40 800 or 1280) and it is not what the driver seems to detect use it.
/linux-2.4.37.9/Documentation/x86_64/
DBUGS8 that would touch offset.h (see arch/x86-64/tools/offset.c on what that is).
/linux-2.4.37.9/include/asm-ppc64/
Dpci-bridge.h41 char what[8]; /* Eye catcher */ member
/linux-2.4.37.9/Documentation/usb/
Dibmcam.txt104 what the camera is trying to say. Blame trade secrets for that.
195 what values do what. 0=off.
198 bits to produce what you want. Usually you don't want
240 what usual "hue" control does. Both controls affect
306 I know now how to read button on Model 2, but what to do with it?
309 what returned data means. If camera fails at some initialization

12345678910