From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/2] sparc32,leon: PCI patches
Date: Fri, 20 May 2011 08:01:11 +0000 [thread overview]
Message-ID: <4DD61FC7.6030204@gaisler.com> (raw)
In-Reply-To: <4DB68838.1020304@gaisler.com>
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. On all LEON PCI systems I have tested IRQ routing is done
the standard way and resource allocation need no special quirks, even
though linux provides means for fixing stuff like that in some degree on
LEON we currently need no fixups. It just runs beautiful and linux sets
everything up for us :)
I'm not sure, but I think on x86 the BIOS setup is sometimes discarded
and linux initializes some resources itself.
>The support you see there is for older and embedded systems.
>
>
LEON is a embedded system.
I will add support for PROM nodes in LEON PCI layer and fix the build
error Jan discovered, I have to do that anyways.
Daniel
next prev parent reply other threads:[~2011-05-20 8:01 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 [this message]
2011-05-20 8:08 ` David Miller
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=4DD61FC7.6030204@gaisler.com \
--to=daniel@gaisler.com \
--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.