From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: U-Boot API - clang support broke ABI
Date: Tue, 19 Nov 2013 10:09:44 +0100 [thread overview]
Message-ID: <528B2AD8.3080906@monstr.eu> (raw)
In-Reply-To: <20131118112659.GB1567@rocoto.smurfnet.nu>
Hi Albert,
I have just bisect why on the latest kernel hello world example doesn't work
and I have end up in this patch too. After reverting hello world example
is working.
Also I would like to know if we have still bootm support for standlone
http://www.denx.de/wiki/view/DULG/UBootStandalone#Section_5.12.3.
Because it is not working for me with error
"ERROR: booting os 'U-Boot' (17) is not supported"
and I can't see IH_OS_U_BOOT in boot_os table in cmd_bootm.c
I have created image like this.
./tools/mkimage -n "hello" -A arm -O u-boot -T standalone -C none -a c100000 -d examples/standalone/hello_world.bin -v /tftpboot/hello.ub
Thanks,
Michal
On 11/18/2013 12:26 PM, Leif Lindholm wrote:
> Hi,
>
> Commit fe1378a - "ARM: use r9 for gd" - broke the ABI for users of the
> U-Boot API on ARM. Users I am aware of are GRUB and the FreeBSD loader.
> Since I only spotted this on Saturday, this code is well and truly in
> the wild, so any users of the API will need to preserve both r8 and r9
> on syscalls for the foreseeable future (which is not the end of the
> world).
>
> Sometime last year I proposed a change to make the API syscall entry
> and exit points responsible for maintaining full procedure-call standard
> compliance, although the patch I provided was on the hackier side of
> good (and probably wrong).
>
> I would now like to ask in a more open-ended way - is there any chance
> that we could solve this in a generic way, such that consumers of the
> API need not be aware of U-Boot internal ABI changes?
>
> If the assumtions that the global data pointer is:
> a) a pointer
> b) writable
> are not both safe, then this could be achieved by arch-specific asm
> entry/exit points.
>
> /
> Leif
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131119/7922c078/attachment.pgp>
next prev parent reply other threads:[~2013-11-19 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 11:26 [U-Boot] arm: U-Boot API - clang support broke ABI Leif Lindholm
2013-11-19 9:09 ` Michal Simek [this message]
2013-11-19 20:07 ` Tom Rini
2013-11-20 7:59 ` [U-Boot] standalone u-boot app - bootm issue was the part of: (Re: arm: U-Boot API - clang support broke ABI) Michal Simek
2013-11-20 13:49 ` Tom Rini
2013-11-20 13:53 ` Michal Simek
2013-11-20 14:01 ` Tom Rini
2013-11-21 15:54 ` Michal Simek
2013-11-19 22:42 ` [U-Boot] arm: U-Boot API - clang support broke ABI Jeroen Hofstee
2013-11-23 11:20 ` Jeroen Hofstee
2013-11-25 10:43 ` Leif Lindholm
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=528B2AD8.3080906@monstr.eu \
--to=monstr@monstr.eu \
--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