From: Antony Pavlov <antonynpavlov@gmail.com>
To: Nancy <nancydreaming@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] About QEMU for MIPS
Date: Tue, 29 Oct 2013 22:43:38 +0400 [thread overview]
Message-ID: <20131029224338.5b70ae229d094a6ba17e757d@gmail.com> (raw)
In-Reply-To: <CADdyJm=ZOOqopmx9RRY=eAKOBrR1FXFVUK5kn-=Keh0BBdPB_A@mail.gmail.com>
On Tue, 29 Oct 2013 21:09:30 +0800
Nancy <nancydreaming@gmail.com> wrote:
Some years ago I have made a set of scripts for building MIPS linux kernel and
rootfs from scratch and running it under qemu.
See https://github.com/frantony/clab for details,
especialy see start-qemu.sh script and files in the qemu-configs/malta-linux-gnu
subdirectory.
Also see a versatile 'buildroot' software for easy rootfs creation (www.buildroot.org).
> 1. When QEMU for MIPS support watchpoint debug facility? Any hint or guide
> to implement that function?
Run qemu with -S and -s options. Next start your cross gdb (e.g. mips-linux-gdb),
next in the gdb cmdline use command "target remote :1234" to connect to qemu.
> 2. qemu-system-mipsel -M malta -kernel vmlinux-2.6.26-1-4kc-malta -hda
> debian_lenny_mipsel_small.qcow2 -append "root=/dev/hda1 console=ttyS0
> kgdboc=ttyS0,115200 kgdbwait" -nographic -serial tcp::1234,server -net
> nic,model=pcnet -net user
>
> Did I miss something? I cannot see the bootup message in the current client
> unless I remove "-serial tcp::1234,server" away. But I need that for kgdb
> debug. What is the right way to configure it?
Do you really need this "in-kernel" gdb support? As I have already write,
qemu itself has gdb server functionality support.
> --
> Best Regards,
> Yu Rong Tan
--
--
Best regards,
Antony Pavlov
next prev parent reply other threads:[~2013-10-29 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 13:09 [Qemu-devel] About QEMU for MIPS Nancy
2013-10-29 18:43 ` Antony Pavlov [this message]
2013-10-30 9:57 ` Nancy
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=20131029224338.5b70ae229d094a6ba17e757d@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=nancydreaming@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).