From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] board/beaglebone: fix boot on BeagleBone Black
Date: Fri, 8 Nov 2019 22:09:44 +0100 [thread overview]
Message-ID: <20191108220944.326df425@windsurf> (raw)
In-Reply-To: <20191102223839.16262-2-unixmania@gmail.com>
Hello Carlos,
On Sat, 2 Nov 2019 19:38:38 -0300
unixmania at gmail.com wrote:
> From: Carlos Santos <unixmania@gmail.com>
>
> Commit 68b5b79b2f has set the getty port to the default console but left
> "ttyO0" in bootargs, in the U-Boot environment. Use "ttyS0", instead.
>
> Also set loadaddr to 0x82000000 and fdtaddr to 0x88000000, replacing the
> ancient U-Boot 2013.10-dirty default values that cause system hangs.
Where are we using U-Boot 2013.10-dirty on BeagleBone ?
$ grep UBOOT_CUSTOM_VERSION_VALUE configs/beaglebone*
configs/beagleboneai_defconfig:BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2019.04"
configs/beaglebone_defconfig:BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2019.07"
configs/beaglebone_qt5_defconfig:BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2016.09.01"
And these are upstream, unpatched, versions.
Could you clarify this? Otherwise the patch looks good, of course.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-08 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 22:38 [Buildroot] [PATCH 0/2] configs/beaglebone: fix boot hang and update kernel unixmania at gmail.com
2019-11-02 22:38 ` [Buildroot] [PATCH 1/2] board/beaglebone: fix boot on BeagleBone Black unixmania at gmail.com
2019-11-08 21:09 ` Thomas Petazzoni [this message]
2019-11-08 23:05 ` Carlos Santos
2019-11-09 16:42 ` Carlos Santos
2019-11-02 22:38 ` [Buildroot] [PATCH 2/2] configs/beaglebone: use the new BeagleBoard/BeagleBone kernel repository unixmania at gmail.com
2019-11-08 21:12 ` Thomas Petazzoni
2019-11-08 23:11 ` Carlos Santos
2019-11-09 14:19 ` 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=20191108220944.326df425@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.