From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Flores, Raul" <raul.flores@lmco.com>
Cc: linuxppc-dev@ozlabs.org, Deepak Pandian <peerlessdeepaks@gmail.com>
Subject: RE: PCI Resource allocation
Date: Mon, 08 Dec 2008 10:00:30 +1100 [thread overview]
Message-ID: <1228690830.7101.25.camel@pasglop> (raw)
In-Reply-To: <28CF047BB51A9C40A89E308370E2DA1117A4AB34@emss07m13.us.lmco.com>
On Thu, 2008-12-04 at 18:12 -0600, Flores, Raul wrote:
> A bit off topic, but since the subject is pci resource allocation:
>
> As entered here:
> http://bugs.gentoo.org/show_bug.cgi?id=249832
>
> the 2.6.24-gentoo-r3 kernel; iomem tree for my video display works, but
> has not worked in the following kernels:
> 2.6.26-gentoo-r2
> 2.6.27-gentoo-r2
> 2.6.28-rc4 (perfmon2 git)
>
> Using g5_defconfig on an iMac G5 iSight PowerMac 12,1 ppc64 (cross 32
> userspace) PPC970FX
>
> Had to hack to arch/powerpc/kernel/pci-common.c in alloc_resource() so
> that I could run the 2.6.28 kernel with perfmon2.
That's strange... looks like something fishy with the PCI-E root
complex, can you enable DEBUG in pci-common.c and pci_64.c and send me
the resulting dmesg output ?
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-07 23:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 18:36 PCI Resource allocation Deepak Pandian
2008-12-04 22:54 ` Benjamin Herrenschmidt
2008-12-05 0:12 ` Flores, Raul
2008-12-07 23:00 ` Benjamin Herrenschmidt [this message]
2008-12-05 3:40 ` Deepak Pandian
-- strict thread matches above, loose matches on Subject: below --
2016-09-19 18:15 PCI Resource Allocation Robert Jones
2016-09-19 19:41 ` Bjorn Helgaas
2016-09-19 20:59 ` Robert Jones
2016-10-01 3:20 ` Yinghai Lu
2002-12-09 14:53 John Traill
2001-08-21 6:11 PCI resource allocation Jim McCloskey
2000-10-04 6:53 Michael Thompson
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=1228690830.7101.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=peerlessdeepaks@gmail.com \
--cc=raul.flores@lmco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.