From owner-freebsd-acpi@FreeBSD.ORG Mon Oct 3 21:53:43 2005 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDD2B16A41F; Mon, 3 Oct 2005 21:53:43 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F91743D46; Mon, 3 Oct 2005 21:53:43 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j93Lrlo5003552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Oct 2005 14:53:48 -0700 Message-ID: <4341A85F.9080204@root.org> Date: Mon, 03 Oct 2005 14:53:35 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20051003203544.GG74917@cell.sick.ru> <200510031750.30674.jhb@FreeBSD.org> In-Reply-To: <200510031750.30674.jhb@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, Gleb Smirnoff Subject: Re: no console with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 21:53:44 -0000 John Baldwin wrote: > On Monday 03 October 2005 04:35 pm, Gleb Smirnoff wrote: > >> John, >> >>regarding no console with ACPI. We have tried your patch from this >>mail: >> >> >>http://lists.freebsd.org/pipermail/freebsd-acpi/2005-September/001941.html >> >>It is strange, but with this patch there is no console with ACPI >>_and without ACPI_, too, unlike before. > > > Grr, now you don't have an isa0 device at all in either case. However, the > device must exist because the legacy0 device didn't add one in the non-ISA > case. The device must not have been attached somehow. Oh, I know what the > problem is. The isa(4) driver only attaches as a child of isab. I've > updated the patch to have the viapm(4) driver also include an isa(4) driver > that attaches as a child of either viapm(4) or viapropm(4). I've updated the > patch at the URL http://www.FreeBSD.org/~jhb/patches/viapm_isab.patch The patch looks good. The right URL is: http://people.freebsd.org/~jhb/patches/via_isab.patch -- Nate