From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "Wimer, Walt" <walt.wimer@timesys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PCI support under 2.6.11.4 on MPC8272ADS ???
Date: Fri, 25 Mar 2005 17:07:15 +0300 [thread overview]
Message-ID: <42441B13.7080703@ru.mvista.com> (raw)
In-Reply-To: <1111705036.15834.29.camel@excalibur.timesys.com>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
Hi Walt,
Well, the incorrect VendorID almost clearly points to the incompatible
PCI bus frequency - try to set it to 33Mhz.
AFAIR, I saw my network card as video adapter in the lspci output.
The 2.4 stuff was tested rather thoroughly. The current 2.6.11 support
is examined with HPT370 and PDC20268 PCI IDE.
You may also try my latest patch to the stock linux 2.5.
Wimer, Walt wrote:
>Using Vitaly's 2.4-based patch below as a starting point, I've been
>adding PCI support to 2.6.11.4 for the MPC8272ADS board.
>
>The good news is that I think I have PCI interrupts pretty well sorted
>out, and I see *something* half-way reasonable from "lspci".
>
>The bad news is that neither of the ethernet cards that I'm trying will
>actually work, and I see some very weird behavior with PCI configuration
>space:
>
> Card 1: Some Realtek RTL8139D-based card
> Card 2: NETGEAR FA311 (National Semi DP83815 chip)
>
>With either card installed alone, both U-Boot and my kernel identify the
>cards correctly in PCI configuration space.
>
>With *both* cards installed, both U-Boot and my kernel see the Realtek-
>based card correctly, but the NETGEAR card has a corrupted Vendor ID
>(e.g. 0x1000 or 0x1003 instead of the correct 0x100b). This happens
>regardless of which PCI slots I use for the cards (I've tried virtually
>every combination). This smells of a power problem or something to me.
>
>And again, even with either card alone, the drivers have serious
>problems talking to the cards. I get various error messages from
>the drivers and I see badly mangled packets on the wire. It's also
>not uncommon for the whole system to freeze...
>
>Has anyone else seen similar behavior?
>
>Has anyone had success with PCI on this board (under any kernel
>version)?
>
>
>Any ideas / data points are appreciated.
>
>
>Thanks!!!
>
>Walt Wimer
>
>
>
>
>
>>This patch adds PCI bridge support for MPC8272 and PQ2FADS to the
>>current linuxppc-2.4 tree. Actually it has been tested with 8272, but
>>PQ2 _should_ also work, though it will complain that host bridge ID is
>>unrecognized.
>>
>>Signed-off-by: Vitaly Bordug <vbordug at ru.mvista.com>
>>
>>--
>>Sincerely, Vitaly
>>
>>-------------- next part --------------
>>A non-text attachment was scrubbed...
>>Name: pq2-pci.patch
>>Type: text/x-patch
>>Size: 20111 bytes
>>Desc: not available
>>Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050218/12060ce8/pq2-pci.bin
>>
>>
>
>
>
>
--
Sincerely,
Vitaly
[-- Attachment #2: Type: text/html, Size: 3062 bytes --]
next prev parent reply other threads:[~2005-03-25 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 22:53 PCI support under 2.6.11.4 on MPC8272ADS ??? Wimer, Walt
2005-03-25 12:11 ` Andrei Konovalov
2005-03-25 14:07 ` Vitaly Bordug [this message]
2005-03-25 14:32 ` Andrey Volkov
2005-03-29 16:01 ` Walter L. Wimer III
2005-03-29 16:41 ` Andrei Konovalov
2005-03-29 8:38 ` Clemens Koller
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=42441B13.7080703@ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=walt.wimer@timesys.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;
as well as URLs for NNTP newsgroup(s).