From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] qemu_x86: update to kernel 3.1 and add readme
Date: Tue, 25 Oct 2011 08:27:17 +0200 [thread overview]
Message-ID: <87aa8py4ai.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1319485334-15790-4-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Mon, 24 Oct 2011 16:42:12 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Gustavo> ---
Gustavo> .../x86/{linux-3.0.config => linux-3.1.config} | 0
Gustavo> board/qemu/x86/readme.txt | 5 +++++
Gustavo> configs/qemu_x86_defconfig | 5 +++--
Gustavo> 3 files changed, 8 insertions(+), 2 deletions(-)
Gustavo> rename board/qemu/x86/{linux-3.0.config => linux-3.1.config} (100%)
Gustavo> create mode 100644 board/qemu/x86/readme.txt
Gustavo> diff --git a/board/qemu/x86/linux-3.0.config b/board/qemu/x86/linux-3.1.config
Gustavo> similarity index 100%
Gustavo> rename from board/qemu/x86/linux-3.0.config
Gustavo> rename to board/qemu/x86/linux-3.1.config
Gustavo> diff --git a/board/qemu/x86/readme.txt b/board/qemu/x86/readme.txt
Gustavo> new file mode 100644
Gustavo> index 0000000..c06d24f
Gustavo> --- /dev/null
Gustavo> +++ b/board/qemu/x86/readme.txt
Gustavo> @@ -0,0 +1,5 @@
Gustavo> +Run the emulation with:
Gustavo> +
Gustavo> + qemu-system-x86_64 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=ide -append root=/dev/sda
Why not qemu-system-i386? I would prefer to have console=ttyS0,115200 on
the cmdline as well.
Gustavo> +
Gustavo> +The login prompt will appear in the graphical window.
And then change this line.
Gustavo> diff --git a/configs/qemu_x86_defconfig b/configs/qemu_x86_defconfig
Gustavo> index d60b38d..8efe9ae 100644
Gustavo> --- a/configs/qemu_x86_defconfig
Gustavo> +++ b/configs/qemu_x86_defconfig
Gustavo> @@ -4,6 +4,7 @@ BR2_x86_pentiumpro=y
Gustavo> # system
Gustavo> BR2_TARGET_GENERIC_GETTY=y
Gustavo> +BR2_TARGET_GENERIC_GETTY_PORT="tty1"
Please keep it on ttyS0.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-10-25 6:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 19:42 [Buildroot] [PATCH 1/6] linux: vmlinux target is valid for powerpc too Gustavo Zacarias
2011-10-24 19:42 ` [Buildroot] [PATCH 2/6] qemu_arm_versatile: use kernel 3.1 and add readme Gustavo Zacarias
2011-10-25 6:20 ` Peter Korsgaard
2011-10-24 19:42 ` [Buildroot] [PATCH 3/6] qemu_mipsel_malta: update to kernel 3.1 Gustavo Zacarias
2011-10-25 6:21 ` Peter Korsgaard
2011-10-24 19:42 ` [Buildroot] [PATCH 4/6] qemu_x86: update to kernel 3.1 and add readme Gustavo Zacarias
2011-10-25 6:27 ` Peter Korsgaard [this message]
2011-10-25 9:52 ` Gustavo Zacarias
2011-10-25 10:30 ` Peter Korsgaard
2011-10-25 10:38 ` Gustavo Zacarias
2011-10-24 19:42 ` [Buildroot] [PATCH 5/6] qemu_sh4_r2d: update to kernel 3.1 and update readme Gustavo Zacarias
2011-10-25 6:24 ` Peter Korsgaard
2011-10-25 9:53 ` Gustavo Zacarias
2011-10-25 10:30 ` Peter Korsgaard
2011-10-25 12:10 ` Gustavo Zacarias
2011-10-24 19:42 ` [Buildroot] [PATCH 6/6] qemu_ppc_g3beige: update to kernel 3.1 Gustavo Zacarias
2011-10-25 6:27 ` Peter Korsgaard
2011-10-25 6:20 ` [Buildroot] [PATCH 1/6] linux: vmlinux target is valid for powerpc too Peter Korsgaard
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=87aa8py4ai.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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