public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: David Bonfrer <ecos@bonfrer.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RE: eCos Loader
Date: Thu, 28 Apr 2005 19:06:00 -0000	[thread overview]
Message-ID: <m31x8urjvu.fsf@xl5.calivar.com> (raw)
In-Reply-To: <4270FCB0.50705@bonfrer.com>

David Bonfrer <ecos@bonfrer.com> writes:

> Where did it go wrong in your dynamic loader?
> 
> I now have the relocation types R_386_GLOB_DAT and R_386_JMP_SLOT
> implemented.

It might work for i386, perhaps the elf tools have all the dynamic
support still in place. It didn't work for ARM, MIPS, PowerPC, SH4
etc. The toolchains don't all have the support. It has to work for all
of the architecture we support, not just one. This is why I believe
that object file loading is better than shared libraries, we won't
have to change the toolchains and rewrite the HALs to support this.

-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-04-28 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200504270959.j3R9xYcY010497@router.bonfrer.thuis>
2005-04-28 10:01 ` Nick Garnett
2005-04-28 15:39   ` David Bonfrer
2005-04-28 19:06     ` Nick Garnett [this message]
     [not found] <20050426204513.30E1BE5BC7@ws7-2.us4.outblaze.com>
2005-04-27  0:21 ` David Bonfrer
2005-04-27  8:25   ` Andrew Lunn
2005-04-27 10:28   ` Nick Garnett
2005-04-27 18:06     ` Paul D. DeRocco
2005-04-28 10:06       ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=m31x8urjvu.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=ecos@bonfrer.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).