From: Chris Cheney <ccheney@cheney.cx>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org,
acpi-devel-request@lists.sourceforge.net, patches@x86-64.org,
ak@suse.de, len.brown@intel.com, pavel@ucw.cz
Subject: Re: [PATCH] x86_64 VIA chipset IOAPIC fix
Date: Thu, 25 Mar 2004 21:04:58 -0600 [thread overview]
Message-ID: <20040326030458.GZ9248@cheney.cx> (raw)
In-Reply-To: <20040325033434.GB8139@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Wed, Mar 24, 2004 at 07:34:34PM -0800, Tony Lindgren wrote:
> Hi Andi & Len,
>
> Sorry for cross posting all over the place, I tried to CC some people who have
> been bugged by this bug.
>
> I finally got the IOAPIC working on my eMachines m6805 amd64 laptop with the
> following patch. I have not tried it on any other machines, so can you guys
> please check the sanity and make the necessary changes if needed?
>
> This fixes at least ACPI bug 2090:
>
> http://bugme.osdl.org/show_bug.cgi?id=2090
>
> Might fix some other x86 VIA bugs too?
Is this actually a "VIA" fix or a just workaround for the broken Arima
bios? I noticed that the Arima bios seems to be pretty buggy in some
other aspects as well.
BTW - Does this also solve the problem with needing USB to be compiled
directly into the kernel in 64bit mode?
Chris
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-26 3:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 3:34 [PATCH] x86_64 VIA chipset IOAPIC fix Tony Lindgren
2004-03-26 0:15 ` Len Brown
2004-03-26 0:47 ` Tony Lindgren
2004-03-26 3:04 ` Chris Cheney [this message]
2004-03-26 3:11 ` Tony Lindgren
2004-03-26 3:13 ` Len Brown
2004-03-26 3:20 ` Chris Cheney
2004-03-26 3:35 ` Tony Lindgren
2004-03-26 4:21 ` Len Brown
2004-03-26 4:34 ` Chris Cheney
2004-03-26 5:10 ` Tony Lindgren
2004-03-30 3:17 ` Randy.Dunlap
2004-03-26 5:02 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 10:53 HurryLin
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=20040326030458.GZ9248@cheney.cx \
--to=ccheney@cheney.cx \
--cc=acpi-devel-request@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
/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