From: maitysanchayan at gmail.com <maitysanchayan@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Query on weak function for board specific initialisation
Date: Sun, 31 May 2015 13:04:07 +0530 [thread overview]
Message-ID: <20150531073407.GA1555@Sanchayan-Arch> (raw)
In-Reply-To: <5569CCD0.7000202@myspectrum.nl>
Hello Jeroen,
On 15-05-30 16:44:32, Jeroen Hofstee wrote:
> Hello Maity,
>
> On 30-04-15 14:57, maitysanchayan at gmail.com wrote:
> >Hello,
> >
> >I am trying to use a weak function in able to provide a board specific
> >initialisation. To be more specific, I am trying to use the __weak
> >board_ehci_hcd_init function in the usb driver code which is called in
> >ehci_hcd_init, the strong function being defined in the board file.
> >This is on lines similar to what I see in the ehci-mx6 driver and some
> >mx6 board files like nitrogen's.
> >
> >Getting a linker error on compiling which is perplexing me at the
> >moment.
> >
> >[snip]
> >drivers/usb/host/built-in.o: In function `ehci_hcd_init':
> >/home/sanchayan/uboot/u-boot/drivers/usb/host/ehci-vf.c:185:
> >undefined reference to `board_echi_hcd_init'
> >/home/sanchayan/gcc-linaro/bin/arm-linux-gnueabihf-ld.bfd: BFD
> >(crosstool-NG linaro-1.13.1-2012.09-20120921 - Linaro GCC 2012.09) 2.22
> >assertion fail
> >/cbuild/slaves/oort14/crosstool-ng/builds/arm-linux-gnueabihf-linux/.build/src/binutils-2.22/bfd/elf32-arm.c:7498
> >/home/sanchayan/gcc-linaro/bin/arm-linux-gnueabihf-ld.bfd: BFD
> >(crosstool-NG linaro-1.13.1-2012.09-20120921 - Linaro GCC 2012.09) 2.22
> >assertion fail
> >/cbuild/slaves/oort14/crosstool-ng/builds/arm-linux-gnueabihf-linux/.build/src/binutils-2.22/bfd/elf32-arm.c:13830
> >/bin/sh: line 1: 1110 Segmentation fault (core dumped)
> >
> >Perhaps I am overlooking something trivial?
>
>
> I suppose you found this already, but for completeness, you made a typo:
>
> board_ehci_hcd_init
> board_echi_hcd_init
>
> To prevent trouble like this, the compiler should actually be set to warn
> if there is no prototype...
Yes, I found the error and also posted the patch. Thanks for the tip, I do
not have that switch turned on, will do so. Lack of sleep and resulting
lack of attention to detail resulted in the trivial noise post :).
prev parent reply other threads:[~2015-05-31 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 12:57 [U-Boot] Query on weak function for board specific initialisation maitysanchayan at gmail.com
2015-05-30 14:44 ` Jeroen Hofstee
2015-05-31 7:34 ` maitysanchayan at gmail.com [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=20150531073407.GA1555@Sanchayan-Arch \
--to=maitysanchayan@gmail.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