On Sat, May 08, 2010 at 04:02:17PM -0700, Jeremy Fitzhardinge wrote: > On 05/08/2010 07:27 AM, Greg KH wrote: > > How would you do that? The symbol resolution will not allow hv_netvsc > > to be loaded without hv_vmbus being around. > > > > Now I do think that just adding the same pci/dmi ids to all of the > > modules is a bit odd, and that something else needs to be done here, but > > at the moment, I can't think of anything better. > > > > Could you make hv_vmbus a real bus implementation, which knows how to > enumerate and probe devices hanging off it? Yes, that's the correct solution here. I originally thought this couldn't be done, but in looking at the code some more, I think it can happen for the network driver, and perhaps some others (but not the block, as both devices work off of the same interface to the hypervisor, so which one do we load?) I'll look into that later if I get the chance. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
