Searched refs:verifying (Results 1 – 8 of 8) sorted by relevance
211 if (ft_driver_state != verifying) { in ftape_verify_segment()219 ftape_set_state(verifying); in ftape_verify_segment()260 if (!verify_done && tail->status == verifying) { in ftape_verify_segment()262 switch(ftape_wait_segment(verifying)) { in ftape_verify_segment()272 ftape_set_state(verifying); in ftape_verify_segment()283 ftape_set_state(verifying); in ftape_verify_segment()291 head->status == verifying) { in ftape_verify_segment()336 head->status = verifying; in ftape_verify_segment()
467 buff->status != verifying)))) { in continue_xfer()551 case verifying: buff->status = verifying; break; in continue_xfer()758 if (fmode == fdc_reading_data && ft_driver_state == verifying) { in handle_fdc_busy()
134 verifying, enumerator
203 (ft_driver_state == reading || ft_driver_state == verifying) in ftape_setup_new_segment()
183 At this point the devices should be recognized. There are two ways of verifying
251 because it has no way of verifying whether a given feature is valid
53 drive; I use it for verifying self-written CDs this way).
37 - (nearly) no retries on "no data errors" when verifying after