From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg KH <greg@kroah.com>,
kernelnewbies <Kernelnewbies@kernelnewbies.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
Date: Sun, 5 Jul 2020 09:47:59 +0800 [thread overview]
Message-ID: <CAAvDm6ZYh7wirQx4QQb13js5VOcK8BcHu_0e1zAQyO+Y2xrk9g@mail.gmail.com> (raw)
In-Reply-To: <20200704200923.GB24405@amd>
I see. Thank you .
Pavel Machek <pavel@ucw.cz> 于2020年7月5日周日 上午4:09写道:
>
> On Sat 2020-07-04 21:34:36, 孙世龙 sunshilong wrote:
> > Thank you for taking the time to respond to me.
> >
> > >These machines are still mostly IBM-PC compatible, so it is likely to
> > >somehow work. You'll likely get worse power and thermal
> > >management. Try it.
> > It's an industrial personal computer with an Intel processor.
> > What I am worried about is that it may damage the hardware.
>
> I'd simply try it. Risk is really quite low...
>
> If in doubt, you could ask vendor.
>
> But you will not get definitive answers on the mailing list...
>
> Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2020-07-05 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 9:15 Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform? 孙世龙 sunshilong
2020-07-01 10:58 ` Greg KH
[not found] ` <CAAvDm6YjbvEq9Y3wG-Lx_-hJtQ_LW28j97BOqvrewYXnEAS2dg@mail.gmail.com>
2020-07-01 12:28 ` 孙世龙 sunshilong
2020-07-19 4:38 ` 孙世龙 sunshilong
2020-07-04 12:22 ` Pavel Machek
2020-07-04 13:34 ` 孙世龙 sunshilong
2020-07-04 20:09 ` Pavel Machek
2020-07-05 1:47 ` 孙世龙 sunshilong [this message]
2020-07-19 5:03 ` 孙世龙 sunshilong
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=CAAvDm6ZYh7wirQx4QQb13js5VOcK8BcHu_0e1zAQyO+Y2xrk9g@mail.gmail.com \
--to=sunshilong369@gmail.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).