From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2242 invoked by alias); 16 Jun 2011 14:05:57 -0000 Received: (qmail 2230 invoked by uid 22791); 16 Jun 2011 14:05:56 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mtaout01-winn.ispmail.ntl.com (HELO mtaout01-winn.ispmail.ntl.com) (81.103.221.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Jun 2011 14:05:35 +0000 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20110616140533.GXJK10265.mtaout01-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com>; Thu, 16 Jun 2011 15:05:33 +0100 Received: from cog.dallaway.org.uk ([213.106.80.48]) by aamtaout02-winn.ispmail.ntl.com (InterMail vG.3.00.04.00 201-2196-133-20080908) with ESMTP id <20110616140533.FFAJ5924.aamtaout02-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Thu, 16 Jun 2011 15:05:33 +0100 Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id p5GE5Ub0026057; Thu, 16 Jun 2011 15:05:31 +0100 Message-ID: <4DFA0DAA.3000601@dallaway.org.uk> Date: Thu, 16 Jun 2011 14:05:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.24 (X11/20101213) MIME-Version: 1.0 To: Frank Pagliughi CC: John Eigelaar , 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> In-Reply-To: <4DFA071F.4060504@mindspring.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/msg00006.txt.bz2 Hi Frank Frank Pagliughi wrote: > On 03/17/2011 09:13 AM, John Eigelaar wrote: > >> On 16/03/2011 13:16, John Dallaway wrote: >> >>> All >>> >>> There has been a lot of delay in getting AT91SAM9 support into the eCos >>> repository. Far too much delay. I think the best way forward now is to >>> focus on Evgeniy Dushitov's contribution (port for AT91SAM9263) >>> initially: >>> >>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819 >>> >>> This seems sensible because: >>> >>> a) The patches themselves are well abstracted. >>> b) Some people are already using these patches as a baseline for >>> further AT91SAM9 ports. >>> c) There is support for running this port under QEMU, allowing >>> wider testing. >>> >>> I would like to invite everyone with an interest in AT91SAM9 support for >>> eCos to add themselves to the CC list for bug 1000819 and contribute to >>> the review process. Let's make this a community effort. >>> >>> John Dallaway >>> eCos maintainer >>> http://www.dallaway.org.uk/john >> >> John >> We, Keystone Electronic Solutions, have already done a Redboot port >> for the AT91SAM9X512 and AT91SAM9260 devices based on Evgeniy's >> patches if anybody is interested. I have no idea as to how up to date >> our patch is but I will be will to provide our source if anybody is >> interested. >> >> I have also used the port to build some test applications for these >> devices but nothing enterprise level yet. We use the Redboot port as >> boot loader for our Linux platforms. >> >> I have a personal copyright assignment for eCos, but will probably >> need a blanket company wide in order to contribute this work. >> >> Regards >> John Eigelaar > > Hey All, > > What's the latest news on the AT91 chip sets? From Bugzilla it appears > that there will be some reshuffling. I've been away from eCos for a few > years, but am looking to start a project with a legacy AT91 then > hopefully move it to a SAM3 in a few months. Welcome back! The information you quote above is still current and I will try to find some time to push forward with the review of Evgeniy Dushitov's contribution soon. > 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. John Dallaway eCos maintainer http://www.dallaway.org.uk/john