Comment 15 for bug 275692

I think madwifi wont be kept for much longer as ath5k / ath9k are supposed to replace it entirely pretty soon (perhaps already in 2.6.28); hence linux-restricted-common seems like the good place to ship the file. I think it's easier to think of changing the value in lrm if we update to a madwifi which doesn't need this hack, but this is very unlikely anyway.

I didn't want to add the file to pm-utils because it makes us pile hardware specific files to parse on suspend/resume which are already slowish on some devices when using pm-utils. (I see it a bit like init script proliferation slowing down boot.)