From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Dave Jones'" <davej@suse.de>, "'Pavel Machek'" <pavel@suse.cz>,
Brad Hards <bhards@bigpond.net.au>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [patch] i386 "General Options" - begone [take 2]
Date: 05 Jun 2002 02:00:04 +0100 [thread overview]
Message-ID: <1023238804.12671.1.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7ED9@orsmsx111.jf.intel.com>
On Wed, 2002-06-05 at 00:09, Grover, Andrew wrote:
> All I can say is using just *part* of ACPI will cause some machine,
> somewhere, to not work.
We've established that pretty comprehensively. Any bit of ACPI causes
some machines somewhere to not work 8)
> I want to avoid scenarios where that happens. If
> there are issues with that, can we discuss them asap, perhaps now?
It may be that the IRQ routing and other bits of ACPI logic need to know
that their are dependancies. We handle that already for other legacy
stuff. If you don't have an MCA bus we don't do MCA bus enumerating. If
you don't have a PCI BIOS32 irq router we don't consider that option and
so forth. Having ACPI IRQ/Enumeration code that says if(!acpi) return
NULL isnt that demanding
next prev parent reply other threads:[~2002-06-04 23:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 23:09 Grover, Andrew
2002-06-04 23:25 ` Dave Jones
2002-06-05 1:00 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 23:31 Grover, Andrew
2002-06-04 21:58 Grover, Andrew
2002-06-04 22:09 ` Dave Jones
2002-06-04 23:16 ` Alan Cox
2002-06-07 5:38 ` fchabaud
2002-06-04 20:59 Grover, Andrew
2002-06-04 21:20 ` Dave Jones
2002-06-05 1:34 ` Brad Hards
2002-06-05 10:29 ` Dave Jones
2002-06-05 23:11 ` Brad Hards
2002-06-03 1:56 Linux 2.5.20 Linus Torvalds
2002-06-03 3:18 ` [patch] i386 "General Options" - begone [take 2] Brad Hards
2002-06-03 22:42 ` Rusty Russell
2002-06-04 14:09 ` Pavel Machek
2002-06-04 22:05 ` Brad Hards
2002-06-02 5:16 ` Pavel Machek
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=1023238804.12671.1.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.com \
--cc=bhards@bigpond.net.au \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®