From owner-freebsd-current@FreeBSD.ORG Tue Sep 21 12:42:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A078C16A4CE for ; Tue, 21 Sep 2004 12:42:39 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF0C643D45 for ; Tue, 21 Sep 2004 12:42:38 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i8LCgce1008361; Tue, 21 Sep 2004 14:42:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Rostislav Krasny From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 21 Sep 2004 05:23:54 PDT." <20040921122354.73480.qmail@web14827.mail.yahoo.com> Date: Tue, 21 Sep 2004 14:42:38 +0200 Message-ID: <8360.1095770558@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: new fdc(4) and new fdcontrol(8) behavior (5.3-BETA5) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 12:42:39 -0000 In message <20040921122354.73480.qmail@web14827.mail.yahoo.com>, Rostislav Kras ny writes: >dmesg fragment from 5.3-BETA5 (verbose): > >fdc0: ic_type 90 part_id 80 >fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on >isa0 >Why the 3F7h port isn't used by new fdc(4) on my system? Is it a >hardware detection bug? Warner is working on this issue. > >2. fdcontrol cannot access /dev/fd0 when there is no diskette inserted > >When no diskette is inserted then running 'fdcontrol [anyflag] >/dev/fd0' produce following error message: > >fdcontrol: open(/dev/fd0): Device not configured We don't have a specific errno for "No media in drive". It would have been nice, but defining errno's is a tricky business. >What is inspected behavior of fdcontrol(8) in 5.3-BETA5? Isn't its >current behavior buggy? Is it concerned with 3F7h port that is not used >on my system by the new fdc(4) driver? The 0x3f7 is a bug, and as I said Warner is working on that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.