Date: Wed, 12 Jul 2006 09:14:51 -0600 From: Scott Long <scottl@samsco.org> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Jung-uk Kim <jkim@FreeBSD.org> Subject: Re: cvs commit: src/sys/dev/fdc fdc.c Message-ID: <44B511EB.3060304@samsco.org> In-Reply-To: <44B48F0E.1050704@FreeBSD.org> References: <200607120049.k6C0nlHN034350@repoman.freebsd.org> <200607112059.39655.jkim@FreeBSD.org> <44B48F0E.1050704@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev wrote: > Jung-uk Kim wrote: > >> On Tuesday 11 July 2006 08:49 pm, Jung-uk Kim wrote: >> >>> jkim 2006-07-12 00:49:47 UTC >>> >>> FreeBSD src repository >>> >>> Modified files: >>> sys/dev/fdc fdc.c >>> Log: >>> Assume floppy disk is not inserted when we have exhausted >>> retries. This significantly reduces booting time when there is >>> broken floppy disk drive, controller, cable, BIOS, etc. >>> When the floppy controller interface is correctly implemented, >>> disk change signal (DSKCHG) is reflected in the Digital Input >>> Register (DIR) at 0x3f7. However, there are many cases that the >>> signal is unusable. Moreover, some BIOS does not reserve the port >>> at all. In those cases, the register may not function. >>> >>> Revision Changes Path >>> 1.311 +3 -0 src/sys/dev/fdc/fdc.c >> >> >> Linux device driver seems to have 'broken_dcl' boot time option to >> work around this issue, i.e., assuming disk change for every floppy >> disk access, which is quite ugly, IMHO. Does anybody have better idea >> to fix these cases? > > > Not really relevant, but who cares about floppy in 2006 when one can buy > 256MB USB flash for the price of the pack of floppies? ;-) > > No offense intended, just curious. > > -Maxim Who cares about ATA in 2006 when one can buy a really good SAS RAID controller? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44B511EB.3060304>