From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Linux kernel recipes
Date: Tue, 20 Feb 2007 16:17:39 +0100 [thread overview]
Message-ID: <200702201617.42247.openembedded@hrw.one.pl> (raw)
Some time ago I added packages/linux/linux_2.6.19.bb (currently
linux_2.6.20.bb) as some kind of generic Linux kernel recipe. Currently
it is used for Progear and Simpad targets.
Today we got linux-x86_2.6.20.bb which differ in just one thing.. NAME. It
does not contain any patches - just source archive and kernel
configuration file. Can it be merged into linux_2.6.20.bb?
We have few other 2.6.20 recipes but they are more machine specific
(efika, ixp4xx, dht-walnut).
Second thing is list of kernels. We have 149 files in packages/linux/ -
some targets have few kernels there - can we get rid of not used ones?
Many machines want 1-2 kernels (stable one and development one) so why we
have 4-6 kernels for one machine? Can this be cleared in some way?
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
In theory there is no difference between practice and theory
next reply other threads:[~2007-02-20 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 15:17 Marcin Juszkiewicz [this message]
2007-02-20 17:01 ` Linux kernel recipes Stelios Koroneos
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=200702201617.42247.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--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 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.