John Bradford wrote:
>>>Of bigger concern is that the inter-block gap is only 0.5 (or maybe 0.75
>>>inches, the memories are dim ;) - and you need to be able to stop and then get
>>>back up to speed in that distance (or decelerate, rewind, and get a running
>>>start).
>>>
>>
>>No, you don't. You just need to make sure you don't have the head
>>active while you overshoot. Performance will *definitely* suffer if
>>you don't, though, since you'd have to rewind.
>
>
> Well, we could make our device dual speed, and either run at E.G. 60
> I.P.S. or 120 I.P.S. depending on whether we want to read a large
> block of data, or just one block that happens to be closer to the
> current head position than the distance we need to accellerate to 120
> I.P.S.
>
Actually, as long as you get enough read speed across the head and can
actually measure the real speed you can presumably vary the speed
arbitrarily, all the way up to the breaking point of the medium.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Apr 30 2003 - 22:00:22 EST