public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Pcihpd-discuss] [PATCH] Convert acpiphp to use generic resource code
Date: Thu, 03 Feb 2005 19:31:58 +0000	[thread overview]
Message-ID: <20050203113158.A22968@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050119183853.C12618@unix-os.sc.intel.com>

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.
> 
I needed the additional patch below to make it work on Tiger4
ia64 systems. I noticed that a similar patch was submitted before
(http://marc.theaimsgroup.com/?l=linux-ia64&m\x107962911317596&w=2)
but don't know why it was not picked up.

Signed-off-by: Rajesh Shah <rajesh.shah@intel.com>
---

 linux-2.6.11-rc1-mm2-t2-rshah1/arch/ia64/pci/pci.c |    1 +
 1 files changed, 1 insertion(+)

diff -puN arch/ia64/pci/pci.c~track_bridge_resources arch/ia64/pci/pci.c
--- linux-2.6.11-rc1-mm2-t2/arch/ia64/pci/pci.c~track_bridge_resources	2005-02-03 11:02:45.397329199 -0800
+++ linux-2.6.11-rc1-mm2-t2-rshah1/arch/ia64/pci/pci.c	2005-02-03 11:03:57.699086126 -0800
@@ -437,6 +437,7 @@ pcibios_fixup_bus (struct pci_bus *b)
 
 	list_for_each_entry(dev, &b->devices, bus_list)
 		pcibios_fixup_device_resources(dev);
+	pci_read_bridge_bases(b);
 
 	return;
 }
_

      parent reply	other threads:[~2005-02-03 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20  2:38 [Pcihpd-discuss] [PATCH] Convert acpiphp to use generic resource code Rajesh Shah
2005-01-20  2:53 ` Li, Shaohua
2005-01-21  2:54 ` Rajesh Shah
2005-02-03 19:31 ` Rajesh Shah [this message]

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=20050203113158.A22968@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