From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 23 22:42:29 2006 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 871E316A41F; Mon, 23 Jan 2006 22:42:29 +0000 (GMT) (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 F2AB644330; Mon, 23 Jan 2006 22:42:28 +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 k0NMgOeY006232; Mon, 23 Jan 2006 17:42:25 -0500 X-ORBL: [71.139.110.185] Received: from [10.0.0.115] (ppp-71-139-110-185.dsl.snfc21.pacbell.net [71.139.110.185]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k0NMgPn5150756; Mon, 23 Jan 2006 17:42:26 -0500 Message-ID: <43D55BE6.3000407@root.org> Date: Mon, 23 Jan 2006 14:42:46 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: JoaoBR References: <200601201851.26858.joao@matik.com.br> <200601231909.02998.joao@matik.com.br> <43D54F28.8080205@root.org> <200601232038.44907.joao@matik.com.br> In-Reply-To: <200601232038.44907.joao@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: need help for DSDT for an Epox Amd64 MB 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, 23 Jan 2006 22:42:29 -0000 JoaoBR wrote: > On Monday 23 January 2006 19:48, Nate Lawson wrote: > >>>well, would you mind saying which one exactly you think of for removing? >> >>Thinking of removing debug.acpi.disabled since it is mostly redundant >>with the hint approach. But more investigation should be done before >>claiming that. > > > ok, means that all acpi subdrivers can not be disabled any more in boot.loader > and would be switched as hints on or off, right > > is this already possible, I mean disabling the acpi subsets as hints? > > let me ask what would be the advantage of using hints instead? Any timeline > for this or just a thought at this time? > grep resource_disabled /sys/dev/acpica/*.c /sys/dev/acpica/acpi.c: if (resource_disabled("acpi", 0)) /sys/dev/acpica/acpi_perf.c: if (resource_disabled("acpi_perf", 0)) /sys/dev/acpica/acpi_throttle.c: if (resource_disabled("acpi_throttle", 0)) > grep acpi_disabled /sys/dev/acpica/*.c /sys/dev/acpica/acpi.c: if (!acpi_disabled("bus")) /sys/dev/acpica/acpi.c: if (acpi_disabled("children")) /sys/dev/acpica/acpi.c: if (acpi_disabled("children")) /sys/dev/acpica/acpi.c:acpi_disabled(char *subsys) /sys/dev/acpica/acpi_acad.c: if (acpi_disabled("acad") || /sys/dev/acpica/acpi_button.c: if (acpi_disabled("button") || /sys/dev/acpica/acpi_cmbat.c: if (acpi_disabled("cmbat") || /sys/dev/acpica/acpi_cpu.c: if (acpi_disabled("cpu") || acpi_get_type(dev) != ACPI_TYPE_PROCESSOR) /sys/dev/acpica/acpi_ec.c: if (acpi_get_type(dev) != ACPI_TYPE_DEVICE || acpi_disabled("ec")) /sys/dev/acpica/acpi_hpet.c: if (acpi_disabled("hpet") || /sys/dev/acpica/acpi_isab.c: if (acpi_disabled("isab") || /sys/dev/acpica/acpi_lid.c: if (acpi_disabled("lid") || /sys/dev/acpica/acpi_pci_link.c: if (acpi_disabled("pci_link") || /sys/dev/acpica/acpi_pcib_acpi.c: if (acpi_disabled("pcib") || /sys/dev/acpica/acpi_pcib_pci.c: acpi_disabled("pci")) /sys/dev/acpica/acpi_resource.c: if (acpi_disabled("sysresource") || /sys/dev/acpica/acpi_smbat.c: if (acpi_disabled("smbat") || /sys/dev/acpica/acpi_thermal.c: if (acpi_get_type(dev) == ACPI_TYPE_THERMAL && !acpi_disabled("thermal")) { /sys/dev/acpica/acpi_timer.c: if (acpi_disabled("timer") || (acpi_quirks & ACPI_Q_TIMER) || /sys/dev/acpica/acpi_video.c: if (acpi_disabled("video") || So it looks like debug.acpi.disabled=thermal is the only way to do it for now. We may want to move to resource_disabled later, but that's for future discusion. -- Nate