Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932251Ab2F2QEU (ORCPT ); Fri, 29 Jun 2012 12:04:20 -0400 Received: from ch1ehsobe001.messaging.microsoft.com ([216.32.181.181]:30841 "EHLO ch1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751336Ab2F2QES (ORCPT ); Fri, 29 Jun 2012 12:04:18 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 0 X-BigFish: VS0(zz98dI1521I1432Izz1202h1082kzzz2dh2a8h668h839hd25he5bhf0ah) Message-ID: <4FEDD1F0.1060000@freescale.com> Date: Fri, 29 Jun 2012 11:04:00 -0500 From: Timur Tabi Organization: Freescale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8 MIME-Version: 1.0 To: Scott Wood CC: Zhao Chenhui-B35336 , "linuxppc-dev@lists.ozlabs.org" , Wood Scott-B07421 , "linux-kernel@vger.kernel.org" , "galak@kernel.crashing.org" , Li Yang-R58472 Subject: Re: [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync References: <1340706359-9455-1-git-send-email-chenhui.zhao@freescale.com> <4FEDD07D.3090103@freescale.com> In-Reply-To: <4FEDD07D.3090103@freescale.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginatorOrg: freescale.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 635 Lines: 20 Scott Wood wrote: >> I wonder if it's possible to dynamically generate the compatible >> string by using the SOC name? > > Where are you going to get the SoC name from? Well, that is why I said "I wonder". I'm disappointed that the "cpus" node doesn't help much. You'd think the name of the CPU would be in the CPU node somewhere. -- Timur Tabi Linux kernel developer at Freescale -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/