mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabrice Gautier <gautier@email.enst.fr>
To: linux-kernel@vger.kernel.org
Subject: PCI: Direct Access and STPC
Date: Thu, 24 May 2001 11:28:20 +0200	[thread overview]
Message-ID: <20010524112805.0A12.GAUTIER@email.enst.fr> (raw)

Hi,

I noticed that when building a kernel with CONFIG_PCI_DIRECT and not
CONFIG_PCI_BIOS, the kernel doesn't detect any PCI bus when runing on a
STPC embeded CPU.

The STPC include a PCI chipset but the configuration methods usednin the
kernel does not seems to match the STPC docs.

The STPC use 0xCF8 and 0xCFC registers to access PCI configuration space.
This seems to match the code of pci_conf1_read_config_byte but the
sanity_check fail pci_check_direct.

The fact is that the north bridge in the STPC have a class code of 0, 
so is not detected as a host bridge. For my own tests i've removed the 
sanity check and so i get the following result in /proc/pci:

PCI devices found:
  Bus  0, device  11, function  0:
    Non-VGA unclassified device: PCI device 100e:0564 (Weitek) (rev 0).
  Bus  0, device  12, function  0:
    ISA bridge: PCI device 100e:55cc (Weitek) (rev 0).
  Bus  0, device  12, function  1:
    IDE interface: PCI device 100e:55cc (Weitek) (rev 0).
      I/O at 0xfc00 [0xfc07].
      I/O at 0xfc20 [0xfc23].
      I/O at 0xfc40 [0xfc47].
      I/O at 0xfc60 [0xfc63].
      I/O at 0xfc80 [0xfc8f].

I've seen some fixup functions that seems to correct some IDs. I guess
in my case I would need one to correct the device CLASS for the north
bridge. Is that correct ?

Thanks. 

-- 
Fabrice Gautier <gautier@email.enstfr>


                 reply	other threads:[~2001-05-24  9:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010524112805.0A12.GAUTIER@email.enst.fr \
    --to=gautier@email.enst.fr \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®