All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Cannot boot reliably vxWorks on PPC44x
Date: Wed, 4 Apr 2007 15:19:53 +0200	[thread overview]
Message-ID: <200704041519.54007.sr@denx.de> (raw)
In-Reply-To: <es9fmb$sek$1@sea.gmane.org>

Hi Niklaus,

On Friday 02 March 2007 16:26, Niklaus Giger wrote:
> BTW, the boot cmd of vxWorks expects a parameter, therefore I think
> it would make sense to apply a patch like
> diff --git a/common/cmd_elf.c b/common/cmd_elf.c
> old mode 100644
> new mode 100755
> index 0e3d56f..dc4eb27
> --- a/common/cmd_elf.c
> +++ b/common/cmd_elf.c
> @@ -213,7 +213,7 @@ int do_bootvx (cmd_tbl_t *cmdtp, int flag, int argc,
> char *argv[])
>                         (char *) bootaddr);
>         printf ("## Starting vxWorks at 0x%08lx ...\n", addr);
>
> -       ((void (*)(void)) addr) ();
> +       ((void (*)(int)) addr) (2); /* 0 => BOOT_NORMAL 2=> BOOT_CLEAR */
>
>         puts ("## vxWorks terminated\n");
>         return 1;

Are you sure that this parameter is supported. A quick "googling" only showed 
this parameter in the VxWorks function reboot(), and I don't think this is 
the entry point of the VxWorks image.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
=====================================================================

  reply	other threads:[~2007-04-04 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 15:26 [U-Boot-Users] Cannot boot reliably vxWorks on PPC44x Niklaus Giger
2007-04-04 13:19 ` Stefan Roese [this message]
2007-04-04 13:30   ` [U-Boot-Users] Antw: " Niklaus Giger
2007-04-04 15:34     ` Stefan Roese

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=200704041519.54007.sr@denx.de \
    --to=sr@denx.de \
    --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.