Date: Sun, 13 Feb 2000 19:30:03 -0800 (PST) From: Jin Guojun (FTG staff) <jin@george.lbl.gov> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/16620: 4.0-20000208-CURRENT fails to boot on ASUS P5A-B Message-ID: <200002140330.TAA33662@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/16620; it has been noted by GNATS. From: Jin Guojun (FTG staff) <jin@george.lbl.gov> To: winter@jurai.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: i386/16620: 4.0-20000208-CURRENT fails to boot on ASUS P5A-B Date: Sun, 13 Feb 2000 19:25:47 -0800 (PST) >> Nop. It could be any one of the following ISA driver with port 0x300 >> since device "ep" no longer has no dependent description -- >> at isa? port 0x300 irq 10 >> in its line, so the other devices may be confused. Is there any way >> to resolve this problem without disable all such ISA driver? > >Disabling the other drivers is the correct solution. I believe the >INSTALL procedure makes specific mention of this. > >The final solution will be to convert everything to newbus and to make >resource reservation, assignment and activation more friendly. It should be possible to have the "ep" driver to tell the caller -- bus scanner -- that "ep" uses the port 0x300, so do not scan any further device that has a dependent description -- at isa? port 0x300. Just like it works before. What is the reason to take out "at isa? port 0x300" from the device ep line? Can we still have this information in "device ep" line? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002140330.TAA33662>