linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: "Karoliya, Abhishek" <Abhishek.Karoliya@fci.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PPC PCI Enumeration::Switch off
Date: Tue, 23 Dec 2003 14:20:15 -0700	[thread overview]
Message-ID: <20031223142015.B23655@home.com> (raw)
In-Reply-To: <903E17B6FF22A24C96B4E28C2C0214D7012BB3D8@sr-bng-exc01.int.tsbu.net>; from Abhishek.Karoliya@fci.com on Wed, Dec 24, 2003 at 12:08:58AM +0530


On Wed, Dec 24, 2003 at 12:08:58AM +0530, Karoliya, Abhishek wrote:
>
> Hi ,
>
>   While porting Linux {we use both flavours MontaVista based on 2.4.18 &
> Kernel.org's 2.4.20} on MPC7447(Dual CPU) + MV64360 based Processor PMC
> boards , we have a scenario where multiple PMC card will reside on the same
> PCI bus . Out of all the boards only one {identified through hardware
> signal} will enumerate the rest and other PCI devices on the board. {Monarch
> mode}.
>
>   Hence we need to turn off PCI enumeration for other {Non-monarch boards }.
> I tried this by  not calling the
> pciauto_bus_scan(){arch/ppc/kernel/pci_auto.c} while setting up the host
> bridge . But the boards still goes forward and does the enumeration.
> Do I have take care of any other section of the code .

Don't call pcibios_alloc_controller() and the PCI subsystem will not
attempt to probe the bus (and enumerate via the fixup hooks).  Just
configure your inbound window(s) on the non-monarch boards and you
are done.

-Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-12-23 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 18:38 PPC PCI Enumeration::Switch off Karoliya, Abhishek
2003-12-23 21:20 ` Matt Porter [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=20031223142015.B23655@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=Abhishek.Karoliya@fci.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).