From: Uros Vampl <mobile.leecher@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Don Zickus <dzickus@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Peter Chubb <peter.chubb@nicta.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Aspire One Happy2 reboots only with the kbd method
Date: Fri, 22 Jun 2012 00:22:28 +0200 [thread overview]
Message-ID: <20120621222228.GA27593@zverina> (raw)
In-Reply-To: <4FE33278.20807@zytor.com>
On 21.06.12 07:40, H. Peter Anvin wrote:
> On 06/21/2012 07:29 AM, Don Zickus wrote:
> > On Thu, Jun 21, 2012 at 03:32:03PM +0200, Uros Vampl wrote:
> >> Add a quirk to make the Acer Aspire One Happy2 reboot properly. For
> >> reference, discussion at the Arch forums:
> >> https://bbs.archlinux.org/viewtopic.php?id=143716
> >>
> >> Signed-off-by: Uroš Vampl <mobile.leecher@gmail.com>
> >
> > Seems fine by me based on the thread above. Not sure if there is another
> > callback that should be tried first before using BOOT_KBD. Probably
> > doesn't matter.
> >
>
> Actually please do the following:
>
> a) please use "acpidump" (from the pmtools package) to dump the ACPI
> tables, specifically the FACP table;
> b) please figure out which of reboot=pci, reboot=kbd, reboot=bios, and
> reboot=triple work on this platform.
>
> -hpa
>
I advised the Arch user to join this discussion and provide the
requested info. I immediately went for kbd as the solution because
that's exactly what I need for my own Aspire One - that AOA110 quirk
that's visible in the context of this patch. I figured it's a pattern,
Aspire One machines quirky in the same way.
Regards,
Uroš
next prev parent reply other threads:[~2012-06-21 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 13:32 [PATCH] x86: Aspire One Happy2 reboots only with the kbd method Uros Vampl
2012-06-21 14:29 ` Don Zickus
2012-06-21 14:40 ` H. Peter Anvin
2012-06-21 22:22 ` Uros Vampl [this message]
2012-06-21 22:27 ` H. Peter Anvin
2013-01-01 13:16 ` Elisey Shemyakin
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=20120621222228.GA27593@zverina \
--to=mobile.leecher@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peter.chubb@nicta.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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