From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] device model bringup of AM335x bbw and sk-evm
Date: Mon, 29 Feb 2016 09:02:50 -0500 [thread overview]
Message-ID: <20160229140250.GL23166@bill-the-cat> (raw)
In-Reply-To: <1456754309-20706-1-git-send-email-mugunthanvnm@ti.com>
On Mon, Feb 29, 2016 at 07:28:26PM +0530, Mugunthan V N wrote:
> This patch series enables Driver Model and Device tree usage for
> AM335x Beagle Bone White and AM335x EVMsk tested it on same with
> loading file from MMC and over TFTP. (Loga [1]). Also pushed a
> branch [2] for reference.
>
> [1]: http://pastebin.ubuntu.com/15243394/
> [2]: git://git.ti.com/~mugunthanvnm/ti-u-boot/mugunth-ti-u-boot.git am335x-dm
I really want to hold off on doing more am335x DM conversions until we
pull in Simon's series that lets us do FIT images in SPL and thus we can
have all of the am335x family at least (and maybe more, we'll have to
see) supported in a single build again, like we can in the non-DM case.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160229/a0de80af/attachment.sig>
prev parent reply other threads:[~2016-02-29 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 13:58 [U-Boot] [PATCH 0/3] device model bringup of AM335x bbw and sk-evm Mugunthan V N
2016-02-29 13:58 ` [U-Boot] [PATCH 1/3] include: configs: am335x_evm: add FAT_ENV configs when env is in fat Mugunthan V N
2016-02-29 13:58 ` [U-Boot] [PATCH 2/3] am335x-bbw: Add am335x_bone_defconfig using CONFIG_DM Mugunthan V N
2016-02-29 13:58 ` [U-Boot] [PATCH 3/3] am437x-sk: add am335x_gp_evm_defconfig " Mugunthan V N
2016-02-29 14:02 ` Tom Rini [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=20160229140250.GL23166@bill-the-cat \
--to=trini@konsulko.com \
--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