OpenBIOS September 2010

openbios@openbios.org

22 participants
46 discussions

Re: [OpenBIOS] Help with some code
by Programmingkid 25 Sep '10

25 Sep '10

On Sep 25, 2010, at 6:00 AM, openbios-request(a)openbios.org wrote: > Message: 2 > Date: Fri, 24 Sep 2010 09:25:28 -0400 > From: Tarl Neustaedter <tarl-b2(a)tarl.net> > To: The OpenBIOS Mailinglist <openbios(a)openbios.org> > Subject: Re: [OpenBIOS] Help with some code > Message-ID: <4C9CA6C8.2050009(a)tarl.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > You should get in the habit of putting stack diagram comments on every line > of code - it will help you keep track of what you are playing with. By > convention, a stack diagram starting with $ indicates a addr,len string > pointer, which you should use in this code for clarity. > > As best I can tell without stack diagrams, you are generating strings of the > form "foo: set-foo foo ! ; foo", and it's probably barfing on "foo:" . I'm not > sure what this is supposed to accomplish. What I'm trying to do is create a new word. The new word's name will be set-_variable_name_. What would be another way to create a new word inside another word? > > Replace the "eval" with a "type" and you should be able to see what it's > generating. I tried your suggestion, but everything looked just fine. The problem shows up at compile-time. Using this code: variable dog : myword 4 -> dog ; What the code should create at compile-time is this: : myword 4 set-dog ; but creates this instead : myword 4 : set-dog ; The problem is with the extra colon between the 4 and the set-dog word. I need a way to eliminate it from the myword word. Other times the compiler will say the word set-dog is undefined. Any clue how to fix this problem?

1 0

[PATCH] fcode-utils: Add type support for Haiku
by Andreas Färber 25 Sep '10

25 Sep '10

Haiku does not have asm/types.h. It does have [u]int*_t but not in sys/types.h. Use stdint.h instead, that works for both Haiku and OpenSolaris and avoids more code duplication in shared/types.h. Signed-off-by: Andreas Färber <andreas.faerber(a)web.de> Cc: Stefan Reinauer <stepan(a)openbios.org> --- shared/types.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/shared/types.h b/shared/types.h index ff24355..9d67c85 100644 --- a/shared/types.h +++ b/shared/types.h @@ -52,9 +52,9 @@ typedef u_int16_t u16; typedef int32_t s32; typedef u_int32_t u32; -#elif defined(__sun__) +#elif defined(__sun__) || defined(__HAIKU__) -#include <sys/types.h> +#include <stdint.h> typedef int8_t s8; typedef uint8_t u8; -- 1.7.1.rc2.7.g3e7f1

3 7

[commit] r863 - trunk/fcode-utils-devel/shared
by repository service 25 Sep '10

25 Sep '10

Author: stepan Date: Sat Sep 25 19:07:10 2010 New Revision: 863 URL: http://tracker.coreboot.org/trac/openbios/changeset/863 Log: Haiku does not have asm/types.h. It does have [u]int*_t but not in sys/types.h. Use C99/POSIX stdint.h types for all platforms. v1 -> v2: * Don't just use stdint.h in place of sys/types.h in the Sun/Haiku code path. Suggested by Stefan. Signed-off-by: Andreas Färber <andreas.faerber(a)web.de> Cc: Stefan Reinauer <stepan(a)openbios.org> Modified: trunk/fcode-utils-devel/shared/types.h Modified: trunk/fcode-utils-devel/shared/types.h ============================================================================== --- trunk/fcode-utils-devel/shared/types.h Sat Sep 11 18:39:32 2010 (r862) +++ trunk/fcode-utils-devel/shared/types.h Sat Sep 25 19:07:10 2010 (r863) @@ -39,22 +39,8 @@ * **************************************************************************** */ -#if defined(__APPLE__) +#include <stdint.h> -#include <sys/types.h> - -typedef int8_t s8; -typedef u_int8_t u8; - -typedef int16_t s16; -typedef u_int16_t u16; - -typedef int32_t s32; -typedef u_int32_t u32; - -#elif defined(__sun__) - -#include <sys/types.h> typedef int8_t s8; typedef uint8_t u8; @@ -68,20 +54,6 @@ typedef int64_t s64; typedef uint64_t u64; -#else - -#include <asm/types.h> - -typedef __s8 s8; -typedef __u8 u8; - -typedef __s16 s16; -typedef __u16 u16; - -typedef __s32 s32; -typedef __u32 u32; - -#endif #ifdef FALSE /* Hack for AIX. */ #undef FALSE

1 0

Help with some code
by Programmingkid 24 Sep '10

24 Sep '10

I'm trying to implement the -> word for setting variables, but it is not working as I hoped. Everything seems find until I reach the first eval word. At that point the evaluated string should make a new word. For some reason, the eval word says that the word can't be found. Here is the code: \ compile time: 4 -> cat \ run time: 4 set-cat \ : set-cat cat ! ; \ sets values for local variables : -> ( x - ) parse-word \ creates a copy of the variable's name 2dup strdup 2dup strdup 2dup strdup \ creates the new variable setting word " : set-" 2swap $cat2 2swap " ! ;" $cat2 " " 2swap $cat2 $cat2 eval \ sets up the new word to be called in place of -> " set-" 2swap $cat2 " postpone " 2swap $cat2 eval ; immediate \ combines two strings together : $cat2 ( $1 $2 -- $3 ) 2 pick over + dup >r alloc-mem >r 2swap tuck r@ swap move ( $2 $1-len ) r@ + swap move ( ) r> r> ; Anybody know what I could be doing wrong?

2 1

x86 multiboot header?
by Nathan Kunkee 21 Sep '10

