From mboxrd@z Thu Jan  1 00:00:00 1970
From: Liu, Changcheng <changcheng.liu@intel.com>
Date: Thu, 16 Jun 2016 11:56:17 +0000
Subject: [U-Boot] u-boot for Galileo board
Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D10287561@SHSMSX103.ccr.corp.intel.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi all,

    I have some questions about the u-boot for Galileo2 board.



    1. Code: https://github.com/LeMaker/u-boot (it's for Galileo board which could be ported for Galileo2 board)



    2. Confusing at the building process.

           a. objcopy  --gap-fill=0xff -O binary -R .start16 -R .resetvec u-boot u-boot.bin

               Question: Why the ".resetvec" section should be removed since it's placed at "0xffffffff0" section according to arch/x86/cpu/u-boot.lds?



           b. cat u-boot.bin dts/dt.dtb > u-boot-dtb.bin

               Question:

               I think ROM is layout at the top of the physical address and quark x1000 SoC will fetch instruction from  FFFF_FFF0H after being power on. If dts/dt.dtb is appended after u-boot.bin, how could the content is effective at FFFF_FFF0H?


B.R.
Changcheng