From: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
To: Patrick Dreker <patrick-G8S07CpUG8qzQB+pC5nmwQ@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] ACPI drop back to pic mode -- linux-2.6.0-test2-acpi-picmode.patch
Date: Thu, 31 Jul 2003 11:21:36 +0100 [thread overview]
Message-ID: <200307311121.36252.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <200307310336.07486.patrick-G8S07CpUG8qzQB+pC5nmwQ@public.gmane.org>
> > Before patching the kernel with the picmode.patch booting with acpi=off
> > was no problem (aside from some devices not getting an IRQ assigned).
> > Whether I enable or disable the APIC (at compile time, as well as with
> > the "noapic" kernel option) does not matter. If ACPI is enabled all is
> > fine. The APIC is enabled and all devices are assigned IRQs (which is not
> > the case without ACPI).
>
> Booting with ACPI enabled and "noapic" outputs a long flood of APIC errors
> on boot. Did not test any further.
Great thanks, I'll have a look into that one.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-07-31 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 20:00 [PATCH] ACPI drop back to pic mode -- linux-2.6.0-test2-acpi-picmode.patch Andrew de Quincey
[not found] ` <200307302100.01386.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-31 0:28 ` Patrick Dreker
[not found] ` <200307310228.35207.patrick-G8S07CpUG8qzQB+pC5nmwQ@public.gmane.org>
2003-07-31 1:36 ` Patrick Dreker
[not found] ` <200307310336.07486.patrick-G8S07CpUG8qzQB+pC5nmwQ@public.gmane.org>
2003-07-31 10:21 ` Andrew de Quincey [this message]
2003-07-31 10:20 ` Andrew de Quincey
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=200307311121.36252.adq_dvb@lidskialf.net \
--to=adq_dvb-fmpxvn3awwjajazl26g0sa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=patrick-G8S07CpUG8qzQB+pC5nmwQ@public.gmane.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