From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: add lzop dependency
Date: Wed, 10 Aug 2016 09:59:53 +0100 [thread overview]
Message-ID: <1470819593.8166.68.camel@linuxfoundation.org> (raw)
In-Reply-To: <BA7DFF44-541C-4FEE-B5B2-586FD82ABC60@gmail.com>
On Tue, 2016-08-09 at 12:27 -0700, Khem Raj wrote:
> > On Aug 9, 2016, at 5:08 AM, Mike Looijmans <mike.looijmans@topic.nl
> > > wrote:
> >
> > I've been adding "lzop-native" to a lot of kernel recipes because
> > you also need it when generating an LZO compressed kernel (I like
> > my boot time to be under 1 second).
> >
> > It's a small dependency which is hard to automatically figure out,
> > since there are a number of ways to trigger it (we just found two).
> > I would welcome this patch very much, and I don't think many will
> > suffer…
>
> From linux.inc days there is a python snippet which can do this
> conditionally e.g. see
>
> https://github.com/kraj/meta-raspberrypi/blob/master/recipes-kernel/l
> inux/linux-rpi.inc#L121
Which is fine if you have a prebuild defconfig file however in many
cases we don't have that :(
Cheers,
Richard
next prev parent reply other threads:[~2016-08-10 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 12:32 [PATCH] kernel.bbclass: add lzop dependency Trevor Woerner
2016-08-01 14:07 ` Bruce Ashfield
2016-08-01 14:08 ` Burton, Ross
2016-08-02 13:52 ` Trevor Woerner
2016-08-03 12:53 ` Trevor Woerner
2016-08-04 1:39 ` Bruce Ashfield
2016-08-05 14:24 ` Trevor Woerner
2016-08-09 12:08 ` Mike Looijmans
2016-08-09 19:27 ` Khem Raj
2016-08-10 8:59 ` Richard Purdie [this message]
2016-08-10 16:07 ` Khem Raj
2016-08-10 16:46 ` Richard Purdie
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=1470819593.8166.68.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.