Darren J Moffat wrote: > Joerg Schilling wrote: >> Alan Coopersmith <alan.coopersm...@sun.com> wrote: >> >>> Is there a public interface to load a kernel module from user space? >>> >>> Looking at the modload source, it seems to use the modctl() system call >>> but I see no man page for that. >> >> I thought that Solaris does not need this because drivers are loaded >> automatically when the device is opened. What kind of usecase do you >> have in mind? > > That was going to be exactly my response as well Joerg, so like you I'm > not sure why Solaris would actually need this. > > Is it because these kernel modules would be 'misc' modules with no other > kernel module depending on them and no path_to_inst entry binding it to > a hardware instance ?
I guess - Xorg is using it for DRI modules, which at least on other platforms are loadable modules that are not the device driver for the hardware in question. I'm not familiar enough with the Solaris kernel implementation of DRI to know if we've decided to make them all device drivers, replacing vgatext on devices that support DRI and making this unnecessary or not. The code change in question that brought it to my attention during code review was integrated today: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=52367847087206b92f18c40d356d36ab9ee89d39 That loads the i915 module, which we seem to ship as a driver instead of a misc module, so I'm guessing leaving it as a no-op on Solaris is okay for now. It sounds like if we do need this at some point, we'll have to follow the Linux style implementation of fork/exec modload. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
