From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: valentin@unimplemented.org
Subject: Re: [PATCH] Fix ACPI halt for certain DSDTs
Date: Wed, 2 Jul 2014 21:56:20 +0400 [thread overview]
Message-ID: <20140702215620.1d67dd4c@opensuse.site> (raw)
In-Reply-To: <3DE0DB36-391C-4CC0-8285-7CFDC56287EC@unimplemented.org>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
В Tue, 1 Jul 2014 01:55:22 +0200
Valentin Dornauer <valentin@unimplemented.org> пишет:
> Hello!
>
> GRUB2 currently seems to be unable to shut down my Fujitsu Lifebook
> E744 laptop using ACPI. After some debugging, I nailed the problem
> down to two problems within GRUB’s ‘acpihalt’ command. Please see
> the attached patch for my solution.
>
See below
> + in skip_ext_op(), correctly parse OpRegionOp (TermArgs aren't always
> + simply strings!); add function to skip TermArgs.
It does not really parse every possible value of Type2Opcode, so commit
message should probably reflect it.
> + case GRUB_ACPI_OPCODE_ADD:
> + case GRUB_ACPI_OPCODE_CONCAT:
> + case GRUB_ACPI_OPCODE_SUBTRACT:
> + case GRUB_ACPI_OPCODE_MULTIPLY:
> ...
Sort by name?
> + if (add == 0)
> + return 0;
You use if (!add) in another places. Let's be consistent :)
> GRUB_ACPI_OPCODE_NAME = 8, GRUB_ACPI_OPCODE_BYTE_CONST = 0x0a,
> + GRUB_ACPI_OPCODE_ALIAS = 0x06,
Looks like list is ordered by opcode value, so it should go between
GRUB_ACPI_OPCODE_NAME and GRUB_ACPI_OPCODE_BYTE_CONST. Same also next hunk.
> + GRUB_ACPI_OPCODE_CONCATRES = 0x80,
In my copy of ACPI spec ConcatRes has opcode 0x84.
Otherwise looks good. Vladimir, is it OK to commit?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-07-02 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 23:55 [PATCH] Fix ACPI halt for certain DSDTs Valentin Dornauer
2014-07-02 17:56 ` Andrey Borzenkov [this message]
2014-07-03 14:00 ` Valentin Dornauer
2014-08-19 22:30 ` Valentin Dornauer
2014-09-21 16:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20140702215620.1d67dd4c@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=valentin@unimplemented.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.