From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 7/7] beaglebone: adds barebox bootloader defconfig
Date: Wed, 20 Apr 2016 00:13:07 +0200 [thread overview]
Message-ID: <5716AD73.30309@mind.be> (raw)
In-Reply-To: <20160419202649.GA20663@smipidev>
On 04/19/16 22:26, Pieter Smith wrote:
> On Tue, Apr 05, 2016 at 01:37:46AM +0200, Arnout Vandecappelle wrote:
>> On 03/20/16 23:35, Pieter Smith wrote:
>>> * Builds the barebox MLO and bootloader.
>>> * Generates a barebox environment that boots from eMMC by default.
>>> * Barebox integrates a perfectly good device-tree for the bbb, so no dtb is
>>> being generated with the kernel.
>>>
>>> Signed-off-by: Pieter Smith <pieter@boesman.nl>
>>> ---
>>> board/beaglebone/barebox.env/boot/sd | 6 +++++
>>> board/beaglebone/barebox.env/config-board | 4 +++
>>> configs/beaglebone_barebox_defconfig | 41 +++++++++++++++++++++++++++++++
>>> 3 files changed, 51 insertions(+)
>>> create mode 100644 board/beaglebone/barebox.env/boot/sd
>>> create mode 100644 board/beaglebone/barebox.env/config-board
>>> create mode 100644 configs/beaglebone_barebox_defconfig
>>>
>>> diff --git a/board/beaglebone/barebox.env/boot/sd b/board/beaglebone/barebox.env/boot/sd
>>> new file mode 100644
>>> index 0000000..7a80e29
>>> --- /dev/null
>>> +++ b/board/beaglebone/barebox.env/boot/sd
>>> @@ -0,0 +1,6 @@
>>> +#!/bin/sh
>>
>> Is that needed/useful?
>
> If you are referring to the interpreter specification: I suspect no, but all
> barebox scripts in barebox specify the interpreter, so I would like not to
> stray from the convention.
That's what I meant. So ok.
>
> If you are referring to the presence of the sd script: Yes. The device name
> needs to be changed from the default to work with the Beaglebone.
>
>>> +
>>> +global.bootm.image=/boot/zImage
>>> +#global.bootm.oftree=/boot/oftree
>>
>> Maybe repeat here the comment about using the built-in DT.
>
> ACK. Will be in v5 of the patch-set. I will not be removing the commented lines
> though. The convention is to leave these in so that the user can tune them if
> he wants something different.
ok.
>
>>> +#global.bootm.initrd=<path to initrd>
>>
>> I would remove this line, it's not very useful.
>
> These are kept in the scripts for a reason. These scripts are left as
> placeholders for easy tuning by the user. I also decided to retain this because
> it is present in the defaults included with barebox. If you feel strongly about
> this, I can remove it, but I would prefer to keep it in.
ok.
>
> [snip]
>
>>> +# system
>>> +BR2_TARGET_GENERIC_HOSTNAME="beaglebone"
>>> +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y
>>> +BR2_TARGET_GENERIC_GETTY_PORT="ttyO0"
>>
>> Does the default (console) not work well?
>
> I inherited this from the beaglebone_defconfig. I know that the beaglebone uses
> a different serial port for the console than the Phytec am33xx modules (the
> default for the BSP), so I am quite sure this is necessary.
The serial port is already set in the barebox config, and is already passed on
the kernel command line, so there shouldn't be a need to set it explicitly again
in the buildroot config. The default getty port is 'console', which means to use
the kernel console as getty port. In most cases that's what you want.
The beaglebone defconfig still had an explicit getty port because it is still
from the time that the default getty port was tty1.
So, ideally, please test that it still works without this line. But since you
don't have a working beaglebone at the moment that will be tough...
[snip]
>>> +# Use the barebox built-in dtb
>>> +# BR2_LINUX_KERNEL_DTS_SUPPORT is not set
>>
>> Good to put this here!
>
> As per your recommendation on v4 of the patch-set.
I'm so great :-)
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-04-19 22:13 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 [this message]
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
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=5716AD73.30309@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