From owner-freebsd-hackers Wed Nov 11 13:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06723 for freebsd-hackers-outgoing; Wed, 11 Nov 1998 13:46:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06715 for ; Wed, 11 Nov 1998 13:46:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA05356; Wed, 11 Nov 1998 13:43:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112143.NAA05356@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ron G. Minnich" cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: pcibridge card (really) In-reply-to: Your message of "Wed, 11 Nov 1998 16:34:34 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 13:43:40 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > SCI is scaleable coherent interface, not scsi. This is a distributed > shared memory system that plugs into the PCI bus in this case. But the > card is configured as a bridge, not a device. I can't figure out how to > get freebsd to call my initialization code short of modifying pcisupport.c > In other words, I'm not real clear on how bridges can be added to the > kernel in the same modular way that pci cards are. Ok, belay my last comment - it does DSM after all. The PCI code *should* be passing the card's vendor/device ID to all the PCI drivers, and that should mean that your driver sees it. It sounds like the "generic chipset" code is ending up in the linker set before your driver though, so it claims it early. You can check to see if this is the case by diking out the call to generic_pci_bridge(). This is germane to Garret's comments about needing to separate 'catchall' drivers from the device-specific ones; if it'll help you at all we can implement an interim solution that will cover what seems to be your problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message