From: Ezequiel Garcia <ezequiel@collabora.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 4/4] rockchip: rk3399: Add Ficus EE board support
Date: Tue, 04 Dec 2018 18:12:54 -0300 [thread overview]
Message-ID: <0ef60c1954aa3247e6bee4ef922f84e9cfc340d9.camel@collabora.com> (raw)
In-Reply-To: <E1g7mvM-0002Cg-UX@mail.theobroma-systems.com>
On Wed, 2018-10-03 at 21:35 +0200, Philipp Tomsich wrote:
> > Add board support for Ficus EE board from Vamrs. This board utilizes
> > common Rock960 family support.
> >
> > Following peripherals are tested and known to work:
> > * Gigabit Ethernet
> > * USB 2.0
> > * MMC
> >
> > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> > [Reworked based on common Rock960 family support]
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > Reviewed-by: Simon Glass <sjg@chromium.org>
> > ---
> >
> > Changes in v3: Modified the DRAM config header from LPDDR3 to DDR3
> >
> > Changes in v2: None
> >
> > arch/arm/dts/Makefile | 1 +
> > arch/arm/dts/rk3399-ficus.dts | 78 ++++++++++++++++++++++++++++++++++
> > configs/ficus-rk3399_defconfig | 71 +++++++++++++++++++++++++++++++
> > 3 files changed, 150 insertions(+)
> > create mode 100644 arch/arm/dts/rk3399-ficus.dts
> > create mode 100644 configs/ficus-rk3399_defconfig
> >
>
> Reviewed-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Two months have passed... guys, what's the problem with this series?
Regards,
Ezequiel
next prev parent reply other threads:[~2018-12-04 21:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 19:02 [U-Boot] [PATCH v3 0/4] Add Rock960 and Ficus 96Board support Manivannan Sadhasivam
2018-09-27 19:02 ` [U-Boot] [PATCH v3 1/4] arm: dts: rockchip: add some common pin-settings to rk3399 Manivannan Sadhasivam
2018-10-03 19:05 ` Peter Robinson
2018-10-03 19:35 ` [U-Boot] [U-Boot, v3, " Philipp Tomsich
2018-12-06 15:02 ` Philipp Tomsich
2018-09-27 19:02 ` [U-Boot] [PATCH v3 2/4] rockchip: rk3399: Add common Rock960 family from Vamrs Manivannan Sadhasivam
2018-10-02 11:21 ` Simon Glass
2018-10-02 14:01 ` Manivannan Sadhasivam
2018-10-03 19:34 ` Philipp Tomsich
2018-10-03 19:36 ` Ezequiel Garcia
2018-10-03 19:41 ` Philipp Tomsich
2018-10-04 3:15 ` Manivannan Sadhasivam
2018-10-03 19:04 ` Peter Robinson
2018-12-06 15:02 ` [U-Boot] [U-Boot, v3, " Philipp Tomsich
2018-09-27 19:03 ` [U-Boot] [PATCH v3 3/4] rockchip: rk3399: Add Rock960 CE board support Manivannan Sadhasivam
2018-10-02 11:21 ` Simon Glass
2018-10-03 19:06 ` Peter Robinson
2018-10-03 19:35 ` [U-Boot] [U-Boot, v3, " Philipp Tomsich
2018-11-22 20:53 ` Ezequiel Garcia
2018-12-06 15:02 ` Philipp Tomsich
2018-09-27 19:03 ` [U-Boot] [PATCH v3 4/4] rockchip: rk3399: Add Ficus EE " Manivannan Sadhasivam
2018-10-02 11:21 ` Simon Glass
2018-10-03 19:35 ` [U-Boot] [U-Boot, v3, " Philipp Tomsich
2018-12-04 21:12 ` Ezequiel Garcia [this message]
2018-12-04 21:21 ` Philipp Tomsich
2018-12-04 22:02 ` Ezequiel Garcia
2018-12-06 14:39 ` Philipp Tomsich
2018-12-06 15:02 ` Philipp Tomsich
2018-09-28 5:35 ` [U-Boot] [PATCH v3 0/4] Add Rock960 and Ficus 96Board support Daniel Lezcano
2018-10-26 17:17 ` Manivannan Sadhasivam
2018-10-26 18:00 ` Philipp Tomsich
2018-12-06 7:53 ` Alexander Graf
2018-12-06 14:57 ` Philipp Tomsich
2018-12-06 15:00 ` Philipp Tomsich
2018-12-06 15:20 ` Tom Rini
2018-12-06 15:37 ` Manivannan Sadhasivam
2018-12-06 16:08 ` 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=0ef60c1954aa3247e6bee4ef922f84e9cfc340d9.camel@collabora.com \
--to=ezequiel@collabora.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