From: Len Brown <len.brown@intel.com>
To: sezero@superonline.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Status of ACPI PIC mode patches ?
Date: 31 Mar 2004 00:43:32 -0500 [thread overview]
Message-ID: <1080711812.3337.305.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F6D64@hdsmsx402.hd.intel.com>
On Tue, 2004-03-30 at 04:35, O.Sezer wrote:
> Hello:
> [Please CC me on replies]
>
> What is the status of PIC mode patches [1] by Andrew de Quincey;
> are they still needed? The -ac / -pac trees still have them.
If the 1st one is needed, I want to know about it.
The 2nd and 3rd have been in for a long time.
> [1] http://marc.theaimsgroup.com/?t=106280426300001&r=1&w=2
> Also see:
This is Andrew's PIC-fallback patch. This is probably
the most effective and well written patch that I've
refused to integrate;-) There are two reasons.
1. it works for some systems, but breaks others.
2. when it works, it hides a failure. Windows doesn't
have that failure. We'd rather see the failure, fix it
and have Linux work as well as Windows.
BTW. SuSE picked up this patch in SL9.0, though I don't
know if they still use it.
> http://marc.theaimsgroup.com/?t=106280426300002&r=1&w=2
This has been in the base for about 5 months. But
Luming Yu found a better way to handle this issue and
his patch was integrated into 2.4 and 2.6 in the
last week:
http://bugzilla.kernel.org/show_bug.cgi?id=1590
We'll probably delete the original retry code
in an upcoming cleanup.
> http://marc.theaimsgroup.com/?t=106280426100003&r=1&w=2
This patch by Jun Nakajima was pulled into the base
about 5 months ago. It was key to getting VIA systems
to work.
cheers,
-Len
next parent reply other threads:[~2004-03-31 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F6D64@hdsmsx402.hd.intel.com>
2004-03-31 5:43 ` Len Brown [this message]
2004-03-30 9:35 Status of ACPI PIC mode patches ? O.Sezer
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=1080711812.3337.305.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sezero@superonline.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