All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build error
Date: Thu, 03 Jan 2008 19:55:04 +0200	[thread overview]
Message-ID: <477D2178.80801@promwad.com> (raw)
In-Reply-To: <477D0F57.9050204@carallon.com>

Hi Will,

I have not used initramfs, usually qtopia and other large stuff (X.org / GTK ) is run
from jffs2 filesystem on flash, e.g rootfs is not in RAM but in flash.

Have you tried to adjust these kernel settings:
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=1
CONFIG_BLK_DEV_RAM_SIZE=14000
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024

?

Regards,
Ivan


Will Wagner wrote:
> Ivan,
> 
> Thanks for your help. Think I have worked out the problem. Appeared to 
> have too large a rootfs so that the initramfs being built was very 
> large. Have worked round it for now by reducing the size of the rootfs 
> (qtopia4 was copying some unneeded files).
> 
> Any idea what the size limit is for a rootfs used with initramfs?
> 
> Thanks,
> 
> Will.
> 
> Ivan Kuten wrote:
>>> Thanks for the hint.
>>>
>>> I have compiled both with and without qtopia4 and got the verbose log. I
>>> can not see any difference on what is on the command line between the
>>> two versions.
>>>
>> Will,
>>
>> I can suggest as workaround to set BR2_KERNEL_none=y
>> and build kernel outside a buildroot tree and see if it working this way.
>>
>> Regards,
>> Ivan
> 


-- 

--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

  reply	other threads:[~2008-01-03 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 14:35 [Buildroot] Build error Will Wagner
2007-12-20 16:00 ` Ivan Kuten
2007-12-21 17:27   ` Will Wagner
2007-12-23 23:50     ` Ivan Kuten
2008-01-03 16:37       ` Will Wagner
2008-01-03 17:55         ` Ivan Kuten [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-23 12:29 Shashi Ranjan

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=477D2178.80801@promwad.com \
    --to=ivan.kuten@promwad.com \
    --cc=buildroot@busybox.net \
    /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.