This is the mail archive of the
ecos-maintainers@sources.redhat.com
mailing list for the eCos project.
Re: eCos Loader testing
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Anthony Tonizzo <atonizzo at lycos dot com>,Nick Garrett <nickg at ecoscentric dot com>
- Cc: eCos Maintainers <ecos-maintainers at ecos dot sourceware dot org>
- Date: Thu, 12 May 2005 08:50:18 +0200
- Subject: Re: eCos Loader testing
- References: <20050511231903.8E03A3384B@ws7-3.us4.outblaze.com>
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