From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB)
Date: Thu, 21 Apr 2016 13:29:05 +0200 [thread overview]
Message-ID: <20160421132905.7c271814@free-electrons.com> (raw)
In-Reply-To: <CAGm1_kughQAzmdbaQo4bBb4+-a1rL9-1aZunOCuLtFH4pgSUhA@mail.gmail.com>
Hello,
On Thu, 21 Apr 2016 12:55:12 +0200, Yegor Yefremov wrote:
> >> Have made basic tests, i.e. changing configuration for barebox and
> >> barebox-2 and running make to see, if proper barebox was compiled.
> >> Everything is working the way it was in v4 from this point of view.
> >
> > Thanks! Did you flash a bare SD card or the internal eMMC with boot.vfat and
> > rootfs.ext4 as part of the tests?
>
> If I copy your images (MLO, barebox.bin) directly to the FAT
> partition, everything starts as expected. But I dd boot.vfat, the
> system doesn't boot and shows only CCCCC, though I have no problems
> mounting the first partition in Linux.
>
> sudo dd if=/tmp/boot.vfat of=/dev/sdd1 bs=1M
So this means that the Barebox build is OK, and only the genimage part
is causing problems. But this doesn't prevent from merging the barebox
aspects of the series (patches 1 to 6), which are really the important
part. The last patch is really more a defconfig proving that it works,
I am not even sure that in practice we want to merge a defconfig for
BeagleBone that is just different from beaglebone_defconfig in the fact
that it uses Barebox instead of U-Boot. Peter?
Peter, I think you looked at using genimage on AM335x, what were your
conclusion? On OMAP3, there were some very strict geometry restrictions
in the romcode, but I don't remember if your conclusion is that they
also apply to AM335x or not.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-21 11:29 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 22:35 [Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB) Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 1/7] barebox: support multi-image-build image selection Pieter Smith
2016-03-31 5:44 ` Yegor Yefremov
2016-04-06 20:28 ` Pieter Smith
2016-04-02 15:31 ` Thomas Petazzoni
2016-04-04 22:08 ` Arnout Vandecappelle
2016-04-04 22:16 ` Arnout Vandecappelle
2016-03-20 22:35 ` [Buildroot] [PATCH v4 2/7] barebox: friendly error on missing built image Pieter Smith
2016-03-31 6:01 ` Yegor Yefremov
2016-03-20 22:35 ` [Buildroot] [PATCH v4 3/7] barebox: support custom barebox output image name Pieter Smith
2016-03-31 6:03 ` Yegor Yefremov
2016-04-04 22:31 ` Arnout Vandecappelle
2016-04-04 23:20 ` Arnout Vandecappelle
2016-04-06 14:53 ` Thomas Petazzoni
2016-04-06 20:14 ` Pieter Smith
2016-04-06 23:06 ` Arnout Vandecappelle
2016-04-08 7:51 ` Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 4/7] barebox: introduce barebox-package function Pieter Smith
2016-03-31 6:12 ` Yegor Yefremov
2016-04-04 22:59 ` Arnout Vandecappelle
2016-04-04 23:23 ` Arnout Vandecappelle
2016-04-06 20:26 ` Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 5/7] barebox: extract package name argument Pieter Smith
2016-03-31 6:16 ` Yegor Yefremov
2016-04-04 23:01 ` Arnout Vandecappelle
2016-03-20 22:35 ` [Buildroot] [PATCH v4 6/7] barebox: support 2nd config build Pieter Smith
2016-03-31 6:17 ` Yegor Yefremov
2016-04-04 23:25 ` Arnout Vandecappelle
2016-04-24 7:53 ` Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 7/7] beaglebone: adds barebox bootloader defconfig Pieter Smith
2016-03-31 6:21 ` Yegor Yefremov
2016-04-04 23:37 ` Arnout Vandecappelle
2016-04-19 20:26 ` Pieter Smith
2016-04-19 22:13 ` Arnout Vandecappelle
2016-04-23 11:39 ` Pieter Smith
2016-03-21 11:38 ` [Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB) Yegor Yefremov
2016-03-21 11:56 ` Pieter Smith
2016-04-19 19:24 ` Thomas Petazzoni
2016-04-19 20:17 ` Pieter Smith
2016-04-20 14:42 ` Yegor Yefremov
2016-04-20 16:42 ` Pieter Smith
2016-04-21 10:55 ` Yegor Yefremov
2016-04-21 11:29 ` Thomas Petazzoni [this message]
2016-04-23 13:01 ` Pieter Smith
2016-04-23 13:11 ` Thomas Petazzoni
2016-04-23 14:35 ` Pieter Smith
2016-04-23 14:50 ` Thomas Petazzoni
2016-04-23 16:18 ` Pieter Smith
2016-04-23 19:26 ` Thomas Petazzoni
2016-04-24 8:04 ` Pieter Smith
2016-04-24 8:16 ` Thomas Petazzoni
2016-04-24 8:32 ` Pieter Smith
2016-04-24 8:47 ` Thomas Petazzoni
2016-04-24 8:50 ` Pieter Smith
2016-04-24 8:47 ` Pieter Smith
2016-04-24 19:18 ` Peter Korsgaard
2016-04-24 21:26 ` Pieter Smith
2016-04-23 13:05 ` Pieter Smith
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=20160421132905.7c271814@free-electrons.com \
--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