From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29052 invoked by alias); 15 Dec 2011 16:57:23 -0000 Received: (qmail 29042 invoked by uid 22791); 15 Dec 2011 16:57:21 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from r-finger.com (HELO r-finger.com) (178.79.160.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Dec 2011 16:57:09 +0000 Received: from [192.168.0.2] (host86-134-170-145.range86-134.btcentralplus.com [86.134.170.145]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by r-finger.com (Postfix) with ESMTPSA id 58D129C08 for ; Thu, 15 Dec 2011 16:57:08 +0000 (GMT) Message-ID: <4EEA26E3.60707@r-finger.com> Date: Thu, 15 Dec 2011 16:57:00 -0000 From: Tomas Frydrych User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Icedove/3.1.13 MIME-Version: 1.0 To: ecos-devel@ecos.sourceware.org Subject: Adding Kinetis boards Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2011-12/txt/msg00005.txt.bz2 Hi, I am looking at adding the Kwikstik to the current Kinetis boards, and I am wondering what would be the best way to approach this. Currently there are two Kinetis boards, the TWR-K40X256 and TWR-K60N512, with the directory structure something like this: kinetis/var/... - Generic Kinetis code kinetis/twr_k40x256 - K40 and twr-k40 code kinetis/twr_k60x256 - K60 and twr-k60 code Kwikstik is based on the same MCU as the twr-k40x256, so it needs the same MCU-specific code as the twr-k40x256 board, which I think is all, or nearly all of the code currently under the twr_k40x256 directory. I initially thought I'd just clone twr_k40x256 into a new kwikstik directory, but that's probably not the best approach for maintainability. I am thinking it might be better to split out the generic K40 code so it can be shared between distinct boards, but I am not sure where to split this to: should there be a separate k40x256 subdirectory and a corresponding package that the twr_k40x256 requires? Or is there a better way of approaching this altogether? Many thanks in advance, Tomas