Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] board: add support for RIoTboard
Date: Thu, 05 Mar 2015 18:55:17 +0200	[thread overview]
Message-ID: <54F88A75.4090807@mail.bg> (raw)
In-Reply-To: <20150305160528.1591f186@free-electrons.com>

Hi Thomas,

On 03/05/2015 05:05 PM, Thomas Petazzoni wrote:
> Dear Nikolay Dimitrov,
>
> On Thu, 05 Mar 2015 16:58:47 +0200, Nikolay Dimitrov wrote:
>
>> Not really. Now as you're asking, I found that I'm doing this by habit
>> (probably inherited by some weird ARM board boot-requirements in the
>> past).
>
> Yes, some boards/bootloader configuration have the limitation that the
> first partition must be a FAT partition. In this case, it definitely
> makes sense to have two partitions, since a Linux root filesystem can
> hardly be stored in a FAT filesystem.
>
>> Would you prefer me to re-send the patch with instructions only for
>> single partition layout?
>
> Well, in the situation of this board, where the bootloader is stored
> raw and is capable of reading an ext2 filesystem, yes I believe a
> single partition makes more sense.
>
> You can ask Buildroot to install the uImage and DTB to /boot in the
> root filesystem. However, for the extlinux.config file, you'll have to
> add a post-build script to do this.

Thanks for your comments. I think this is better than my initial
proposal. Patch is on the way.

Regards,
Nikolay

      reply	other threads:[~2015-03-05 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 14:31 [Buildroot] [PATCH v2 1/1] board: add support for RIoTboard Nikolay Dimitrov
2015-03-05 14:37 ` Thomas Petazzoni
2015-03-05 14:58   ` Nikolay Dimitrov
2015-03-05 15:05     ` Thomas Petazzoni
2015-03-05 16:55       ` Nikolay Dimitrov [this message]

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=54F88A75.4090807@mail.bg \
    --to=picmaster@mail.bg \
    --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