From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 00/87] mtd: Add SPI-NOR core support
Date: Mon, 28 Mar 2016 09:31:45 -0400 [thread overview]
Message-ID: <20160328133145.GD23166@bill-the-cat> (raw)
In-Reply-To: <CAD6G_RTGMqh9J2FOT=ttuLXAe3GscMf1gURaBGjXNbgEa=ocig@mail.gmail.com>
On Mon, Mar 28, 2016 at 05:02:45PM +0530, Jagan Teki wrote:
> On 22 March 2016 at 20:25, Tom Rini <trini@konsulko.com> wrote:
> > On Tue, Mar 22, 2016 at 01:19:25PM +0530, Jagan Teki wrote:
> > [snip]
> >> Issues:
> >> -------
> >> 1) undefined reference to `__aeabi_ldivmod'
> >>
> >> 59: config: Enable SPI-NOR framework
> >> arm: + nyan-big
> >> +drivers/mtd/spi-nor/built-in.o: In function `spi_nor_write':
> >> +build/../drivers/mtd/spi-nor/spi-nor.c:585: undefined reference to
> >> `__aeabi_ldivmod'
> >> +arm-unknown-linux-gnueabi-ld.bfd: BFD (GNU Binutils) 2.24 assertion
> >> fail /home/tony/buildall/src/binutils/bfd/elf32-arm.c:7696
> >> +arm-unknown-linux-gnueabi-ld.bfd: error: required section
> >> '.rel.plt' not found in the linker script
> >> +arm-unknown-linux-gnueabi-ld.bfd: final link failed: Invalid operation
> >> +make[1]: *** [u-boot] Error 1
> >> +make: *** [sub-make] Error 2
> >
> > So this is a 64bit division problem somewhere along the lines that needs
> > to be using one of the normal helper functions.
> >
> >> 2) Build issues on dra72_evm, dra74_evm
> >
> > What are they?
>
> Build issue with spl, I guess this is because dm used for normal
> u-boot and not used for spl.
Yes, this is still true. It sounds like you need to make sure that the
code continues to build for both cases?
>
> Mugunthan, can you look in to this?
>
> >
> >> 3) SPL image too big
> >>
> >> 59: config: Enable SPI-NOR framework
> >> arm: + axm
> >> +arm-unknown-linux-gnueabi-ld.bfd: SPL image too big
> >> +arm-unknown-linux-gnueabi-ld.bfd: SPL image BSS too big
> >> +make[2]: *** [spl/u-boot-spl] Error 1
> >> +make[1]: *** [spl/u-boot-spl] Error 2
> >> +make: *** [sub-make] Error 2
> >
> > Sounds like you need to go back and take some care about how we do this
> > in SPL. Given the current gcc issue wrt merging strings together, we
> > may need to be more careful about what files we compile and link for SPL
> > in this case and perhaps need to split a file or two up.
>
> With proper commenting code for SPL build on mtdcore and changes on
> SPL size macros, build look fine.
>
> +++ b/include/configs/taurus.h
> -#define CONFIG_SPL_MAX_SIZE (31 * SZ_512)
> +#define CONFIG_SPL_MAX_SIZE (36 * SZ_512)
> -#define CONFIG_SPL_BSS_MAX_SIZE (3 * SZ_512)
> +#define CONFIG_SPL_BSS_MAX_SIZE (4 * SZ_512)
OK, but we can't just increase the sizes here, these platforms have a
small footprint we need to stick to. We need to see what can be trimmed
out to make them continue to fit.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160328/ea69ef0f/attachment.sig>
prev parent reply other threads:[~2016-03-28 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:37 [U-Boot] [PATCH v7 00/87] mtd: Add SPI-NOR core support Jagan Teki
2016-03-22 7:47 ` Jagan Teki
2016-03-22 7:49 ` Jagan Teki
2016-03-22 10:14 ` Jagan Teki
2016-03-22 14:55 ` Tom Rini
2016-03-28 11:32 ` Jagan Teki
2016-03-28 13:31 ` Tom Rini [this message]
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=20160328133145.GD23166@bill-the-cat \
--to=trini@konsulko.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