Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Questions about the building process (Olimex lime2)


I'm testing a Olimex a20-olinuxino-lime2 board.

The support is included in u-boot and there is the corresponding dts
file in ./external/gpl2/dts/dist/arch/arm64/boot/dts/allwinner/.

The support is not directly included (at least for the dts) in the
SUNXI config file.

There is a dedicated kernel config file, added by Manuel Bouyer,

This last kernel is not compiled and not present in the releasedir.

I was at the moment of interpolating in the SUNXI config file what is
needed for the board (at the minimum the DTS) but I was wondering if
this is the right place and I was trying to find how only the DTS
specified by the option in the SUNXI config "makeoptions DTS=" ended
in the armv7.img and why the OLIMEXLIME2 kernel was not built while
almost all the others in the directory were.

So the questions relate to the building with:

./build.sh -O $OBJDIR -V RELEASEDIR=$RELEASEDIR -m evbarm -a earmv7hf\
	-U -u -x release

How does the build process determine the kernels to build (obviously not
simply by listing the configs in the dir since the OLIMEXLIME2 is in
the dir and is not included)?

How does the build process determine what has to go in the image,
specifically the compiled dtb files?---since I found only one mention of
the DTS and it was in the SUNXI kernel config.

Where do the files piloting u-boot and present in the image are
generated? And what is the sequence of u-boot script files actually
used?---because there seems to be conditionals about some dtb files and
it seems to me that the first found will be used and it may not
correspond to the device tree of the board (but it's a problem if and
only if this script file is actually used).

        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

Home | Main Index | Thread Index | Old Index