linux-mips
[Top] [All Lists]

Re: RBTX4927 with VxWorks boot loader crashes in prom_getenv()

To: Geert.Uytterhoeven@sonycom.com
Subject: Re: RBTX4927 with VxWorks boot loader crashes in prom_getenv()
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Fri, 24 Oct 2008 23:02:50 +0900 (JST)
Cc: linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.64.0810241118120.27263@vixen.sonytel.be>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.LNX.4.64.0810241118120.27263@vixen.sonytel.be>
Sender: linux-mips-bounce@linux-mips.org
On Fri, 24 Oct 2008 11:39:07 +0200 (CEST), Geert Uytterhoeven 
<Geert.Uytterhoeven@sonycom.com> wrote:
> My RBTX4927 with VxWorks boot loader crashes in prom_getenv() since commit
> 860e546c19d88c21819c7f0861c505debd2d6eed ("MIPS: TXx9: Early command-line
> preprocessing"):
...
> | fw_arg0 = 0x80002000
> | fw_arg1 = 0x80001fe0
> | fw_arg2 = 0x2000
> | fw_arg3 = 0x20
> 
> So your assumption that bootloaders other than YAMON pass NULL for fw_arg2 is
> apparently wrong.

Indeed.  We should know what sort of value was passed by fw_arg2, and
I hope auto-detection.

Do you know what value the boot loader passes via fw_arg2?  If fw_arg2
is always small integer (i.e. a not KSEG0/KSEG1 address), we can
autodetect fw_arg2 was a pointer or not.

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>