From owner-freebsd-current@FreeBSD.ORG Tue Apr 4 02:30:13 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7899616A400 for ; Tue, 4 Apr 2006 02:30:13 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF1A043D48 for ; Tue, 4 Apr 2006 02:30:12 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k342U6bJ012482 for ; Mon, 3 Apr 2006 22:30:06 -0400 X-ORBL: [71.139.14.61] Received: from [10.0.5.51] (ppp-71-139-14-61.dsl.snfc21.pacbell.net [71.139.14.61]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k342U6Pp110708; Mon, 3 Apr 2006 22:30:06 -0400 Message-ID: <4431DA08.3020002@root.org> Date: Mon, 03 Apr 2006 19:29:28 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "Angka H. K." References: <4c40c4e70604030346g3305dc9bo580413026c33e148@mail.gmail.com> <20060403151534.eqdmhc6f404o4co0@netchild.homeip.net> <4c40c4e70604030716k429d263ek29e8b8edf31be664@mail.gmail.com> In-Reply-To: <4c40c4e70604030716k429d263ek29e8b8edf31be664@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , current@freebsd.org Subject: Re: My snd_ich working well X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2006 02:30:13 -0000 Angka H. K. wrote: > Thanks for the replay > I am updating my source now and planing to rebuild it again, but I don't see > any changes on ACPI code. > > I was mistype on the val that return by kernel, the error should be "acpi: > bad write to port 0x073(8) val 20", I am sorry. > Hope it'll be fixed soon. Ok, I fixed the range check on ports so 0x73 should not trigger it. If you have some other write to a port that IS in the blacklist, you'll still get the warning. Ultimately, I intend to emulate what Windows does which is block all writes to the PIC, and block all writes on XP or newer BIOSen. -- Nate