Home
last modified time | relevance | path

Searched refs:writing (Results 1 – 25 of 109) sorted by relevance

12345

/linux-2.4.37.9/drivers/ide/pci/
Dtrm290.c186 unsigned int count, reading = 2, writing = 0; in trm290_ide_dma_write() local
189 writing = 1; in trm290_ide_dma_write()
202 hwif->OUTL(hwif->dmatable_dma|reading|writing, hwif->dma_command); in trm290_ide_dma_write()
237 unsigned int count, reading = 2, writing = 0; in trm290_ide_dma_read() local
246 hwif->OUTL(hwif->dmatable_dma|reading|writing, hwif->dma_command); in trm290_ide_dma_read()
/linux-2.4.37.9/drivers/char/ftape/lowlevel/
Dftape-write.c100 : writing); in ftape_start_writing()
137 while ((ft_driver_state == writing || ft_driver_state == deleting) && in ftape_loop_until_writes_done()
194 ? deleting : writing); in write_segment()
Dfdc-isr.c465 (write && (buff->status != writing)) || in continue_xfer()
552 case writing: buff->status = writing; break; in continue_xfer()
559 buff->status = write ? writing : reading; in continue_xfer()
Dfdc-io.h132 writing, enumerator
/linux-2.4.37.9/drivers/char/drm-4.0/
Dr128_cce.c844 int writing = 1;
853 writing = 0;
862 writing = 0;
867 writing = 0;
881 return writing;
893 int writing = 1;
899 writing = r128_verify_command( dev_priv, tmp, &psize );
903 if ( writing ) {
/linux-2.4.37.9/Documentation/filesystems/
Dudf.txt10 Write support requires a block driver which supports writing. The current
11 scsi and ide cdrom drivers do not support writing.
/linux-2.4.37.9/Documentation/fb/
Dpvr2fb.txt19 at the time of this writing.
55 XF86_FBDev should work, in theory. At the time of this writing it is
/linux-2.4.37.9/drivers/char/
Dau1000_usbtty.c107 int writing; /* a packet write is in progress */ member
399 if (port->writing) { in serial_write()
419 port->writing = 1; in serial_write()
573 port->writing = usbdev_get_byte_count(port->in_ep_addr) <= 0 ? 0 : 1; in port_send_complete()
/linux-2.4.37.9/Documentation/powerpc/
Dcpu_features.txt33 that shouldn't be used by writing nop's over it. Using cpufeatures requires
55 __ftr_fixup, and if the required feature is not present it will loop writing
Dsmp.txt10 If you want to help by writing code or testing different hardware please
/linux-2.4.37.9/Documentation/usb/
Dehci.txt22 At this writing, this driver has been seen to work with implementations
52 At this writing the driver should comfortably handle all control, bulk,
57 at this writing no Linux drivers have been using that support.
160 At this writing, individual USB 2.0 devices tend to max out at around
192 In typical situations, a usb_bulk_msg() loop writing out 4 KB chunks is
/linux-2.4.37.9/drivers/scsi/
Dst.h19 int writing; member
DREADME.st23 new tape is loaded into the drive or if writing begins at the
26 QIC-drives). The result is that any tape can be read, writing can be
83 writing and the last operation has been a write. Two filemarks can be
113 Asynchronous writing. Writing the buffer contents to the tape is
221 opens the device for writing if the tape contents will be modified
223 not open for writing for, e.g., erase).
294 MT_ST_TWO_FM writing of two filemarks (global)
340 reading/writing.
Dst.c334 if ((STp->buffer)->writing && in st_sleep_done()
431 STbuffer->buffer_bytes -= STbuffer->writing; in write_behind_check()
437 STps->drv_block += STbuffer->writing / STp->block_size; in write_behind_check()
439 STbuffer->writing = 0; in write_behind_check()
489 if ((STp->buffer)->writing) { in flush_write_buffer()
981 (STp->buffer)->writing = 0; in st_open()
1281 if ((STp->buffer)->writing) { in st_write()
1523 (STp->buffer)->writing = (STp->buffer)->buffer_bytes; in st_write()
1525 residual = (STp->buffer)->writing; in st_write()
1531 SRpnt = st_do_scsi(SRpnt, STp, cmd, (STp->buffer)->writing, in st_write()
[all …]
/linux-2.4.37.9/drivers/char/ftape/zftape/
Dzftape-write.c127 if (ftape_get_status()->fti_state == writing) { in zft_update_header_segments()
202 if (ftape_get_status()->fti_state != writing && !need_flush) { in zft_flush_buffers()
Dzftape-rw.c295 if (ftape_get_status()->fti_state == writing) { in zft_verify_write_segments()
/linux-2.4.37.9/drivers/ide/
Dide-cd.h87 __u8 writing : 1; /* pseudo write in progress */ member
100 __u8 writing : 1; /* the drive is currently writing */ member
/linux-2.4.37.9/Documentation/networking/
Dcomx.txt30 At the moment of writing this document, the (Cisco)-HDLC, LAPB, SyncPPP and
124 jumpers on the board) by writing the kbps value into the file named 'clock'.
134 clock rate (if enabled by jumpers on the small adapter boards) by writing
241 You can enable a debug options by writing its name prepended by a '+' into
/linux-2.4.37.9/Documentation/ia64/
Defirtc.txt40 enables flexibility and permits writing wrapper code is ncase things change.
119 However writing such a program should be hard by simply using those two
DIRQ-redir.txt6 By writing to /proc/irq/IRQ#/smp_affinity the interrupt routing can be
/linux-2.4.37.9/Documentation/
Dkernel-docs.txt126 a practical approach to writing Linux device drivers as kernel
149 abstract: "This article, the third of four on writing character
150 device drivers, introduces concepts of reading, writing, and using
159 writing character device drivers as loadable kernel modules. This
163 writing, and several different facilities have been provided for
196 Description: Introductory 50-minutes (sic) tutorial on writing
229 Description: 68 pages paper on writing character drivers. A little
306 (have data ready to be read or are ready for writing). Ideally you
Dtty.txt19 and writing over an existing ldisc will cause demons to eat your computer.
52 write() - A process is writing data from user space
/linux-2.4.37.9/arch/s390/boot/
Dipldump.S72 # subroutine for writing to tape
/linux-2.4.37.9/arch/s390x/boot/
Dipldump.S72 # subroutine for writing to tape
/linux-2.4.37.9/Documentation/i386/
Dzero-page.txt69 0x228 4 bytes unknown, but writing this in setup.S makes

12345