From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27411 invoked by alias); 12 May 2005 06:50:36 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 27368 invoked from network); 12 May 2005 06:50:31 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org with SMTP; 12 May 2005 06:50:31 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1DW7WU-0007dW-00; Thu, 12 May 2005 08:50:18 +0200 Date: Thu, 12 May 2005 06:50:00 -0000 To: Anthony Tonizzo , Nick Garrett Cc: eCos Maintainers Subject: Re: eCos Loader testing Message-ID: <20050512065018.GZ31731@lunn.ch> References: <20050511231903.8E03A3384B@ws7-3.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050511231903.8E03A3384B@ws7-3.us4.outblaze.com> User-Agent: Mutt/1.5.9i From: Andrew Lunn X-SW-Source: 2005-05/txt/msg00004.txt.bz2 On Wed, May 11, 2005 at 06:19:03PM -0500, Anthony Tonizzo wrote: > Andrew: > > Are you interested in testing an eCos loader, before I > submit it? I would like to do some extensive test, since right > now the whole thing is pretty crude. For obvious reasons, > I would like to draft some "expert witnesses" for the job. > > Currently it is working in my PowerPC system. I can compile > libraries into .o files, then load the files from a file > system with dlopen() (I use Savin's FAT on a CardFlash, but JFFS2 > will work as well) and access symbols through dlsym() calls. > The libraries can also make calls to the operating system using > selected functions of your choice. I have compiled a simple > library that holds a disassembler function for the PowerPC and the > threads of the twothread example, for a total of about 40K of code. > The library works flawlessy now. > > There are two architecture dependent function (which ideally > would go in packages/hal): One is to test that a specific > library was written for the proper architecture (endiannes > and all...) and the second does the actual relocation. > > The rest is architecture independent. > > I need direction and plenty of suggestions for improvement. > Any interest? Hi Anthony Unfortunetely i go on Holiday for three weeks starting tomorrow. So i think it would be better for a different maintainer to take a look at your code. The obvious candidate is Nick Garrett. Nick, can you do this? Thanks Andrew