Date: Sun, 07 Apr 2013 20:15:01 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: lev@FreeBSD.org Cc: Adrian Chadd <adrian@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Intel D2500CC motherboard and strange RS232/UART behavior Message-ID: <5847.1365365701@critter.freebsd.dk> In-Reply-To: <1428566376.20130407234355@serebryakov.spb.ru> References: <229402991.20130407172016@serebryakov.spb.ru> <2866.1365348969@critter.freebsd.dk> <454119968.20130407211356@serebryakov.spb.ru> <5068.1365356114@critter.freebsd.dk> <CAJ-VmonoeKeY3vQGXghvBJdbBEDJJZVbqW6F=KQfNBnNHBP9vA@mail.gmail.com> <962552272.20130407232944@serebryakov.spb.ru> <5698.1365363110@critter.freebsd.dk> <1428566376.20130407234355@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5847.1365365701>