21 Sep '10

Hi all, As of revision 861, I am unable to build a working multiboot image. I am working on Ubuntu 10.4, gcc 4.4. Although OpenSolaris b134, gcc4, also doesn't work. Grub 1.95 doesn't recognize the file as a multiboot file. QEMU crashes when passed this via -kernel (something about running code near 0xa000). Sure enough, I can find the second header for 0x2BAD but not 0x1BAD. Is the linker script that prefixes the header off? Thank you in advance for any assistance! Nathan

2 1

is it GPL?
by kim.jin 20 Sep '10

20 Sep '10

Hi, Is it all open firmware GPL? such as OpenBIOS, Smart Firmware, Open Firmware, and OpenBoot? Can any one I can use it free? My project need one boot tool. Best Regards! Kim King 2010-09-20

3 4

Re: [OpenBIOS] PReP PowerPC "emulation"
by Laurent Vivier 18 Sep '10

18 Sep '10

> OK, maybe I make a mistake. It's not a problem. > My goals is to run AIX 4.3, 5.1 and 6.1 on QEMU!!!!!. > Can you help me? What you suggest? > I think there is a lot of confusion ( I also make confusion). > How I can run QEMU to "emulate" CHRP platform ? By default, qemu-system-ppc emulates a CHRP. To run AIX 4.3 and 5.1 you can use a 32bit machine (qemu-system-ppc), to run AIX 6.1 you need a 64bit machine (qemu-system-ppc64). But to be able to run AIX, there are some improvements to add: - to OpenBIOS: at least RTAS is missing. - to qemu: emulate hardware supported by AIX (disk controller, network interface, graphic card, ...) As said before: patches are welcome... Regards, Laurent -- --------------------- Laurent(a)vivier.eu --------------------- "Tout ce qui est impossible reste à accomplir" Jules Verne "Things are only impossible until they're not" Jean-Luc Picard

8 9

PReP PowerPC "emulation"
by Massimo Montecchi 16 Sep '10

16 Sep '10

Hi, I have tried qemu from 0.11 to latest git (as of 11/09/2010) with latest openbios inside, but if i want to use PREP PPC "machine" the error is the same: qemu: hardware error: PowerPC 601 / 620 / 970 need a 1MB BIOS CPU #0: NIP 00000000 LR 00000000 CTR 00000000 XER 00000000 MSR 00000000 HID0 00000000 HF 00000000 idx 0 TB 00000000 00000000 DECR ffffffff GPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 CR 00000000 [ - - - - - - - - ] RES 00000000 FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000 FPSCR 00000000 SRR0 00000000 SRR1 00000000 SDR1 00000000 How can I use openbios to start an AIX with qemu ? -- Cordiali Saluti/Best Regards Massimo Montecchi Modena - Italy

5 7

Re: [OpenBIOS] corrections to vocabulary.fs
by Programmingkid 16 Sep '10

16 Sep '10

On Sep 15, 2010, at 6:00 AM, openbios-request(a)openbios.org wrote: > Message: 1 > Date: Wed, 15 Sep 2010 09:50:07 +0100 > From: Mark Cave-Ayland <mark.cave-ayland(a)siriusit.co.uk> > To: The OpenBIOS Mailinglist <openbios(a)openbios.org> > Subject: Re: [OpenBIOS] corrections to vocabulary.fs > Message-ID: <4C9088BF.4060803(a)siriusit.co.uk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Programmingkid wrote: > >> I found a few documentation mistakes in the vocabulary.fs file. In the comment section of get-order and set-order, their comments are incorrect. For get-order the comment should be ( -- widn .. wid1 n). For set-order the comment should be ( widn .. wid1 n -- ). This page is where I found the correct comments: http://lars.nocrew.org/dpans/dpans16.htm#16.6.1.2197 > > Nice work. Can you provide a patch for us to review and commit? > > > ATB, > > Mark. > > -- I'm not very good with making patches, but I think this might work: --- ./vocabulary.fs 2009-11-15 21:03:50.000000000 -0500 +++ /vocabulary.fs 2010-09-15 18:09:40.000000000 -0400 @@ -39,14 +39,14 @@ here 0 , ; -: get-order ( -- wid1 .. widn n ) +: get-order ( -- widn .. wid1 n ) #order @ 0 ?do #order @ i - 1- cells context + @ loop #order @ ; -: set-order ( wid1 .. widn n -- ) +: set-order ( widn .. wid1 n -- ) dup -1 = if drop forth-last 1 \ push system default word list and number of lists then

1 0

sparc32 openbios - passing nvram options
by Dmitriy Kargapolov 15 Sep '10

15 Sep '10

Hello, I tried to install netbsd 5.0.2 to qemu-system-sparc (which uses openbios). Boot from cdrom image and installation passed with no problems. But I was not able to boot from hdd. All the -boot, -prom-env options kind of ignored by qemu-system-sparc... All tries end up with booting fromn cdrom (if presented). Configuration device id QEMU version 1 machine id 64 UUID: 00000000-0000-0000-0000-000000000000 CPUs: 1 x TI,TMS390Z55 invalid nvram partition length nvram error detected, zapping pram [sparc] Booting file 'cdrom' with parameters '' Trying cdrom (/iommu/sbus/espdma/esp/sd@2,0) It looks like something wrong happens in the way of passing nvram parameters to openbios. Looking at the sources, I found that key method void arch_nvram_get(char*) is missing from openbios-1.0/arch/sparc32/openbios.c, but it is included in openbios-1.0/arch/sparc64/openbios.c. How nvram settings are passed from qemu command line to openbios-sparc32 in this case? Isn't this a bug? Thanks.

3 4