mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: PCI bridge handling 2.4.0-test10 -> 2.4.2-pre3
Date: Mon, 12 Feb 2001 14:04:20 +0100	[thread overview]
Message-ID: <20010212140419.A11619@lug-owl.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3163 bytes --]

Hi!

I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID
controller. The mainboard is ServerWorks based and however, 2.4.2-pre3
fails to find the RAID controller. I think there's a problem at
scanning PCI busses behind PCI bridges. Here's the PCI bus layout as
2.4.0-test10 recognizes it:

-+-[01]-+-04.0  Adaptec 7899P
 |      +-04.1  Adaptec 7899P
 |      \-0a.0-[02]--+-08.0  Digital Equipment Corporation: Unknown device 1065
 |                   \-09.0  Mylex Corporation eXtremeRAID support Device
 \-[00]-+-00.0  Relience Computer CNB20HE
        +-00.1  Relience Computer CNB20HE
        +-02.0  ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC]
        +-03.0  Intel Corporation 82557 [Ethernet Pro 100]
        +-06.0  Intel Corporation 82557 [Ethernet Pro 100]
        +-07.0  Intel Corporation 82557 [Ethernet Pro 100]
        +-0f.0  Relience Computer: Unknown device 0200
        \-0f.1  Relience Computer: Unknown device 0211

Here's log output from both 2.4.0-test10 (successfully booting) and
2.4.2-pre3 (no success due to missing root fs):

----------------------- 2.4.0-test10 -----------------------
PCI: PCI BIOS revision 2.10 entry at 0xfdb3c, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ServerWorks host bridge: secondary bus 00
PCI: ServerWorks host bridge: secondary bus 01
PCI->APIC IRQ transform: (B1,I4,P0) -> 16
PCI->APIC IRQ transform: (B1,I4,P1) -> 17
PCI->APIC IRQ transform: (B2,I8,P0) -> 20
PCI->APIC IRQ transform: (B0,I2,P0) -> 19
PCI->APIC IRQ transform: (B0,I3,P0) -> 18
PCI->APIC IRQ transform: (B0,I6,P0) -> 26
PCI->APIC IRQ transform: (B0,I7,P0) -> 23
[...]
DAC960: ***** DAC960 RAID Driver Version 2.4.8 of 19 August 2000 *****
DAC960: Copyright 1998-2000 by Leonard N. Zubkoff <lnz@dandelion.com>
DAC960#0: Configuring Mylex DAC1164P PCI RAID Controller
DAC960#0:   Firmware Version: 5.07-0-79, Channels: 3, Memory Size: 16MB
DAC960#0:   PCI Bus: 2, Device: 8, Function: 0, I/O Address: Unassigned
DAC960#0:   PCI Address: 0xFB110000 mapped at 0xE0800000, IRQ Channel: 20
DAC960#0:   Controller Queue Depth: 128, Maximum Blocks per Command: 128
DAC960#0:   Driver Queue Depth: 127, Scatter/Gather Limit: 33 of 33 Segments
DAC960#0:   Stripe Size: 64KB, Segment Size: 8KB, BIOS Geometry: 255/63
DAC960#0:   SAF-TE Enclosure Management Enabled

----------------------- 2.4.2-pre3 -------------------------------
PCI: PCI BIOS revision 2.10 entry at 0xfdb3c, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ServerWorks host bridge: last bus ff
PCI->APIC IRQ transform: (B0,I2,P0) -> 19
PCI->APIC IRQ transform: (B0,I3,P0) -> 18
PCI->APIC IRQ transform: (B0,I6,P0) -> 26
PCI->APIC IRQ transform: (B0,I7,P0) -> 23


Can you give me some advice on how to hack those PCI bridges?

MfG, JBG

-- 
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

             reply	other threads:[~2001-02-12 13:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12 13:04 Jan-Benedict Glaw [this message]
2001-02-12 23:38 ` Adam Lackorzynski
2001-02-13 11:20   ` Jan-Benedict Glaw
2001-02-13 14:41     ` Adam Lackorzynski
2001-02-13 16:58       ` Tim Wright
2001-02-13 17:11         ` Jeff Garzik
2001-02-13 17:30 Zink, Dan
2001-02-14  6:27 ` Jeff Garzik

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=20010212140419.A11619@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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®