From: Randy Dunlap <rdunlap@xenotime.net>
To: Xianghua Xiao <xiaoxianghua@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: Disable PCI while CONFIG_PCI=y
Date: Wed, 13 Apr 2011 15:37:24 -0700 [thread overview]
Message-ID: <20110413153724.5776f7e5.rdunlap@xenotime.net> (raw)
In-Reply-To: <BANLkTi=KvxPNuvZnL90SAmkQna=ARE6xyQ@mail.gmail.com>
On Wed, 13 Apr 2011 17:01:38 -0500 Xianghua Xiao wrote:
> Yes I read that but my ARCH is arm.
>
It would probably make sense to implement
pci=off
for any $arch.
Any problem with that, linux-pci??
>
> On Wed, Apr 13, 2011 at 3:10 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On Wed, 13 Apr 2011 15:05:59 -0500 Xianghua Xiao wrote:
> >
> >> Is it possible to do something like 'pci=off' to have the same effect
> >> as turning of CONFIG_PCI during menuconfig?
> >> I want to build one image for both PCIE RC and PCIE EP(endpoint), for
> >> EP I do not need PCI to be enabled at all.
> >>
> >> looking at drivers/pci/pci.c I don't see such option exists, am I
> >> missing something?
> >
> > Hm. Documentation/kernel-parameters.txt says:
> >
> >
> > pci=option[,option...] [PCI] various PCI subsystem options:
> > earlydump [X86] dump PCI config space before the kernel
> > changes anything
> > off [X86] don't probe for the PCI bus
> >
> > What $ARCH are you using?
> >
> > See arch/x86/pci/common.c::pcibios_setup() for code that handles
> > pci=off
> >
> > ---
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-04-13 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 20:05 Xianghua Xiao
2011-04-13 20:10 ` Randy Dunlap
2011-04-13 22:01 ` Xianghua Xiao
2011-04-13 22:37 ` Randy Dunlap [this message]
2011-04-14 16:38 ` Jesse Barnes
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=20110413153724.5776f7e5.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=xiaoxianghua@gmail.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
all inboxes | Powered by JetHome®