From: Rajesh Shah <rajesh.shah@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Convert acpiphp to use generic resource code
Date: Thu, 20 Jan 2005 02:14:32 +0000 [thread overview]
Message-ID: <20050119181432.B12618@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050119185120.GE25940@parcelfarce.linux.theplanet.co.uk>
On Wed, Jan 19, 2005 at 01:44:58PM -0800, Greg KH wrote:
> On Wed, Jan 19, 2005 at 06:51:20PM +0000, Matthew Wilcox wrote:
> >
> > This patch converts acpiphp to use the generic PCI resource assignment
> > code. It's quite large, but most of it is deleting the acpiphp_pci and
> > acpiphp_res files. It's tested on an hp Integrity rx8620 (which won't
> > work without this patch). Testers with other hardware welcomed.
>
> Unfortunatly I don't have access to any systems that support acpi pci
> hotplug. Anyone else out there able to test this patch to make sure it
> works properly on their i386 boxes?
>
For this to work properly on i386 (and x86_64), we will need to
port Matthew's other patch at
http://marc.theaimsgroup.com/?l=linux-ia64&m\x110614534704894&w=2
to i386 too. This sets up the bus resources correctly for root
bridges, and is needed for pci_bus_assign_resources() to work
properly.
I can take a crack at doing that, but I'm going to have to hunt
around for an acpiphp capable i386 box too. I will also test this
on a Tiger ia64 box.
Rajesh
next prev parent reply other threads:[~2005-01-20 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 18:51 [PATCH] Convert acpiphp to use generic resource code Matthew Wilcox
2005-01-19 21:44 ` Greg KH
2005-01-20 2:14 ` Rajesh Shah [this message]
2005-01-20 2:43 ` Matthew Wilcox
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=20050119181432.B12618@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=linux-ia64@vger.kernel.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