From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/2] sparc32,leon: PCI patches
Date: Fri, 20 May 2011 08:08:16 +0000 [thread overview]
Message-ID: <20110520.040816.1411861187670192730.davem@davemloft.net> (raw)
In-Reply-To: <4DB68838.1020304@gaisler.com>
From: Daniel Hellstrom <daniel@gaisler.com>
Date: Fri, 20 May 2011 10:01:11 +0200
> David Miller wrote:
>
>>From: Daniel Hellstrom <daniel@gaisler.com>
>>Date: Thu, 19 May 2011 15:13:14 +0200
>>
>>
>>>The PowerPC for example assign resources
>>>(arch/powerpc/kernel/pci-common.c), and PowerPC may also have a
>>>OpenBoot loader:
>>>
>>
>>On some powerpc systems, like sparc64 Niagara, you can't blindly go
>>poking around the PCI config space at all and must rely completely
>>and entirely upon the OpenBoot device tree.
>>
> I see, that may be because IRQ routing or resource allocation is done
> in a non-standard way I guess, perhaps because of bugs on some of the
> motherboards.
Or because PCI accesses have to go through a hypervisor.
The point is that having it all setup in OpenBoot is a great
abstraction because you don't have to care.
It also allows things like being able to disable devices with things
like "pcia-probe-list" and "pcib-probe-list" properties in the PCI
host controller node, which we end up honoring on sparc64 simply
because we never directly probe PCI space to probe devices.
next prev parent reply other threads:[~2011-05-20 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 8:54 [PATCH 0/2] sparc32,leon: PCI patches Daniel Hellstrom
2011-05-16 20:01 ` David Miller
2011-05-19 13:13 ` Daniel Hellstrom
2011-05-19 19:01 ` David Miller
2011-05-20 8:01 ` Daniel Hellstrom
2011-05-20 8:08 ` David Miller [this message]
2011-05-20 14:22 ` Daniel Hellstrom
2011-05-20 18:24 ` David Miller
2011-05-23 8:49 ` Daniel Hellstrom
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=20110520.040816.1411861187670192730.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@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 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.