From owner-cvs-src@FreeBSD.ORG Wed Jul 12 06:21:45 2006 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BC4216A4E6 for ; Wed, 12 Jul 2006 06:21:45 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0829D43D5D for ; Wed, 12 Jul 2006 06:21:41 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id o37so5960nzf for ; Tue, 11 Jul 2006 23:21:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=Ju7Cf1Erp/VzWKbJsQlS1XJamOQ2515dGCHvHB7BppPfo2ePB2srnfwcMciWEVr1eXO+ims/T12h+j9JQ99vibSSogwqch4TyF5MH8vCpGYDt+BakqM853JQlrlncoJcyPKOhlEOUQzN6rd3NcfQ/3gnNrC0qJQ9uuaHixSmSSo= Received: by 10.36.12.12 with SMTP id 12mr394716nzl; Tue, 11 Jul 2006 23:21:41 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 8sm679130nzn.2006.07.11.23.21.38; Tue, 11 Jul 2006 23:21:41 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k6C6M3Md011244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jul 2006 15:22:03 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k6C6M3ZI011243; Wed, 12 Jul 2006 15:22:03 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 12 Jul 2006 15:22:03 +0900 From: Pyun YongHyeon To: Maxim Sobolev Message-ID: <20060712062203.GC9542@cdnetworks.co.kr> References: <200607120049.k6C0nlHN034350@repoman.freebsd.org> <200607112059.39655.jkim@FreeBSD.org> <44B48F0E.1050704@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B48F0E.1050704@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Jung-uk Kim Subject: Re: cvs commit: src/sys/dev/fdc fdc.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 06:21:45 -0000 On Tue, Jul 11, 2006 at 10:56:30PM -0700, 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. > I think it's very valuable boot device for sparc64 and really like to add fdc(4) for sparc64. The fdc(4) patch I wrote basically worked but dd(1) performance on Ebus based ultrasparcs was poor when a single block(512bytes) is used. The same issue was observed on some old i386 machine too but the root cause is not yet known. -- Regards, Pyun YongHyeon