From owner-freebsd-hackers Thu May 21 18:20:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21601 for freebsd-hackers-outgoing; Thu, 21 May 1998 18:20:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles145.castles.com [208.214.165.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21541 for ; Thu, 21 May 1998 18:20:43 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA05820; Thu, 21 May 1998 17:16:54 -0700 (PDT) Message-Id: <199805220016.RAA05820@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Vinay Bannai cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Probing a PCI device!! In-reply-to: Your message of "Thu, 21 May 1998 17:48:32 PDT." <199805220048.RAA15095@shell6.ba.best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 May 1998 17:16:54 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi folks, > > I am trying to probe a PCI device and I am in the odd situation where the > firmware has to be downloaded onto the card before I can check the > Vendor/Device ID. It is set by the firmware.. > > How do I solve the chicken and egg problem? Or am I missing something? It's possible that the card is using a generic PCI bridge chip - have a look at the card and see. If this is the case, you could try matching against the interface vendor/model rather than the device set if the device set is invalid. Do the device IDs default to anything sensible? -- \\ 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