Lines Matching defs:implemented
138 implemented the \cdrom\ $ioctl()$ calls through their own routines. This
161 The routines for the \UCD\ interface level are implemented in the file
185 declared above are all implemented in \cdromc, since this file is the
195 (VFS) any more. The interface implemented in \cdromc\ is carried out
222 of pointers to the functions which are implemented in the low-level
258 function is not implemented, however, this $struct$ should contain a
338 following sections. Two functions {\em must\/} be implemented, namely
372 The function $drive_status$, if implemented, should provide
399 This function, if implemented, should control the tray movement. (No
494 implemented by the routines described above, and hence the function
575 driver has implemented the code for loading and ejecting \cdrom's, and
611 new $ioctl$s implemented in \cdromc, that allow you to control the
633 are implemented entirely through $ioctl$s, presumably because the
662 implemented (some drivers implement checking for write-related flags,
792 function becomes active. A strategy is implemented in this routine,
812 categories: $ioctl$s that can be directly implemented by device
817 \subsubsection{Directly implemented $ioctl$s}
820 The following `old' \cdrom-$ioctl$s are implemented by directly
821 calling device-operations in $cdrom_device_ops$, if implemented and
836 The following set of $ioctl$s are all implemented through a call to
900 implemented in the low level drivers, but is now carried out
951 if implemented. No memory allocation or verification is carried out.
978 in section~\ref{cdrom.c}. Most likely you have already implemented