All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junqian Gordon Xu <xjqian@gmail.com>
To: angstrom-distro-devel@linuxtogo.org
Cc: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [Angstrom-devel] [RFC] add kernel-module-loop to roofs for	collie and tosa
Date: Wed, 30 Jan 2008 06:22:52 -0600	[thread overview]
Message-ID: <47A06C1C.10205@gmail.com> (raw)
In-Reply-To: <200801301223.17721.openembedded@haerwu.biz>

On 01/30/2008 05:23 AM, Marcin Juszkiewicz wrote:
> Dnia Wednesday, 30 of January 2008, Junqian Gordon Xu napisał:
>> altboot-console-image needs loopback file support either in the kernel
>> or as kernel module. 
> 
> It is not 'altboot-console-image' which needs it but altboot. 

You are right, but practically it's not nice to have users to go find 
kernel-module-loop before they can install roofs as a loopback image at 
SD/CF. For tosa, the typical case is to install altboot-console-image 
first then use altboot to install another image.

>> CONFIG_BLK_DEV_LOOP=m were set for both collie and tosa. Other Z deviced
>> has loopback file support built into the kernel. 
> 
> Probably not for long as kernel size increase with each version ;(

We can set it as module for all devices, sooner or later.

>> 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.
> 
> As altboot needs it then it has to be added as RRECOMMENDS to altboot 
> recipe rather.

The point is to have it available with altboot at the very beginning. 
Although it's not techinically RDEPENDS, should we set it as RDEPENDS to 
altboot recipe?

Regards
Gordon



  reply	other threads:[~2008-01-30 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 11:11 [RFC] add kernel-module-loop to roofs for collie and tosa Junqian Gordon Xu
2008-01-30 11:23 ` [Angstrom-devel] " Marcin Juszkiewicz
2008-01-30 12:22   ` Junqian Gordon Xu [this message]
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=47A06C1C.10205@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.