mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Beniamino Galvani <b.galvani@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/11] ARM: add initial support for Rockchip boards
Date: Mon, 28 Apr 2014 09:26:27 +0200	[thread overview]
Message-ID: <20140428072627.GN5858@pengutronix.de> (raw)
In-Reply-To: <1398591044-3616-1-git-send-email-b.galvani@gmail.com>

Hi Beniamino,

On Sun, Apr 27, 2014 at 11:30:33AM +0200, Beniamino Galvani wrote:
> This series adds an initial support for Rockchip SoCs and has been
> tested on a Radxa Rock board, on which I'm able to load a kernel from
> the network and boot it [1].
> 
> At the moment Barebox must be chainloaded from the Rockchip binary
> bootloader which performs low-level initializations and loads Barebox
> from the "boot" partition on the NAND.
> 
> Barebox should be written using the same procedure used for kernels:
> it must be prepared with the mkimage tool and then written with
> rkflashkit.
> 
> There is a u-boot code released by Rockchip [2] which probably
> includes all the low-level initializations but I'm not brave enough to
> try it.
> 
> The patchset adds ethernet and pinctrl drivers, PLL and clocks
> initialization, and code to power on the external PHY of the board
> through the PMIC.

Awesome! I'm happy to see barebox support for one of the more popular
Linux ARM architectures.

The patches look quite good and there's not much to be done to
make them ready for merging.

I'm just on the way to merge the Linux devicetree files into barebox
and use them where possible so we do not duplicate the devicetrees in
barebox. Could you post a followup once to base the rockchip dts files
on the Linux dts files once I have everything in place? I saw that you
already use the mainline dts files, but these do not contain the
ethernet nodes for example.

Also I'd like to let rockchip use the multi image mechanism. This is not
much work when you know what to do. You could change it yourself or I do
the change for you, but in this case, could you give the result a test?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2014-04-28  7:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27  9:30 Beniamino Galvani
2014-04-27  9:30 ` [PATCH 01/11] net: add ARC EMAC driver Beniamino Galvani
2014-04-27  9:30 ` [PATCH 02/11] mfd: add act8846 driver Beniamino Galvani
2014-04-27  9:30 ` [PATCH 03/11] ARM: add basic support for Rockchip SoCs Beniamino Galvani
2014-04-27  9:30 ` [PATCH 04/11] ARM: rockchip: add PLL initialization function Beniamino Galvani
2014-04-27  9:30 ` [PATCH 05/11] clk: gate: add flags argument to clock gate constructor Beniamino Galvani
2014-04-27  9:30 ` [PATCH 06/11] clk: gate: unify enable and disable functions handling Beniamino Galvani
2014-04-27  9:30 ` [PATCH 07/11] clk: gate: add CLK_GATE_HIWORD_MASK flag Beniamino Galvani
2014-04-27  9:30 ` [PATCH 08/11] clk: add rockchip clock gate driver Beniamino Galvani
2014-04-27  9:30 ` [PATCH 09/11] pinctrl: add rockchip pinctrl and gpio drivers Beniamino Galvani
2014-04-27  9:30 ` [PATCH 10/11] ARM: dts: add Rockchip devicetree files Beniamino Galvani
2014-04-27  9:30 ` [PATCH 11/11] ARM: rockchip: add radxa-rock board Beniamino Galvani
2014-04-28  7:26 ` Sascha Hauer [this message]
2014-04-28 20:54   ` [PATCH 00/11] ARM: add initial support for Rockchip boards Beniamino Galvani
2014-04-29  7:05     ` Sascha Hauer
2014-04-29 21:13       ` Beniamino Galvani
2014-04-29 21:59         ` Heiko Stübner
2014-05-01  7:48           ` Beniamino Galvani

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=20140428072627.GN5858@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=b.galvani@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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