On Mon, Nov 1, 2010 at 9:59 PM, Eliad Peller <eliad@xxxxxxxxxx> wrote: >>> add RECOVER testmode command. >>> this command triggers a recovery sequence (by enqueueing a recovery_work). >>> >>> Signed-off-by: Eliad Peller <eliad@xxxxxxxxxx> >>> --- >> >> So, the point of this patch is to allow hardware recovery from the >> userspace? In what kind of scenario do you need this? >> > > yes. > it's mainly for testing (or if we want to recover manually for some reason). > this is why i implemented it as a testmode command. Isn't testmode for features used during regulatory testing, that the user should be unable to access to ensure further regulatory compliance? > > i added it after observing some recovery issues (until applying > Juuso's "wl1271: Check interface state in op_* functions" :) ) > > Eliad. > -- > 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 > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) -- 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