public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Zynq build failure
Date: Tue, 8 Sep 2015 16:36:21 +0200	[thread overview]
Message-ID: <55EEF265.9090207@xilinx.com> (raw)
In-Reply-To: <CAD6G_RQq6mJiYyFRmiZc4Bxe+=Ws0nuSysaZE-=f6F-kzezboQ@mail.gmail.com>

On 09/08/2015 11:48 AM, Jagan Teki wrote:
> On 4 September 2015 at 14:22, Jagan Teki <jteki@openedev.com> wrote:
>> Hi Michal/Siva,
>>
>> Any fix for this failure?
>>
>>   CC      spl/drivers/mtd/spi/spi_spl_load.o
>> drivers/mtd/spi/spi_spl_load.c: In function 'spi_load_image_os':
>> drivers/mtd/spi/spi_spl_load.c:26:24: error:
>> 'CONFIG_SYS_SPI_KERNEL_OFFS' undeclared (first use in this function)
>> drivers/mtd/spi/spi_spl_load.c:26:24: note: each undeclared identifier
>> is reported only once for each function it appears in
>> drivers/mtd/spi/spi_spl_load.c:38:24: error:
>> 'CONFIG_SYS_SPI_ARGS_OFFS' undeclared (first use in this function)
>> drivers/mtd/spi/spi_spl_load.c:39:10: error:
>> 'CONFIG_SYS_SPI_ARGS_SIZE' undeclared (first use in this function)
>> make[3]: *** [spl/drivers/mtd/spi/spi_spl_load.o] Error 1
> 
> Any help?
> 

It is just MTD map. It means it can be whatever. :-)

Let's say - bitstream first - max 0x1100000 for 7z100
Then DTB - 0.5MB max
and the rest kernel

#define CONFIG_SYS_SPI_ARGS_OFFS 0x1100000
#define CONFIG_SYS_SPI_ARGS_SIZE 0x80000
#define CONFIG_SYS_SPI_KERNEL_OFFS (CONFIG_SYS_SPI_ARGS_OFFS +
CONFIG_SYS_SPI_ARGS_SIZE)

Adding this to zynq-common and we are done.
Do you want me to send the patch for it?

Thanks,
Michal

  reply	other threads:[~2015-09-08 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  8:52 [U-Boot] Zynq build failure Jagan Teki
2015-09-08  9:48 ` Jagan Teki
2015-09-08 14:36   ` Michal Simek [this message]
2015-09-08 17:51     ` Jagan Teki
2015-09-09  5:32       ` Siva Durga Prasad Paladugu
2015-09-09  7:27         ` Jagan Teki
2015-09-09  8:55           ` Siva Durga Prasad Paladugu
2015-09-09  9:51             ` Jagan Teki

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=55EEF265.9090207@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=u-boot@lists.denx.de \
    /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