| /linux-2.4.37.9/drivers/usb/storage/ |
| D | shuttle_usbat.c | 332 int usbat_wait_not_busy(struct us_data *us, int minutes) { in usbat_wait_not_busy() argument
344 for (i=0; i<1200+minutes*60; i++) { in usbat_wait_not_busy()
373 minutes); in usbat_wait_not_busy()
383 int minutes) { in usbat_write_block() argument
409 return usbat_wait_not_busy(us, minutes); in usbat_write_block()
425 int minutes) { in usbat_rw_block_test() argument
545 return usbat_wait_not_busy(us, minutes); in usbat_rw_block_test()
|
| D | shuttle_usbat.h | 66 int use_sg, int minutes);
|
| /linux-2.4.37.9/Documentation/ |
| D | laptop-mode.txt | 36 This means you could potentially loose 10 minutes worth of data, if you
58 10 minutes worth of drive spin down. Provided your work load is cached,
59 the disk will only spin up every 10 minutes (well actually, 9 minutes and 55
|
| D | moxa-smartio | 256 b. make clean /* take a few minutes */
257 c. make dep /* take a few minutes */
258 d. make bzImage /* take probably 10-20 minutes */
277 is inevitable. And it takes about 10 to 20 minutes depends on the
|
| D | using-newer-gcc.txt | 39 Solution : the two-minutes process
44 is rather fast. I call that a two-minutes process because building an
|
| D | watchdog-api.txt | 102 if the device has a granularity of minutes for its timeout.
385 Hardcoded timeout of 3 minutes
|
| D | pm.txt | 176 closes), system power policy (eg. sleep after 30 minutes of console
178 minutes of inactivity)
|
| D | rtc.txt | 51 kernel will write the time back to the CMOS clock every 11 minutes. In
|
| D | kernel-docs.txt | 196 Description: Introductory 50-minutes (sic) tutorial on writing
|
| /linux-2.4.37.9/drivers/ide/raid/ |
| D | silraid.h | 14 unsigned char minutes; /* 0x10D */ member
|
| /linux-2.4.37.9/include/asm-ppc/ |
| D | todc.h | 58 int minutes; member
411 todc_info->minutes = clock_type ##_MINUTES; \
|
| /linux-2.4.37.9/arch/ppc/kernel/ |
| D | todc_time.c | 308 min = todc_read_val(todc_info->minutes) & 0x7f; in todc_get_rtc_time()
393 todc_write_val(todc_info->minutes, tm.tm_min); in todc_set_rtc_time()
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | README.dpti | 74 * a command may take up to 6 minutes to complete after it has been sent
|
| D | cpqfcTSinit.c | 819 int days, hours, minutes, secs; in cpqfcTS_proc_info() local
823 minutes = (DeltaSecs % 3600 / 60); // minutes in cpqfcTS_proc_info()
825 …(&info, "Fibre Channel Stats (time dd:hh:mm:ss %02u:%02u:%02u:%02u\n", days, hours, minutes, secs); in cpqfcTS_proc_info()
|
| D | README.st | 338 default is 900 seconds (15 minutes). The timeout should be
|
| D | README.BusLogic | 175 minutes of operation, then tagged queuing will be disabled for that target
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | PLIP.txt | 35 minutes' work, no need to search for a [supported] netcard. This might
|
| D | slicecom.hun | 340 Data in Interval 1 (15 minutes):
|
| D | slicecom.txt | 331 Data in Interval 1 (15 minutes):
|
| D | z8530drv.txt | 548 Example: sccparam /dev/scc0 maxdefer 240 # 2 minutes
|
| D | ip-sysctl.txt | 88 will be aborted after ~11 minutes of retries.
|
| /linux-2.4.37.9/Documentation/BK-usage/ |
| D | bk-kernel-howto.txt | 27 and merges. You will need to take a few minutes to think about
|
| /linux-2.4.37.9/Documentation/usb/ |
| D | ibmcam.txt | 107 it needs few minutes to "relax" before it can be plugged in again
|
| /linux-2.4.37.9/Documentation/video4linux/ |
| D | Zoran | 81 about 20 minutes of full motion NTSC (I live in Mexico) video capture
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | proc.txt | 213 loadavg Load average of last 1, 5 & 15 minutes
|