On 3/4/10, Ozan Çağlayan <ozan@xxxxxxxxxxxxx> wrote: > Jon Masters wrote: >> On Tue, 2010-03-02 at 19:55 +0200, Ozan Çağlayan wrote: >>> Jon Masters wrote: >>>> On Thu, 2010-02-25 at 17:11 +0000, Alan Jenkins wrote: >>>> >>>>> Next on my list was a prototype I started to make Andreas' softdep code >>>>> >>>>> a bit simpler. >>>> Don't worry too much about my other mail, I see the three softdep >>>> branches in your tree - I fetched them to take a look. More doc cleanups >>>> in the dev branch now, and a fix for the locking problem coming shortly. >>> Offtopic: Is there any doc/webpage/README about "what a softdep is?" >>> somewhere? >> >> So you never really got a good answer. Sorry about that, I'm busy doing >> lots of cleanup work at the moment and getting things more organized. >> Anyway, the point behind softdeps is to express dependencies that are >> not otherwise explicit through the modpost scripts and depmod figuring >> out one module should load before another. Think of e.g. some module >> providing optional sysctls, a sound synth module not directly required >> but basically very useful when you load core sound pieces, etc. These >> are just abstract examples of the kinds of hints that might happen. > > Hey thanks for the answer. So it's like the "Suggests"/"Recommends" relation > in the popular package management > systems. Sounds good and useful. > > BTW, one thing that I'm missing from m-i-t is to unload a module-chain by > one command e.g. when we load snd-hda-intel > it brings a lot of dependencies but we're not able to remove them all at > once. I think rmmod should provide a parameter > for traversing the dependency chain and rmmoding the modules in the > ascending order of reference counts. > > That's what I'm doing actually from shell. Try "modprobe -r" :-). Regards Alan -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
