From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>, Koen Kooi <koen@beagleboard.org>
Subject: Re: [PATCH V2] [RFC] kernel: rework kernel and module classes to allow for building out-of-tree modules
Date: Mon, 21 Mar 2011 17:28:39 +0000 [thread overview]
Message-ID: <1300728519.30423.3935.camel@rex> (raw)
In-Reply-To: <4D81E52E.7030808@mlbassoc.com>
On Thu, 2011-03-17 at 04:40 -0600, Gary Thomas wrote:
> On 03/16/2011 01:26 PM, Darren Hart wrote:
> > On 03/16/2011 10:54 AM, Koen Kooi wrote:
> >>
> >> Op 16 mrt 2011, om 18:04 heeft Darren Hart het volgende geschreven:
> >>
> >>> NOT FOR INCLUSION
> >>>
> >>> Before we include something like this, it needs review from folks like Koen and
> >>> Gary to confirm it works in their environment as well.
> >>>
> >>> The existing infrastructure uses an external build tree which references the
> >>> kernel source in the work dir. If run with rm work, building external modules
> >>> will fail.
> >>>
> >>> This patch places a configured source tree in sysroots. Striking a balance
> >>> between minimal size and minimal maintenance is difficult. A fully configured
> >>> tree is about 500MB after a clean. This version leans on the side of caution and
> >>> removes only the obviously unecessary parts of the source tree to conserve
> >>> space, resulting in about 170MB. The arch directories would be some additional
> >>> pruning we could do. Given examples from the devel package from distributions, I
> >>> suspect this size could be reduced to 75MB or so, but at the cost of a much more
> >>> complex recipe which is likely to require a great deal more maintenance to keep
> >>> current with kernel releases.
> >>>
> >>> Care is also taken to clean the hostprogs in scripts, and the modules are
> >>> responsible for building them as needed. Although it is unclear to me if this is
> >>> really necessary, especially considering that modules put these bits back as
> >>> soon as they compile. If we are not generating an sstate package, I suspect we
> >>> can ignore these.
> >>>
> >>> Please try this with your modules and let me know how it does. I tried to take
> >>> non linux-yocto kernel recipes into account, but I have only tested with
> >>> linux-yocto and the hello-mod recipe so far.
> >>>
> >>> V2: o Address 000 perm quilt files (don't copy .pc dir)
> >>> o Clear linux-yocto meta dir from sysroots
> >>>
> >>> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> >>
> >> This one works beautifully, so:
> >>
> >> Acked-by: Koen Kooi<koen@dominion.thruhere.net>
> >
> > Thanks Koen.
> >
> > Gary, can you give this version a spin?
> >
> > If it works, I'm going to suggest we take this as is and carefully prune away bits we don't need over time so we can get adequate testing across multiple archs, platforms, and
> > modules. Same for the hostprogs cleaning bits.
> >
>
> It also worked for me. Thanks - you can add
>
> Acked-by: Gary Thomas <gary@mlbassoc.com>
Thanks all, I'm going to merge this to master.
Cheers,
Richard
prev parent reply other threads:[~2011-03-21 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 17:04 [PATCH V2] [RFC] kernel: rework kernel and module classes to allow for building out-of-tree modules Darren Hart
2011-03-16 17:54 ` Koen Kooi
2011-03-16 19:26 ` Darren Hart
2011-03-17 10:40 ` Gary Thomas
2011-03-21 17:28 ` Richard Purdie [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=1300728519.30423.3935.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=koen@beagleboard.org \
--cc=openembedded-core@lists.openembedded.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