From: Ian Campbell <Ian.Campbell@citrix.com>
To: "stefano.stabellini@eu.citrix.com" <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"keir@xen.org" <keir@xen.org>
Subject: Re: [PATCH v2 4/4] Clone and build Seabios by default
Date: Thu, 8 Sep 2011 11:00:22 -0700 [thread overview]
Message-ID: <1315504825.3180.51.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <1315504038-21733-4-git-send-email-stefano.stabellini@eu.citrix.com>
On Thu, 2011-09-08 at 13:47 -0400, stefano.stabellini@eu.citrix.com
wrote:
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> diff -r ef27b472d4f3 Config.mk
> --- a/Config.mk Thu Sep 08 17:19:12 2011 +0000
> +++ b/Config.mk Thu Sep 08 17:29:50 2011 +0000
> @@ -195,6 +195,8 @@ endif
> # Only available through the git protocol at the moment
> QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/people/sstabellini/qemu-dm.git
> QEMU_UPSTREAM_TAG ?= origin/xen-stable-0.15
> +SEABIOS_UPSTREAM_URL=git://git.qemu.org/seabios.git
> +SEABIOS_UPSTREAM_TAG ?= 7fc039e9c262b4199fab497f3e12f4e425c37560
I guess we should have a default tree on xenbits for this?
[...]
> +$(SEABIOS_DIR):
> + set -ex; \
> + if [ ! -d seabios-remote ]; then \
> + rm -rf seabios-remote seabios-remote.tmp; \
> + mkdir seabios-remote.tmp; rmdir seabios-remote.tmp; \
> + $(GIT) clone $(SEABIOS_UPSTREAM_URL) seabios-remote.tmp; \
> + if [ "$(SEABIOS_UPSTREAM_TAG)" ]; then \
> + cd seabios-remote.tmp; \
> + $(GIT) branch -D dummy >/dev/null 2>&1 ||:; \
> + $(GIT) checkout -b dummy $(SEABIOS_UPSTREAM_TAG); \
> + cd ..; \
> + fi; \
> + mv seabios-remote.tmp seabios-remote; \
> + fi; \
> + rm -f seabios-dir; \
> + ln -sf seabios-remote seabios-dir; \
> + cp seabios-config seabios-dir/.config;
This looks a lot like the qemu stuff which you only just moved into its
own script. Can we not share it?
> diff -r ef27b472d4f3 tools/firmware/hvmloader/Makefile
> --- a/tools/firmware/hvmloader/Makefile Thu Sep 08 17:19:12 2011 +0000
> +++ b/tools/firmware/hvmloader/Makefile Thu Sep 08 17:29:50 2011 +0000
> @@ -47,7 +47,7 @@ endif
> ifneq ($(SEABIOS_DIR),)
> OBJS += seabios.o
> CFLAGS += -DENABLE_SEABIOS
> -SEABIOS_ROM := $(SEABIOS_DIR)/out/bios.bin
> +SEABIOS_ROM := ../$(SEABIOS_DIR)/out/bios.bin
> endif
>
> STDVGA_ROM := ../vgabios/VGABIOS-lgpl-latest.bin
next prev parent reply other threads:[~2011-09-08 18:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 17:47 [PATCH v2 1/4] Move the ioemu-dir-find shell script to an external file stefano.stabellini
2011-09-08 17:47 ` [PATCH v2 2/4] Rename ioemu-dir as qemu-xen-traditional-dir stefano.stabellini
2011-09-08 17:47 ` [PATCH v2 3/4] Clone and build upstream Qemu by default stefano.stabellini
2011-09-08 17:56 ` Ian Campbell
2011-09-09 10:18 ` Stefano Stabellini
2011-09-09 13:59 ` Ian Campbell
2011-09-09 14:31 ` Ian Campbell
2011-09-09 16:43 ` Stefano Stabellini
2011-09-09 17:18 ` Ian Campbell
2011-09-08 17:47 ` [PATCH v2 4/4] Clone and build Seabios " stefano.stabellini
2011-09-08 18:00 ` Ian Campbell [this message]
2011-09-09 10:19 ` Stefano Stabellini
2011-09-09 10:36 ` George Dunlap
2011-09-09 10:46 ` Stefano Stabellini
2011-09-09 11:23 ` Keir Fraser
2011-09-09 14:13 ` Ian Campbell
2011-09-09 14:32 ` Stefano Stabellini
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=1315504825.3180.51.camel@cthulhu.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).