From owner-freebsd-current@FreeBSD.ORG Sun Apr 7 20:15:02 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 DDE9E6F7; Sun, 7 Apr 2013 20:15:02 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id A50CCE38; Sun, 7 Apr 2013 20:15:02 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 967C389FBE; Sun, 7 Apr 2013 20:15:01 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.6/8.14.6) with ESMTP id r37KF1mf005848; Sun, 7 Apr 2013 20:15:01 GMT (envelope-from phk@phk.freebsd.dk) To: lev@FreeBSD.org Subject: Re: Intel D2500CC motherboard and strange RS232/UART behavior In-reply-to: <1428566376.20130407234355@serebryakov.spb.ru> From: "Poul-Henning Kamp" References: <229402991.20130407172016@serebryakov.spb.ru> <2866.1365348969@critter.freebsd.dk> <454119968.20130407211356@serebryakov.spb.ru> <5068.1365356114@critter.freebsd.dk> <962552272.20130407232944@serebryakov.spb.ru> <5698.1365363110@critter.freebsd.dk> <1428566376.20130407234355@serebryakov.spb.ru> Content-Type: text/plain; charset=ISO-8859-1 Date: Sun, 07 Apr 2013 20:15:01 +0000 Message-ID: <5847.1365365701@critter.freebsd.dk> Cc: Adrian Chadd , freebsd-current@freebsd.org 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: Sun, 07 Apr 2013 20:15:02 -0000 In message <1428566376.20130407234355@serebryakov.spb.ru>, Lev Serebryakov writ es: >It doesn't look so. And uart1 and uart3 doesn't have interrupt >according to `vmstat -i' (but share irq4 according to boot messages). Ohh, there you go... Interrupt sharing on ISA requires special magic... With sio(4) one could hardcode interrupt sharing with hints.flags, but with uart(4) I think you have to go through puc(4) to do it. Not sure how that that should work in a case like this... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.