public inbox for
 help / color / mirror / Atom feed
From: Andrew Lunn <>
To: Anthony Tonizzo <>,
	Nick Garrett <>
Cc: eCos Maintainers <>
Subject: Re: eCos Loader testing
Date: Thu, 12 May 2005 06:50:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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? 


       reply	other threads:[~2005-05-12  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2005-05-12  6:50 ` Andrew Lunn [this message]
2005-05-12  8:51   ` Nick Garnett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).