All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org,
	Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	qemu-devel@nongnu.org, Collin Walling <walling@linux.ibm.com>,
	Farhan Ali <alifm@linux.ibm.com>
Subject: [Qemu-devel] [PATCH v2 0/4] pc-bios/s390-ccw: Allow network booting via pxelinux.cfg
Date: Thu,  7 Jun 2018 14:22:30 +0200	[thread overview]
Message-ID: <1528374154-14680-1-git-send-email-thuth@redhat.com> (raw)

This patch series adds pxelinux.cfg-style network booting to the s390-ccw
firmware. The core pxelinux.cfg loading and parsing logic has recently
been merged to SLOF, so these patches now just have to make sure to call
the right functions to get the config file loaded and parsed. Once this is
done, the kernel and initrd are loaded separately, and are then glued
together in RAM.

v2:
 - Update SLOF submodule now that the git mirror is in sync again
 - Last parameter to tftp_get_error_info() must not be NULL
 - Check CC when calling STSI, and use a #define for the UUID offset
 - Only support files with the magic "# pxelinux" string comment when
   trying to guess the contents of a file that has been downloaded via
   the "bootfile" DHCP parameter. This is just for developers' convenience,
   the official way to specify pxelinux.cfg files is to use the DHCP
   options 209 and 210 instead.

Thomas Huth (4):
  roms: Update SLOF submodule to current status
  pc-bios/s390-ccw/net: Update code for the latest changes in SLOF
  pc-bios/s390-ccw/net: Add support for pxelinux-style config files
  pc-bios/s390-ccw/net: Try to load pxelinux.cfg file accoring to the
    UUID

 pc-bios/s390-ccw/netboot.mak |   9 +-
 pc-bios/s390-ccw/netmain.c   | 226 +++++++++++++++++++++++++++++--------------
 roms/SLOF                    |   2 +-
 3 files changed, 162 insertions(+), 75 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2018-06-07 12:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 12:22 Thomas Huth [this message]
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 1/4] roms: Update SLOF submodule to current status Thomas Huth
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 2/4] pc-bios/s390-ccw/net: Update code for the latest changes in SLOF Thomas Huth
2018-06-08  7:45   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 3/4] pc-bios/s390-ccw/net: Add support for pxelinux-style config files Thomas Huth
2018-06-07 12:22 ` [Qemu-devel] [PATCH v2 4/4] pc-bios/s390-ccw/net: Try to load pxelinux.cfg file accoring to the UUID Thomas Huth
2018-06-07 12:31 ` [Qemu-devel] [PATCH v2 0/4] pc-bios/s390-ccw: Allow network booting via pxelinux.cfg no-reply
2018-06-07 17:01   ` Thomas Huth
2018-06-11  9:08 ` Viktor VM Mihajlovski
2018-06-11 11:12   ` Thomas Huth
2018-06-11 12:03     ` Viktor VM Mihajlovski
2018-06-12  6:17       ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-06-13 10:56         ` Viktor VM Mihajlovski
2018-06-13 11:01           ` Thomas Huth
2018-06-11  9:13 ` [Qemu-devel] " Christian Borntraeger

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=1528374154-14680-1-git-send-email-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=mihajlov@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=walling@linux.ibm.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.