ACPI vs. /dev/fd0

[Terry Lambert]

Terry Lambert wrote:
> Jeff Walters wrote:
> > I cannot load the ACPI module in 5.0-current and get a working floppy drive
> > simultaneously.  With ACPI loaded the dmesg | grep fdc0 is:
> >
> > fdc0: cmd 3 failed at out byte 1 of 3
> > fdc0: cmd 3 failed at out byte 1 of 3
> > fdc0: cannot reserve I/O port range (6 ports)
> >
> > With the ACPI module disabled in /boot/loader.conf, I get:
> >
> > fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port
> > 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
> > fdc0: FIFO enabled, 8 bytes threshold
> > fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> 
> Probably it needs to be explicitly enabled, having been disabled
> by default.  Is this an external/drive-swap-bay floppy?

More comments: it's probably worth checking the status on each
open request, and enabling it if it's currently disabled, and
checking the status to make sure it did it.  A lot of ACPI
assumes that the OS will take over responsibility for power
management and things like that.  I've seen more than one ACPI
setup that powered down things under it's control.  This may
mean that there needs to be a power management layer integrated
into the device management subsystems in FreeBSD, at some point.

-- Terry