From owner-freebsd-current@FreeBSD.ORG Sun Apr 7 21:46:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 78602744; Sun, 7 Apr 2013 21:46:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by mx1.freebsd.org (Postfix) with ESMTP id DF4DA1A2; Sun, 7 Apr 2013 21:46:35 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id c10so2018634wiw.1 for ; Sun, 07 Apr 2013 14:46:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NglN/adBiyBq/zBZnhu1933QnidDE3Ouk3JRs1xqfUc=; b=umsA/MIu/yMjbhlwEwSPUbaq7fIe9TuDK/ElZISOtn0/BdLGucmiqFe3y4HCEnUl/E LLaIRhfyMQqlNyg5l1Sq56xFI9M9X68wk9IB2GvD8C6n8EntY2KALUPNvRnMiX4HazyK Bzyxo230xKcAFRoQkG+ui69W7ZfT7HuAlIEWAYR9ju7ipm0U1b8E2pY3s8C99EOwDZ6F yeeyy3crDcBxmcNqdQZdPJNkt1fOi5ED2pHGCn/Su10icvvhpZKjsT87EE05h/S1OPGz biv/gBC2TPQI0i03ev7d4g0OA7Caf612cjDiYXi6/qhnxp8bU/ItpzqmnJXneVVc0+5d rw1A== MIME-Version: 1.0 X-Received: by 10.194.222.3 with SMTP id qi3mr27644920wjc.28.1365371194960; Sun, 07 Apr 2013 14:46:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.121.136 with HTTP; Sun, 7 Apr 2013 14:46:34 -0700 (PDT) In-Reply-To: <5847.1365365701@critter.freebsd.dk> 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> <5847.1365365701@critter.freebsd.dk> Date: Sun, 7 Apr 2013 14:46:34 -0700 X-Google-Sender-Auth: gPkDjBUa-U2v2etu-v2Hkhw_4ko Message-ID: Subject: Re: Intel D2500CC motherboard and strange RS232/UART behavior From: Adrian Chadd To: Poul-Henning Kamp Content-Type: text/plain; charset=ISO-8859-1 Cc: lev@freebsd.org, 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 21:46:36 -0000 On 7 April 2013 13:15, Poul-Henning Kamp wrote: > 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... .. did we really break shared interrupt handling on ISA? > 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. What were the hints? It's possible you can still drop the hint somewhere and it'll get picked up even if acpi is providing the io/irq resources. > Not sure how that that should work in a case like this... God, you made me remember ISA interrupt sharing. I thought the main source of evilness is edge shared interrupts? (Level shared interrupts should be the same no matter what bus they're on..) Adrian