On Thu, 28 Feb 2008 09:34:16 +0200, "Cyril Plisko" <[EMAIL PROTECTED]> wrote: > Steve, > > What catches my eye is the 7th argument to the DDI_DEFINE_STREAM_OPS() > macro > It should be a xx_getinfo() entry point. Since it is a network driver > and it can get away > without proper getinfo() it should be nodev() or ddi_no_info(). I am > really not sure what > happens if NULL is passed there. > > Well, I just checked the kernel source, and it appears that there is > at least one point > where getinfo() provided by the driver is called without checking it > is non-NULL beforehand. > Since it is called from uts/common/os/driver.c::bdev_strategy() I > highly doubt it has something > to do with your problem. Still leaving it as NULL bothers me.
Gotcha. Is there any reason why I would use ddi_no_info over nodev? > Back to your problem. Have you tried to dtrace the driver loading > process ? We'd see > what was called and in which sequence. Thats a very good idea - I did not even think to check the fbt probes. I'll give it a shot this evening. Thanks, Steve -- Yet magic and hierarchy arise from the same source, and this source has a null pointer. Reference the NULL within NULL, it is the gateway to all wizardry. _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
