From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V5 2/2] board/qemu/csky/readme.txt: Add C-SKY Qemu run Documentation
Date: Mon, 3 Jun 2019 09:32:12 +0200 [thread overview]
Message-ID: <20190603093212.74f84255@windsurf> (raw)
In-Reply-To: <CAJF2gTSGEKBE6=EL7PyKvxJ0mF+2wFjXvBxyCZOfFPJ8jVW7hg@mail.gmail.com>
Hello,
On Mon, 3 Jun 2019 14:47:09 +0800
Guo Ren <guoren@kernel.org> wrote:
> Qemu upstream is under way and I want to add host-qemu for C-SKY after that.
>
> See here:
> https://gitlab.com/c-sky/buildroot/tree/master/package/csky-qemu
> I don't use package/qemu to build csky qemu and I add another
> csky-qemu package for simple.
Well, why not simply adding C-SKY support to the existing
package/qemu ? It should be fairly easy, just change the
version/source/site, and that's it ? Since you're in the process of
upstreaming, I assume you're using a recent version of Qemu, so all the
logic in qemu.mk for upstream Qemu should apply to the C-SKY variant as
well.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Guo Ren <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 2/2] board/qemu/csky/readme.txt: Add C-SKY Qemu run Documentation
Date: Mon, 3 Jun 2019 09:32:12 +0200 [thread overview]
Message-ID: <20190603093212.74f84255@windsurf> (raw)
In-Reply-To: <CAJF2gTSGEKBE6=EL7PyKvxJ0mF+2wFjXvBxyCZOfFPJ8jVW7hg@mail.gmail.com>
Hello,
On Mon, 3 Jun 2019 14:47:09 +0800
Guo Ren <guoren@kernel.org> wrote:
> Qemu upstream is under way and I want to add host-qemu for C-SKY after that.
>
> See here:
> https://gitlab.com/c-sky/buildroot/tree/master/package/csky-qemu
> I don't use package/qemu to build csky qemu and I add another
> csky-qemu package for simple.
Well, why not simply adding C-SKY support to the existing
package/qemu ? It should be fairly easy, just change the
version/source/site, and that's it ? Since you're in the process of
upstreaming, I assume you're using a recent version of Qemu, so all the
logic in qemu.mk for upstream Qemu should apply to the C-SKY variant as
well.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-03 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 9:41 [Buildroot] [PATCH V5 1/2] configs/qemu_cskyXXX_virt: new defconfig guoren at kernel.org
2019-06-02 9:41 ` guoren
2019-06-02 9:41 ` [Buildroot] [PATCH V5 2/2] board/qemu/csky/readme.txt: Add C-SKY Qemu run Documentation guoren at kernel.org
2019-06-02 9:41 ` guoren
2019-06-02 11:46 ` [Buildroot] " Thomas Petazzoni
2019-06-02 11:46 ` Thomas Petazzoni
2019-06-03 6:47 ` Guo Ren
2019-06-03 6:47 ` Guo Ren
2019-06-03 7:32 ` Thomas Petazzoni [this message]
2019-06-03 7:32 ` Thomas Petazzoni
2019-06-02 10:32 ` [Buildroot] [PATCH V5 1/2] configs/qemu_cskyXXX_virt: new defconfig Thomas Petazzoni
2019-06-02 10:32 ` Thomas Petazzoni
2019-06-03 7:00 ` Guo Ren
2019-06-03 7:00 ` Guo Ren
2019-06-03 7:30 ` Thomas Petazzoni
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=20190603093212.74f84255@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 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.