Date: Sun, 26 Sep 2004 09:23:04 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: rosti_bsd@yahoo.com Cc: freebsd-current@freebsd.org Subject: Re: new fdc(4) and new fdcontrol(8) behavior (5.3-BETA5) Message-ID: <20040926.092304.127427023.imp@bsdimp.com> In-Reply-To: <20040926143209.44197.qmail@web14828.mail.yahoo.com> References: <20040921.143546.63053469.imp@bsdimp.com> <20040926143209.44197.qmail@web14828.mail.yahoo.com>
index | next in thread | previous in thread | raw e-mail
In message: <20040926143209.44197.qmail@web14828.mail.yahoo.com>
Rostislav Krasny <rosti_bsd@yahoo.com> writes:
: --- "M. Warner Losh" <imp@bsdimp.com> wrote:
: > In message: <20040921122354.73480.qmail@web14827.mail.yahoo.com>
: > Rostislav Krasny <rosti_bsd@yahoo.com> writes:
: > : Why the 3F7h port isn't used by new fdc(4) on my system? Is it a
: > : hardware detection bug?
: >
: > It is a minor, hardware detection bug. Your bios doesn't list it as a
: > resource, but should. We do use it, but we don't allocate it with the
: > bus system, which is why it doesn't appear in dmesg. A
: > mostly-harmless cosmetic issue.
:
: How the 0x3f7 port could be used without allocation? My BIOS doesn't list
: 0x3f0-0x3f1 ports as resurces of the PNP0700 device too, but fdc(4) use them
: anyhow:
:
: PNP0700: adding dma mask 0x4
: PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0
: PNP0700: adding irq mask 0x40
: pnpbios: handle 12 device ID PNP0700 (0007d041)
:
: # devinfo -uv | grep -e "0x37[0-5,7]" -e "0x3f[0-5,7]"
: 0x300-0x375 (root0)
: 0x377 (root0)
: 0x3f0-0x3f5 (fdc0)
: 0x3f7 (root0)
Interesting.... Can you send me a full verbose boot? That is, the
dmesg from boot -v?
Warner
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040926.092304.127427023.imp>