From: Greg KH <greg@kroah.com>
To: Len Brown <len.brown@intel.com>
Cc: Matthew Wilcox <willy@debian.org>,
Sundarapandian Durairaj <sundarapandian.durairaj@intel.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
Harinarayanan Seshadri <harinarayanan.seshadri@intel.com>,
Vladimir Kondratiev <vladimir.kondratiev@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: [PATCH] pci-mmconfig for 2.6.3-rc1
Date: Mon, 9 Feb 2004 23:39:52 -0800 [thread overview]
Message-ID: <20040210073951.GB20139@kroah.com> (raw)
In-Reply-To: <1076390140.4105.671.camel@dhcppc4>
On Tue, Feb 10, 2004 at 12:15:40AM -0500, Len Brown wrote:
> On Mon, 2004-02-09 at 23:45, Matthew Wilcox wrote:
> > Another round of the MMCONFIG patch. Changes since last time ...
>
> If the system has no MADT, then acpi_boot_init() will never call
> acpi_parse_mcfg() -- looks like that call needs to be moved up. (And
> yes, it seems that HPET has the same problem).
>
> I see i386 and ia64 updates -- are they the only platforms that will
> support pci-express?
I know of some other platforms that will need pci-express support for
them, but that will probably happen some time next year due to hardware
availability...
I think we can only test i386 and ia64 at this time, unless someone else
knows differently?
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-10 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 4:45 Matthew Wilcox
2004-02-10 5:15 ` Len Brown
2004-02-10 7:39 ` Greg KH [this message]
2004-02-10 16:49 ` Matthew Wilcox
2004-02-10 8:25 Durairaj, Sundarapandian
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=20040210073951.GB20139@kroah.com \
--to=greg@kroah.com \
--cc=akpm@zip.com.au \
--cc=harinarayanan.seshadri@intel.com \
--cc=jun.nakajima@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=sundarapandian.durairaj@intel.com \
--cc=vladimir.kondratiev@intel.com \
--cc=willy@debian.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
all inboxes | Powered by JetHome®