From owner-freebsd-bugs@FreeBSD.ORG Thu Oct 5 16:51:06 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27C5616A412 for ; Thu, 5 Oct 2006 16:51:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9A0643E1B for ; Thu, 5 Oct 2006 16:50:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k95GoPva078458 for ; Thu, 5 Oct 2006 16:50:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k95GoPiT078457; Thu, 5 Oct 2006 16:50:25 GMT (envelope-from gnats) Date: Thu, 5 Oct 2006 16:50:25 GMT Message-Id: <200610051650.k95GoPiT078457@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Eugene Grosbein Cc: Subject: Re: kern/103841: [fdc] fdc(4) does not work (regression) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Grosbein List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 16:51:06 -0000 The following reply was made to PR kern/103841; it has been noted by GNATS. From: Eugene Grosbein To: Robert Watson Cc: FreeBSD Stable , bug-followup@freebsd.org Subject: Re: kern/103841: [fdc] fdc(4) does not work (regression) Date: Fri, 6 Oct 2006 00:48:21 +0800 On Thu, Oct 05, 2006 at 10:48:52PM +0800, Eugene Grosbein wrote: > > >It's definetely a regression from 4.11-STABLE that runs fine on this > > >system with ACPI fully enabled > > Hmm, I was wrong about 4.11 using ACPI - it does not use it here really, > it uses "good old" APM. > > > It would be interesting to know how 4.x probes the hardware vs. how it > > apperas in the 6.x dmesg. > > 4.11-STABLE: > > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > 6.2-PRERELEASE: > > fdc0: port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 I managed to know that fdc_initial_reset() in sys/dev/fdc/fdc.c probes my fdc controller as "Enhanced floppy controller" (ic_type==0x90) vs. 4.x's "NEC close". BTW, does in possible to obtain fdc's probe result vs. fdc_acpi's result without addition of call to "fdc_print_child(device_get_parent(dev), dev);" to fdc_initial_reset()? I've forced sys/dev/fdc/fdc.c to probe my controller as "NEC clone" by moving "case 0x90:" upwards to "case 0x80" in this function but that does not help, no change in behavour was observed. Eugene Grosbein