From: John Miller <jamiller1110@cox.net>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Instruction error with cache opcode
Date: Sun, 14 May 2006 16:14:48 -0400 [thread overview]
Message-ID: <44678FB8.4070104@mountolympos.net> (raw)
In-Reply-To: <009501c6778e$947c3ff0$10eca8c0@grendel>
>
> Have you got your sources properly installes so that include/asm is
> a symlink to include/asm-mips?
Yes, include/asm is symlinked to include/asm-mips. Let me provide a
little more detail. I did not want to modify head.S (since this is a
kernel file) but I noticed an undefined macro,
kernel_entry_setup # cpu specific setup
and the include #include <kernel-entry-init.h>
I found at least one kernel-entry-init.h file in a hardware specific
directory so I made my own under include/asm-mips/rb500 and added a line
to the Makefile. Within kernel-entry-init.h are the include for
cacheops.h as well as the macro definition. regdef.h is included in
head.s.
> I've done the experiment at my end,
> and it builds just fine so long as regdef.h and cacheops.h are really
> on the include path of the compilation. If they're not, I get:
>
> [kevink@cthulhu tmp]$ mipsel-linux-gcc -I ~/smtchead/include -c cacheop.S
> cacheop.S: Assembler messages:
> cacheop.S:4: Error: Instruction cache requires absolute expression
> cacheop.S:4: Error: Instruction cache requires absolute expression
> cacheop.S:4: Error: illegal operands `cache'
>
>
Well, it looks like I am missing something somewhere, just need to pin
down what I did wrong.
next prev parent reply other threads:[~2006-05-14 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 13:51 Instruction error with cache opcode John Miller
2006-05-14 13:51 ` John Miller
2006-05-14 14:17 ` Kevin D. Kissell
2006-05-14 14:17 ` Kevin D. Kissell
2006-05-14 18:39 ` John Miller
2006-05-14 19:42 ` Kevin D. Kissell
2006-05-14 19:42 ` Kevin D. Kissell
2006-05-14 20:14 ` John Miller [this message]
2006-05-14 23:29 ` Thiemo Seufer
2006-05-15 1:06 ` Atsushi Nemoto
2006-05-15 1:35 ` John Miller
2006-05-15 1:38 ` John Miller
2006-05-15 1:38 ` John Miller
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=44678FB8.4070104@mountolympos.net \
--to=jamiller1110@cox.net \
--cc=kevink@mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox