Date: Wed, 10 Aug 2016 14:19:20 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: mattia.rossi.mailinglists@gmail.com Cc: freebsd-arm@freebsd.org Subject: Re: Allwinner H3 - OrangePi Plus Status Message-ID: <20160810141920.d2994dee3c277f7b89451360@bidouilliste.com> In-Reply-To: <c4303640-eb52-40fe-e45c-775b6ebf2dd3@gmail.com> References: <64ad8272-a97f-e51f-19f1-d37e12c4e4bf@gmail.com> <E9103052-2177-42C0-BFFD-C48BDC7ACDFE@cs.huji.ac.il> <868ae805-bf93-50f9-e22c-1d2ea13f8555@gmail.com> <8FDE95E3-C66E-40D5-8133-67FD987BE729@cs.huji.ac.il> <3454388a-02bc-8dbe-4f8f-c33a726e406c@gmail.com> <20160810103501.0aef31d4c27cf08b6e54d20f@bidouilliste.com> <141a4b87-1914-a9f5-c15a-3173f6d4659a@gmail.com> <20160810115617.aa7ad5c9ae538660dc5cc0d8@bidouilliste.com> <c4303640-eb52-40fe-e45c-775b6ebf2dd3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Aug 2016 13:06:48 +0200 Mattia Rossi <mattia.rossi.mailinglists@gmail.com> wrote: > > > Am 10.08.2016 um 11:56 schrieb Emmanuel Vadot: > > On Wed, 10 Aug 2016 11:07:04 +0200 > > Mattia Rossi <mattia.rossi.mailinglists@gmail.com> wrote: > > > >>> ubldr will load the file described by the "fdtfile" u-boot variable (ubldr import the needed uboot variables). > >>> The uboot variable is hardcoded in the uboot port patch (https://svnweb.freebsd.org/ports/head/sysutils/u-boot-olimex-a20-som-evb/files/patch-include_configs_sunxi-common.h?revision=418446&view=markup#l44). > >>> Alternativelly you can do from ubldr prompt : > >>> load -t dtb filename > >>> It will search for the file in /boot/dtb (or you can use the fullpath if it's elsewhere) > >>> > >> It's weird that such a thing is hardcoded.. Although it seems that it's > >> set through CONFIG_DEFAULT_DEVICE_TREE, so I guess it can be controlled > >> through a config file (Makefile?) > > Not weird at all since uboot is always compiled for one particular board. > > The CONFIG_DEFAULT_DEVICE_TREE is set in the uboot config file (configs/boardname) but it is currently not used as we override the environ in the board include file. > > > Okay, so just to get the whole picture: > If I want everything set up for an OrangePi Plus 2 I need the following > puzzle pieces > > A u-boot port which points to an orangepi plus 2 dtb Yes, just copying the orangepi-one port and modify it should be ok (if u-boot 2016.07 have a a config for this board) > An orangepi plus 2 dts/dtb (which might differ from the plus dtb, I > don't know yet, there are no real specs available) Yes, as said earlier in this thread you will need to wait for the linux 4.7 dts import for this. > An orangepi plus 2 kernel config (which like the .dts might differ from > the standard allwinner config) No, the ALLWINNER kernel config is what you should use. > And of course kernel support for all the (as of yet unknown) devices of > the board. Yes :) > I'm going to work towards that, depending on how much information I can > gather about the board and depending on how much it differs from the > plus version. > > For now I'll see if the plus version of everything works :-) - wish me > luck ;-) > > Cheers, > > Mat -- Emmanuel Vadot <manu@bidouilliste.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160810141920.d2994dee3c277f7b89451360>