From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Mallon Subject: Re: [PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data Date: Wed, 02 Mar 2011 14:27:34 +1300 Message-ID: <4D6D9D06.2020204@bluewatersys.com> References: <1273587331-24604-1-git-send-email-eduardo.valentin@nokia.com> <20110216115729.GA29817@besouro.research.nokia.com> <4D6B78BF.1020102@stericsson.com> <4D6C7B56.9060109@codeaurora.org> <4D6D9B10.9000606@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D6D9B10.9000606@codeaurora.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Saravana Kannan Cc: ext Nishanth Menon , ext Tony Lindgren , Peter De-Schrijver , ext Linus Walleij , Ambresh , Jouni Hogander , "felipe.balbi@nokia.com" , Lee Jones , Russell King , Jonas ABERG , ext Kevin Hilman , David Brown , Maxime Coquelin , linux-arm-msm@vger.kernel.org, loic.pallardy@stericsson.com, "eduardo.valentin@nokia.com" , Linux-OMAP , "linux-arm-kernel@lists.infradead.org" , Daniel Walker , LKML List-Id: linux-arm-msm@vger.kernel.org On 03/02/2011 02:19 PM, Saravana Kannan wrote: > On 03/01/2011 05:13 PM, Andrei Warkentin wrote: >> On Mon, Feb 28, 2011 at 10:51 PM, Saravana Kannan >> wrote: >> What would an "arch" file mean? The name of the soc platform? > > The arch file would pretty much be the "xxxx" from arch/arm/mach-xxxx or > similar paths. If that info is already available elsewhere, then that > file is not needed. I proposed using the arch since that will remove the > need to maintain some database of unique/reserved names/numbers for each > implementation of socinfo (like the machinetypes list we have). /proc/cpuinfo already tells you what the CPU is, which gives more information than just the architecture name. Why is the arch information even required by userspace? ~Ryan -- Bluewater Systems Ltd - ARM Technology Solution Centre Ryan Mallon 5 Amuri Park, 404 Barbadoes St ryan@bluewatersys.com PO Box 13 889, Christchurch 8013 http://www.bluewatersys.com New Zealand Phone: +64 3 3779127 Freecall: Australia 1800 148 751 Fax: +64 3 3779135 USA 1800 261 2934 From mboxrd@z Thu Jan 1 00:00:00 1970 From: ryan@bluewatersys.com (Ryan Mallon) Date: Wed, 02 Mar 2011 14:27:34 +1300 Subject: [PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data In-Reply-To: <4D6D9B10.9000606@codeaurora.org> References: <1273587331-24604-1-git-send-email-eduardo.valentin@nokia.com> <20110216115729.GA29817@besouro.research.nokia.com> <4D6B78BF.1020102@stericsson.com> <4D6C7B56.9060109@codeaurora.org> <4D6D9B10.9000606@codeaurora.org> Message-ID: <4D6D9D06.2020204@bluewatersys.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 03/02/2011 02:19 PM, Saravana Kannan wrote: > On 03/01/2011 05:13 PM, Andrei Warkentin wrote: >> On Mon, Feb 28, 2011 at 10:51 PM, Saravana Kannan >> wrote: >> What would an "arch" file mean? The name of the soc platform? > > The arch file would pretty much be the "xxxx" from arch/arm/mach-xxxx or > similar paths. If that info is already available elsewhere, then that > file is not needed. I proposed using the arch since that will remove the > need to maintain some database of unique/reserved names/numbers for each > implementation of socinfo (like the machinetypes list we have). /proc/cpuinfo already tells you what the CPU is, which gives more information than just the architecture name. Why is the arch information even required by userspace? ~Ryan -- Bluewater Systems Ltd - ARM Technology Solution Centre Ryan Mallon 5 Amuri Park, 404 Barbadoes St ryan at bluewatersys.com PO Box 13 889, Christchurch 8013 http://www.bluewatersys.com New Zealand Phone: +64 3 3779127 Freecall: Australia 1800 148 751 Fax: +64 3 3779135 USA 1800 261 2934