From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] adding a new machine configuration
Date: Thu, 1 Mar 2012 14:39:34 +0100 [thread overview]
Message-ID: <20120301143934.073f50a0@skate> (raw)
In-Reply-To: <4F4F74A4.2060909@gmail.com>
Le Thu, 01 Mar 2012 15:07:48 +0200,
Roland <rolandu@gmail.com> a ?crit :
> I have created a new machine configuration file.
>
> Target is Voipac iMX25 module ( http://voipac.com/#X25-DMM-254 ).
>
> I'm gonna also create one for iMX51.
>
> The problem is, the generated filesystem image won't work if don't
> change the fs/ubinize.cfg file (problem with alignment). And
> currently it's not possible to edit ubinize.cfg file in the buildroot
> configuration file.
I guess you're talking about the vol_alignment parameter, is this
correct?
> I'm interested in sharing the config and other files so, it can be
> merged to buildroot's git.
> But it's probably not possible until ubinize.cfg is configurable.
>
> Any comments by the people, who have commit access?
You can simply add a new configuration option in the menuconfig to
specify the alignment, with a default value equal to the one used in
the current ubinize.cfg. Then, you change the ubinize.cfg to something
like:
vol_alignment=__BR_VOL_ALIGNMENT__
And then when the filesystem image is built, you copy this ubinize.cfg
somewhere, making the replacement of __BR_VOL_ALIGNMENT__ with the
value from the configuration, and you run ubinize with it.
Is this what you're looking for?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-01 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 13:07 [Buildroot] adding a new machine configuration Roland
2012-03-01 13:39 ` Thomas Petazzoni [this message]
2012-03-02 16:46 ` Roland
2012-03-02 22:41 ` Arnout Vandecappelle
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=20120301143934.073f50a0@skate \
--to=thomas.petazzoni@free-electrons.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