From: bhupinder sahran <bhup_sah@yahoo.com>
To: Tamas Bara <tba@mixed-mode.de>,
"Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PCI on MPC8265
Date: Tue, 21 Oct 2003 09:00:24 -0700 (PDT) [thread overview]
Message-ID: <20031021160024.27655.qmail@web41507.mail.yahoo.com> (raw)
In-Reply-To: <3F95161F.1080206@mixed-mode.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1192 bytes --]
Hi
I think problen is with the idselect on pci back
plane.
Looks like same card is connected to more than one
ideselect, so when kernel is doing enumertaion for
different idselect, same card is responding and kernel
thinks that you have multiple card sitting on pci back
plane. In place of changing the kernel, you shall fix
your hardware....that is a better solution...
Bhupi
Linux +Hypertransport --> Silicon
www.gdatech.com
--- Tamas Bara <tba@mixed-mode.de> wrote:
>
> 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/
prev parent reply other threads:[~2003-10-21 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 11:18 PCI on MPC8265 Tamas Bara
2003-10-21 16:00 ` bhupinder sahran [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=20031021160024.27655.qmail@web41507.mail.yahoo.com \
--to=bhup_sah@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tba@mixed-mode.de \
/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).