From: Angelo Dureghello <angelo@sysam.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] m68k: 3 boards are broken
Date: Sat, 28 Mar 2015 09:38:04 +0100 [thread overview]
Message-ID: <5516686C.1010209@sysam.it> (raw)
In-Reply-To: <CAK7LNAQNTy4fkzKgsNoG9O=-fuWBHQgda8ak0TBibwgqFcbbTw@mail.gmail.com>
Dear Masahiro,
On 27/03/2015 08:05, Masahiro Yamada wrote:
> Hi Alison, Angelo
>
>
> I found 3 m68k boards are broken:
> eb_cpu5282_defconfig
> eb_cpu5282_internal_defconfig
> M53017EVB_defconfig
>
>
> LD u-boot
> common/built-in.o: In function `reserve_video':
> /home/yamada/workspace/u-boot/common/board_f.c:501: undefined
> reference to `video_setmem'
> make: *** [u-boot] Error 1
>
>
>
> Can you figure it out, please?
>
Fixed the first 2 boards, there is no reserve_video needed
for m68k.
The third (M53017EVB) is a relocation issue.
arch/m68k/cpu/mcf532x/start.o: In function `_start':
/home/angelo/sysam/u-boot/arch/m68k/cpu/mcf532x/start.S:159:(.text+0x462):
relocation truncated to fit: R_68K_PC16 against symbol `board_init_f'
defined in .text.board_init_f section in common/built-in.o
Makefile:1094: set di istruzioni per l'obiettivo "u-boot" non riuscito
make: *** [u-boot] Errore 1
For some reason this board have a different text section
in the linker script, and this cause the error. Also
board.c in m68k/lib is no more built-in.
SECTIONS
{
/* Read-only sections, merged into text segment: */
.text :
{
arch/m68k/cpu/mcf532x/start.o (.text*)
arch/m68k/cpu/mcf532x/built-in.o (.text*)
arch/m68k/lib/built-in.o (.text*)
. = DEFINED(env_offset) ? env_offset : .;
common/env_embedded.o (.text*)
*(.text*)
}
_etext = .;
Studying on this last issue.
Hope to post the full patch later.
Regards
Angelo
next prev parent reply other threads:[~2015-03-28 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 7:05 [U-Boot] m68k: 3 boards are broken Masahiro Yamada
2015-03-28 8:38 ` Angelo Dureghello [this message]
2015-03-28 10:16 ` Angelo Dureghello
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=5516686C.1010209@sysam.it \
--to=angelo@sysam.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.