Thread (38 messages) 38 messages, 10 authors, 2011-03-03

[PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data

From: Jamie Iles <hidden>
Date: 2011-03-02 15:18:14
Also in: linux-arm-msm, linux-omap

On Wed, Mar 02, 2011 at 03:42:33PM +0100, Linus Walleij wrote:
2011/3/2 Jamie Iles [off-list ref]:
quoted
quoted
quoted
/sys/devices/system/soc/
/sys/devices/system/soc/unique_id<- Unified way to export an ID for all machs
Arbitrary number of bits? Some will have a 64-bit ID, some will have 32-bit
etc.

Should we say it's a hex string of 64 bits?
Could we provide hooks for the platform that takes the buffer and length
and let the platform do the snprintf()? ?Our devices have a 128-bit
serial number and I'm sure there must be others.
Isn't it better to just make it 64-bit so that apps can always parse it,
and then you can have your high-res numbers under mach?

If there is no solid ABI for this there is no point to make it
generic under /soc/unique_id at all.
I guess I'd argue that a arbitrary length hex string could be considered 
as a solid ABI but you're right that it's probably more important to get 
something out there and I'm probably being too picky, so apologies!

Jamie
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help