All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: KokHow.Teh@infineon.com
Cc: linux-mips@linux-mips.org
Subject: Re: Arch/mips/kernel/vpe.c
Date: Sat, 5 Jan 2008 17:05:46 +0000	[thread overview]
Message-ID: <20080105170546.GG22809@networkno.de> (raw)
In-Reply-To: <31E09F73562D7A4D82119D7F6C1729860320EADA@sinse303.ap.infineon.com>

KokHow.Teh@infineon.com wrote:
> Hi;
> 	I am working on MIPS34KC with APRP kernel and I use uclibc
> gccc-3.4.4 to build applications to run on VPE1. The present
> implementation of VPE loader is limited to a few relocation types which
> are used when mips_sde compiler is used. However, the relocatable binary
> churn out from my uclibc-gcc-3.4.4 has more other relocation types than
> the ones defined in arch/mips/kernel/vpe.c, especially those with GOT
> relocation types. I have taken a look at the System V ABI Third Edition
> but if anybody has any code reference and pointers to how each
> relocation types should be implemented in C-code, it would be very
> helpful.

The most likely place to look at would be the binutils source code. That
said, you can probably get away without enhancing the VPE loader by using
  a) fully linked (non-relocatable) executables, or
  b) non-PIC code, like SDE does

Regardless of your choice, you will have to make sure the uclibc toolchain
doesn't use any libraries which need Linux facilities, as the bare-metal
environment on VPE1 doesn't provide them. For that reason I believe you
are better of with SDE or a similiar mips*-elf configured toolchain.


Thiemo

  reply	other threads:[~2008-01-05 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 11:29 Arch/mips/kernel/vpe.c KokHow.Teh
2008-01-05 11:29 ` Arch/mips/kernel/vpe.c KokHow.Teh
2008-01-05 17:05 ` Thiemo Seufer [this message]
2008-01-07 16:18   ` Arch/mips/kernel/vpe.c Ralf Baechle

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=20080105170546.GG22809@networkno.de \
    --to=ths@networkno.de \
    --cc=KokHow.Teh@infineon.com \
    --cc=linux-mips@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.