From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Len Brown <len.brown@intel.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Matthew Wilcox <willy@debian.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
"linux-pci@atrey.karlin.mff.cuni.cz"
<linux-pci@atrey.karlin.mff.cuni.cz>
Subject: Re: ACPI & 2.4 (Re: [BK PATCH] PCI Express patches for 2.4.27-pre3)
Date: Wed, 26 May 2004 10:45:54 -0400 [thread overview]
Message-ID: <40B4ADA2.2020604@pobox.com> (raw)
In-Reply-To: <20040526073752.GF6742@devserv.devel.redhat.com>
Arjan van de Ven wrote:
> On Wed, May 26, 2004 at 03:35:34AM -0400, Len Brown wrote:
>
>>Yes, the ACPI part to enable MMconfig was pretty small.
>>We parse a table in the standard way and set a global variable --
>>that's about it.
>>
>>I submitted it to 2.4 for the sole purpose
>>to enable Greg to enable native PCIExpress.
>>
>>I expect demand for this in 2.4 as the major distros'
>>enterprise releases are still 2.4 based and the hardware has
>>arrived...
>
>
> yet those enterprise releases won't go to newer 2.4 upstream releases....
Len is right in guessing enterprise releases want PCI Express support
though :)
Jeff
next prev parent reply other threads:[~2004-05-26 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FC676@hdsmsx403.hd.intel.com>
2004-05-26 7:35 ` ACPI & 2.4 (Re: [BK PATCH] PCI Express patches for 2.4.27-pre3) Len Brown
2004-05-26 7:37 ` Arjan van de Ven
2004-05-26 14:45 ` Jeff Garzik [this message]
2004-05-28 12:09 ` Marcelo Tosatti
2004-05-28 14:56 ` Len Brown
2004-05-28 15:38 ` Marcelo Tosatti
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=40B4ADA2.2020604@pobox.com \
--to=jgarzik@pobox.com \
--cc=arjanv@redhat.com \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=marcelo.tosatti@cyclades.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