Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Rani Assaf <rani@paname.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: Changes to head.S
Date: Sun, 3 Mar 2002 23:19:06 +0100	[thread overview]
Message-ID: <20020303231906.A17147@dea.linux-mips.net> (raw)
In-Reply-To: <20020303230449.K1788@paname.org>; from rani@paname.org on Sun, Mar 03, 2002 at 11:04:49PM +0100

On Sun, Mar 03, 2002 at 11:04:49PM +0100, Rani Assaf wrote:

> On Sun, Mar 03, 2002 at 10:56:31PM +0100, Ralf Baechle wrote:
> > you're observing an alignment problem I suspect you're using a too old
> > egcs 1.1.2 variant.
> 
> Hmm.. It's the redhat one on ftp://oss.sgi.com/pub/linux/mips/:
> 
> Reading specs from
> /opt/Mipsel/bin/../lib/gcc-lib/mipsel-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-99.1)

Just doublechecked it.  The way the alignment guarantee works is through
these two lines in the linker script arch/mips/ld.script.in:

  . = ALIGN(8192);
  .data.init_task : { *(.data.init_task) }

> Is there anything newer/better (I thought  that this is the place were
> H.J. Lu binutils/gcc is stored)?
> 
> BTW, is there any interest in integrating the RC32355 support into the
> main tree?

Sure, send patches to me.

> (I can provide the code that runs on IDT eval boards though
> we're not using them anymore).

I certainly would appreciate somebody to take care of maintaining support
for such eval boards.  By now the number of supported platforms means
that the code for platforms otherwise soon would start to bitrot.

  Ralf

  reply	other threads:[~2002-03-03 23:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-03 17:50 Changes to head.S Rani Assaf
2002-03-03 21:56 ` Ralf Baechle
2002-03-03 22:04   ` Rani Assaf
2002-03-03 22:19     ` Ralf Baechle [this message]
2002-03-03 22:54       ` Rani Assaf
2002-03-03 23:32         ` 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=20020303231906.A17147@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=rani@paname.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