Date: Sun, 19 Mar 2000 14:05:31 -0500 From: "David E. Cross" <crossd@cs.rpi.edu> To: Doug Rabson <dfr@nlsystems.com> Cc: "David E. Cross" <crossd@cs.rpi.edu>, freebsd-new-bus@freebsd.org Subject: Re: when is dinfo instantiated? Message-ID: <200003191905.OAA66603@cs.rpi.edu> In-Reply-To: Message from Doug Rabson <dfr@nlsystems.com> of "Sun, 19 Mar 2000 17:44:34 GMT." <Pine.BSF.4.21.0003191744030.66122-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, that is what I thought. It would appear that something is not doing its job... below is a my current test case 'pci_attach()' function in pci.c: static int pci_attach(device_t dev) { printf("dinfo: 0x%08lx\n", device_get_ivars(dev)); return (bus_generic_attach(dev)); } This is the only change I have made to the kernel, with the exception of changing the device_method_t for pci.c to point to that attach method. On bootup I get the following messages (dmesg | grep dinfo): dinfo: 0x00000000 dinfo: 0x00000000 I am correct in thinking that the ivars should be set by the parent of a device? Am I making an icorrect assumption that I should be able to get information for a PCI bus from this interface? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003191905.OAA66603>