From: Tony Lindgren <tony@atomide.com>
To: Eduardo Valentin <eduardo.valentin@nokia.com>
Cc: ext Kevin Hilman <khilman@deeprootsystems.com>,
"De-Schrijver Peter (Nokia-D/Helsinki)"
<Peter.De-Schrijver@nokia.com>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 4/4] OMAP3: PM: export chip IDCODE, Production ID and Die ID
Date: Tue, 27 Apr 2010 07:51:21 -0700 [thread overview]
Message-ID: <20100427145121.GY7225@atomide.com> (raw)
In-Reply-To: <20100427101321.GC332@besouro.research.nokia.com>
* Eduardo Valentin <eduardo.valentin@nokia.com> [100427 03:08]:
> Hello Tony,
>
> On Mon, Apr 26, 2010 at 08:28:12PM +0200, ext Tony Lindgren wrote:
> > * Eduardo Valentin <eduardo.valentin@nokia.com> [100426 01:20]:
> > > +
> > > + /* Append OMAP3 IDCODE, Production ID and Die ID to system_soc_info */
> > > + sz = strlen(system_soc_info);
> > > + snprintf(system_soc_info + sz, SYSTEM_SOC_INFO_SIZE - sz,
> > > + "\n\tIDCODE\t: %08x\n\tPr. ID\t: %08x %08x %08x %08x\n"
> > > + "\tDie ID\t: %08x %08x %08x %08x\n",
> > > + read_tap_reg(OMAP_TAP_IDCODE),
> > > + read_tap_reg(OMAP_TAP_PROD_ID_0),
> > > + read_tap_reg(OMAP_TAP_PROD_ID_1),
> > > + read_tap_reg(OMAP_TAP_PROD_ID_2),
> > > + read_tap_reg(OMAP_TAP_PROD_ID_3),
> > > + read_tap_reg(OMAP_TAP_DIE_ID_0),
> > > + read_tap_reg(OMAP_TAP_DIE_ID_1),
> > > + read_tap_reg(OMAP_TAP_DIE_ID_2),
> > > + read_tap_reg(OMAP_TAP_DIE_ID_3));
> > > }
> > >
> > > /*
> >
> > We should not expose the Die ID info unless specifically compiled in
> > with some Kconfig option. Please search for "pentium serial number privacy"
> > or similar.
>
> Yeah, I remember now that you actually have already asked to do it. I'll
> repost this series again with this change. It will couple with the same
> protection mechanism there is for x86 pn. it is not a compilation config,
> but a kernel parameter:
>
>
> static int __init x86_serial_nr_setup(char *s)
> {
> disable_x86_serial_nr = 0;
> return 1;
> }
> __setup("serialnumber", x86_serial_nr_setup);
Sounds good to me.
Tony
prev parent reply other threads:[~2010-04-27 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 8:24 [PATCH 0/4] Adding soc related info into /proc/cpuinfo Eduardo Valentin
2010-04-26 8:24 ` [PATCH 1/4] ARM: Introduce SoC Info " Eduardo Valentin
2010-04-26 8:24 ` [PATCH 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 " Eduardo Valentin
2010-04-26 8:24 ` [PATCH 3/4] mach-omap1: Add SoC info data for OMAP into /proc/cpuinfo1 Eduardo Valentin
2010-04-26 8:24 ` [PATCH 4/4] OMAP3: PM: export chip IDCODE, Production ID and Die ID Eduardo Valentin
2010-04-26 8:33 ` Shilimkar, Santosh
2010-04-26 8:35 ` Shilimkar, Santosh
2010-04-26 18:28 ` Tony Lindgren
2010-04-27 10:13 ` Eduardo Valentin
2010-04-27 14:51 ` Tony Lindgren [this message]
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=20100427145121.GY7225@atomide.com \
--to=tony@atomide.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=eduardo.valentin@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.