Hannes Reinecke | 28 May 12:20 2015
Picon

Feedback on iBFT update?

Hi Micheal,

I've send an updated patchset for my IPv6 & iBFT support (cf
[PATCHv3 00/11] IPv6 and iBFT update).
With that I've _thought_ to have addressed your concerns.
Any feedback on them?
Note, there's a minor issue with the iBFT flags (which need to be
set correctly depending on which interface the system has booted
from), but before I'm resending that I'd like to get some feedback
on the overall state, most notably the IPv6 support.
Hardly a point in pursuing here if you don't like that approach ...

Cheers,

Hannes
--

-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare <at> suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
_______________________________________________
ipxe-devel mailing list
ipxe-devel <at> lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Michael Brown | 28 May 12:12 2015

Re: [ipxe] Add ixgbevf driver (#9)

Closed #9.


Reply to this email directly or view it on GitHub.

<div>
<p>Closed <a href="https://github.com/ipxe/ipxe/pull/9" class="issue-link" title="Add ixgbevf driver">#9</a>.</p>

<p>&mdash;<br>Reply to this email directly or <a href="https://github.com/ipxe/ipxe/pull/9#event-315839790">view it on GitHub</a>.</p>
<div itemscope itemtype="http://schema.org/EmailMessage">
  <div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
    </div>
  </div>
</div>
Michael Bazzinotti | 26 May 16:24 2015

[PATCH] [iPXE] Add compile-time support for no modifier keys

From: "Michael J. Bazzinotti" <mbazzinotti@...>

This is a patch stemming from the discussion at
http://lists.ipxe.org/pipermail/ipxe-devel/2015-May/004237.html

This patch makes sure to add functionality without doing the following:

* break existing behavior
* add behavior inconsistent with on-screen instructions
* generate overly verbose on-screen instructions

It does this by adding a new preprocessor definition
MENU_KEYS_NO_MODIFIER, disabled by default. It can be enabled by
uncommenting the relative line in config/general.h.

Signed-off-by: Michael J. Bazzinotti <mbazzinotti@...>
---
 src/config/general.h      | 11 +++++++++++
 src/hci/tui/settings_ui.c | 30 ++++++++++++++++++++++++------
 src/usr/autoboot.c        |  7 +++++++
 3 files changed, 42 insertions(+), 6 deletions(-)

diff --git a/src/config/general.h b/src/config/general.h
index 7676f15..7087a63 100644
--- a/src/config/general.h
+++ b/src/config/general.h
 <at>  <at>  -30,6 +30,17  <at>  <at>  FILE_LICENCE ( GPL2_OR_LATER_OR_UBDL );
 #define ROM_BANNER_TIMEOUT	( 2 * BANNER_TIMEOUT )

 /*
+ * Keyboard -- use of Modifier keys
+ *
+ * Some platforms do not support modifier keys, such as those using EFI
+ * 1.1 without support for the EFI_SIMPLE_TEXT_INPUT_EX_PROTOCOL (ie. Mac)
+ *
+ * If you are using a mac, or find that you cannot use Ctrl-B to cancel the
+ * autoboot process and enter a shell, try enabling this configuration option.
+ */
+//#define MENU_KEYS_NO_MODIFIER
+
+/*
  * Network protocols
  *
  */
diff --git a/src/hci/tui/settings_ui.c b/src/hci/tui/settings_ui.c
index be421cc..0970c12 100644
--- a/src/hci/tui/settings_ui.c
+++ b/src/hci/tui/settings_ui.c
 <at>  <at>  -35,6 +35,7  <at>  <at>  FILE_LICENCE ( GPL2_OR_LATER_OR_UBDL );
 #include <ipxe/ansicol.h>
 #include <ipxe/jumpscroll.h>
 #include <ipxe/settings_ui.h>
+#include <config/general.h>
 #include <config/branding.h>

 /**  <at> file
 <at>  <at>  -43,6 +44,23  <at>  <at>  FILE_LICENCE ( GPL2_OR_LATER_OR_UBDL );
  *
  */

+/* Keys Configuration */
+#ifdef MENU_KEYS_NO_MODIFIER
+#define KEY_DISCARD_CHANGES ESC
+#define KEY_DELETE_SETTING BACKSPACE
+#define KEY_EXIT ESC
+#define KEY_DISCARD_CHANGES_STR "ESC"
+#define KEY_DELETE_SETTING_STR "BACKSPACE"
+#define KEY_EXIT_STR "ESC"
+#else
+#define KEY_DISCARD_CHANGES CTRL_C
+#define KEY_DELETE_SETTING CTRL_D
+#define KEY_EXIT CTRL_X
+#define KEY_DISCARD_CHANGES_STR "Ctrl-C"
+#define KEY_DELETE_SETTING_STR "Ctrl-D"
+#define KEY_EXIT_STR "Ctrl-X"
+#endif /* MENU_KEYS_NO_MODIFIER */
+
 /* Screen layout */
 #define TITLE_ROW		1U
 #define SETTINGS_LIST_ROW	3U
 <at>  <at>  -384,12 +402,12  <at>  <at>  static void draw_instruction_row ( struct settings_ui *ui ) {
 	if ( ui->row.editing ) {
 		msg ( INSTRUCTION_ROW,
 		      "Enter - accept changes" INSTRUCTION_PAD
-		      "Ctrl-C - discard changes" );
+		      KEY_DISCARD_CHANGES_STR " - discard changes" );
 	} else {
 		msg ( INSTRUCTION_ROW,
-		      "%sCtrl-X - exit configuration utility",
+		      "%s" KEY_EXIT_STR " - exit configuration utility",
 		      ( ( ui->row.origin == ui->settings ) ?
-			"Ctrl-D - delete setting" INSTRUCTION_PAD : "" ) );
+			KEY_DELETE_SETTING_STR " - delete setting" INSTRUCTION_PAD : "" ) );
 	}
 }

 <at>  <at>  -486,7 +504,7  <at>  <at>  static int main_loop ( struct settings *settings ) {
 				if ( ( rc = save_setting ( &ui ) ) != 0 )
 					alert ( " %s ", strerror ( rc ) );
 				/* Fall through */
-			case CTRL_C:
+			case KEY_DISCARD_CHANGES:
 				select_setting_row ( &ui, ui.scroll.current );
 				redraw = 1;
 				break;
 <at>  <at>  -516,7 +534,7  <at>  <at>  static int main_loop ( struct settings *settings ) {

 		/* Handle non-navigation keys */
 		switch ( key ) {
-		case CTRL_D:
+		case KEY_DELETE_SETTING:
 			if ( ! ui.row.setting.name )
 				break;
 			if ( ( rc = delete_setting ( ui.settings,
 <at>  <at>  -526,7 +544,7  <at>  <at>  static int main_loop ( struct settings *settings ) {
 			select_setting_row ( &ui, ui.scroll.current );
 			redraw = 1;
 			break;
-		case CTRL_X:
+		case KEY_EXIT:
 			return 0;
 		case CR:
 		case LF:
diff --git a/src/usr/autoboot.c b/src/usr/autoboot.c
index ccafeae..8d8c508 100644
--- a/src/usr/autoboot.c
+++ b/src/usr/autoboot.c
 <at>  <at>  -532,10 +532,17  <at>  <at>  static int shell_banner ( void ) {

 	/* Prompt user */
 	printf ( "\n" );
+#ifdef MENU_KEYS_NO_MODIFIER
+	return ( prompt ( "Press ESC for the " PRODUCT_SHORT_NAME
+			  " command line...",
+			  ( ( BANNER_TIMEOUT * TICKS_PER_SEC ) / 10 ),
+			  ESC ) == 0 );
+#else
 	return ( prompt ( "Press Ctrl-B for the " PRODUCT_SHORT_NAME
 			  " command line...",
 			  ( ( BANNER_TIMEOUT * TICKS_PER_SEC ) / 10 ),
 			  CTRL_B ) == 0 );
+#endif /* MENU_KEYS_NO_MODIFIER */
 }

 /**
--

-- 
2.3.6

Torcz, Tomasz (GE Capital | 26 May 14:59 2015
Picon

[PATCH] [monojob] only display percentage when bigger than 0%

  This change will continue to show dots as progress until
 percentage crosses 1%.
  This is needed to work around problem with TFTP server on
 my old, unsupported Cisco switch.  It provides nonsensical
 values for size, which causes percentage progress to be stuck
 at 0% during whole transfer.  After the change dots are shown
 during whole transfer, providing at least some progress indicator.

Tomasz Torcz
T +48 58 307 64 44
tomasz.torcz@...

  This change will continue to show dots as progress until
 percentage crosses 1%.
  This is needed to work around problem with TFTP server on
 my old, unsupported Cisco switch.  It provides nonsensical
 values for size, which causes percentage progress to be stuck
 at 0% during whole transfer.  After the change dots are shown
 during whole transfer, providing at least some progress indicator.

Tomasz Torcz
T +48 58 307 64 44
tomasz.torcz@...

bazz | 23 May 17:02 2015

[PATCH 0/2] Support platforms that do not process the CTRL key

iPXE does not function properly on platforms that do not support the CTRL key.
An example of such a platform is the Apple Macbook Pro (2009). This patchset 
provides core functionality on these unsupported platforms.

Issues Solved:

 * When booting into iPXE, CTRL-B does not cancel autoboot and spawn a shell. 

 * When in the 'config' command menu, cannot exit the menu (CTRL-X) or clear
and delete entries.

This patch series solves these problems.

In the 'config' menu, it provides backwards support to the old keys.

There may exist other unpatched sections of iPXE that use the CTRL keys. 

Michael J. Bazzinotti (2):
  [autoboot] Support platforms which don't process the CTRL key
  [config] Support platforms which do not process the CTRL key

 src/hci/tui/settings_ui.c | 9 ++++++---
 src/usr/autoboot.c        | 4 ++--
 2 files changed, 8 insertions(+), 5 deletions(-)

--

-- 
2.3.6

Michael Brown | 20 May 12:37 2015
Picon

Re: 回复: ipxe CODE immigrating to MCU applications

On 20 May 2015 01:36:56 GMT+03:00, "郭鹏" <120721080 <at> qq.com> wrote:
>Hi Michael :
>
>
>Thanks very much for your advice . Is there any documents to illustrate
>the arch of IPXE software package ?
>
>
>I am trying to find the driver or hardware related files .  I find
>SRC\DRIVERS\NET . There are some files such as
>
>
>Intel.c ,REALTEK.C . It seems that I need to create one new file to
>support my NIC .
>
>
>br
>Peter Guo
>
>
>
>
>------------------ 原始邮件 ------------------
>发件人: "Michael Brown";<mbrown <at> fensystems.co.uk>;
>发送时间: 2015年5月20日(星期三) 凌晨2:31
>收件人: "郭鹏"<120721080 <at> qq.com>; "ipxe-devel"<ipxe-devel <at> lists.ipxe.org>; 
>
>主题: Re: [ipxe-devel] ipxe CODE immigrating to MCU applications
>
>
>
>On 19 May 2015 04:08:18 GMT+03:00, "郭鹏" <120721080 <at> qq.com> wrote:
>>Dear  IPXE engineers :
>>
>>I am working on a case needing PXE function . But we do not choose
>>generation ethernet controller such as Intel ,BCM or realtek products
>.
>>We choose 
>>
>>
>>FPGA as the the core chip on the NIC . So  I hope to find a way to
>>implement the PXE function with the MCU inside the FPGA which is build
>>by softare .
>>
>>
>>I read the documents and descriptions on your website . I found that
>>the IPXE is basing on specified application and target hardware
>>platform such as 
>>
>>
>>controller IC . Could you help to give me some advice or guideline
>>about how to immigrate this IPXE to standalone CPU ? Thanks very much
>.
>>
>>
>>br
>>
>>
>>Peter Guo
>>From China
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>ipxe-devel mailing list
>>ipxe-devel <at> lists.ipxe.org
>>https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>
>iPXE (as with any other PXE stack) is code which executes on the host
>CPU (e.g. Intel/AMD), not on the NIC's embedded CPU.
>
>The NIC provides a PCI expansion ROM BAR containing the PXE code, but
>it's the host CPU which executes it.
>
>You would need to write (or pay someone else to write) an iPXE driver
>for your NIC. This process is very similar to writing a Linux or
>Windows driver for the NIC.
>
>Hope that helps.
>
>Michael

Correct; you will need to add a driver for your NIC under drivers/net/.

You can look at the intel.c, realtek.c, and other drivers for examples of how to structure the code.

Michael
_______________________________________________
ipxe-devel mailing list
ipxe-devel <at> lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Tufan Karadere | 19 May 20:47 2015
Picon

SHA-384

Hello all,

I've been trying to enable HTTPS support and I noticed that it wasn't working for the certificates with sha384WithRSAEncryption until I added the object identifiers (attached the diff).

Documentation (http://ipxe.org/crypto) doesn't list it as supported but git logs looked like otherwise.

So I wanted to ask about the 'official' status for SHA-384, SHA-512 and SHA-224 support.

Thank you,

/tufan


<div><div dir="ltr">
<div>
<div>
<div>Hello all,<br><br>
</div>I've been trying to enable HTTPS support and I noticed that it wasn't working for the certificates with sha384WithRSAEncryption until I added the object identifiers (attached the diff). <br><br>Documentation (<a href="http://ipxe.org/crypto">http://ipxe.org/crypto</a>) doesn't list it as supported but git logs looked like otherwise. <br><br>
</div>So I wanted to ask about the 'official' status for SHA-384, SHA-512 and SHA-224 support.<br><br>
</div>
<div>Thank you,<br><br>
</div>/tufan<br><div>
<br><br>
</div>
</div></div>
郭鹏 | 19 May 03:08 2015

ipxe CODE immigrating to MCU applications

Dear  IPXE engineers :


    I am working on a case needing PXE function . But we do not choose generation ethernet controller such as Intel ,BCM or realtek products . We choose 

FPGA as the the core chip on the NIC . So  I hope to find a way to implement the PXE function with the MCU inside the FPGA which is build by softare .

I read the documents and descriptions on your website . I found that the IPXE is basing on specified application and target hardware platform such as 

controller IC . Could you help to give me some advice or guideline about how to immigrate this IPXE to standalone CPU ? Thanks very much .

br

Peter Guo
From China
<div>
<p>Dear &nbsp;IPXE engineers :</p>
<div><br></div>
<div>&nbsp; &nbsp; I am working on a case needing PXE function . But we do not choose generation ethernet controller such as Intel ,BCM or realtek products . We choose&nbsp;</div>
<div><br></div>
<div>FPGA as the the core chip on the NIC . So &nbsp;I hope to find a way to implement the PXE function with the MCU inside the FPGA which is build by softare .</div>
<div><br></div>
<div>I read the documents and descriptions on your website . I found that the IPXE is basing on specified application and target hardware platform such as&nbsp;</div>
<div><br></div>
<div>controller IC . Could you help to give me some advice or guideline about how to immigrate this IPXE to standalone CPU ? Thanks very much .</div>
<div><br></div>
<div>br</div>
<div><br></div>
<div>Peter Guo</div>
<div>From China</div>
</div>
Michael Brown | 18 May 06:32 2015

Re: Support for Solarflare 10Gb Cards

On 15/05/15 21:31, Daniel Browne wrote:
> Does iPXE support or plan to support 10Gb ethernet cards manufactured by
> Solarflare? Even from the latest code base I cannot seem to build a kpxe
> image that will boot properly off one of their cards. After loading the
> kpxe image, booting always halts with error code 040ee119 trying to
> initialize the network interface even though it succeeded in the initial
> stage since it is able to get the image in the first place.

The Solarflare PXE stack is (AFAIK) still built from iPXE, though the 
codebase has been maintained separately for a number of years now.

If you obtain the latest Solarflare code (under GPL), it should still be 
possible to add the driver files to the iPXE tree.

Michael
Robin Smidsrød | 17 May 07:59 2015
Picon

Re: Support for Solarflare 10Gb Cards

On 15.05.2015 22:31, Daniel Browne wrote:
> Does iPXE support or plan to support 10Gb ethernet cards manufactured by
> Solarflare? Even from the latest code base I cannot seem to build a kpxe
> image that will boot properly off one of their cards. After loading the
> kpxe image, booting always halts with error code 040ee119 trying to
> initialize the network interface even though it succeeded in the initial
> stage since it is able to get the image in the first place.

According to http://ipxe.org/appnote/hardware_drivers you should be able
to use the etherfabric driver. If your PCI vendor/device ID is not
listed you can try to add a PCI_ROM() line to etherfabric.c and see if
it works. Try to build etherfabric.usb and boot it from a USB stick to
verify. Alternatively you can try to chainload it with etherfabtic.pxe.

If none of these work you should be able to drive it with undionly.kpxe
via chainloading (although that doesn't use the native etherfabric driver).

-- Robin

Daniel Browne | 15 May 22:31 2015

Support for Solarflare 10Gb Cards

Does iPXE support or plan to support 10Gb ethernet cards manufactured by Solarflare? Even from the latest code base I cannot seem to build a kpxe image that will boot properly off one of their cards. After loading the kpxe image, booting always halts with error code 040ee119 trying to initialize the network interface even though it succeeded in the initial stage since it is able to get the image in the first place.

Thank you,

-Dan


--
Framestore | Dan Browne | Systems Engineer
London - New York - Los Angeles - Montréal

8616 National Boulevard
Culver City, CA 90232
T: 310 975 7300
C: 415 609 1612
framestore.com
Facebook | Twitter
<div><div dir="ltr">Does iPXE support or plan to support 10Gb ethernet cards manufactured by Solarflare? Even from the latest code base I cannot seem to build a kpxe image that will boot properly off one of their cards. After loading the kpxe image, booting always halts with error code 040ee119 trying to initialize the network interface even though it succeeded in the initial stage since it is able to get the image in the first place.<br clear="all"><div><br></div>
<div>Thank you,</div>
<div><br></div>
<div>-Dan</div>
<div><br></div>
<div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Framestore |&nbsp;Dan Browne | Systems Engineer<br>London - New York -&nbsp;Los Angeles&nbsp;- Montr&eacute;al<br><br>8616 National Boulevard<br>Culver City, CA 90232<br>T:&nbsp;<a value="+13109757300">310 975 7300</a><br>C: 415 609 1612<br><a href="http://www.framestore.com/" target="_blank"></a><a href="http://www.framestore.com/" target="_blank">framestore.com</a><br><a href="https://www.facebook.com/Framestore" target="_blank"></a><a>Facebook</a>&nbsp;|&nbsp;<a href="http://twitter.com/Framestore" target="_blank"></a><a>Twitter</a><br>
</div></div>
</div></div>

Gmane