85xx sync to msync necessary?
Hi,
I found that there was an unclear assembly usage on 'sync' for 85xx in current tree. On P202 of E500CORERM.pdf, it says that 'sync' has replaced by 'msync' in BOOK-E and E500. But there are still some 'sync' for 85xx at cpu/mpc85xx folder and other files like drivers/ tsec.c.
I changed all 'sync' as 'msync' on my customized 8548 boards. Seems no obvious difference. Both OK.
So I wonder whether we should fix it. Thoughts?
Thanks,
Sam
___________________________________________________________
????????-3.5G???20M???
http://cn.mail.yahoo.com
Sam,
sync and msync end up being the exact same thing on e500. Its better to leave the code in drivers and such to use sync since then it will build on non-e500 cores. But all binutils should assemble sync and msync as the same instruction for e500.
- k
Quoted 37 lines · Sam Song
Hi,
I found that there was an unclear assembly usage on 'sync' for 85xx in current tree. On P202 of E500CORERM.pdf, it says that 'sync' has replaced by 'msync' in BOOK-E and E500. But there are still some 'sync' for 85xx at cpu/mpc85xx folder and other files like
drivers/tsec.c.I changed all 'sync' as 'msync' on my customized 8548 boards. Seems no obvious difference. Both OK.
So I wonder whether we should fix it. Thoughts?
Thanks,
Sam
___________________________________________________________
????????-3.5G???20M???
http://cn.mail.yahoo.com----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV________________________________
_______________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
Quoted 5 lines · In message <[email protected]> you wrote:
sync and msync end up being the exact same thing on e500. Its better to leave the code in drivers and such to use sync since then it will build on non-e500 cores. But all binutils should assemble sync and msync as the same instruction for e500.
Verified on ELDK 4.x:
-> cat foo.c
void do_sync() { asm ("sync"); }
void do_msync() { asm ("msync"); }
-> ppc_85xx-gcc -O -c foo.c
-> ppc_85xx-objdump -D -S foo.o
foo.o: file format elf32-powerpc
Disassembly of section .text:
00000000 <do_sync>:
0: 7c 00 04 ac sync 4: 4e 80 00 20 blr
00000008 <do_msync>:
8: 7c 00 04 ac sync c: 4e 80 00 20 blr
...
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de What the gods would destroy they first submit to an IEEE standards committee.
Quoted 7 lines · Wolfgang Denk
Quoted 6 lines · Kumar Gala
sync and msync end up being the exact same thing on e500. Its better to leave the code in drivers and such to use sync since then it will build on non-e500 cores. But all binutils should assemble sync and msync as the same instruction
for > > e500.
Quoted 13 lines
Verified on ELDK 4.x:
-> cat
foo.c
voiddo_sync(){ asm ("sync"); }
voiddo_msync(){ asm ("msync"); }
-> ppc_85xx-gcc -O -cfoo.c
-> ppc_85xx-objdump -D -S foo.ofoo.o: file format elf32-powerpc
Disassembly of section .text:
Quoted 8 lines
00000000 <
do_sync>:0: 7c 00 04 ac sync 4: 4e 80 00 20 blr00000008 <
do_msync>:8: 7c 00 04 ac sync c: 4e 80 00 20 blr...
Uh, clear enough:-)
Thanks a lot,
Sam
___________________________________________________________
Mp3???-???????
http://music.yahoo.com.cn/?source=mail_mailbox_footer