From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] Etherboot for E100 NIC
Date: Fri, 01 Feb 2008 21:39:25 +0900 [thread overview]
Message-ID: <47A312FD.9070605@ab.jp.nec.com> (raw)
In-Reply-To: <18337.61060.423400.93623@mariner.uk.xensource.com>
Ian Jackson wrote:
> Following on from the changes recently made to build etherboot
> ourselves from source, I've adapted Yosuke Iwamatsu's idea to work in
> this context.
>
> The result is below and appears to work. The set of supported NICs
> can be adjusted by changing the setting of NICS in
> tools/firmware/etherboot/Makefile.
>
> The added file tools/firmware/etherboot/make-eb-rom-list needs to have
> chmod +x run on it before committing.
Thanks for your work.
I tried the latest staging tree and got etherboot work fine.
The attached patch (applied to cs16963) was needed to build etherboot
in my test environment.
I also found that build failed with "debug=y" specified,
though I don't know how to fix it yet.
Yosuke.
----------------------
diff -r d29d74d4eeac tools/firmware/etherboot/Config
--- a/tools/firmware/etherboot/Config Fri Feb 01 12:01:34 2008 +0000
+++ b/tools/firmware/etherboot/Config Fri Feb 01 21:40:48 2008 +0900
@@ -10,4 +10,6 @@ CFLAGS+= -UPXE_DHCP_STRICT
CFLAGS+= -UPXE_DHCP_STRICT
CFLAGS+= -DPXE_DHCP_STRICT
+CFLAGS+= -fno-stack-protector
+
# Also, the Makefile arranges for us to use GCC 3
next prev parent reply other threads:[~2008-02-01 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 23:07 [PATCH] Etherboot for E100 NIC Yosuke Iwamatsu
2008-01-29 11:40 ` Ian Jackson
2008-01-29 12:19 ` Yosuke Iwamatsu
2008-01-29 12:19 ` Ian Jackson
2008-01-31 15:51 ` Ian Jackson
2008-02-01 12:39 ` Yosuke Iwamatsu [this message]
2008-02-02 11:33 ` Keir Fraser
2008-02-04 11:13 ` Ian Jackson
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=47A312FD.9070605@ab.jp.nec.com \
--to=y-iwamatsu@ab.jp.nec.com \
--cc=Ian.Jackson@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 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.