Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/8] configs: defconfigs for Atmel boards
Date: Fri, 01 May 2015 14:02:08 +0200	[thread overview]
Message-ID: <55436B40.3030007@mind.be> (raw)
In-Reply-To: <20150501093459.1814ec0f@free-electrons.com>

On 05/01/15 09:34, Thomas Petazzoni wrote:
> Ryan, Alex,
> 
> On Thu, 30 Apr 2015 09:33:50 -0500, Ryan Barnett wrote:
> 
>> Since you are moving all of the Atmel boards to use NAND boot
>> configuration, it would be good to have a 'README' that explains how
>> to load the boards utilizing the SAM-BA tool (it appears all the NAND
>> configurations are using this). At minimum it would be to point to
>> Linux4SAM wiki for loading instructions.
> 
> Fully agreed.
> 
> Alexandre, please also include generating a NAND capable filesystem
> image as part of those defconfig, so that they can easily be
> flashed/used on the boards. I guess UBI images is going to be the most
> appropriate solution. But clearly, such defconfigs should not generate
> just a tarball.

 Actually, I think it's better to use SD card images where possible.

- If you're using it just for experimentation, then the SD card is a much more
flexible and less risky way to experiment. Personally, I even prefer
kernel-linked-with-initramfs (and DTB) images, since that's just a single file
and it automatically gives you the rest of the SD card as a FAT partition.

- If you want to use it for an actual product (prototype), then you're anyway
going to have to study in a bit more detail how the flash works and you'll
probably want to do a slightly more complicated flash partitioning.


 That said, I do think it's really useful to have those tcl scripts for using
SAM-BA.


 And of course, since I never use the defconfigs myself, my opinion is probably
not that important.


 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2015-05-01 12:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 12:51 [Buildroot] [PATCH 0/8] configs: defconfigs for Atmel boards Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 1/8] configs: update at91sam9g45m10ek defconfig Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 2/8] configs: add defconfig for Atmel at91sam9rlek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 3/8] configs: add defconfig for Atmel at91sam9x5ek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 4/8] configs: add defconfig for Atmel sama5d3xek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 5/8] configs: add defconfig for Atmel sama5d4ek Alexandre Belloni
2015-04-30 12:51 ` [Buildroot] [PATCH 6/8] configs: add defconfig for Atmel sama4d4 Xplained Ultra Alexandre Belloni
2015-05-01  7:35   ` Thomas Petazzoni
2015-04-30 12:51 ` [Buildroot] [PATCH 7/8] configs: add defconfig for Atmel sama5d3 Xplained Alexandre Belloni
2015-04-30 14:46   ` Ryan Barnett
2015-04-30 15:14     ` Alexandre Belloni
2015-04-30 15:16       ` Ryan Barnett
2015-05-01  7:33       ` Thomas Petazzoni
2015-04-30 12:51 ` [Buildroot] [PATCH 8/8] configs: rename atmel_xplained_defconfig Alexandre Belloni
2015-04-30 14:36   ` Ryan Barnett
2015-04-30 14:40     ` Alexandre Belloni
2015-04-30 14:33 ` [Buildroot] [PATCH 0/8] configs: defconfigs for Atmel boards Ryan Barnett
2015-04-30 14:40   ` Alexandre Belloni
2015-05-01  7:34   ` Thomas Petazzoni
2015-05-01 12:02     ` Arnout Vandecappelle [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=55436B40.3030007@mind.be \
    --to=arnout@mind.be \
    --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