OpenBIOS April 2015

openbios@openbios.org

10 participants
28 discussions

Re: [OpenBIOS] [PATCH 0/2] add incremental Mac OS 9 support
by Mark Cave-Ayland 16 Apr '15

16 Apr '15

On 10/04/15 21:01, Cormac O'Brien wrote: > On Fri, Apr 10, 2015 at 2:34 PM, Programmingkid > <programmingkidx(a)gmail.com> wrote: > >> 2 of 2 didn't want to apply at all. Had to apply it by hand. > > I'll take a look and resubmit if necessary. It's probably something simple like a whitespace issue. >> I tried my Mac OS 9 software restore cd. The only effect I saw were two numbers >> on the stack. So that could indicate a little progress. > > This is the result of an interpreting issue that I still have to look > into. It can be fixed by > converting carriage returns to newlines, but I felt that a hack like that wasn't > appropriate to add in a patch. Once I can get the OS to actually boot > I'll take a look > at the interpreter and try to fix it. Oh that's interesting. Can you post more information about this, including the stack output so that we can try and work out what it is? ATB, Mark.

1 0

[PATCH 0/2] add incremental Mac OS 9 support
by Cormac O'Brien 16 Apr '15

16 Apr '15

These patches provide a small increase in OpenBIOS OS 9 support by fixing an out-of-memory error and adding a necessary Adler-32 checksum function, respectively.

3 5

help with debugging
by Programmingkid 14 Apr '15

14 Apr '15

I am also trying to debug Mac OS 9. I need to know where booting for Mac OS 9 stops. In the client.c file, I uncommented DEBUG_CIF and DUMP_IO, but I still don't see anything printed anywhere. I have checked the serial and parallel screens in QEMU. Nothing is printed. How can I debug a client interface program?

1 0

Re: [OpenBIOS] Allow building on Mac OS X
by BALATON Zoltan 13 Apr '15

13 Apr '15

Hello, I've seen your patches on the OpenBIOS mailing list, here are some comments. * instead on disabling -Werror completely you may want to try -fno-strict-aliasing (and if possible only set it for the file which exhibits this problem but I'm not sure how to do that with the used build system). The usb driver came from coreboot and probably had this problem there already but I did not see these warnings. It may be a peculiarity of your compiler or build environment. * At least on OS X 10.9 /bin/sh is the same as /bin/bash and /usr/bin/uname -m returns x86_64 (the same as I get on Linux) so these changes should not be needed. (I did not check on older versions though.) Are you running a 32 bit OS and compile for 64-bit target on that? Or do you have another version of these commands in your path overriding the system provided ones? Regards, BALATON Zoltan

2 1

Allow building on Mac OS X
by Programmingkid 13 Apr '15

13 Apr '15

