Agreed with waiting to see if someone accepts/rejects him as power kernel maintainer...

On the other hand, humans tend to get possessive of their projects, and titan certainly put a lot of time and effort into the power kernel originally.

Anyway, by the same logic though, lxp's power kernel package wasn't exactly an official power kernel either. It was effectively almost the same, just with cfg80211 compiled as module instead of statically linked or whatever - yet I can install lxp's power kernel debs, and then power kernel settings installs just fine. Just because it's not an official package doesn't mean it can't be packaged so that it accurately represents itself as a sufficient dependency for the power kernel settings package - seeing as how that's what those fields are for and that is exactly true - it is a sufficient dependency for power kernel settings.

One thing I kinda want to see though, semi-off-topic as this is, is a kernel compiled in such a way that the lxp modules are the default wifi modules - or even only wifi modules. Combined with the osso-wlan fix (except using an identical version number field, so that it doesn't break the update process... actually, can't that osso-wlan fix be placed inside the CSSU? Seems like a good place for it. I'll bug someone about that later), there's really not a good reason to stay with the "stock" wifi driver... we've got a bunch of people on the same driver, and as far as I know, the majority do not have any actual bugs from the thing. I remember people complaining early on about it using up battery quickly, but I had no such thing (unless I left the card in monitor mode for hours... but that's a bit self explanatory). I mean, it was lxp's original monitor mode patches that went into the default wifi driver in the power kernel - so the power kernel already did something along these lines in the first place. It's just that lxp's release of the injection mode patches went through such a circumstancially different path, first as a contract for neopwn then through a donation scheme, and only then completely free-to-download, and by then Titan wasn't actually that active anymore.

I mean, right now I have done this by replacing the scripts that Advanced Interface Switcher uses to load/unload the wifi drivers with modified versions (to give full instead of relative paths) of the load.sh/unload.sh scripts. This means I only deal with the stock wifi driver if I manually modprobe it, or right after a reboot (which I usually just unload the wifi driver at that point until I need to use wifi, so mostly I'm already on always-lxp-driver use... It does more when needed than the stock one, and does the same stuff the stock one does without no new problems that I've ever seen... *Shrug*