The driver for the NCR 53C810 is "PCI Aware" in that it uses the
PCI configuration information to figure things out.

On the other hand, the BT driver (which get's used for the 946C),
isn't PCI aware.  It gets the configuration information from the
BusLogic's own (private registers. 

Could this cause problems?  Could the PCI autoconfig process cause
something to end up mismatched versus the BusLogic's view?
Could/will other drivers be made PCI aware?

I've been unable to use the BT946C on a system that
also has an NCR 53C810 (ASUS SPG motherboard).  If I plug in the
946C and move my SCSI devices to it, the system starts to boot, 
get's through all the probes, but then hangs after the 
biomask message.  Relevant info follows...

Successful (NCR only boot):

Nov 27 11:09:57 nirvana /netbsd: pci0 at isa0 port 0x0-0x665: configuration mode 2
Nov 27 11:09:57 nirvana /netbsd: pci0 bus 0 device 0: identifier 04838086 class 00000004 not configured
Nov 27 11:09:57 nirvana /netbsd: ncr0 at pci0 bus 0 device 1
Nov 27 11:09:57 nirvana /netbsd: pci_map_mem: memory mapped at c0000000-c0000fff
Nov 27 11:09:57 nirvana /netbsd: pci_map_int: pin A mapped to irq 11
Nov 27 11:09:57 nirvana /netbsd: ncr0: restart (scsi reset).
Nov 27 11:09:57 nirvana /netbsd: ncr0 scanning for targets 0..6 ($Revision: 1.2 $)
Nov 27 11:09:57 nirvana /netbsd: scsibus1 at ncr0
Nov 27 11:09:57 nirvana /netbsd: ncr0 targ 0 lun 0: <SEAGATE ST3600N         8336> SCSI2 direct fixed
Nov 27 11:09:57 nirvana /netbsd: sd0 at scsibus1sd0(ncr0:0:0): asynchronous.
Nov 27 11:09:57 nirvana /netbsd: : 500MB, 1872 cyl, 7 head, 78 sec, 512 bytes/sec
Nov 27 11:09:57 nirvana /netbsd: ncr0 targ 2 lun 0: <MAXTOR  7345-SCSI       1761> SCSI2 direct fixed
Nov 27 11:09:57 nirvana /netbsd: sd1 at scsibus1: 329MB, 2220 cyl, 4 head, 76 sec, 512 bytes/sec
Nov 27 11:09:57 nirvana /netbsd: ncr0 targ 3 lun 0: <FUJITSU M2624F-512      0405> SCSI1 direct fixed
Nov 27 11:09:58 nirvana /netbsd: sd2 at scsibus1: 496MB, 1429 cyl, 11 head, 64 sec, 512 bytes/sec
Nov 27 11:09:58 nirvana /netbsd: ncr0 targ 5 lun 0: <ARCHIVE VIPER 150  21247-005> SCSI1 sequential removable
Nov 27 11:09:58 nirvana /netbsd: st0 at scsibus1: rogue, density code 0x0, 512-byte blocks, write-enabled
Nov 27 11:09:58 nirvana /netbsd: pci0 bus 0 device 2: identifier 04848086 class 00000003 not configured
Nov 27 11:09:58 nirvana /netbsd: pci0 bus 0 device 6: identifier 88c05333 class 00010000 not configured
Nov 27 11:09:58 nirvana /netbsd: sb: couldn't reset card
Nov 27 11:09:58 nirvana /netbsd: ed0 at isa0 port 0x300-0x31f irq 12: address 00:00:e8:c4:18:97, type NE2000 (16-bit)
Nov 27 11:09:58 nirvana /netbsd: npx0 at isa0 port 0xf0-0xff: using exception 16
Nov 27 11:09:58 nirvana /netbsd: biomask 840 netmask 123a ttymask 23a
Nov 27 11:09:58 nirvana /netbsd: sd2(ncr0:3:0): 

Note the messageless sd2 message...always get it.

Anyway, a failed boot with both gives the BusLogic probe wich finds all
the devices, then the NCR probe (which comes up empty).  I don't have output
for that because it never gets the root filesystem mounted.

Has anyone else tried the 946C with or without success?
The PCI BIOS appears correctly configured (the 946Cs
IRQ matches the one assigned to it's PCI slot).  The only thing
I haven't tried (but will RSN) is disabling the NCR controller completely,
but they should work togather, no?
--
Mark Gooderum
mark@good.com