From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC: problem with syscalls
Date: Thu, 28 Nov 2002 13:39:53 +0100 [thread overview]
Message-ID: <3DE60E99.1DB09169@staubli.com> (raw)
Hello everybody,
I've a problem with examples/timer.c. I've tried to launch it on my
mpc860t board, if I start the timer and if I
press a key after one or more interrupts occured, the u-boot crashes.
The problem is that an interrupt handler
uses a system call (mon_printf) while the main loop is inside a system
call (mon_getc). During a system call,
the LR and SRRx are saved at a fixed location (0xcf4, 0xcf8 and 0xcfc)
then the return address of the mon_printf
in the main loop is overridden by the return address of the mon_getc in
the interrupt handler. To avoid this problem,
I think that we need to use a stack to store the return addresses (and
the SRRx) of the system calls.
What's your opinion ?
Best regards
next reply other threads:[~2002-11-28 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 12:39 Pierre AUBERT [this message]
2002-11-29 12:04 ` [U-Boot-Users] PPC: problem with syscalls Pierre AUBERT
2002-12-06 22:06 ` Wolfgang Denk
2002-12-06 21:59 ` Wolfgang Denk
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=3DE60E99.1DB09169@staubli.com \
--to=p.aubert@staubli.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