Date: Tue, 9 Apr 2013 16:58:22 -0400 From: John Baldwin <jhb@freebsd.org> To: lev@freebsd.org Cc: Adrian Chadd <adrian@freebsd.org>, freebsd-current@freebsd.org, Poul-Henning Kamp <phk@phk.freebsd.dk> Subject: Re: Intel D2500CC motherboard and strange RS232/UART behavior Message-ID: <201304091658.22810.jhb@freebsd.org> In-Reply-To: <105818341.20130410004451@serebryakov.spb.ru> References: <229402991.20130407172016@serebryakov.spb.ru> <201304091608.09257.jhb@freebsd.org> <105818341.20130410004451@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, April 09, 2013 4:44:51 pm Lev Serebryakov wrote: > Hello, John. > You wrote 10 =E0=EF=F0=E5=EB=FF 2013 =E3., 0:08:09: >=20 > JB> When did it ever work? > Problem is, that every uart device now is independent from each > other in good "OOP" style, and it looks like interrupt sharing we > need one interrupt handler per irq (not per device), which will now > about several UARTs. Something like "multiport" device, bot not > exactly. No, the interrupt code itself will handle shared interrupts (it will call all handlers). I think in practice that uart is setting INTR_EXCL or some such and/or uart doesn't set RF_SHAREABLE when allocating the IRQ. It is probably the latter. You could try just adding RF_SHAREABLE to the bus_alloc_resource_any() for the IRQ to uart and see if that fixes it. =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304091658.22810.jhb>