From: Ira Snyder <iws@ovro.caltech.edu>
To: Scott Coulter <scott.coulter@cyclone.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: correct way for handling PCIe in endpoint mode
Date: Tue, 10 Feb 2009 08:22:49 -0800 [thread overview]
Message-ID: <20090210162249.GB9592@ovro.caltech.edu> (raw)
In-Reply-To: <43EB80E07C42E1408726E4905FB96B04C074D9@CYBORG3.cyclone.com>
On Tue, Feb 10, 2009 at 07:39:47AM -0500, Scott Coulter wrote:
>
> Hi all,
>
> Maybe a silly questions, but what is the suggested way for handling a
> processor which has a PCIe interface, but the interface is not
> configured to be the root complex (endpoint only)?
>
> Should the PCIe interface appear in the dts? If so, with what
> parameters?
>
> Should the kernel config contain CONFIG_PCI, etc. ?
>
I'm in a similar situation, except I'm using PCI instead of PCIe. I've
tried both removing the PCI interface from the dts, and disabling
CONFIG_PCI. Both work fine.
You probably don't want to leave the PCI interface in the dts and also
leave CONFIG_PCI enabled. I ran into some really strange issues this
way... (Linux ran through the quirks and tried to re-initialize a
network card, even though the driver was disabled, etc.)
I think the suggested way is to remove the PCI interface from the dts,
that way you can potentially share a kernel between similar boards with
and without PCI root interfaces, just by changing the dts.
Ira
prev parent reply other threads:[~2009-02-10 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 12:39 correct way for handling PCIe in endpoint mode Scott Coulter
2009-02-10 16:22 ` Ira Snyder [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=20090210162249.GB9592@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=linuxppc-dev@ozlabs.org \
--cc=scott.coulter@cyclone.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox