From owner-freebsd-current@FreeBSD.ORG Wed Apr 10 06:30:16 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 18FC1CFB; Wed, 10 Apr 2013 06:30:16 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id D003D75E; Wed, 10 Apr 2013 06:30:15 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:900d:c887:884e:713b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 2EE104AC57; Wed, 10 Apr 2013 10:30:14 +0400 (MSK) Date: Wed, 10 Apr 2013 10:30:10 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1424327083.20130410103010@serebryakov.spb.ru> To: "Poul-Henning Kamp" Subject: Re: Intel D2500CC motherboard and strange RS232/UART behavior In-Reply-To: <54189.1365540724@critter.freebsd.dk> References: <229402991.20130407172016@serebryakov.spb.ru> <5847.1365365701@critter.freebsd.dk> <201304091608.09257.jhb@freebsd.org> <105818341.20130410004451@serebryakov.spb.ru> <54189.1365540724@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Adrian Chadd , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2013 06:30:16 -0000 Hello, Poul-Henning. You wrote 10 =E0=EF=F0=E5=EB=FF 2013 =E3., 0:52:04: >> 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. PHK> That is what the puc(4) driver does... Yes, for PCI devices only :( --=20 // Black Lion AKA Lev Serebryakov