Re: Rewriting floppy.c was Re: Free Linux Driver Development!

From: Jan Engelhardt
Date: Wed Jan 31 2007 - 14:25:35 EST



On Jan 31 2007 13:58, Lennart Sorensen wrote:
>On Wed, Jan 31, 2007 at 07:24:54PM +0100, Jan Engelhardt wrote:
>> How much different hardware does the (old)floppy.c do? I imagine that
>> today, where floppies phase out, there will be, in descending order:
>>
>> * USB floppy drives (atm handled by sd.c, could be better to have sf.c)
>> * FDCs on mainboards
>> * 1.44M drives
>> * 1.2M drives
>>
>> Even a working 2.88M, as cool as it sounds, never landed in my hands ever
>> since I've been into computing. Perhaps the oldest, smallest disk I once
>> had was a 360K 5.25", but the B floppy drive to read it was already
>> multi-compliant that read up to 1.2M disks.
>
>So what is wrong with the current floppy driver (other than being 120k
>of code apparently)?

>From my standpoint, nothing. Developers knowing it better might disagree.
(It looks a little ugly, but well, it worked last time I tried.)

>As for floppies that should work, well I imagine on x86 that would have
>to be 360k and 1200k 5-1/4", and 720k, 1200k and 1440k 3-1/2". Would
>perhaps be nice to still support 160, 180 and 320k on the 5-1/4" drive
>too just in case anyone ever wants to read one. Of course some people

Do the special formats (entries 9, 12, 13, 16, 17 in floppy.c)
even cost something more than their line in that struct?

>might also want support for the higher capacity formats on the 1440k

Note that I was able to format a floppy with 1680k [21 spt] once under
Linux (including using it). No other OS (including the BIOS) could do
something with it though, and it had to be accessed explicitly through
/dev/fd0u1680. Maybe also the 1760k [22 spt] one, but can't remember.

With regular "1.44M" disks you get in any store, to be noted.

I'm glad to still have a 5.25" drive buried in a 386 [linux 2.6.13] :=)




Jan
--
ft: http://freshmeat.net/p/chaostables/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/