Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developers Meeting after FOSDEM 2013
Date: Sun, 27 Jan 2013 21:41:05 +0200	[thread overview]
Message-ID: <510582D1.9040306@petroprogram.com> (raw)
In-Reply-To: <201301271709.49546.yann.morin.1998@free.fr>

27.1.2013 18:09, Yann E. MORIN kirjoitti:
> Thomas, All,
>
> On Friday 28 December 2012 Thomas Petazzoni wrote:
>> As was announced after the previous Developers Meeting, the next one
>> will take place on February 4th and 5th 2013 in Brussels, right after
>> the FOSDEM conference (http://www.fosdem.org).
>>
>> I've set up a Wiki page to coordinate the organization of this meeting,
>> see http://elinux.org/Buildroot:DeveloperDaysFOSDEM2013.

Oh, goody. <pkg>_CONFIG_FIXUP is on the list :-)
Submitting, final v3 tomorrow, I promise.... just get sidetracked by
other things

> I've started adding a few topics to be discused during the meeting, by
> adding the latest topics that have flown on the mailing list in the past
> few weeks. I've undoubtfully missed some of them!
>
> Please review, and add to this list.
>
> Looking forward to this moment! :-)
>
> Regards,
> Yann E. MORIN.
>

I think the current state of generating initramfs could be added to that
topic list too.

I did some quick testing of buildroot (2012.08)  kernel with embedded
initramfs size vs. also buildroot kernel but with hand made initramfs
inside it (both from the same sources of course)
and the results were 57 MB vs. 37 MB (xz-compressed kernel with no
compression for built-in initramfs).

Exactly same software stuff in both but different sizes because
different configuration knobs in linux .config-files and different
compression methods used.

So optimal initramfs generation (with right linux .config settings and
maybe with Gustavo's initramfs patches) with benchmark maybe
(size of output, ram taking to load/decompress and speed taking to
decompress) would be cool topic. :-)

Regards
Stefan

  parent reply	other threads:[~2013-01-27 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 20:29 [Buildroot] Buildroot Developers Meeting after FOSDEM 2013 Thomas Petazzoni
2012-12-28 20:45 ` Yann E. MORIN
2013-01-27 16:09 ` Yann E. MORIN
2013-01-27 16:22   ` Thomas Petazzoni
2013-02-01  4:01     ` Alex Bradbury
2013-02-01  8:31       ` Thomas Petazzoni
2013-01-27 19:41   ` Stefan Fröberg [this message]
2013-01-27 19:45     ` Stefan Fröberg

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=510582D1.9040306@petroprogram.com \
    --to=stefan.froberg@petroprogram.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox