From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] configs/acmesystems_aria_g25: new configs
Date: Tue, 30 Jun 2015 08:24:41 -0300 [thread overview]
Message-ID: <55927C79.1080700@zacarias.com.ar> (raw)
In-Reply-To: <CA+TH9Vkn625DJy8xzD-WCSZMpbPF_jE2C_eZ_jnVSfNFRv7NcA@mail.gmail.com>
On 30/06/15 07:21, Angelo Compagnucci wrote:
> Hi Gustavo,
Hi Angelo.
>> create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config
>> create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config
>> create mode 100644 board/acmesystems/aria-g25/readme.txt
>> create mode 100644 configs/acmesystems_aria_g25_128mb_defconfig
>> create mode 100644 configs/acmesystems_aria_g25_256mb_defconfig
>
> Can we agree on the configs name format? Sergio usually uses the
> format "acme-BOARD-MEMORY", I used acme-arietta-128m_defconfig for
> example. I really prefer to have a standard name format!
Of course, though i don't know who Sergio is :)
But you must follow the rule as well, is it acme (configs/) or
acmesystems (board/) ?
It's not consistent for them to differ.
> This is better:
>
> echo ',32,6\n;' | sfdisk -uM /dev/sdX
I've used the xplained readme as basis.
Ideally we should script this thing up, probably making a somewhat
generic one that takes parameters from an image file defined in the BR
config.
> Config files for at91bootstrap are not really needed cause Sergio
> shipped them in it's own at91bootstrap fork, so you should simply use
> something like this in your bootstrap defconfig:
>
> BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="aria-128m"
I've missed the fact that the kernel command line is specified in the
dts, so yes it seems reasonable.
Regards.
next prev parent reply other threads:[~2015-06-30 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 21:38 [Buildroot] [PATCH v2] configs/acmesystems_aria_g25: new configs Gustavo Zacarias
2015-06-30 3:23 ` Baruch Siach
2015-06-30 11:07 ` Gustavo Zacarias
2015-06-30 10:21 ` Angelo Compagnucci
2015-06-30 11:24 ` Gustavo Zacarias [this message]
2015-06-30 12:09 ` Angelo Compagnucci
2015-06-30 12:12 ` Thomas Petazzoni
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=55927C79.1080700@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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