From: Ralf Baechle <ralf@linux-mips.org>
To: Kurt Schwemmer <kurts@vitesse.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Cross compile kernel w/ buildroot toolchain
Date: Mon, 13 Mar 2006 20:56:30 +0000 [thread overview]
Message-ID: <20060313205630.GA17247@linux-mips.org> (raw)
In-Reply-To: <389E6A416914954182ECDFCD844D8269434FBF@MX-COS.vsc.vitesse.com>
On Mon, Mar 13, 2006 at 01:39:53PM -0700, Kurt Schwemmer wrote:
> I got 2.6.15 "a while back" (>1 month).
>
> I'll try getting the most recent source. Sorry, I avoided this due to my
> company blocking rsync and thus making it a pain to get the sources...
The reason your case is odd is that the kernel only uses a single
jr.hb instruction which is in the instruction_hazard() macro in
include/asm-mips/hazards.h. This macro first of all is a gcc inline
assembler macro and also wraps the jr.hb instruction between
.set mips64r2 ... .set mips0, so you should never ever get an error
message. And you're getting an error message for entry.S, an assembler
file. Seems you must have done some not so kosher changes to that tree?
Ralf
next prev parent reply other threads:[~2006-03-13 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 20:39 Cross compile kernel w/ buildroot toolchain Kurt Schwemmer
2006-03-13 20:39 ` Kurt Schwemmer
2006-03-13 20:45 ` Ralf Baechle
2006-03-13 20:56 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 22:03 Kurt Schwemmer
2006-03-13 22:03 ` Kurt Schwemmer
2006-03-13 21:07 Kurt Schwemmer
2006-03-13 21:07 ` Kurt Schwemmer
2006-03-13 21:16 ` David Daney
2006-03-13 21:25 ` Thiemo Seufer
2006-03-13 20:17 Kurt Schwemmer
2006-03-13 20:17 ` Kurt Schwemmer
2006-03-13 20:33 ` Ralf Baechle
2006-03-13 20:48 ` Thiemo Seufer
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=20060313205630.GA17247@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kurts@vitesse.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.