From: Junqian Gordon Xu <xjqian@gmail.com>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@lists.openembedded.org>
Cc: angstrom-distro-devel@linuxtogo.org
Subject: [RFC] add kernel-module-loop to roofs for collie and tosa
Date: Wed, 30 Jan 2008 05:11:14 -0600 [thread overview]
Message-ID: <47A05B52.6000202@gmail.com> (raw)
altboot-console-image needs loopback file support either in the kernel
or as kernel module. CONFIG_BLK_DEV_LOOP=m were set for both collie and
tosa. Other Z deviced has loopback file support built into the kernel.
I would propose the following change [both dev and stable] to pack
kernel-module-loop into the default rootfs for collie and tosa; and bump
PR for task-base.
============================================================
--- conf/machine/collie.conf c23a85835bc13ac978f36742cfc8ccf5880e0ec8
+++ conf/machine/collie.conf 062e7d70c35cf3f4db0e10e8b9f254fd47e39952
@@ -14,5 +14,7 @@ IMAGE_FSTYPES ?= "jffs2 tar.gz"
IMAGE_LINGUAS = ""
IMAGE_FSTYPES ?= "jffs2 tar.gz"
+MACHINE_EXTRA_RRECOMMENDS += "kernel-module-loop"
+
ROOT_FLASH_SIZE = "14"
# actually 14680064, see EXTRA_IMAGECMD above
============================================================
--- conf/machine/tosa.conf bdda7deb7ee9f2d950ee255097efcdfa1cf7a39a
+++ conf/machine/tosa.conf 94e6eda28ba66d57c2ef49c6c11c78bf0c311349
@@ -7,6 +7,6 @@ IMAGE_FSTYPES ?= "jffs2"
IMAGE_FSTYPES ?= "jffs2"
# wlan-ng Modules
-MACHINE_EXTRA_RRECOMMENDS += "wlan-ng-modules-usb"
+MACHINE_EXTRA_RRECOMMENDS += "wlan-ng-modules-usb kernel-module-loop"
ROOT_FLASH_SIZE = "28"
Regards
Gordon
next reply other threads:[~2008-01-30 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 11:11 Junqian Gordon Xu [this message]
2008-01-30 11:23 ` [Angstrom-devel] [RFC] add kernel-module-loop to roofs for collie and tosa Marcin Juszkiewicz
2008-01-30 12:22 ` Junqian Gordon Xu
2008-01-30 16:11 ` Marcin Juszkiewicz
2008-02-01 4:21 ` Junqian Gordon Xu
2008-01-30 12:45 ` Thomas Kunze
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=47A05B52.6000202@gmail.com \
--to=xjqian@gmail.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--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.