From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH] dns323: Support for HW rev C1
Date: Wed, 21 Apr 2010 09:37:02 +0100 [thread overview]
Message-ID: <20100421083702.GA11425@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1271838700.2330.143.camel@pasglop>
On Wed, Apr 21, 2010 at 06:31:40PM +1000, Benjamin Herrenschmidt wrote:
> Do you have a hook in ARM for adding something to /proc/cpuinfo where I
> could export the board revision ? Or a "standard" practice to do that ?
That's the purpose of system_rev, originally provided for Netwinders to
identify revision 3, 4, or 5 of the Netwinder hardware.
next prev parent reply other threads:[~2010-04-21 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 8:28 [RFC/PATCH] dns323: Support for HW rev C1 Benjamin Herrenschmidt
2010-04-21 8:31 ` Benjamin Herrenschmidt
2010-04-21 8:37 ` Russell King - ARM Linux [this message]
2010-04-21 8:41 ` Benjamin Herrenschmidt
2010-04-21 14:32 ` Nicolas Pitre
2010-04-21 21:11 ` Benjamin Herrenschmidt
2010-04-21 18:07 ` Lennert Buytenhek
2010-04-21 20:15 ` Russell King - ARM Linux
2010-04-21 21:26 ` Benjamin Herrenschmidt
2010-04-21 21:23 ` Benjamin Herrenschmidt
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=20100421083702.GA11425@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).