> On Apr 13, 2015, at 3:58 PM, BALATON Zoltan wrote: > > Hello, Good to hear from you again. It has been a while. Hopefully you haven't given up on making MorphOS boot in QEMU. > I've seen your patches on the OpenBIOS mailing list, here are some comments. > > * instead on disabling -Werror completely you may want to try -fno-strict-aliasing (and if possible only set it for the file which exhibits this problem but I'm not sure how to do that with the used build system). The usb driver came from coreboot and probably had this problem there already but I did not see these warnings. It may be a peculiarity of your compiler or build environment. There are differences between Apple's supplied gcc and what Linux users usually use. That could be the reason for the errors on Mac OS X. If it is possible to set that option for the problem file, I will try to do so. Disabling Werror doesn't seem like such a big deal. Without it I can see the warning messages and still continue compiling ... a win-win situation. > * At least on OS X 10.9 /bin/sh is the same as /bin/bash and /usr/bin/uname -m returns x86_64 (the same as I get on Linux) so these changes should not be needed. (I did not check on older versions though.) The change from sh to bash was not to accommodate Mac OS X, it was to fix a problem on Linux. This code "filtered_list=${filtered_list:0:$end}" would fail on Debian Linux when the sh shell was set. I read on stackoverflow.com that Linux usually has sh set to Dash instead of bash. The switch in shells didn't cause anymore problems, so it seems good. > Are you running a 32 bit OS and compile for 64-bit target on that? Not doing that. Here is the output of uname -a: Linux debian 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux > Or do you have another version of these commands in your path overriding the system provided ones? I'm not aware of anything like this happening. Thank you for reviewing my patch.

1 0

[patch v2] Allow building on Mac OS X
by Programmingkid 13 Apr '15

13 Apr '15

This patch allows for the building of OpenBIOS on Mac OS X. Version 2 of this patch is a complete rewrite. Rather than adding compiler prefix after compiler prefix, we give the user the ability to specify their compiler's prefix using the -prefix option. My compiler is called ppc-elf-gcc. So I would use -prefix ppc-elf-. This way the user is free to decide what they want to use as a prefix. Another feature this patch gives is the ability to specify the computer's architecture. This feature fixes a problem with compiling on Mac OS X. Its uname command doesn't always return the correct cpu architecture. To go around this problem, the user can just specify the architecture with the -arch option like this: -arch amd64. This patch has been tested on Mac OS 10.6 and Debian Linux without problem. Index: Makefile.target =================================================================== --- Makefile.target (revision 1334) +++ Makefile.target (working copy) @@ -29,7 +29,7 @@ CFLAGS+= -Wall -Wredundant-decls -Wshadow -Wpointer-arith CFLAGS+= -Wstrict-prototypes -Wmissing-declarations -Wundef -Wendif-labels CFLAGS+= -Wstrict-aliasing -Wwrite-strings -Wmissing-prototypes -Wnested-externs -CFLAGS+= -Werror +# CFLAGS+= -Werror # Flags for dependency generation CFLAGS+= -MMD -MP -MT $@ -MF '$(*D)/$(*F).d' INCLUDES := -I$(SRCDIR)/include -I$(SRCDIR)/kernel/include -I$(ODIR)/target/include Index: config/scripts/switch-arch =================================================================== --- config/scripts/switch-arch (revision 1334) +++ config/scripts/switch-arch (working copy) @@ -1,4 +1,4 @@ -#!/bin/sh +#!/bin/bash # # MOLPATH is needed if you want to build openbios-mol.elf @@ -6,7 +6,7 @@ MOLPATH=$HOME/mol-0.9.71 if [ x"$1" = x -o "$1" = "-help" ]; then - printf "Usage:\n $0 [arch-config]...\n" + printf "Usage:\n $0 [arch-config] [-arch architecture] [-prefix compiler prefix]\n" printf "arch-config values supported for native or cross compiled builds:\n" printf " amd64, ppc, sparc32, sparc64, x86\n\n" printf "Add \"unix-\" prefix to compile openbios-unix executable (native only)\n" @@ -13,7 +13,13 @@ printf "Add \"builtin-\" prefix to compile openbios-builtin executables\n\n" printf "Without prefixes, builtin and unix targets are selected\n\n" printf "Special targets: mol-ppc briq-ppc pearpc-ppc qemu-ppc qemu-ppc64 xbox-x86\n\n" - printf "Example: $0 builtin-sparc32 unix-amd64 builtin-amd64\n" + printf "Example: $0 builtin-sparc32 unix-amd64 builtin-amd64\n\n" + printf "The -arch option is used if your uname command does not output the correct\n" + printf "value for your system. This is an issue for some versions of Mac OS X.\n" + printf "Example: -arch amd64\n\n" + printf "The -prefix option is for specifying your compiler prefix.\n" + printf "If your compiler is called ppc-elf-gcc, then your prefix would be ppc-elf-\n" + printf "In this case you would use -prefix ppc-elf-\n\n" exit 0 fi @@ -89,28 +95,106 @@ CROSSCFLAGS=$cflags } + +## Determines if user specified an architecture ## +architecture_specified() +{ + for arg in $SCRIPT_ARGS + do + if [ "$arg" = "-arch" ] + then + return 1 + fi + done + return 0 +} + +## Returns the user specified architecture ## +get_specified_architecture() +{ + while [ "$1" != "" ] + do + if [ "$1" = "-arch" ] + then + shift + echo "$1" + return + fi + shift + done + echo "ERROR: architecture value not found!" +} + archname() { - HOSTARCH=`uname -m | sed -e s/i.86/x86/ -e s/i86pc/x86/ \ - -e s/sun4u/sparc64/ -e s/sparc$/sparc32/ \ - -e s/arm.*/arm/ -e s/sa110/arm/ -e s/x86_64/amd64/ \ - -e "s/Power Macintosh/ppc/"` + architecture_specified $SCRIPT_ARGS + if [ "$?" -eq 1 ] + then + HOSTARCH=`get_specified_architecture $SCRIPT_ARGS` + else + HOSTARCH=`uname -m | sed -e s/i.86/x86/ -e s/i86pc/x86/ \ + -e s/sun4u/sparc64/ -e s/sparc$/sparc32/ \ + -e s/arm.*/arm/ -e s/sa110/arm/ -e s/x86_64/amd64/ \ + -e "s/Power Macintosh/ppc/"` + fi } -select_prefix() +## Determines if user specified compiler prefix ## +prefix_specified() { - for TARGET in ${1}-unknown-linux-gnu- ${1}-linux-gnu- ${1}-linux- ${1}-elf- ${1}-eabi- + for arg in $SCRIPT_ARGS do - if type ${TARGET}gcc > /dev/null 2>&1 + if [ "$arg" = "-prefix" ] then + return 1 + fi + done + return 0 +} + +## Returns the user specified compiler prefix ## +get_specified_prefix() +{ + while [ "$1" != "" ] + do + if [ "$1" = "-prefix" ] + then + shift + echo "$1" return fi - done - if [ "$ARCH" = "$HOSTARCH" ]; then - return + shift + done + echo "ERROR: prefix value not found!" +} + +select_prefix() +{ + prefix_specified + if [ "$?" -eq 1 ] # if the -prefix option is used + then + if type $(get_specified_prefix $SCRIPT_ARGS)"gcc" > /dev/null 2>&1 + then + TARGET=$(get_specified_prefix $SCRIPT_ARGS) + return + else + echo "Error: can't find specified prefix!" + return + fi + else + for TARGET in ${1}-unknown-linux-gnu- ${1}-linux-gnu- ${1}-linux- ${1}-elf- ${1}-eabi- + do + if type ${TARGET}gcc > /dev/null 2>&1 + then + return + fi + done + if [ "$ARCH" = "$HOSTARCH" ]; then + return + fi + echo "ERROR: no ${1} cross-compiler found !" 1>&2 + exit 1 fi - echo "ERROR: no ${1} cross-compiler found !" 1>&2 - exit 1 } config_set_boolean() @@ -127,6 +211,7 @@ SRCDIR=`dirname "$0"`/../.. BUILDDIR=`pwd` +SCRIPT_ARGS=$* # needed for functions that need to know arguments send to this script # make source path absolute SRCDIR=`cd "$SRCDIR"; pwd` @@ -147,7 +232,32 @@ fi target_list="" -for target in $*; do + +# filters out the -prefix and -arch options from the target list +awk -v arg_string="$*" 'BEGIN { + prefix_position = index(arg_string, "-prefix") + arch_position = index(arg_string, "-arch") + if(prefix_position == 0 && arch_position == 0) { + exit length(arg_string) + } + if(prefix_position == 0) { + exit (arch_position - 1) + } + else if (arch_position == 0) { + exit (prefix_position - 1) + } + + if(arch_position < prefix_position) + exit (arch_position - 1) + else + exit (prefix_position - 1) +}' + +end=$? +filtered_list=$* +filtered_list=${filtered_list:0:$end} + +for target in $filtered_list; do case $target in unix-*|builtin-*|plain-*|mol-ppc|briq-ppc|pearpc-ppc|qemu-ppc|qemu-ppc64|xbox-x86) target_list="$target_list $target"

1 0

[Patch] Allow building on Mac OS X
by Programmingkid 10 Apr '15

10 Apr '15

This patch allows OpenBIOS to be built on Mac OS X. Notes: I had to disable the -Werror flag because the file usbohci.c produces a lot of warnings when compiling. Here is what I see: "usbohci.c:230: warning: dereferencing type-punned pointer will break strict-aliasing rules". This warning is repeated many times in this file. Since I don't use usb, I'm not worried about these warnings. The uname -m option does not work properly on Mac OS X. It incorrectly reports i386 when it should report amd64. That is why it can't be counted on. Another command is used instead to determine the correct architecture type. The ppc-elf-gcc compiler is available from here: http://awos.wilcox-tech.com/downloads/AWOS-CC.bz2. It is quick and easy to download. It gives the user a gcc compiler that can make elf executables on Mac OS X. It is the reason why I added ppc-elf to the select_prefix() function. Index: Makefile.target =================================================================== --- Makefile.target (revision 1334) +++ Makefile.target (working copy) @@ -29,7 +29,7 @@ CFLAGS+= -Wall -Wredundant-decls -Wshadow -Wpointer-arith CFLAGS+= -Wstrict-prototypes -Wmissing-declarations -Wundef -Wendif-labels CFLAGS+= -Wstrict-aliasing -Wwrite-strings -Wmissing-prototypes -Wnested-externs -CFLAGS+= -Werror +# CFLAGS+= -Werror # Flags for dependency generation CFLAGS+= -MMD -MP -MT $@ -MF '$(*D)/$(*F).d' INCLUDES := -I$(SRCDIR)/include -I$(SRCDIR)/kernel/include -I$(ODIR)/target/include Index: config/scripts/switch-arch =================================================================== --- config/scripts/switch-arch (revision 1334) +++ config/scripts/switch-arch (working copy) @@ -97,9 +97,30 @@ -e "s/Power Macintosh/ppc/"` } +archname() + { + OS_NAME=`uname` + + # If running on Mac OS X + # uname -m is inncorrect on Mac OS X so we can't depend on it + if test "$OS_NAME" = "Darwin"; then + IS_64BIT=`sysctl hw.cpu64bit_capable` + if test "$IS_64BIT" = "hw.cpu64bit_capable: 1"; then + HOSTARCH="amd64" + else + HOSTARCH="x86" + fi + else + HOSTARCH=`uname -m | sed -e s/i.86/x86/ -e s/i86pc/x86/ \ + -e s/sun4u/sparc64/ -e s/sparc$/sparc32/ \ + -e s/arm.*/arm/ -e s/sa110/arm/ -e s/x86_64/amd64/ \ + -e "s/Power Macintosh/ppc/"` + fi +} + select_prefix() { - for TARGET in ${1}-unknown-linux-gnu- ${1}-linux-gnu- ${1}-linux- ${1}-elf- ${1}-eabi- + for TARGET in ${1}-unknown-linux-gnu- ${1}-linux-gnu- ${1}-linux- ${1}-elf- ${1}-eabi- ppc-elf- do if type ${TARGET}gcc > /dev/null 2>&1 then

1 0

Re: [OpenBIOS] [PATCH 0/2] add incremental Mac OS 9 support
by Programmingkid 10 Apr '15

10 Apr '15

On Apr 8, 2015, at 9:35 PM, Cormac O'Brien wrote: > These patches provide a small increase in OpenBIOS OS 9 support by fixing an > out-of-memory error and adding a necessary Adler-32 checksum function, > respectively. > I have tried them. 1 of 2 applied easily enough. 2 of 2 didn't want to apply at all. Had to apply it by hand. I kept seeing this error: "patching file libopenbios/bootinfo_load.c Hunk #1 FAILED at 30". It could be that I am on Mac OS X and you are on Linux. I tried my Mac OS 9 software restore cd. The only effect I saw were two numbers on the stack. So that could indicate a little progress.

2 1