linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: ashish anand <ashisha@india.infogain.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PCI Config access doesn't return correct data...
Date: Thu, 19 Jul 2001 10:55:31 -0700	[thread overview]
Message-ID: <3B571F13.8F067B1@mvista.com> (raw)
In-Reply-To: 3B567E57.D2339645@india.infogain.com


ashish anand wrote:

> Hi all,
> I found a strange behaviour of pci config access on my board.
> my host bridge is MPC107(address map b)
> indirect pci config access method with config_addr and config_data ports
> at 0xfec00000 and 0xfee00000.
>
> I am using sandpoint+750 board and Bluecat Linux.

Do yourself a favor and either use the latest 2_4_devel kernel or hhl2.0 kernel from mvista
for the sandpoint.

>
> I have a case of pci config not returning devid and vendorid correctly
> sometime 0x00000000 , hence the cards put in slot are not even detected ,
> in following conditions.
> (card not behaving correctly are scsi aha 294xxx and 3c905b n/w card
> but surprisingly INTEL 82559 always behaves correctly)
>
> 1> when you boot through osloader
>
> 2> when you put your scsi or 3com card in OUTER slot only
>
> but when i put mb() in definition of pcibios_xxxx_config_xxxx in file indirect_pci.c
> before and after the reading and writing the pci_config_addr and pci_config_data ports
> everything behaves correctly.
>
> it is clear that it was a reordering problem.
> i want a further comment on this ,why it should happen?
> noteworthy point is that it only happens when you ,
>
> boot through osloader + with scsi and 3com cards not intel one +  only when cards are put
> in OUTER slots.
>


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

      reply	other threads:[~2001-07-19 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19  6:29 PCI Config access doesn't return correct data ashish anand
2001-07-19 17:55 ` Mark A. Greer [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=3B571F13.8F067B1@mvista.com \
    --to=mgreer@mvista.com \
    --cc=ashisha@india.infogain.com \
    --cc=linuxppc-dev@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).