[lkml]   [2004]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: modprobe + request_module() deadlock
    Gerd Knorr wrote:

    >> Well, how about to add a new marker in the driver code such as
    >> MODULE_DEPENDS_ON("somemodule");
    >> so that depmod can pick it up?
    > Wouldn't work for me as this isn't static. saa7134 has to look at the
    > hardware, then decide whenever it should load saa7134-empress,
    > saa7134-dvb or none of them.
    > On the other hand I don't depend on request_module() waiting for the
    > modprobe being finished. So maybe we can solve that with a
    > request_module_async()?

    Unfortunately I am not an expert here, but wouldn't it be sufficient to
    export in sysfs the information needed to distinguish between those two
    saa7134-* modules, and then submit a new agent to linux-hotplug-devel? Then
    hotplug will take care of loading the correct module (and hotplug is always
    called asynchronously).

    Alexander E. Patrakov

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:08    [W:0.019 / U:0.476 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site