From: Danny Home Educator <dannyhsdad@gmail.com>
To: linux-mips@linux-mips.org
Subject: QEMU and mips linux
Date: Thu, 11 Aug 2005 12:19:08 -0500 [thread overview]
Message-ID: <1634a4f105081110194fe8603d@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
I've gotten the binutils and gcc per chain tools directions (except for
mips-unknown-linux-gnu i.e., 32 bit version of the compiler, etc.) and built
my own mips cross compiler (I'm on Linux/x86). Then I got the kernel source
from CVS and in the make menuconfig, all I did was change the machine
selection to be QEMU and CPU selection to be R4x00.
Then I hand edited the .config to enable CONFIG_CROSSCOMPILE and then I
built the kernel:
make CROSS_COMPILE=mips-unknown-linux-gnu-
And then I got compile failure with:
LD init/built-in.o
LD .tmp_vmlinux1
arch/mips/kernel/built-in.o: In function `show_cpuinfo':
proc.c:(.text+0x9c88): undefined reference to `get_system_type'
proc.c:(.text+0x9c88): relocation truncated to fit: R_MIPS_26 against
`get_system_type'
make: *** [.tmp_vmlinux1] Error 1
I then edited arch/mips/qemu/q-setup.c to add:
9,14d8
< const char *get_system_type(void)
< {
< return "QEMU MIPS";
< }
<
<
And I was able to build vmlinux. I've gotten qemu-0.7.1, created blank
bios.bin file and when I try to run it, I get:
% qemu-system-mips -kernel vmlinux -m 16 -nographic
(qemu) mips_r4k_init: start
mips_r4k_init: load BIOS '/usr/local/share/qemu/mips_bios.bin' size 131072
And hangs there.
Has anyone else tried qemu with the latest mips linux? Thanks.
[-- Attachment #2: Type: text/html, Size: 1619 bytes --]
next reply other threads:[~2005-08-11 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 17:19 Danny Home Educator [this message]
2005-08-11 17:41 ` QEMU and mips linux Ralf Baechle
2005-08-15 11:07 ` 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=1634a4f105081110194fe8603d@mail.gmail.com \
--to=dannyhsdad@gmail.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.