Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: Ralf Baechle <ralf@linux-mips.org>, mipslist <linux-mips@linux-mips.org>
Subject: Re: [PATCH]: for poor sools with old I2 & 64 bits kernel
Date: 19 Dec 2002 22:40:55 +0100	[thread overview]
Message-ID: <m2r8cdhel4.fsf@demo.mitica> (raw)
In-Reply-To: <20021219212817.GL449@rembrandt.csv.ica.uni-stuttgart.de>

>>>>> "thiemo" == Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> writes:

thiemo> Juan Quintela wrote:
>> >>>>> "thiemo" == Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> writes:
>> 
thiemo> Juan Quintela wrote:
>> >> 
>> >> Hi
>> >> this small patch made possible to compile a 64bit kernel for
>> >> people that have old proms that only accept ecoff.  As usual
>> >> stolen from the 32 bits version.
>> >> 
>> >> The easiest way is creating the file in arch/mips/boot,
>> >> otherwise we need to copy elf2ecoff.c to mips64.
>> 
thiemo> Sorry, but I plainly doubt you have tested this.
>> 
thiemo> I tried such a method today, and elf2ecoff failed to work on ELF64 files.
thiemo> Maybe a recent enough objcopy is the better choice for this purpose.
>> 
>> I tested it and it works :)

thiemo> How is this possible, given that elf2ecoff uses Elf32_* variables to
thiemo> process the ELF file? elf2ecoff might be bad enough at error checking
thiemo> to produce some binary garbage.

>> Notice that I am using egcs for MIPS64 as I am not able to compile the
>> kernel with gcc-3.2 :(

thiemo> I don't think this is compiler dependent. :-)

from  arch/mips64/Makefile:

#
# Some machines like the Indy need 32-bit ELF binaries for booting purposes.
# Other need ECOFF, so we build a 32-bit ELF binary for them which we then
# convert to ECOFF using elf2ecoff.
#
ifdef CONFIG_BOOT_ELF32
GCCFLAGS += -Wa,-32 $(shell if $(CC) -Wa,-mgp64 -c -o /dev/null -xc /dev/null > /dev/null 2>&1; then echo "-Wa,-mgp64"; fi)
LINKFLAGS += -T arch/mips64/ld.script.elf32
endif

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  reply	other threads:[~2002-12-19 21:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 20:04 [PATCH]: for poor sools with old I2 & 64 bits kernel Juan Quintela
2002-12-19 21:01 ` Thiemo Seufer
2002-12-19 21:11   ` Juan Quintela
2002-12-19 21:28     ` Thiemo Seufer
2002-12-19 21:40       ` Juan Quintela [this message]
2002-12-19 22:22         ` Thiemo Seufer
2002-12-20  2:44 ` Ralf Baechle
2002-12-20 14:48   ` Juan Quintela
2002-12-21 18:55     ` Maciej W. Rozycki
2002-12-21 20:07       ` Juan Quintela
2002-12-21 21:28         ` Maciej W. Rozycki
2002-12-21 22:14           ` Juan Quintela
2002-12-21 22:49             ` Maciej W. Rozycki

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=m2r8cdhel4.fsf@demo.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox