From: "Nick Bartos" <spam99-1EIjRwF9Gc5s5w19saIqfg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi=force safe?
Date: Fri, 6 Feb 2004 06:54:36 -0600 (CST) [thread overview]
Message-ID: <41685.65.28.18.238.1076072076.squirrel@mail.diamondcpu.com> (raw)
In-Reply-To: <20040206064023.2a80a4dd.ak-l3A5Bk7waGM@public.gmane.org>
So if I have a /proc/acpi dir then it is safe? What is the worst that
could happen if the acpi is broken in the board and I force it? Just
courious, what if I forced it for a really old board that didn't have acpi
at all and thus technically couldn't work anyway (I wouldn't do that but I
do wonder)? Would the acpi files in proc still exist or not?
> On Thu, 5 Feb 2004 23:14:15 -0600 (CST)
> "Nick Bartos" <spam99-1EIjRwF9Gc5s5w19saIqfg@public.gmane.org> wrote:
>
>> I can do acpi=force, but I worry about causing stability issues.
>
> If the machine works with that it is safe. However many older boards
> have broken ACPI, that is why it is disabled by default for older boards.
>
> -Andi
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-06 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 5:14 acpi=force safe? Nick Bartos
[not found] ` <40678.65.28.18.238.1076044455.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 5:40 ` Andi Kleen
[not found] ` <20040206064023.2a80a4dd.ak-l3A5Bk7waGM@public.gmane.org>
2004-02-06 12:54 ` Nick Bartos [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 16:17 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB685-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org >
2004-02-06 17:16 ` Nick Bartos
[not found] ` <16644.65.164.3.3.1076087775.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 21:13 ` Bruno Ducrot
[not found] ` <20040206211334.GH13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-06 21:49 ` Nick Bartos
[not found] ` <40747.65.164.3.3.1076104152.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-07 3:31 ` Bruno Ducrot
2004-02-06 22:46 ` Nick Bartos
[not found] ` <24294.65.164.3.3.1076107609.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 23:06 ` Bruno Ducrot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41685.65.28.18.238.1076072076.squirrel@mail.diamondcpu.com \
--to=spam99-1eijrwf9gc5s5w19saiqfg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox