From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] SoC name and revision in /proc/cpuinfo
Date: Fri, 24 Sep 2010 15:06:52 +0100 [thread overview]
Message-ID: <20100924140652.GA14809@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100924135356.GA17651@game.jcrosoft.org>
On Fri, Sep 24, 2010 at 03:53:56PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> Hi Russell,
>
> On AT91 for some userland library we need to known the cpu model and revision
> so I'd like to known if it's ok with you to extend it?
>
> as
> cpu familly: at91
> cpu type: at91sam9g20
> cpu revision: 1.1
You're mixing up the CPU with the SoC. The CPU is what's in the core of
the SoC and has no peripherals etc. The SoC is the entire chip. "Central
Processing Unit." "System on a Chip."
I'd much rather see SoC information kept separate from the CPU information.
next prev parent reply other threads:[~2010-09-24 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 13:53 [RFC] SoC name and revision in /proc/cpuinfo Jean-Christophe PLAGNIOL-VILLARD
2010-09-24 14:06 ` Russell King - ARM Linux [this message]
2010-09-24 14:42 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-24 19:23 ` Bryan Huntsman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100924140652.GA14809@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).