All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/rauc: needs kernel headers >= 3.0
Date: Fri, 24 Aug 2018 14:37:28 +0200	[thread overview]
Message-ID: <20180824143728.05576d39@windsurf> (raw)
In-Reply-To: <20180824120119.GO9365@scaer>

Hello,

On Fri, 24 Aug 2018 14:01:19 +0200, Yann E. MORIN wrote:

> That is not really possible, because emmc support is core to rauc; it is
> not even optional in the current code. Removing it (by making it
> conditional) does not make sense IMHO (but I'm not using rauc).
> 
> And then, technically, it would require quite some overhaul in rauc,
> because access to the emmc code is made from a lot of places.

Tadada. The problematic piece of code is not used for eMMC support in
general, just for eMMC boot partition support. It was added by a single
commit between v0.3 and v0.4 and is pretty self-contained and
well-isolated.

So I took what you said as a challenge, and came up with:

  http://patchwork.ozlabs.org/patch/961842/

Which has the added benefit of fixing the build issue of host-rauc :-)

Since it took me 36 minutes between your e-mail and this e-mail being,
I don't think "quite some overhaul in rauc" was really needed :-P

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-24 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  8:02 [Buildroot] [PATCH] package/rauc: needs kernel headers >= 3.0 Yann E. MORIN
2018-08-24 11:49 ` Thomas Petazzoni
2018-08-24 12:01   ` Yann E. MORIN
2018-08-24 12:37     ` Thomas Petazzoni [this message]
2018-08-24 15:40       ` Yann E. MORIN

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=20180824143728.05576d39@windsurf \
    --to=thomas.petazzoni@bootlin.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 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.