From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: guoren@kernel.org
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
arnout@mind.be, Guo Ren <ren_guo@c-sky.com>,
zhiwei_liu@c-sky.com, linux-csky@vger.kernel.org,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH V5 1/2] configs/qemu_cskyXXX_virt: new defconfig
Date: Sun, 2 Jun 2019 12:32:18 +0200 [thread overview]
Message-ID: <20190602123218.244963b8@windsurf> (raw)
In-Reply-To: <1559468510-22085-1-git-send-email-guoren@kernel.org>
Hello Guo,
On Sun, 2 Jun 2019 17:41:49 +0800
guoren@kernel.org wrote:
> From: Guo Ren <ren_guo@c-sky.com>
>
> Add C-SKY defconfig for QEMU virt machine.
>
> Tested with https://gitlab.com/c-sky/buildroot/pipelines
>
> Signed-off-by: Guo Ren <ren_guo@c-sky.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thanks, it looks a lot better, but there are still a few things to
improve.
First, the readme.txt file should be in the same patch.
Second, you should update the DEVELOPES file so that it covers those
additional files (board/qemu/csky and configs/qemu_csky*).
See below for other comments.
> diff --git a/board/qemu/csky/linux-ck610.config.fragment b/board/qemu/csky/linux-ck610.config.fragment
> new file mode 100644
> index 0000000..d80d0ee
> --- /dev/null
> +++ b/board/qemu/csky/linux-ck610.config.fragment
> @@ -0,0 +1,5 @@
> +CONFIG_COMPILE_TEST=y
> +CONFIG_CPU_CK610=y
> +CONFIG_CPU_PM_WAIT=y
> +CONFIG_CSKY_APB_INTC=y
> +CONFIG_GX6605S_TIMER=y
Thanks, this is _much_ better!
> diff --git a/configs/qemu_csky610_virt_defconfig b/configs/qemu_csky610_virt_defconfig
> new file mode 100644
> index 0000000..9a82d57
> --- /dev/null
> +++ b/configs/qemu_csky610_virt_defconfig
> @@ -0,0 +1,20 @@
> +# Architecture
> +BR2_csky=y
> +BR2_ck610=y
You need to add an option like this:
# Linux headers same as kernel, a 5.0 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_0=y
> +# System
> +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
Please don't enable mdev.
> +BR2_TARGET_ROOTFS_INITRAMFS=y
> +
> +# Toolchain
> +BR2_OPTIMIZE_2=y
> +BR2_SHARED_STATIC_LIBS=y
> +BR2_TOOLCHAIN_BUILDROOT_CXX=y
> +BR2_PACKAGE_HOST_GDB=y
Please remove those options.
> +# Kernel
> +BR2_LINUX_KERNEL=y
> +BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.0.12"
> +BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
> +BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/qemu/csky/linux-ck610.config.fragment"
And of course, it should be changed similarly in all other defconfigs.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-02 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 9:41 [PATCH V5 1/2] configs/qemu_cskyXXX_virt: new defconfig guoren
2019-06-02 9:41 ` [PATCH V5 2/2] board/qemu/csky/readme.txt: Add C-SKY Qemu run Documentation guoren
2019-06-02 11:46 ` [Buildroot] " Thomas Petazzoni
2019-06-03 6:47 ` Guo Ren
2019-06-03 7:32 ` Thomas Petazzoni
2019-06-02 10:32 ` Thomas Petazzoni [this message]
2019-06-03 7:00 ` [Buildroot] [PATCH V5 1/2] configs/qemu_cskyXXX_virt: new defconfig Guo Ren
2019-06-03 7:30 ` Thomas Petazzoni
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=20190602123218.244963b8@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=ren_guo@c-sky.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=zhiwei_liu@c-sky.com \
/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).