From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] ti: Add am335x-pocketbeagle to am335x_evm_defconfig.
Date: Tue, 30 Apr 2019 10:02:11 -0700 [thread overview]
Message-ID: <871s1jctpo.fsf@ponder> (raw)
In-Reply-To: <20190430151605.GJ31207@bill-the-cat>
On 2019-04-30, Tom Rini wrote:
> On Mon, Apr 29, 2019 at 04:12:30PM -0700, Vagrant Cascadian wrote:
>
>> Add am335x-pocketbeagle to CONFIG_OF_LIST in am335x_evm_defconfig.
>>
>> Signed-off-by: Vagrant Cascadian <vagrant@debian.org>
>
> We need to update include/configs/am335x_evm.h too so that it detects
> this variant and loads the right dtb.
I believe this was already added in the original commit that added
partial support:
"findfdt="\
...
"if test $board_name = A335PBGL; then " \
"setenv fdtfile am335x-pocketbeagle.dtb; fi; " \
In my tests, it loaded the correct .dtb file; Is there something I'm
missing?
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190430/368c4298/attachment.sig>
next prev parent reply other threads:[~2019-04-30 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 23:12 [U-Boot] [PATCH 0/2] Finish support for enabling BeagleBoard.org PocketBeagle Vagrant Cascadian
2019-04-29 23:12 ` [U-Boot] [PATCH 1/2] ti: Add device-tree for am335x-pocketbeagle Vagrant Cascadian
2019-04-30 15:16 ` Tom Rini
2019-05-03 18:21 ` Tom Rini
2019-04-29 23:12 ` [U-Boot] [PATCH 2/2] ti: Add am335x-pocketbeagle to am335x_evm_defconfig Vagrant Cascadian
2019-04-30 15:16 ` Tom Rini
2019-04-30 17:02 ` Vagrant Cascadian [this message]
2019-04-30 17:24 ` Tom Rini
2019-05-01 11:40 ` Tom Rini
2019-05-03 18:21 ` Tom Rini
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=871s1jctpo.fsf@ponder \
--to=vagrant@debian.org \
--cc=u-boot@lists.denx.de \
/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