From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/23] xtensa overlay application rework
Date: Tue, 14 Mar 2017 21:20:24 +0100 [thread overview]
Message-ID: <20170314212024.0585e0e8@free-electrons.com> (raw)
In-Reply-To: <1489516252-3803-1-git-send-email-jcmvbkbc@gmail.com>
Hello,
On Tue, 14 Mar 2017 11:30:29 -0700, Max Filippov wrote:
> This series cleans up xtensa overlay application code, making
> it uniform across its users in the toolchain, reducing the number of
> configuration variables and making it possible to use compressed
> overlays and download overlays from network.
> This is a subset of a series initially submitted by Yann E. MORIN
> in 2015, I've forward-ported the original submission, addressed the
> posted comments and added overlay application to linux and U-Boot.
A big question is: why do we have this weird overlay mechanism,
specifically for this CPU architecture? Why don't they use patches like
everybody else?
It has always bothered me that we had this mechanism, and I'd like to
challenge the fact that we need this, and see if a better solution is
possible.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-14 20:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 18:30 [Buildroot] [PATCH 00/23] xtensa overlay application rework Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 01/23] core: include arch-specific definitions Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 02/23] arch/xtensa: add definitions for the Xtensa overlay Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 03/23] package/binutils: use the Xtensa variables Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 04/23] package/gdb: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 05/23] package/gcc: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 06/23] arch/xtensa: add macro to extract the overlay Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 07/23] package/binutils: use macro to extract Xtensa overlay Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 08/23] package/gdb: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 09/23] package/gcc: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 10/23] package/binutils: extract Xtensa overlay as post-extract hook Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 11/23] package/gdb: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 12/23] arch/xtensa: add macros to generate hooks Max Filippov
2017-03-26 19:44 ` Thomas Petazzoni
2017-07-05 20:03 ` Arnout Vandecappelle
2017-07-06 8:27 ` Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 13/23] package/binutils: use the Xtensa macro generators Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 14/23] package/gdb: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 15/23] package/gcc: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 16/23] arch/xtensa: get rid of an intermediate blind kconfig option Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 17/23] arch/xtensa: allow specifying path to tarball file Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 18/23] arch/xtensa: accept the overlay to be compressed Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 19/23] arch/xtensa: accept the overlay to be an URL Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 20/23] configs/qemu-xtensa: use overlay from the github repository Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 21/23] linux: apply xtensa overlay Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 22/23] uboot: " Max Filippov
2017-03-14 18:30 ` [Buildroot] [PATCH 23/23] linux: enable uBoot image type for xtensa kernel Max Filippov
2017-03-14 20:55 ` Thomas Petazzoni
2017-03-14 20:20 ` Thomas Petazzoni [this message]
2017-03-14 23:07 ` [Buildroot] [PATCH 00/23] xtensa overlay application rework Max Filippov
2017-03-26 19:41 ` Thomas Petazzoni
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=20170314212024.0585e0e8@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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