From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "", Issuer "NORTEL" (not verified)) by ozlabs.org (Postfix) with ESMTPS id BEF86DDE0E for ; Fri, 1 Aug 2008 06:39:39 +1000 (EST) Message-ID: <489222F9.2020806@nortel.com> Date: Thu, 31 Jul 2008 14:39:21 -0600 From: "Chris Friesen" MIME-Version: 1.0 To: Grant Likely Subject: Re: Board level compatibility matching References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: devicetree-discuss@ozlabs.org, linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Grant Likely wrote: > Doing so should simplify adding new board ports. In many cases it > would just involve dropping in a new .dts file. However, it retains > the flexability of overriding generic code with platform specific > fixups as the need arises. If it makes it easier for board vendors to do a clean port, you get a vote from me. I've seen a large amount of vendor code from that needed a lot of massaging before it would play nice with support for similar boards from other vendors--not to mention how ugly it looked with all the board-specific ifdefs. Chris