From: martinwguy@gmail.com (Martin Guy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ep93xx: added chip revision reading function
Date: Sat, 20 Mar 2010 19:48:21 +0000 [thread overview]
Message-ID: <56d259a01003201248r37c238fck9499bab795fda7dd@mail.gmail.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B02708426976368B755D3@AUSP01VMBX24.collaborationhost.net>
On 3/20/10, H Hartley Sweeten <hartleys@visionengravers.com> wrote:
> The ep93xx unique serial number, also called the MaverickCrunch ID, can
> be found in the Sercurity registers. There are actually two of them.
> One is a 32-bit unique ID the other is a 128-bit random ID. Random
> meaning random per chip not per boot since it is created by means of
> fuseable links on the chip that are set during manufacture. These
> also are not currently exposed to the user in any fashion.
>
> I had submitted a patch previously that adds an architecture specific
> extension to /proc/cpuinfo that would allow exposing this information
> on the ep93xx. The same extension could be used on platforms like the
> TS-7200 to show the jumper settings on the board.
>
> If there is any interest I will re-post that patch series.
Thanks.
Yes, being able to see the unique ID is certainly useful. I use this
in userspace to set a different MAC address on each board for DHCP
purposes in a classroom of otherwise identical diskless X terminals
based on this chip.
M
next prev parent reply other threads:[~2010-03-20 19:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 16:59 [PATCH v2 0/3] spi: driver for Cirrus EP93xx SPI controller Mika Westerberg
2010-03-18 17:00 ` [PATCH v2 1/3] spi: implemented " Mika Westerberg
2010-03-18 17:00 ` [PATCH v2 2/3] ep93xx: added chip revision reading function Mika Westerberg
2010-03-18 17:00 ` [PATCH v2 3/3] ep93xx: SPI driver platform support code Mika Westerberg
2010-03-18 17:27 ` [spi-devel-general] [PATCH v2 2/3] ep93xx: added chip revision reading function H Hartley Sweeten
2010-03-25 9:06 ` Mika Westerberg
2010-03-25 17:20 ` H Hartley Sweeten
2010-03-26 15:40 ` Martin Guy
2010-03-20 18:07 ` Martin Guy
2010-03-20 18:25 ` Daniel Mack
2010-03-20 18:40 ` Martin Guy
2010-03-20 19:31 ` H Hartley Sweeten
2010-03-20 19:48 ` Martin Guy [this message]
2010-03-20 18:31 ` Mika Westerberg
2010-03-20 19:42 ` H Hartley Sweeten
2010-03-21 18:45 ` Mika Westerberg
2010-03-25 13:49 ` [PATCH v2 1/3] spi: implemented driver for Cirrus EP93xx SPI controller Martin Guy
2010-03-25 18:43 ` Mika Westerberg
2010-04-01 0:15 ` Martin Guy
2010-04-01 3:00 ` Ryan Mallon
2010-04-01 6:26 ` Mika Westerberg
2010-04-06 5:44 ` Mika Westerberg
2010-04-06 12:50 ` Martin Guy
2010-04-06 18:18 ` Mika Westerberg
2010-04-06 21:28 ` Martin Guy
2010-04-09 17:56 ` Martin Guy
2010-04-09 18:08 ` Martin Guy
2010-04-10 15:54 ` Mika Westerberg
2010-04-11 14:24 ` Martin Guy
2010-04-12 10:03 ` Martin Guy
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=56d259a01003201248r37c238fck9499bab795fda7dd@mail.gmail.com \
--to=martinwguy@gmail.com \
--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).