linux-kernel - Re: [2.6.24 patch] restore blackfin HARDWARE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200712291428.50359.rgetz@blackfin.uclinux.org>
Date:	Sat, 29 Dec 2007 14:28:50 -0500
From:	Robin Getz <rgetz@...ckfin.uclinux.org>
To:	"Mathieu Desnoyers" <mathieu.desnoyers@...ymtl.ca>
Cc:	"Adrian Bunk" <bunk@...nel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Randy Dunlap" <randy.dunlap@...cle.com>, bryan.wu@...log.com,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.24 patch] restore blackfin HARDWARE_PM support

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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/