Alain Knaff wrote:
Jules Richardson wrote:
(Note that this question is only relevant for well designed clones of the NEC and Intel chips - lots of broken clones don't support FM mode at all...)
Is it possible from user-space to either:
a) put the linux floppy driver permanently into FM recording mode for all subsequent requests, or
Using setfdprm, you can add the "fm" options to instruct the driver that the current disk should be accessed in FM mode.
Example
setfdprm /dev/fd0 sect=9 fm=1
aha - thanks - I'd missed the 'fm' parameter when looking at the source.
Does anyone know if there's documentation anywhere covering how the kernel floppy driver works? I really need to access floppy data at the sector level - in other words, send a true raw command to the FDC chip (command byte plus several bytes of parameters).
It's unclear to me at the moment whether I can actually do this with the standard Linux floppy driver - the 'floppy_raw_cmd' structure holds 16 bytes for the command, but it's not obvious at the moment whether this is actually for a single command byte + parameters, or whether it's just for specifying multiple commands within one command structure.
If it *is* for command byte + parameters, then the 'flags' field seems a little redundant. If it's just for chaining commands, then why also have the 'next' pointer there in the structure? Unfortunately the comments don't say one way or the other!
I've got a horrible feeling I'll need to write my own kernel floppy driver, as the kernel's idea of what a 'raw' command is will turn out to be at a higher level than actually sending raw data to the FDC chip...
cheers
Jules
_______________________________________________ fdutils mailing list fdutils@tux.org http://www.tux.org/mailman/listinfo/fdutils