On Tue, May 4, 2010 at 2:51 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: > On Tue, May 4, 2010 at 2:11 PM, Pavel Roskin <proski@xxxxxxx> wrote: >> On Tue, 2010-05-04 at 13:44 -0700, Luis R. Rodriguez wrote: >>> It seems there is a reasonable need to find out what version of >>> compat-wireless you have running. This will be a dated thing when >>> based on linux-next but more importantly it will contain the 2.6.3x.y >>> release the release was based on for the stable releases. Any ideas of >>> what filesystem API to use for this, I was thinking maybe a simple >>> sysfs entry for the compat module. Thoughts, preferences? >> >> We could use a read-only parameter of the compat module. Then the >> version would be in /sys/module/compat/parameters/version >> >> Module parameters are visible in sysfs even if the code is compiled into >> the kernel. > > Neat trick thanks for the tip, will give that a shot. Oh wow, and look at that, even if you enable the module as built-in to the kernel you still get the module parameter sysfs file for it. For example I just built-in cfg80211 on my kernel and I still see the ieee80211_regdom module parameter: mcgrof@tux ~ $ lsmod | grep cfg mcgrof@tux ~ $ cat /sys/module/cfg80211/parameters/ieee80211_regdom 00 This is important as some distributions [1] might built-in some stable compat-wireless releases into their older kernel releases. Luis [1] http://src.chromium.org/cgi-bin/gitweb.cgi?p=kernel.git;a=commit;h=73ec6aa6d7ed254d235939bf00ea49cbb6526e6f -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
