From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10691 invoked by alias); 16 Jun 2011 14:29:08 -0000 Received: (qmail 10675 invoked by uid 22791); 16 Jun 2011 14:29:07 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from elasmtp-dupuy.atl.sa.earthlink.net (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Jun 2011 14:28:54 +0000 Received: from [68.114.62.146] (helo=[192.168.0.5]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1QXDYv-0004vs-QR; Thu, 16 Jun 2011 10:28:49 -0400 Message-ID: <4DFA1320.7090500@mindspring.com> Date: Thu, 16 Jun 2011 14:29:00 -0000 From: Frank Pagliughi User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: John Eigelaar CC: John Dallaway , eCos Development List Subject: Re: eCos on AT91SAM9 - call to action References: <4D809BF2.6040205@dallaway.org.uk> <4D8208F0.5010500@kses.net> <4DFA071F.4060504@mindspring.com> <4DFA0DAA.3000601@dallaway.org.uk> <1308233778.22353.4.camel@hp-study> In-Reply-To: <1308233778.22353.4.camel@hp-study> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 4d82f965df0f6dd9e3f977c6d1ea408f0a9da525759e26541597f0f385695824c3d28f11d74f596278c914e01878b5fc350badd9bab72f9c350badd9bab72f9c 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-06/txt/msg00009.txt.bz2 On 06/16/2011 10:16 AM, John Eigelaar wrote: >>> Has anyone started work on the SAM3's? >>> How can I help? >> I am not aware of anyone working with eCos on AT91SAM3 hardware. There >> are existing Cortex-M variant ports for eCos on LM3S8xx, LPC17xx and >> STM32 processor families so I would expect variant support for AT91SAM3 >> to be fairly straightforward. Hopefully some of the existing AT91 >> drivers can be reused for AT91SAM3. >> >> I am sure that others within the eCos community will be interested in >> variant support for AT91SAM3. Be sure to let us all know if/when you >> start work on this. > > We, Keystone Electronic Solutions, did a port for the AT91SAM3U. The > port was completed and was using most of the AT91 drivers from the SAM7 > family. We have, however, decided to use an STM32 part instead of the > SAM3. The port is still available if anybody is interested > Errr. Yeah. I guess you could send it to me. But maybe it would be better to formally submit it to eCos, and I can jump on it to test, validate, and patch if necessary. Plus I'm looking more to the SAM3S for this project, so could use your port to expand the offerings to a couple different SAM3 chip sets. But I suppose the sooner the better. I'm also considering the STM32 for the upgrade, so better to get this done before I change my mind, like you did! Thanks, Frank