Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/rauc: needs kernel headers >= 3.0
Date: Fri, 24 Aug 2018 17:40:54 +0200	[thread overview]
Message-ID: <20180824154054.GP9365@scaer> (raw)
In-Reply-To: <20180824143728.05576d39@windsurf>

Thomas, All,

On 2018-08-24 14:37 +0200, Thomas Petazzoni spake thusly:
> 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

Wooo... You took the bait quite easily! ;-)

But seriously, I indeed only skimmed for 'emmc' in the code. and there
are quite a few call sites. Now, does it make sense to disable this emmc
boot support at all? Let's see what upstream has to say about that. ;-)

Regards,
Yann E. MORIN.

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

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2018-08-24 15:40 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
2018-08-24 15:40       ` Yann E. MORIN [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=20180824154054.GP9365@scaer \
    --to=yann.morin.1998@free.fr \
    --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