On Thu, Aug 27, 2009 at 10:43 AM, Hin-Tak Leung<hintak.leung@xxxxxxxxx> wrote: > On Thu, Aug 27, 2009 at 8:14 AM, Johannes Berg<johannes@xxxxxxxxxxxxxxxx> wrote: >> On Wed, 2009-08-26 at 16:45 -0700, Luis R. Rodriguez wrote: >> >>> Johannes, did kernels < 2.6.31 have /sys/class/rfkill ? >> >> Yes, but I never understood why that matters. If you've got >> compat-wireless "rfkill" loaded then the original rfkill can't be loaded >> anyway. And their symbols would probably clash anyway if the original is >> built in, in which case you can't use compat. >> >> You haven't renamed cfg80211's sysfs either, so why rfkill? >> >> johannes >> > > There are a couple of wimax drivers which depends on rfkill... or > bluetooth drivers? I think one likely reason is that there are valid > situations or hardware combinations which requires having both of them > loaded. (but that's a whole can of worms ) Argh, I just have a stacktrace after reboot - toshiba_acpi.ko (on a toshiba laptop) requires the stock-kernel rfkill-* symbols, and rfkill won't load because of my modified compat-wireless rfkill_backport.ko which takes up /sys/class/rfkill rather than /sys/class/rfkill_backport . There's your reason from sysfs renaming. I wonder why/how I could unload rfkill.ko earlier, since the *_acpi.ko needs it - maybe I had acpi unloaded as a side-effect also. I guess we'll need hal to treat /sys/class/rfkill_backport like /sys/class/rfkill then - will file a bug somewhere on freedesktop, although I hear hal is on its way out.... -- 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
