From owner-freebsd-current@FreeBSD.ORG Tue Apr 9 20:58:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 757AF198; Tue, 9 Apr 2013 20:58:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 50F06DC6; Tue, 9 Apr 2013 20:58:30 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8959FB941; Tue, 9 Apr 2013 16:58:29 -0400 (EDT) From: John Baldwin To: lev@freebsd.org Subject: Re: Intel D2500CC motherboard and strange RS232/UART behavior Date: Tue, 9 Apr 2013 16:58:22 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <229402991.20130407172016@serebryakov.spb.ru> <201304091608.09257.jhb@freebsd.org> <105818341.20130410004451@serebryakov.spb.ru> In-Reply-To: <105818341.20130410004451@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201304091658.22810.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 09 Apr 2013 16:58:29 -0400 (EDT) Cc: Adrian Chadd , freebsd-current@freebsd.org, Poul-Henning Kamp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2013 20:58:30 -0000 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