From: "Grégory Hermant" <gregory.hermant@calao-systems.com>
To: buildroot@busybox.net
Subject: [Buildroot] gcc-4.7.3 potential issue with barebox
Date: Mon, 17 Jun 2013 14:57:21 +0200 [thread overview]
Message-ID: <51BF07B1.6060900@calao-systems.com> (raw)
Hi all,
I noticed an issue with barebox binary about the nandflash detection.
Indeed barebox is unable to detect the nandflash when i build barebox from gcc-4.7.3 (buildroot-2013.05)
By digging a little bit i noticed that the size of atmel_nand.o was different according to the toolchain release (atmel_nand.o 4732bytes vs 5096 bytes for gcc-4.6.3 )
If i disassemble atmel_nand.o i notice that atmel_nand_enable & atmel_nand_disable are missing.
Is it an known issue ?
Gr?gory
next reply other threads:[~2013-06-17 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 12:57 Grégory Hermant [this message]
2013-06-17 14:25 ` [Buildroot] gcc-4.7.3 potential issue with barebox Thomas Petazzoni
2013-06-18 15:02 ` Grégory Hermant
2013-06-18 17:05 ` Thomas Petazzoni
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=51BF07B1.6060900@calao-systems.com \
--to=gregory.hermant@calao-systems.com \
--cc=buildroot@busybox.net \
/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