2.6 modules search path

[Tim Fenn <fenn@xxxxxxxxxxxx>]

I recently upgraded to FC2, and everything has been working fine.
however, I'd like to try out some experimental v4l modules.  I can
install them fine in /lib/modules/2.6.6-1.435/v4l, but modprobe still
insists on using the stock modules in
/lib/modules/2.6.6-1.435/kernel/drivers - is there a way around this
other than overwriting the stock modules?  I remember in the days of
modules.conf, one could use "path[toplevel]=/dir/to/stuff"
declarations, but from what I understand of modprobe.conf, this isn't
possible (yet?) in the 2.6 series releases.

Thanks for any pointers.

Regards,
Tim F.