From: Alan Cox <alan@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Borislav Petkov <bp@alien8.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
"Li, Aubrey" <aubrey.li@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Len.Brown@intel.com, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Bypass legacy PIC and PIT on ACPI hardware reduced platform
Date: Thu, 05 Mar 2015 16:05:02 +0000 [thread overview]
Message-ID: <1425571502.3838.151.camel@linux.intel.com> (raw)
In-Reply-To: <8129220.9HmyqjfodP@vostro.rjw.lan>
> Besides, the "ACPI reduced hardware" case is kind of a red herring here,
> because it most likely is not the only case when we'll want has_8259_pic()
> to return 0 (quite likely, we'll want that on all BayTrail-based systems,
> for example).
No. Only those with ACPI reduced firmware. For others you do want to
touch the 8259.
It *is* about ACPI reduced.
Alan
next prev parent reply other threads:[~2015-03-05 16:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 3:23 [PATCH] x86: Bypass legacy PIC and PIT on ACPI hardware reduced platform Li, Aubrey
2015-03-04 5:08 ` Ingo Molnar
2015-03-04 5:26 ` Li, Aubrey
2015-03-04 5:31 ` Ingo Molnar
2015-03-04 6:04 ` Li, Aubrey
2015-03-04 7:37 ` Ingo Molnar
2015-03-04 8:43 ` Arjan van de Ven
2015-03-04 9:50 ` Borislav Petkov
2015-03-04 14:16 ` Rafael J. Wysocki
2015-03-04 14:05 ` Borislav Petkov
2015-03-04 14:38 ` Rafael J. Wysocki
2015-03-04 20:21 ` Alan Cox
2015-03-04 21:52 ` Rafael J. Wysocki
2015-03-05 11:26 ` Li, Aubrey
2015-03-05 16:05 ` Alan Cox [this message]
2015-03-04 14:36 ` Arjan van de Ven
2015-03-04 20:11 ` Ingo Molnar
2015-03-05 11:13 ` Li, Aubrey
2015-03-05 11:36 ` Ingo Molnar
2015-03-05 12:42 ` Li, Aubrey
2015-03-05 16:06 ` Alan Cox
2015-03-09 23:26 ` Li, Aubrey
2015-03-10 8:06 ` Ingo Molnar
2015-03-11 4:14 ` Li, Aubrey
2015-03-04 20:18 ` Alan Cox
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=1425571502.3838.151.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=Len.Brown@intel.com \
--cc=arjan@linux.intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--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 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.