From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] kernel NOTE messages fix
Date: Tue, 28 Sep 2010 13:06:30 -0700 [thread overview]
Message-ID: <4CA24AC6.9080502@mentor.com> (raw)
In-Reply-To: <AANLkTinMWT7K-h+hH0LvPD119Nxxpitro=f6igQvL7-K@mail.gmail.com>
Frans Meulenbroeks wrote:
[snip]
> 2) add them to kernel-dev. That way the NOTE disappears. However this
> does increase the kernel-dev package size with 90 MB or so.
> Technically it would allow building out-of-kernel modules on the
> target. Then again currently this is not possible and I have never
> heard complaints about it (actually for embedded systems it is often
> not a good plan to build on the target, although with current high end
> systems this becomes more feasible).
Did you try implementing this? Without a few other changes (that I
couldn't get 100% right) there's problems with the scripts/ and
arch/$ARCH/boot/ tools being the wrong binary format. Which is a shame
as we could provide a kernel-src package with that stuff fixed.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-28 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 16:39 [RFC] kernel NOTE messages fix Frans Meulenbroeks
2010-09-28 17:04 ` Denys Dmytriyenko
2010-09-28 17:15 ` Roman I Khimov
2010-09-28 20:06 ` Tom Rini [this message]
2010-09-28 21:16 ` Petr Štetiar
2010-09-28 21:14 ` Petr Štetiar
2010-09-29 6:34 ` Eric Bénard
2010-09-29 6:46 ` Frans Meulenbroeks
2010-09-29 18:18 ` Tom Rini
2010-09-29 18:37 ` Denys Dmytriyenko
2010-09-29 20:16 ` Frans Meulenbroeks
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=4CA24AC6.9080502@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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