Date: Wed, 12 Jul 2006 07:58:42 -0700 From: othermark <atkin901@yahoo.com> To: freebsd-acpi@freebsd.org Subject: Re: sio0 wiring to a resource patch Message-ID: <e932is$6lj$1@sea.gmane.org> In-Reply-To: <20060711.150742.1649768833.imp@bsdimp.com> References: <20060711.005639.-233674225.imp@bsdimp.com> <e90md5$q6f$1@sea.gmane.org> <20060711.150742.1649768833.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote: > In message: <e90md5$q6f$1@sea.gmane.org> > othermark <atkin901@yahoo.com> writes: > : M. Warner Losh wrote: > : > : > Please find enclosed an experimental patch. It does two things. > : [...] > : > Anyway, please test these patches out and let me know if you have > : > problems. > : > > : > Warner > > Doh! I forgot to include that in my patch. My mistake. Comes from > doing too many things in that branch. > > http://people.freebsd.org/~imp/wire-unit.diff > > Basically, delete the sio_pci_kludge_unit function, remove its > declaration and the one place it calls it. That URL/page gives a 404, so I deleted sio_pci_kludge_unit function, declaration and it's call in sio_pci.c and compiled and installed a new kernel. I then removed the DSDT.aml and loader.conf files for the machine and rebooted. sio0 and sio1 were still backwards and device.hints in boot wasn't overruling the acpi info. When the machine boots up, I know that device.hints was loaded correctly from kenv, although sio0 was wired to 0x2f8 irq 3 hint.sio.0.at="isa" hint.sio.0.flags="0x10" hint.sio.0.irq="4" hint.sio.0.port="0x3F8" hint.sio.1.at="isa" hint.sio.1.irq="3" hint.sio.1.port="0x2F8" hint.sio.2.at="isa" hint.sio.2.disabled="1" hint.sio.2.irq="5" hint.sio.2.port="0x3E8" hint.sio.3.at="isa" hint.sio.3.disabled="1" hint.sio.3.irq="9" hint.sio.3.port="0x2E8" sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FAST] sio1: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A sio1: [FAST] In short, not working on this machine at least... Let me know what other information I can provide. -Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e932is$6lj$1>