Date: Wed, 10 Dec 2008 17:00:24 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: Boris Samorodov <bsam@ipt.ru> Cc: freebsd-current@FreeBSD.org, rea-fbsd@codelabs.ru Subject: Re: Timeda 8-multiport adapter: only 2 ports available Message-ID: <19F75E66-0535-4982-9726-E2C0A03117EA@mac.com> In-Reply-To: <26719629@bb.ipt.ru> References: <92804393@bb.ipt.ru> <26722819@bb.ipt.ru> <dgryeQY4GEVsW/%2Bo7hiHda0rsyw@Nv45r0f9gWT8HCu35qu0Xm2Zg98> <26719629@bb.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 10, 2008, at 4:02 PM, Boris Samorodov wrote: > Seems that just the same card should work: > http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042505.html > > I've added some diagnistic. But 'rid' is not what you want, I guess: The RID is fine. It should always be 0. * > uart4: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: no errors, exiting * > uart4: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: no errors, exiting * > uart5: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: no errors, exiting * > uart5: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: no errors, exiting * > uart6: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: got MCR wrong register, exiting with ENXIO * > uart6: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: got MCR wrong register, exiting with ENXIO * > uart6: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: got MCR wrong register, exiting with ENXIO * > uart6: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: got MCR wrong register, exiting with ENXIO * > uart6: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: got MCR wrong register, exiting with ENXIO * > uart6: /usr/src/sys/dev/uart/uart_core.c:374: continue with rid=0x0 > ns8250_probe: got MCR wrong register, exiting with ENXIO It looks like the mapping is wrong. That is, uart(4) gets to probe 8 ports but rejects 6. I would add debugging information to puc(4) and in particular to where resources are assigned to ports so that we can see what the BAR and offsets within the BAR are for each port. FYI, -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19F75E66-0535-4982-9726-E2C0A03117EA>