On Thu, May 21, 2009 at 7:50 PM, Andrew Gallatin <[email protected]> wrote: > Masa Murayama wrote: > >> I'm developping nic drivers. I don't put my drivers into /kernel/drv >> directory when they aren't stable. Instead of that, I load the drivers >> into kernel space explicitly by using "modload my_driver". > > Does your /kernel/drv/my_driver.conf file get re-read when > just using modload? If not, is there a way to force a re-read > in some other way? > > FWIW, I do sort of the same thing as you, except I softlink my drivers > into /kernel/drv and use add_drv / rem_drv. My method worked great > when I started on S10GA before the evil bootarchive. But with > bootarchive, I have problems rebooting similar to the OP. My > workaround is to just always make sure I have a working serial > console (which I tend to want for kmdb anway). > > Drew
IMO the answer is "no". Only during attaching the bindings, such as during add_drv. _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
