All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC: problem with syscalls
Date: Fri, 29 Nov 2002 13:04:03 +0100	[thread overview]
Message-ID: <3DE757B3.F88ACDBA@staubli.com> (raw)
In-Reply-To: 3DE60E99.1DB09169@staubli.com

Pierre AUBERT wrote:

> 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.
>

Dear Wolfgang,

Please find attached a patch fixing the problem described above. A little
stack (located between the end of the syscall exception handler and the
beginning of the following exception) is used to save the LR and SRRx.
With this patch, examples/timer is running fine.

Best regards.


CHANGELOG:
* Patch by Pierre Aubert , 28 Nov 2002
  Fix nested syscalls bug in standalone applications.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: syscalls.patch
Type: application/octet-stream
Size: 7657 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20021129/736d50b2/attachment.obj 

  reply	other threads:[~2002-11-29 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 12:39 [U-Boot-Users] PPC: problem with syscalls Pierre AUBERT
2002-11-29 12:04 ` Pierre AUBERT [this message]
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=3DE757B3.F88ACDBA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.