On Sat 29 Dec 2007 01:23, Mathieu Desnoyers pondered: > Ok, and do we really need to make HARDWARE_PM a tristate ? I see that > part of it must be compiled into the kernel in core .S files. Does it > really make sense for it to be a module ?
I don't think so. > Also, op_model_bf533.c sits in the arch/blackfin/oprofile directory, > (built if HARDWARE_PM is y or m) but depends on PROFILING, not OPROFILE. > Is HARDWARE_PM useful at all without OPROFILE ? There was an out of tree patch that was floating around that gave people a sys or proc interface to the hardware registers - since oprofile doesn't work that well on a bash-less system. I don't think I will have time to look at the patch over the weekend, but will do after Jan 1. -Robin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/