From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamie@jamieiles.com (Jamie Iles) Date: Wed, 2 Mar 2011 15:18:14 +0000 Subject: [PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data In-Reply-To: References: <4D6D9D06.2020204@bluewatersys.com> <4D6D9FC7.1090206@codeaurora.org> <4D6DA290.2010607@bluewatersys.com> <4D6DAA24.3000204@codeaurora.org> <4D6DAE6E.4030701@bluewatersys.com> <4D6DB1B1.4060908@codeaurora.org> <4D6DFE67.3020801@stericsson.com> <20110302113823.GB2728@pulham.picochip.com> Message-ID: <20110302151814.GA2919@pulham.picochip.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Mar 02, 2011 at 03:42:33PM +0100, Linus Walleij wrote: > 2011/3/2 Jamie Iles : > > >> > /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