From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Gary Hade" <garyhade@us.ibm.com>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/pci: add pci=skip_isa_align command lines.
Date: Thu, 27 Mar 2008 09:10:37 -0700 [thread overview]
Message-ID: <86802c440803270910q6602606aode3c355bf7947d32@mail.gmail.com> (raw)
In-Reply-To: <20080327084557.GH15626@elte.hu>
On Thu, Mar 27, 2008 at 1:45 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Yinghai Lu <yhlu.kernel.send@gmail.com> wrote:
>
> > [PATCH] x86/pci: add pci=skip_isa_align command lines.
> >
> > so we don't align the io port start address for pci cards.
> >
> > also move out dmi check out acpi.c, because it has nothing to do with
> > acpi. it could spare some calling when we have several peer root
> > buses.
>
> i like this feature, and i've applied your patch to x86.git for testing,
> but i'd like to hear what the ACPI and PCI guys think about this.
>
> Also, we should try as hard as possible to make it a blacklist instead
> of a whitelist? It would be cool to support more PCI cards/devices on
> all new(-ish) systems by default and if we didnt have to maintain the
> DMI whitelist for eternity. (a whitelist will always be incomplete and
> will lag behind reality)
yeah, blacklist is more good. that limitation is quite old...
YH
next prev parent reply other threads:[~2008-03-27 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 8:31 Yinghai Lu
2008-03-27 8:45 ` Ingo Molnar
2008-03-27 16:10 ` Yinghai Lu [this message]
2008-03-27 17:59 ` Gary Hade
2008-03-27 18:07 ` Yinghai Lu
2008-03-27 18:42 ` H. Peter Anvin
2008-03-27 21:46 ` H. Peter Anvin
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=86802c440803270910q6602606aode3c355bf7947d32@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=garyhade@us.ibm.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
Powered by JetHome