hi, i've been fighting some xen pciback vs modprobe issues; namely, problems with expected module loading behavior with pciback in kernel as module vs compiled-in. it would be helpful for me to get some clarity as to WHY our kernel config has "CONFIG_XEN_PCIDEV_BACKEND=m" and "CONFIG_XEN_PCIDEV_BACKEND_VPCI=y". i.e., why not BOTH as module or BOTH compiled in? there seems to be some consistent opinion @ xen-devel that compiled-in is arguably 'better' ... in any case, i've found the problems, have a workaound, and will endeavor to write them up in a bugreport. knowing a bit more abt kernel config choice(s) will be helpful. thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org