public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alexander Lobakin <alobakin@pm.me>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Paul Burton <paulburton@kernel.org>,
	Paul Cercueil <paul@crapouillou.net>,
	Huacai Chen <chenhc@lemote.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mips-next 0/2] mips: boot: add support for self-extracting FIT images (vmlinuz.itb)
Date: Thu, 12 Nov 2020 23:49:46 +0100	[thread overview]
Message-ID: <20201112224946.GF19695@alpha.franken.de> (raw)
In-Reply-To: <WnsVNeMB9c330hqKGdZ32JHsKO2ZbTM1BOGv74ZSJ9o@cp4-web-014.plabs.ch>

On Sun, Nov 01, 2020 at 03:11:07PM +0000, Alexander Lobakin wrote:
> Commit c3e2ee657418 ("MIPS: generic: Add support for zboot") added
> support for self-extracting images to Generic MIPS. However, the
> intended way to boot Generic MIPS kernels is using FIT Images and
> UHI boot protocol, but currently there's no way to make self-extracting
> FIT Image (only legacy uzImages).
> 
> This set consists of two parts:
> 1) various cleanups in arch/mips/boot/compressed/Makefile as a
>    prerequisite;
> 2) a new target named "vmlinuz.itb" for composing self-extracting
>    FIT Images, which allows to have the advantages of both UHI and
>    vmlinuz.
> 
> The second part involves some scenarios duplication, but I think it
> can be a subject for another series (for constifying and unifying
> FIT Images rules across the architectures).
> 
> Alexander Lobakin (2):
>   mips: boot: clean up self-extracting targets scenarios
>   mips: boot: add support for self-extracting FIT images (vmlinuz.itb)
> 
>  arch/mips/Makefile                 |  3 +-
>  arch/mips/boot/.gitignore          |  1 +
>  arch/mips/boot/compressed/Makefile | 96 +++++++++++++++++++++++++-----
>  3 files changed, 85 insertions(+), 15 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2020-11-12 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-01 15:11 [PATCH mips-next 0/2] mips: boot: add support for self-extracting FIT images (vmlinuz.itb) Alexander Lobakin
2020-11-04 11:26 ` Paul Cercueil
2020-11-04 13:39   ` Alexander Lobakin
2020-11-12 22:49 ` Thomas Bogendoerfer [this message]

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=20201112224946.GF19695@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=alobakin@pm.me \
    --cc=chenhc@lemote.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=paul@crapouillou.net \
    --cc=paulburton@kernel.org \
    /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