Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Scott A McConnell <samcconn@cotw.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: loadaddr
Date: Tue, 10 Apr 2001 15:49:40 -0700	[thread overview]
Message-ID: <3AD38E04.696F2085@cotw.com> (raw)
In-Reply-To: 20010410183854.C1932@bacchus.dhis.org

Ralf Baechle wrote:

> On Tue, Apr 10, 2001 at 09:42:02AM -0700, Scott A McConnell wrote:
>
> > What am I doing that is causing the  leading ffffffff in the addresses?
>
> Everything right :-)
>
> 32-bit addresses on MIPS get sign extended into 64-bit addresses.  Binutils
> had related bugs; I assume you switched binutils versions between the
> two builds?

OK, I wasn't sure so I asked. Yes, I changed the tools.

I have been able to build a 2.4.2 kernel but I can't make it run.

I have also steped up to the latest kernel in cvs. Having a bit more trouble
with that:

mipsel-linux-gcc -I /opt/mips/linux-2.4.3/include/asm/gcc -D__KERNEL__
-I/opt/mips/linux-2.4.3/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer  -G 0 -mno-abicalls -fno-pic -mcpu=r5000 -mips2
-Wa,--trap -pipe    -c -o vgacon.o vgacon.c
{standard input}: Assembler messages:
{standard input}:1978: Error: expression too complex
{standard input}:1978: Fatal error: internal Error, line 1823,
../../binutils-patched/gas/config/tc-mips.c
make[3]: *** [vgacon.o] Error 1
make[3]: Leaving directory `/opt/mips/linux-2.4.3/drivers/video'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/opt/mips/linux-2.4.3/drivers/video'
make[1]: *** [_subdir_video] Error 2
make[1]: Leaving directory `/opt/mips/linux-2.4.3/drivers'
make: *** [_dir_drivers] Error 2

  reply	other threads:[~2001-04-10 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 16:42 loadaddr Scott A McConnell
2001-04-10 16:38 ` loadaddr Ralf Baechle
2001-04-10 22:49   ` Scott A McConnell [this message]
2001-04-10 22:17     ` loadaddr Pete Popov

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=3AD38E04.696F2085@cotw.com \
    --to=samcconn@cotw.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.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