Lines Matching full:drive
30 devices; the way a particular drive reacts to a `standard` *ioctl()*
44 When the CD-ROM was developed, the interface between the CD-ROM drive
52 most of the `NoName` manufacturers). In cases where a new drive really
65 capabilities of a particular drive, in an *ad hoc* manner. More
86 layer that sits on top of the low-level device drivers for each CD-ROM drive.
105 more than one CD-ROM drive, possibly of mixed types. It is important
108 drive. In the months that I was busy writing a Linux driver for it,
112 16 speed CD-ROM drive, and 24 speed drives are common.
127 CD-ROM drive behavior, and to provide a common set of services to the various
186 This structure contains information about a particular CD-ROM drive,
190 Registering a particular CD-ROM drive with the Uniform CD-ROM Driver
236 CD-ROM hardware and/or low-level CD-ROM driver when a CD-ROM drive
248 The drive-specific, minor-like information that is registered with
281 struct and specifications of properties of the drive are stored in this
285 in *ops->capability*, if a specific drive doesn't support a feature
287 drive, measured in units of normal audio speed (176kB/sec raw data or
289 because they describe properties of the drive, which don't change after
292 A few registers contain variables local to the CD-ROM drive. The
299 data that is specific to a minor drive, can be accessed through *handle*,
355 information on the status of the drive (not the status of the disc,
356 which may or may not be in the drive). If the drive is not a changer,
386 drive allows this. The value of *lock* controls the desired locking
401 are several reasons for changing the speed of a CD-ROM drive. Badly
411 drive, measured in units of standard cdrom speed (176kB/sec raw data
412 or 150kB/sec file system data). So to request that a CD-ROM drive
415 maximum data-rate or real-time audio rate. If the drive doesn't have
454 This call should perform a hard-reset on the drive (although in
455 circumstances that a hard-reset is necessary, a drive may very well not
457 caller only after the drive has finished resetting. If the drive is no
531 of a CD-ROM drive. This can be done by ORing any number of
539 CDC_SELECT_DISC /* drive is juke-box */
546 CDC_DRIVE_STATUS /* driver implements drive status */
550 inform `cdrom.c` of what the driver can do. If the drive found
555 CD-ROM drive might be a caddy system, which can't load the tray, and
556 hence for this drive the *cdrom_device_info* struct will have set
573 have made the drive's support available to the Linux community. The
611 *ioctl* commands, regardless of the state the drive is in.
613 On the other hand, when used as a removable-media disc drive (what the
615 disc drive is ready for operation upon opening the device. In the old
618 attempt for mounting a CD-ROM on an empty drive occurs. This is not a
621 drive for a couple of seconds, after which the system complains it
623 removable medium in a drive, and we believe we should exploit that
628 These two ways of using a CD-ROM drive, principally for data and
655 successful, unless the whole device doesn't exist. The drive will take
707 it is verified that a disc is in the drive and, if *CDO_CHECK_TYPE* is
710 system corruption. If the drive is opened for audio (*O_NONBLOCK* is
887 drive found in the *cdrom_dops*.
911 Returns the status of the drive by a call to
914 current playing activity of the drive; this can be polled through
920 Returns the type of the disc currently in the drive.
923 disc that is inserted in the drive. This functionality used to be
962 Reset the drive.
964 Returns the *capability* flags for the drive. Refer to section
967 Locks the door of the drive. `arg == 0` unlocks the door,
987 - Change the 3rd argument of *register_blkdev* from `&<your-drive>_fops`
992 register_cdrom(&<your-drive>_info);*