Hi Beniamino, very cool that you're working on getting a better boot loader for us :-) Am Dienstag, 29. April 2014, 23:13:14 schrieb Beniamino Galvani: > On Tue, Apr 29, 2014 at 09:05:58AM +0200, Sascha Hauer wrote: > > On Mon, Apr 28, 2014 at 10:54:53PM +0200, Beniamino Galvani wrote: > > > On Mon, Apr 28, 2014 at 09:26:27AM +0200, Sascha Hauer wrote: > > > > 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. hehe, that goes for me too :-) > > BTW I noticed the upstream radxa rock dts file does not have a board > > specific compatible. I added this in my patch, but this should be done > > upstream. > > CC'ing Heiko, who is the Linux Rockchip maintainer. Until now I didn't give it much thought, but according to usage-model.txt the board-specific compatible is a required property. So we'll need to add it to the board dts in the kernel too. So you could send a patch, or I'll prepare one in the next days. Heiko _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
