[OpenBIOS] Sparc64 OpenBIOS

[Nick Couchman]

> 
> Yes it does, but with my patch from yesterday also applied, now it looks 
> as if something else is broken:
> 
> 
> OpenBIOS for Sparc64
> Configuration device id QEMU version 1 machine id 0
> CPUs: 1 x SUNW,UltraSPARC-II
> UUID: 00000000-0000-0000-0000-000000000000
> Welcome to OpenBIOS v1.0 built on Nov 20 2009 15:53
>    Type 'help' for detailed information
> 
> [sparc64] Booting file 'cdrom' with parameters ''
> Not a bootable ELF image
> Not a Linux kernel image
> Not a bootable a.out image
> Loading FCode image...
> Loaded 7084 bytes
> entry point is 0x4000
> Evaluating FCode...
> Unhandled Exception 0x00000004ff702000
> PC = 0x00000000ffd102b8 NPC = 0x00000000ffd102bc
> Stopping execution
> 

After updating to r624, I get the following:

0 > boot cdrom 
[sparc64] Booting file 'cdrom' with parameters ''
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Loading FCode image...
Loaded 7120 bytes
entry point is 0x4000
Evaluating FCode...
Unhandled Exception 0x9000280200000000
PC = 0x00000000ffd0f05c NPC = 0x00000000ffd0f060
Stopping execution

When I use gdb to trace down the source of the exception, it looks like this:

(gdb) l *0x00000000ffd0f05c
0xffd0f05c is in enterforth (../kernel/internal.c:71).
66	#define dbg_internal_printk( a... )	printk( a )
67	#endif
68	
69	
70	static inline void processxt(ucell xt)
71	{
72		void (*tokenp) (void);
73	
74		dbg_interp_printk("processxt: pc=%x, xt=%x\n", PC, xt);
75		tokenp = words[xt];


-Nick




--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.