linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tamas Bara <tba@mixed-mode.de>
To: "Linuxppc-Embedded@Lists. Linuxppc. Org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: PCI on MPC8265
Date: Tue, 21 Oct 2003 13:18:55 +0200	[thread overview]
Message-ID: <3F95161F.1080206@mixed-mode.de> (raw)


Hi,

I´m running Linux 2.4.4 on a TQM8260 board with
an MPC8265 on it and an Ethernet controller on
the PCI Bus.

When Linux scans the PCI Bus it detects the
controller multiple times. I could change the for
loop to devfn < 9 since I only got the internal
host bridge and the controller on the bus:

/* Go find them, Rover! */
for (devfn = 0; devfn < 0x100; devfn += 8) {
	dev0.devfn = devfn;
	pci_scan_slot(&dev0);
}

This works, but I don´t want to change the kernel.
So I´m looking for a different solution.

How does the kernel know that it already detected
a device before?

Thanks


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

             reply	other threads:[~2003-10-21 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 11:18 Tamas Bara [this message]
2003-10-21 16:00 ` PCI on MPC8265 bhupinder sahran

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=3F95161F.1080206@mixed-mode.de \
    --to=tba@mixed-mode.de \
    --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).