On Thu, Jan 31, 2013 at 1:24 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, Jan 30, 2013 at 02:07:53PM -0500, Nicolas Pitre wrote:
On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this information may decide what module
to load or how to configure some specific (and processor-depended)
settings or so.
However, since really different SoCs can share
On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this information may decide what module
to load or how to configure some specific (and processor-depended)
settings or
On Wed, Jan 30, 2013 at 1:07 PM, Nicolas Pitre n...@fluxnic.net wrote:
On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this information may decide what module
to load or
On Wed, 30 Jan 2013, Matt Sealey wrote:
On Wed, Jan 30, 2013 at 1:07 PM, Nicolas Pitre n...@fluxnic.net wrote:
On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this
On Wed, Jan 30, 2013 at 02:07:53PM -0500, Nicolas Pitre wrote:
On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this information may decide what module
to load or
On Wed, 30 Jan 2013, Russell King - ARM Linux wrote:
On Wed, Jan 30, 2013 at 02:07:53PM -0500, Nicolas Pitre wrote:
On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace
On 17:01 Wed 30 Jan , Ruslan Bilovol wrote:
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this information may decide what module
to load or how to configure some specific (and processor-depended)
settings