From: Akshay Bhat <akshay.bhat@timesys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: imx: Add support for GE Bx50v3 boards
Date: Tue, 8 Mar 2016 17:48:32 -0500 [thread overview]
Message-ID: <56DF56C0.1080608@timesys.com> (raw)
In-Reply-To: <20160130040658.GA4528@linux-7smt.suse>
Hi Stefano,
On 01/29/2016 11:07 PM, Peng Fan wrote:
> Hi Akshay,
>
> On Fri, Jan 29, 2016 at 03:16:40PM -0500, Akshay Bhat wrote:
>> Add support for GE B450v3, B650v3 and B850v3 boards. The boards
>> are based on Advantech BA16 module which has a i.MX6D processor.
>> The boards support:
>> - FEC Ethernet
>> - USB Ports
>> - SDHC and MMC boot
>> - SPI NOR
>> - LVDS and HDMI display
>>
>> Basic information about the module:
>> - Module manufacturer: Advantech
>> - CPU: Freescale ARM Cortex-A9 i.MX6D
>> - SPECS:
>> Up to 2GB Onboard DDR3 Memory;
>> Up to 16GB Onboard eMMC NAND Flash
>> Supports OpenGL ES 2.0 and OpenVG 1.1
>> HDMI, 24-bit LVDS
>> 1x UART, 2x I2C, 8x GPIO,
>> 4x Host USB 2.0 port, 1x USB OTG port,
>> 1x micro SD (SDHC),1x SDIO, 1x SATA II,
>> 1x 10/100/1000 Mbps Ethernet, 1x PCIe X1 Gen2
>>
>> Signed-off-by: Akshay Bhat <akshay.bhat@timesys.com>
>
>
> Reviewed-by: Peng Fan <peng.fan@nxp.com>
>
> Regards,
> Peng.
>
If there are no further review comments, can this patch be applied in
the next merge window (for v2016.05)?
Also I have couple updates to the bx50v3.c file. Should I wait for this
patch to be applied before sending a new patch with the changes (wasn't
sure if you had a -next branch where the v2 patch was already applied)?
Thanks,
Akshay
next prev parent reply other threads:[~2016-03-08 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 20:16 [U-Boot] [PATCH v2] arm: imx: Add support for GE Bx50v3 boards Akshay Bhat
2016-01-30 4:07 ` Peng Fan
2016-03-08 22:48 ` Akshay Bhat [this message]
2016-03-08 23:31 ` Fabio Estevam
2016-03-09 8:36 ` Stefano Babic
2016-03-09 8:35 ` Stefano Babic
2016-03-09 11:47 ` Stefano Babic
2016-03-09 15:07 ` Akshay Bhat
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=56DF56C0.1080608@timesys.com \
--to=akshay.bhat@timesys.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