From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Wed, 25 Sep 2013 13:02:34 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1]:48200 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S6817090Ab3IYLCcasMso (ORCPT ); Wed, 25 Sep 2013 13:02:32 +0200 Received: from scotty.linux-mips.net (localhost.localdomain [127.0.0.1]) by scotty.linux-mips.net (8.14.7/8.14.4) with ESMTP id r8PB2VYd026364; Wed, 25 Sep 2013 13:02:31 +0200 Received: (from ralf@localhost) by scotty.linux-mips.net (8.14.7/8.14.7/Submit) id r8PB2Vxr026363; Wed, 25 Sep 2013 13:02:31 +0200 Date: Wed, 25 Sep 2013 13:02:31 +0200 From: Ralf Baechle To: "Maciej W. Rozycki" Cc: linux-mips@linux-mips.org Subject: Re: [PATCH] MIPS: Tell R4k SC and MC variations apart Message-ID: <20130925110231.GM31185@linux-mips.org> References: <20130924084845.GA21257@linux-mips.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 37970 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Wed, Sep 25, 2013 at 12:37:42AM +0100, Maciej W. Rozycki wrote: > > My reservations may have been about userland reading /proc/cpuinfo and > > looking at the CPU type. Some software may know how to handle the > > PC/SC variants but not the MC versions. But this seems to be a fairly > > weak concern - and I trust you checked gcc's parsing of /proc/cpuinfo. > > Actually I wasn't actually aware GCC's got /proc/cpuinfo-based native > arch support for the MIPS target these days, thanks for the hint. > > I have now checked the relevant source file and support is pretty weak > there, only half a dozen processors are recognised and no R4k model is > among them. In any case strstr is used to check for matches there so I'd > expect strings like "R4000" or "R4400" without a further suffix to be > chosen. It'd be worth a change in particular for users how higher end CPUs and enhanced ISAs such as Octeons. Or should we just default to O32 w/ MIPS I + LL/SC as the MIPS Esperanto forever ... Ralf