Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756067Ab0FTR5x (ORCPT ); Sun, 20 Jun 2010 13:57:53 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:46293 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752808Ab0FTR5v convert rfc822-to-8bit (ORCPT ); Sun, 20 Jun 2010 13:57:51 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:reply-to:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; b=KzTlGTS5qRYUEAS407kjtmxeDjKvHGoEbhB13LFkucU47zHRsKSfHnG6PnOikH2V6d 4Zg22g6cOs/O+h4c0FcrC0CgeAEPM7LnOEvbYYzq8/b8CGa5fcLhYV8HerIDVxvD8dLu 4H21/eWg+SmaMij/qJix3kAtxrSgBt0V4nZA8= From: Florian Fainelli Reply-To: Florian Fainelli To: Thomas Bogendoerfer Subject: Re: [PATCH v2 00/26] Add support for the Ingenic JZ4740 System-on-a-Chip Date: Sun, 20 Jun 2010 19:57:54 +0200 User-Agent: KMail/1.13.3 (Linux/2.6.34-1-amd64; KDE/4.4.4; x86_64; ; ) Cc: "Lars-Peter Clausen" , Ralf Baechle , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, Graham Gower References: <1276924111-11158-1-git-send-email-lars@metafoo.de> <4C1E467D.5030204@metafoo.de> <20100620170111.GA8650@alpha.franken.de> In-Reply-To: <20100620170111.GA8650@alpha.franken.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Message-Id: <201006201957.56978.florian@openwrt.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1342 Lines: 28 Hi, Le Sunday 20 June 2010 19:01:11, Thomas Bogendoerfer a ?crit : > On Sun, Jun 20, 2010 at 06:49:01PM +0200, Lars-Peter Clausen wrote: > > different to JZ4750 and JZ4760. So JZ47xx wont fit either. > > Right now there is no practical use to moving things around, and there > > wont be until somebody who can actually test it starts adding support > > for a different JZ47XX SoC. > > great, I like such attitude:-( I have to agree with Thomas here, if your concern is about the naming, then just have a look at the vendor sources and find similarities for what is worth being named JZ47XX and what deserves a name which is more specific. Also, it is much easier to do that factoring job now instead of when there will be 3 or more flavors of that SoC to be supported. Take a look at BCM63xx for instance, it is named like that because it supports 4 different versions of the family SoC, even though the internals of the SoC have been varying a lot, still we support it with a single kernel and what is really family specific is named accordingly from what is chip-specific. -- Florian -- 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/