[Qemu-devel] CUDA has problems with Mac OS 10.4

[Qemu-devel] CUDA has problems with Mac OS 10.4

[Programmingkid]

I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use the mac99 target. Here is the error message: 

panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR

This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99

I think there is still something wrong with CUDA. But we might not have to "fix" it. When we use the mac99 target, the PowerMac3,1 Macintosh system is what we are trying to emulate. My sources indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is used for ADB communications. Using it only on the BeigeG3 target makes sense. 

My sources for the PowerMac3,1 system is this link: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html

and this device tree:

PowerMac G4 device tree

ff839ab8: /cpus
ff839ce8:   /PowerPC,G4@0
ff83a060:     /l2-cache
ff83ab58: /chosen
ff83ace8: /memory@0
ff83af00: /openprom
ff83b008:   /client-services
ff83c1a8: /rom@ff800000
ff83c330:   /boot-rom@fff00000
ff83c4a8:   /macos
ff83c528: /options
ff83c5a8: /aliases
ff83cec8: /packages
ff83cf30:   /deblocker
ff83d798:   /disk-label
ff83e198:   /obp-tftp
ff8439f0:   /mac-parts
ff844850:   /mac-files
ff847540:   /hfs-plus-files
ff84c1c8:   /fat-files
ff84def8:   /iso-9660-files
ff84eb00:   /bootinfo-loader
ff8507a0:   /xcoff-loader
ff8511b8:   /pe-loader
ff851b90:   /elf-loader
ff8531c0:   /usb-hid-class
ff8554d8:   /usb-ms-class
ff8576a8:   /sbp2-disk
ff858ac0:   /ata-disk
ff859cd8:   /atapi-disk
ff85b348:   /bootpath-search
ff861b68:   /terminal-emulator
ff861c00: /psuedo-hid
ff861c88:   /keyboard
ff862308:   /mouse
ff862820: /multiboot
ff86e7f0: /diagnostics
ff86e858: /tools-node
ff8704b8: /rtas
ff8706b8: /nvram@fff04000
ff871180: /uni-n@f8000000
ff8713c8:   /i2c@f8001000
ff871b10:     /cereal
ff8721c0: /pci@f0000000
ff898cd0:   /uni-north-agp@b
ff898f40:   /ATY,Rage128Ps@10
ff873268: /pci@f2000000
ff8742d8:   /pci-bridge@d
ff876368:     /mac-io@7
ff8773a0:       /interrupt-controller@40000
ff877548:       /gpio@50
ff877630:         /extint-gpio1
ff8777c8:         /programmer-switch
ff877900:       /escc-legacy@12000
ff877af8:         /ch-a@12004
ff877c78:         /ch-b@12000
ff877df8:       /escc@13000
ff878000:         /ch-a@13020
ff8789a8:         /ch-b@13000
ff8792c0:       /davbus@14000
ff879540:         /sound
ff879c40:       /timer@15000
ff879da8:       /via-pmu@16000
ff87ccf0:         /rtc
ff87d3e0:         /power-mgt
ff8bf378:           /usb-power-mgt
ff87d648:       /i2c@18000
ff87ded8:         /cereal
ff87e5a0:       /ata-4@1f000
ff880318:         /disk
ff8809e8:       /ata-3@20000
ff882760:         /disk
ff882da8:       /ata-3@21000
ff884b20:         /disk
ff8864c8:     /ethernet@4
ff888690:     /usb@8
ff88dd50:     /usb@9
ff8be3f0:       /hub@1
ff8be580:         /keyboard@1
ff893410:     /firewire@a
ff8752e8: /pci@f4000000
ff8bb128:   /ethernet@f

Re: [Qemu-devel] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 11/11/15 15:15, Programmingkid wrote:

> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use the mac99 target. Here is the error message: 
> 
> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR
> 
> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
> 
> I think there is still something wrong with CUDA. But we might not have to "fix" it. When we use the mac99 target, the PowerMac3,1 Macintosh system is what we are trying to emulate. My sources indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is used for ADB communications. Using it only on the BeigeG3 target makes sense. 
> 
> My sources for the PowerMac3,1 system is this link: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
> 
> and this device tree:
> 
> PowerMac G4 device tree
> 
> ff839ab8: /cpus
> ff839ce8:   /PowerPC,G4@0
> ff83a060:     /l2-cache
> ff83ab58: /chosen
> ff83ace8: /memory@0
> ff83af00: /openprom
> ff83b008:   /client-services
> ff83c1a8: /rom@ff800000
> ff83c330:   /boot-rom@fff00000
> ff83c4a8:   /macos
> ff83c528: /options
> ff83c5a8: /aliases
> ff83cec8: /packages
> ff83cf30:   /deblocker
> ff83d798:   /disk-label
> ff83e198:   /obp-tftp
> ff8439f0:   /mac-parts
> ff844850:   /mac-files
> ff847540:   /hfs-plus-files
> ff84c1c8:   /fat-files
> ff84def8:   /iso-9660-files
> ff84eb00:   /bootinfo-loader
> ff8507a0:   /xcoff-loader
> ff8511b8:   /pe-loader
> ff851b90:   /elf-loader
> ff8531c0:   /usb-hid-class
> ff8554d8:   /usb-ms-class
> ff8576a8:   /sbp2-disk
> ff858ac0:   /ata-disk
> ff859cd8:   /atapi-disk
> ff85b348:   /bootpath-search
> ff861b68:   /terminal-emulator
> ff861c00: /psuedo-hid
> ff861c88:   /keyboard
> ff862308:   /mouse
> ff862820: /multiboot
> ff86e7f0: /diagnostics
> ff86e858: /tools-node
> ff8704b8: /rtas
> ff8706b8: /nvram@fff04000
> ff871180: /uni-n@f8000000
> ff8713c8:   /i2c@f8001000
> ff871b10:     /cereal
> ff8721c0: /pci@f0000000
> ff898cd0:   /uni-north-agp@b
> ff898f40:   /ATY,Rage128Ps@10
> ff873268: /pci@f2000000
> ff8742d8:   /pci-bridge@d
> ff876368:     /mac-io@7
> ff8773a0:       /interrupt-controller@40000
> ff877548:       /gpio@50
> ff877630:         /extint-gpio1
> ff8777c8:         /programmer-switch
> ff877900:       /escc-legacy@12000
> ff877af8:         /ch-a@12004
> ff877c78:         /ch-b@12000
> ff877df8:       /escc@13000
> ff878000:         /ch-a@13020
> ff8789a8:         /ch-b@13000
> ff8792c0:       /davbus@14000
> ff879540:         /sound
> ff879c40:       /timer@15000
> ff879da8:       /via-pmu@16000
> ff87ccf0:         /rtc
> ff87d3e0:         /power-mgt
> ff8bf378:           /usb-power-mgt
> ff87d648:       /i2c@18000
> ff87ded8:         /cereal
> ff87e5a0:       /ata-4@1f000
> ff880318:         /disk
> ff8809e8:       /ata-3@20000
> ff882760:         /disk
> ff882da8:       /ata-3@21000
> ff884b20:         /disk
> ff8864c8:     /ethernet@4
> ff888690:     /usb@8
> ff88dd50:     /usb@9
> ff8be3f0:       /hub@1
> ff8be580:         /keyboard@1
> ff893410:     /firewire@a
> ff8752e8: /pci@f4000000
> ff8bb128:   /ethernet@f

I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
issues that broke OS X among other things) and posted it to the
qemu-devel list at
https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.

The patchset posted works well for me here, and I suspect will fix the
issues that you've been seeing. Note that you'll also need the separate
OpenBIOS binary mentioned in the link above if you want to try booting
OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
since it regresses other images.


ATB,

Mark.

Re: [Qemu-devel] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:

> On 11/11/15 15:15, Programmingkid wrote:
> 
>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use the mac99 target. Here is the error message: 
>> 
>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR
>> 
>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>> 
>> I think there is still something wrong with CUDA. But we might not have to "fix" it. When we use the mac99 target, the PowerMac3,1 Macintosh system is what we are trying to emulate. My sources indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is used for ADB communications. Using it only on the BeigeG3 target makes sense. 
>> 
>> My sources for the PowerMac3,1 system is this link: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>> 
>> and this device tree:
>> 
>> PowerMac G4 device tree
>> 
>> ff839ab8: /cpus
>> ff839ce8:   /PowerPC,G4@0
>> ff83a060:     /l2-cache
>> ff83ab58: /chosen
>> ff83ace8: /memory@0
>> ff83af00: /openprom
>> ff83b008:   /client-services
>> ff83c1a8: /rom@ff800000
>> ff83c330:   /boot-rom@fff00000
>> ff83c4a8:   /macos
>> ff83c528: /options
>> ff83c5a8: /aliases
>> ff83cec8: /packages
>> ff83cf30:   /deblocker
>> ff83d798:   /disk-label
>> ff83e198:   /obp-tftp
>> ff8439f0:   /mac-parts
>> ff844850:   /mac-files
>> ff847540:   /hfs-plus-files
>> ff84c1c8:   /fat-files
>> ff84def8:   /iso-9660-files
>> ff84eb00:   /bootinfo-loader
>> ff8507a0:   /xcoff-loader
>> ff8511b8:   /pe-loader
>> ff851b90:   /elf-loader
>> ff8531c0:   /usb-hid-class
>> ff8554d8:   /usb-ms-class
>> ff8576a8:   /sbp2-disk
>> ff858ac0:   /ata-disk
>> ff859cd8:   /atapi-disk
>> ff85b348:   /bootpath-search
>> ff861b68:   /terminal-emulator
>> ff861c00: /psuedo-hid
>> ff861c88:   /keyboard
>> ff862308:   /mouse
>> ff862820: /multiboot
>> ff86e7f0: /diagnostics
>> ff86e858: /tools-node
>> ff8704b8: /rtas
>> ff8706b8: /nvram@fff04000
>> ff871180: /uni-n@f8000000
>> ff8713c8:   /i2c@f8001000
>> ff871b10:     /cereal
>> ff8721c0: /pci@f0000000
>> ff898cd0:   /uni-north-agp@b
>> ff898f40:   /ATY,Rage128Ps@10
>> ff873268: /pci@f2000000
>> ff8742d8:   /pci-bridge@d
>> ff876368:     /mac-io@7
>> ff8773a0:       /interrupt-controller@40000
>> ff877548:       /gpio@50
>> ff877630:         /extint-gpio1
>> ff8777c8:         /programmer-switch
>> ff877900:       /escc-legacy@12000
>> ff877af8:         /ch-a@12004
>> ff877c78:         /ch-b@12000
>> ff877df8:       /escc@13000
>> ff878000:         /ch-a@13020
>> ff8789a8:         /ch-b@13000
>> ff8792c0:       /davbus@14000
>> ff879540:         /sound
>> ff879c40:       /timer@15000
>> ff879da8:       /via-pmu@16000
>> ff87ccf0:         /rtc
>> ff87d3e0:         /power-mgt
>> ff8bf378:           /usb-power-mgt
>> ff87d648:       /i2c@18000
>> ff87ded8:         /cereal
>> ff87e5a0:       /ata-4@1f000
>> ff880318:         /disk
>> ff8809e8:       /ata-3@20000
>> ff882760:         /disk
>> ff882da8:       /ata-3@21000
>> ff884b20:         /disk
>> ff8864c8:     /ethernet@4
>> ff888690:     /usb@8
>> ff88dd50:     /usb@9
>> ff8be3f0:       /hub@1
>> ff8be580:         /keyboard@1
>> ff893410:     /firewire@a
>> ff8752e8: /pci@f4000000
>> ff8bb128:   /ethernet@f
> 
> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
> issues that broke OS X among other things) and posted it to the
> qemu-devel list at
> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
> 
> The patchset posted works well for me here, and I suspect will fix the
> issues that you've been seeing. Note that you'll also need the separate
> OpenBIOS binary mentioned in the link above if you want to try booting
> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
> since it regresses other images.

It looks like you are saying you wish to keep the CUDA device. Mac OS 9 is most
likely hard coded to expect via-pmu instead of via-cuda on the mac99 target.
Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
I will still try your patches. Do you have a repo that I could just clone? It is a
lot less error prone than patches. 

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Andreas Tobler]

On 11.11.15 19:55, Programmingkid wrote:
>
> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>
>> On 11/11/15 15:15, Programmingkid wrote:
>>
>>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use the mac99 target. Here is the error message:
>>>
>>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR
>>>
>>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>>>
>>> I think there is still something wrong with CUDA. But we might not have to "fix" it. When we use the mac99 target, the PowerMac3,1 Macintosh system is what we are trying to emulate. My sources indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is used for ADB communications. Using it only on the BeigeG3 target makes sense.
>>>
>>> My sources for the PowerMac3,1 system is this link: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>>>
>>> and this device tree:
>>>
>>> PowerMac G4 device tree
>>>
>>> ff839ab8: /cpus
>>> ff839ce8:   /PowerPC,G4@0
>>> ff83a060:     /l2-cache
>>> ff83ab58: /chosen
>>> ff83ace8: /memory@0
>>> ff83af00: /openprom
>>> ff83b008:   /client-services
>>> ff83c1a8: /rom@ff800000
>>> ff83c330:   /boot-rom@fff00000
>>> ff83c4a8:   /macos
>>> ff83c528: /options
>>> ff83c5a8: /aliases
>>> ff83cec8: /packages
>>> ff83cf30:   /deblocker
>>> ff83d798:   /disk-label
>>> ff83e198:   /obp-tftp
>>> ff8439f0:   /mac-parts
>>> ff844850:   /mac-files
>>> ff847540:   /hfs-plus-files
>>> ff84c1c8:   /fat-files
>>> ff84def8:   /iso-9660-files
>>> ff84eb00:   /bootinfo-loader
>>> ff8507a0:   /xcoff-loader
>>> ff8511b8:   /pe-loader
>>> ff851b90:   /elf-loader
>>> ff8531c0:   /usb-hid-class
>>> ff8554d8:   /usb-ms-class
>>> ff8576a8:   /sbp2-disk
>>> ff858ac0:   /ata-disk
>>> ff859cd8:   /atapi-disk
>>> ff85b348:   /bootpath-search
>>> ff861b68:   /terminal-emulator
>>> ff861c00: /psuedo-hid
>>> ff861c88:   /keyboard
>>> ff862308:   /mouse
>>> ff862820: /multiboot
>>> ff86e7f0: /diagnostics
>>> ff86e858: /tools-node
>>> ff8704b8: /rtas
>>> ff8706b8: /nvram@fff04000
>>> ff871180: /uni-n@f8000000
>>> ff8713c8:   /i2c@f8001000
>>> ff871b10:     /cereal
>>> ff8721c0: /pci@f0000000
>>> ff898cd0:   /uni-north-agp@b
>>> ff898f40:   /ATY,Rage128Ps@10
>>> ff873268: /pci@f2000000
>>> ff8742d8:   /pci-bridge@d
>>> ff876368:     /mac-io@7
>>> ff8773a0:       /interrupt-controller@40000
>>> ff877548:       /gpio@50
>>> ff877630:         /extint-gpio1
>>> ff8777c8:         /programmer-switch
>>> ff877900:       /escc-legacy@12000
>>> ff877af8:         /ch-a@12004
>>> ff877c78:         /ch-b@12000
>>> ff877df8:       /escc@13000
>>> ff878000:         /ch-a@13020
>>> ff8789a8:         /ch-b@13000
>>> ff8792c0:       /davbus@14000
>>> ff879540:         /sound
>>> ff879c40:       /timer@15000
>>> ff879da8:       /via-pmu@16000
>>> ff87ccf0:         /rtc
>>> ff87d3e0:         /power-mgt
>>> ff8bf378:           /usb-power-mgt
>>> ff87d648:       /i2c@18000
>>> ff87ded8:         /cereal
>>> ff87e5a0:       /ata-4@1f000
>>> ff880318:         /disk
>>> ff8809e8:       /ata-3@20000
>>> ff882760:         /disk
>>> ff882da8:       /ata-3@21000
>>> ff884b20:         /disk
>>> ff8864c8:     /ethernet@4
>>> ff888690:     /usb@8
>>> ff88dd50:     /usb@9
>>> ff8be3f0:       /hub@1
>>> ff8be580:         /keyboard@1
>>> ff893410:     /firewire@a
>>> ff8752e8: /pci@f4000000
>>> ff8bb128:   /ethernet@f
>>
>> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
>> issues that broke OS X among other things) and posted it to the
>> qemu-devel list at
>> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
>>
>> The patchset posted works well for me here, and I suspect will fix the
>> issues that you've been seeing. Note that you'll also need the separate
>> OpenBIOS binary mentioned in the link above if you want to try booting
>> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
>> since it regresses other images.
>
> It looks like you are saying you wish to keep the CUDA device. Mac OS 9 is most
> likely hard coded to expect via-pmu instead of via-cuda on the mac99 target.
> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
> I will still try your patches. Do you have a repo that I could just clone? It is a
> lot less error prone than patches.


I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it. 
Unfortunately it still doesn't work ... but hope is still here ;)

Mark, is your complete qemu patch available somewhere? Then I could test 
32-bit PowerPC on FreeBSD which still hangs on adb... up to now.

TIA,
Andreas

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 11, 2015, at 4:32 PM, Andreas Tobler wrote:

> On 11.11.15 19:55, Programmingkid wrote:
>> 
>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>> 
>>> On 11/11/15 15:15, Programmingkid wrote:
>>> 
>>>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use the mac99 target. Here is the error message:
>>>> 
>>>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR
>>>> 
>>>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>>>> 
>>>> I think there is still something wrong with CUDA. But we might not have to "fix" it. When we use the mac99 target, the PowerMac3,1 Macintosh system is what we are trying to emulate. My sources indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is used for ADB communications. Using it only on the BeigeG3 target makes sense.
>>>> 
>>>> My sources for the PowerMac3,1 system is this link: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>>>> 
>>>> and this device tree:
>>>> 
>>>> PowerMac G4 device tree
>>>> 
>>>> ff839ab8: /cpus
>>>> ff839ce8:   /PowerPC,G4@0
>>>> ff83a060:     /l2-cache
>>>> ff83ab58: /chosen
>>>> ff83ace8: /memory@0
>>>> ff83af00: /openprom
>>>> ff83b008:   /client-services
>>>> ff83c1a8: /rom@ff800000
>>>> ff83c330:   /boot-rom@fff00000
>>>> ff83c4a8:   /macos
>>>> ff83c528: /options
>>>> ff83c5a8: /aliases
>>>> ff83cec8: /packages
>>>> ff83cf30:   /deblocker
>>>> ff83d798:   /disk-label
>>>> ff83e198:   /obp-tftp
>>>> ff8439f0:   /mac-parts
>>>> ff844850:   /mac-files
>>>> ff847540:   /hfs-plus-files
>>>> ff84c1c8:   /fat-files
>>>> ff84def8:   /iso-9660-files
>>>> ff84eb00:   /bootinfo-loader
>>>> ff8507a0:   /xcoff-loader
>>>> ff8511b8:   /pe-loader
>>>> ff851b90:   /elf-loader
>>>> ff8531c0:   /usb-hid-class
>>>> ff8554d8:   /usb-ms-class
>>>> ff8576a8:   /sbp2-disk
>>>> ff858ac0:   /ata-disk
>>>> ff859cd8:   /atapi-disk
>>>> ff85b348:   /bootpath-search
>>>> ff861b68:   /terminal-emulator
>>>> ff861c00: /psuedo-hid
>>>> ff861c88:   /keyboard
>>>> ff862308:   /mouse
>>>> ff862820: /multiboot
>>>> ff86e7f0: /diagnostics
>>>> ff86e858: /tools-node
>>>> ff8704b8: /rtas
>>>> ff8706b8: /nvram@fff04000
>>>> ff871180: /uni-n@f8000000
>>>> ff8713c8:   /i2c@f8001000
>>>> ff871b10:     /cereal
>>>> ff8721c0: /pci@f0000000
>>>> ff898cd0:   /uni-north-agp@b
>>>> ff898f40:   /ATY,Rage128Ps@10
>>>> ff873268: /pci@f2000000
>>>> ff8742d8:   /pci-bridge@d
>>>> ff876368:     /mac-io@7
>>>> ff8773a0:       /interrupt-controller@40000
>>>> ff877548:       /gpio@50
>>>> ff877630:         /extint-gpio1
>>>> ff8777c8:         /programmer-switch
>>>> ff877900:       /escc-legacy@12000
>>>> ff877af8:         /ch-a@12004
>>>> ff877c78:         /ch-b@12000
>>>> ff877df8:       /escc@13000
>>>> ff878000:         /ch-a@13020
>>>> ff8789a8:         /ch-b@13000
>>>> ff8792c0:       /davbus@14000
>>>> ff879540:         /sound
>>>> ff879c40:       /timer@15000
>>>> ff879da8:       /via-pmu@16000
>>>> ff87ccf0:         /rtc
>>>> ff87d3e0:         /power-mgt
>>>> ff8bf378:           /usb-power-mgt
>>>> ff87d648:       /i2c@18000
>>>> ff87ded8:         /cereal
>>>> ff87e5a0:       /ata-4@1f000
>>>> ff880318:         /disk
>>>> ff8809e8:       /ata-3@20000
>>>> ff882760:         /disk
>>>> ff882da8:       /ata-3@21000
>>>> ff884b20:         /disk
>>>> ff8864c8:     /ethernet@4
>>>> ff888690:     /usb@8
>>>> ff88dd50:     /usb@9
>>>> ff8be3f0:       /hub@1
>>>> ff8be580:         /keyboard@1
>>>> ff893410:     /firewire@a
>>>> ff8752e8: /pci@f4000000
>>>> ff8bb128:   /ethernet@f
>>> 
>>> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
>>> issues that broke OS X among other things) and posted it to the
>>> qemu-devel list at
>>> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
>>> 
>>> The patchset posted works well for me here, and I suspect will fix the
>>> issues that you've been seeing. Note that you'll also need the separate
>>> OpenBIOS binary mentioned in the link above if you want to try booting
>>> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
>>> since it regresses other images.
>> 
>> It looks like you are saying you wish to keep the CUDA device. Mac OS 9 is most
>> likely hard coded to expect via-pmu instead of via-cuda on the mac99 target.
>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>> I will still try your patches. Do you have a repo that I could just clone? It is a
>> lot less error prone than patches.
> 
> 
> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it. Unfortunately it still doesn't work ... but hope is still here ;)

On a new world Mac? I'm thinking a mistake has been made. Maybe you mean via-pmu? According to FreeBSD's website all Macintoshes with a built-in USB port are supported. This would only mean new world Macs and they only have a via-pmu - no cuda device. 

> Mark, is your complete qemu patch available somewhere? Then I could test 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.

I'm thinking removing ADB support would fix this problem. Most real new world Macs have no ADB support. 

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[BALATON Zoltan]

On Wed, 11 Nov 2015, Programmingkid wrote:
> On Nov 11, 2015, at 4:32 PM, Andreas Tobler wrote:
>>> It looks like you are saying you wish to keep the CUDA device. Mac OS 9 is most
>>> likely hard coded to expect via-pmu instead of via-cuda on the mac99 target.
>>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>>> I will still try your patches. Do you have a repo that I could just clone? It is a
>>> lot less error prone than patches.
>>
>> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it. Unfortunately it still doesn't work ... but hope is still here ;)
>
> On a new world Mac? I'm thinking a mistake has been made. Maybe you mean 
> via-pmu? According to FreeBSD's website all Macintoshes with a built-in 
> USB port are supported. This would only mean new world Macs and they 
> only have a via-pmu - no cuda device.

I think you are right that mac99 should have via-pmu instead of cuda but 
it is not as simple as renaming it in the device tree because it is a 
different chip which we have no emulation for so first an emulation should 
be written. It is probably similar enough to cuda so using cuda instead 
works as long as the OS in only using the main functions. It is also hard 
to find a documentation on how via-pmu should behave. I've only found 
this:

http://mcosre.sourceforge.net/docs/apple_io.html

which is not very clear or detailed. The only hint from it was that pmu99 
uses gpio which I've seen OS-es try to access but I don't know anything on 
that or what should be emulated for it.

>> Mark, is your complete qemu patch available somewhere? Then I could test 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.
>
> I'm thinking removing ADB support would fix this problem. Most real new world Macs have no ADB support.

This may be a good idea to match the hardware we are trying to emulate 
better but some OSes may depend on ADB for now. I've noticed Finnix had no 
keyboard in debug mode without ADB (which may be a bug in Finnix, I could 
not verify if it works on real hardware or has the same problem there).

Regards,
BALATON Zoltan

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 11, 2015, at 6:14 PM, BALATON Zoltan wrote:

> On Wed, 11 Nov 2015, Programmingkid wrote:
>> On Nov 11, 2015, at 4:32 PM, Andreas Tobler wrote:
>>>> It looks like you are saying you wish to keep the CUDA device. Mac OS 9 is most
>>>> likely hard coded to expect via-pmu instead of via-cuda on the mac99 target.
>>>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>>>> I will still try your patches. Do you have a repo that I could just clone? It is a
>>>> lot less error prone than patches.
>>> 
>>> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it. Unfortunately it still doesn't work ... but hope is still here ;)
>> 
>> On a new world Mac? I'm thinking a mistake has been made. Maybe you mean via-pmu? According to FreeBSD's website all Macintoshes with a built-in USB port are supported. This would only mean new world Macs and they only have a via-pmu - no cuda device.
> 
> I think you are right that mac99 should have via-pmu instead of cuda but it is not as simple as renaming it in the device tree because it is a different chip which we have no emulation for so first an emulation should be written. It is probably similar enough to cuda so using cuda instead works as long as the OS in only using the main functions. It is also hard to find a documentation on how via-pmu should behave. I've only found this:
> 
> http://mcosre.sourceforge.net/docs/apple_io.html
> 
> which is not very clear or detailed. The only hint from it was that pmu99 uses gpio which I've seen OS-es try to access but I don't know anything on that or what should be emulated for it.

Thank you very much for this information. A quick check of PearPC shows it also uses CUDA, so we can't copy any code for via-pmu.

> 
>>> Mark, is your complete qemu patch available somewhere? Then I could test 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.
>> 
>> I'm thinking removing ADB support would fix this problem. Most real new world Macs have no ADB support.
> 
> This may be a good idea to match the hardware we are trying to emulate better but some OSes may depend on ADB for now. I've noticed Finnix had no keyboard in debug mode without ADB (which may be a bug in Finnix, I could not verify if it works on real hardware or has the same problem there).

Interesting. Did you use "-usb -device usb-keyboard" to enable usb support in QEMU when running Finnix? 

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[BALATON Zoltan]

On Thu, 12 Nov 2015, Programmingkid wrote:
> On Nov 11, 2015, at 6:14 PM, BALATON Zoltan wrote:
>> better but some OSes may depend on ADB for now. I've noticed Finnix had 
>> no keyboard in debug mode without ADB (which may be a bug in Finnix, I 
>> could not verify if it works on real hardware or has the same problem 
>> there).
>
> Interesting. Did you use "-usb -device usb-keyboard" to enable usb 
> support in QEMU when running Finnix?

Yes (or more exactly I had a patch always adding usb keyboard instead of 
adb one to match hardware) and I think it worked once booted fully but 
with debug I could only type with ADB keyboard. Maybe it's only that ADB 
driver is compiled in the Finnix kernel while OHCI is not. I did not 
investigate.

Regards,
BALATON Zoltan

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Segher Boessenkool]

On Thu, Nov 12, 2015 at 07:45:40PM +0100, BALATON Zoltan wrote:
> >Interesting. Did you use "-usb -device usb-keyboard" to enable usb 
> >support in QEMU when running Finnix?
> 
> Yes (or more exactly I had a patch always adding usb keyboard instead of 
> adb one to match hardware)

Some mac99/pmu99 hardware has an ADB keyboard, fwiw (tibook, for example).
The do have built-in USB; that, and being newworld, are not directly
related things.


Segher

Re: [Qemu-devel] [Qemu-ppc] [OpenBIOS] CUDA has problems with Mac OS 10.4

[BALATON Zoltan]

On Thu, 19 Nov 2015, Segher Boessenkool wrote:
> Some mac99/pmu99 hardware has an ADB keyboard, fwiw (tibook, for example).
> The do have built-in USB; that, and being newworld, are not directly
> related things.

Maybe, but the PowerMac3,1 we are trying to emulate here does not have ADB 
AFAIK. Although qemu's mac99 is not a real machine now we should move to 
being closer to some existing hardware if we want OSes written for that 
hardware to run.

Regards,
BALATON Zoltan

Re: [Qemu-devel] [Qemu-ppc] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 20, 2015, at 8:39 AM, BALATON Zoltan wrote:

> On Thu, 19 Nov 2015, Segher Boessenkool wrote:
>> Some mac99/pmu99 hardware has an ADB keyboard, fwiw (tibook, for example).
>> The do have built-in USB; that, and being newworld, are not directly
>> related things.
> 
> Maybe, but the PowerMac3,1 we are trying to emulate here does not have ADB AFAIK. Although qemu's mac99 is not a real machine now we should move to being closer to some existing hardware if we want OSes written for that hardware to run.

I use to have the same belief until Mark set me straight. We are only making an emulator of a new world Mac, not a simulator of a PowerMac3,1. This means we might be able to get away with not exactly mirroring a real Mac. The fact that Mac OS 9 can boot up at all does give me hope we are on the right path.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Alfonso Gamboa]

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

booting into MacOS9 with qemu to the Desktop is now possible, see:

http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250

Some issues,  remain,  certain extensions crash on boot.
On Nov 20, 2015 7:46 AM, "Programmingkid" <programmingkidx@gmail.com> wrote:

>
> On Nov 20, 2015, at 8:39 AM, BALATON Zoltan wrote:
>
> > On Thu, 19 Nov 2015, Segher Boessenkool wrote:
> >> Some mac99/pmu99 hardware has an ADB keyboard, fwiw (tibook, for
> example).
> >> The do have built-in USB; that, and being newworld, are not directly
> >> related things.
> >
> > Maybe, but the PowerMac3,1 we are trying to emulate here does not have
> ADB AFAIK. Although qemu's mac99 is not a real machine now we should move
> to being closer to some existing hardware if we want OSes written for that
> hardware to run.
>
> I use to have the same belief until Mark set me straight. We are only
> making an emulator of a new world Mac, not a simulator of a PowerMac3,1.
> This means we might be able to get away with not exactly mirroring a real
> Mac. The fact that Mac OS 9 can boot up at all does give me hope we are on
> the right path.
> --
> OpenBIOS                 http://openbios.org/
> Mailinglist:  http://lists.openbios.org/mailman/listinfo
> Free your System - May the Forth be with you
>

[-- Attachment #2: Type: text/html, Size: 1905 bytes --]

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[BALATON Zoltan]

On Fri, 20 Nov 2015, Alfonso Gamboa wrote:
> booting into MacOS9 with qemu to the Desktop is now possible, see:
>
> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250

Very nice.

> On Nov 20, 2015 7:46 AM, "Programmingkid" <programmingkidx@gmail.com> wrote:
>> I use to have the same belief until Mark set me straight. We are only
>> making an emulator of a new world Mac, not a simulator of a PowerMac3,1.
>> This means we might be able to get away with not exactly mirroring a real
>> Mac. The fact that Mac OS 9 can boot up at all does give me hope we are on
>> the right path.

I'm clear on that but what I've meant was that we probably have to make a 
closer emulation of the real PowerMac (not one to one but close enough) to 
make OSes written for that hardware happy. I think we are missing some i2c 
and gpio emulation that these OSes might expect but I'm not sure.

One thing that might help to hint at what's missing is to compile QEMU 
with DEBUG_UNASSIGNED (this will generate a lot of logs) and try to find 
out what is accessed that is not emulated.

Regards,
BALATON Zoltan

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 20/11/15 22:40, BALATON Zoltan wrote:

> On Fri, 20 Nov 2015, Alfonso Gamboa wrote:
>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>>
>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
> 
> Very nice.
> 
>> On Nov 20, 2015 7:46 AM, "Programmingkid" <programmingkidx@gmail.com>
>> wrote:
>>> I use to have the same belief until Mark set me straight. We are only
>>> making an emulator of a new world Mac, not a simulator of a PowerMac3,1.
>>> This means we might be able to get away with not exactly mirroring a
>>> real
>>> Mac. The fact that Mac OS 9 can boot up at all does give me hope we
>>> are on
>>> the right path.
> 
> I'm clear on that but what I've meant was that we probably have to make
> a closer emulation of the real PowerMac (not one to one but close
> enough) to make OSes written for that hardware happy. I think we are
> missing some i2c and gpio emulation that these OSes might expect but I'm
> not sure.
> 
> One thing that might help to hint at what's missing is to compile QEMU
> with DEBUG_UNASSIGNED (this will generate a lot of logs) and try to find
> out what is accessed that is not emulated.

Just to clarify here that this doesn't mean that I'm unwilling to accept
patches that move the device model more towards a real Mac, only that
any such patches must provide replacements for any new peripherals
introduced so that during the transition there is no loss of functionality.


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 20/11/15 17:06, Alfonso Gamboa wrote:

> booting into MacOS9 with qemu to the Desktop is now possible, see:
> 
> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
> 
> Some issues,  remain,  certain extensions crash on boot.

Hi Alfonso,

Has there been any progress at all as to which extensions may be causing
the crashes?


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:

> On 20/11/15 17:06, Alfonso Gamboa wrote:
> 
>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>> 
>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
>> 
>> Some issues,  remain,  certain extensions crash on boot.
> 
> Hi Alfonso,
> 
> Has there been any progress at all as to which extensions may be causing
> the crashes?

Trying to find that out is going to be hard. The extension manager does not appear when the space bar is held down.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:

> On 20/11/15 17:06, Alfonso Gamboa wrote:
> 
>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>> 
>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
>> 
>> Some issues,  remain,  certain extensions crash on boot.
> 
> Hi Alfonso,
> 
> Has there been any progress at all as to which extensions may be causing
> the crashes?

Remove these extensions from the Extensions folder and Mac OS 9 will boot to the desktop:

Apple Audio Extension
Apple Enet
Multiprocessing folder
Open Transport aslm modules
Text Encoding Converter

Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 21/11/15 22:59, Programmingkid wrote:

> On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:
> 
>> On 20/11/15 17:06, Alfonso Gamboa wrote:
>>
>>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>>>
>>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
>>>
>>> Some issues,  remain,  certain extensions crash on boot.
>>
>> Hi Alfonso,
>>
>> Has there been any progress at all as to which extensions may be causing
>> the crashes?
> 
> Remove these extensions from the Extensions folder and Mac OS 9 will boot to the desktop:
> 
> Apple Audio Extension
> Apple Enet
> Multiprocessing folder
> Open Transport aslm modules
> Text Encoding Converter
> 
> Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.

Now this is definitely helpful. Just to confirm that the presence of any
*one* of these modules causes boot to fail?


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 22, 2015, at 6:58 AM, Mark Cave-Ayland wrote:

> On 21/11/15 22:59, Programmingkid wrote:
> 
>> On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:
>> 
>>> On 20/11/15 17:06, Alfonso Gamboa wrote:
>>> 
>>>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>>>> 
>>>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
>>>> 
>>>> Some issues,  remain,  certain extensions crash on boot.
>>> 
>>> Hi Alfonso,
>>> 
>>> Has there been any progress at all as to which extensions may be causing
>>> the crashes?
>> 
>> Remove these extensions from the Extensions folder and Mac OS 9 will boot to the desktop:
>> 
>> Apple Audio Extension
>> Apple Enet
>> Multiprocessing folder
>> Open Transport aslm modules
>> Text Encoding Converter
>> 
>> Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.
> 
> Now this is definitely helpful. Just to confirm that the presence of any
> *one* of these modules causes boot to fail?

Yes. That is correct. 

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 22/11/15 17:39, Programmingkid wrote:

>>>> Hi Alfonso,
>>>>
>>>> Has there been any progress at all as to which extensions may be causing
>>>> the crashes?
>>>
>>> Remove these extensions from the Extensions folder and Mac OS 9 will boot to the desktop:
>>>
>>> Apple Audio Extension
>>> Apple Enet
>>> Multiprocessing folder
>>> Open Transport aslm modules
>>> Text Encoding Converter
>>>
>>> Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.
>>
>> Now this is definitely helpful. Just to confirm that the presence of any
>> *one* of these modules causes boot to fail?
> 
> Yes. That is correct. 

I've just done some testing here on my 9.2.2 ISO and I've found the
following:

- Removing "Apple Audio Extension" appears to prevent some kind of
corruption which allows MacsBugs to give non-corrupt stack traces

- The resulting stack trace points at "AINI 8042 05AE Startup ASLM PPC"

- Further removing "Open Transport ASLM Modules" allows boot to proceed
nearly all the way except for a hang just before the progress bar
reaches the end

- Finally removing "Multiprocessing" allows boot to proceed all the way
to the desktop

Alfonso/John can you confirm whether removing these 3 extensions works
for your images too? If you are able to run the OS 9 installer all the
way through and manually mount the hd images to remove them by hand
before the next boot, do you end up with a bootable OS 9 HD image?


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:

> On 22/11/15 17:39, Programmingkid wrote:
> 
>>>>> Hi Alfonso,
>>>>> 
>>>>> Has there been any progress at all as to which extensions may be causing
>>>>> the crashes?
>>>> 
>>>> Remove these extensions from the Extensions folder and Mac OS 9 will boot to the desktop:
>>>> 
>>>> Apple Audio Extension
>>>> Apple Enet
>>>> Multiprocessing folder
>>>> Open Transport aslm modules
>>>> Text Encoding Converter
>>>> 
>>>> Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.
>>> 
>>> Now this is definitely helpful. Just to confirm that the presence of any
>>> *one* of these modules causes boot to fail?
>> 
>> Yes. That is correct. 
> 
> I've just done some testing here on my 9.2.2 ISO and I've found the
> following:
> 
> - Removing "Apple Audio Extension" appears to prevent some kind of
> corruption which allows MacsBugs to give non-corrupt stack traces
> 
> - The resulting stack trace points at "AINI 8042 05AE Startup ASLM PPC"
> 
> - Further removing "Open Transport ASLM Modules" allows boot to proceed
> nearly all the way except for a hang just before the progress bar
> reaches the end
> 
> - Finally removing "Multiprocessing" allows boot to proceed all the way
> to the desktop
> 
> Alfonso/John can you confirm whether removing these 3 extensions works
> for your images too? If you are able to run the OS 9 installer all the
> way through and manually mount the hd images to remove them by hand
> before the next boot, do you end up with a bootable OS 9 HD image?

Which version of Macsbug are you using? Do you have an 9.2.2 image file
available for download that has macsbug installed? I tried installing Macsbug
6.6.3 into my iso file, but Mac OS 9 always stops booting right before the debugger
message is suppose to appear.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 24/11/15 03:28, Programmingkid wrote:

>> I've just done some testing here on my 9.2.2 ISO and I've found the
>> following:
>>
>> - Removing "Apple Audio Extension" appears to prevent some kind of
>> corruption which allows MacsBugs to give non-corrupt stack traces
>>
>> - The resulting stack trace points at "AINI 8042 05AE Startup ASLM PPC"
>>
>> - Further removing "Open Transport ASLM Modules" allows boot to proceed
>> nearly all the way except for a hang just before the progress bar
>> reaches the end
>>
>> - Finally removing "Multiprocessing" allows boot to proceed all the way
>> to the desktop
>>
>> Alfonso/John can you confirm whether removing these 3 extensions works
>> for your images too? If you are able to run the OS 9 installer all the
>> way through and manually mount the hd images to remove them by hand
>> before the next boot, do you end up with a bootable OS 9 HD image?
> 
> Which version of Macsbug are you using? Do you have an 9.2.2 image file
> available for download that has macsbug installed? I tried installing Macsbug
> 6.6.3 into my iso file, but Mac OS 9 always stops booting right before the debugger
> message is suppose to appear.

One other thing I forgot to mention: if you install MacsBugs onto your
ISO, you need to provide some mouse or keyboard input around the time
when the happy mac icon appears (I normally capture the mouse and move
it around a little), otherwise as you mention you see a freeze just
before "Debugger Installed" appears.

My guess is that MacsBugs is trying to work out whether to use ADB or
USB for keyboard, so unless the OS 9 ADB driver gets any input then it
can't decide and hangs on boot. Then again this could be another bug
somewhere in the QEMU ADB emulation...


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Alfonso Gamboa]

[-- Attachment #1: Type: text/plain, Size: 3889 bytes --]

On Tue, Nov 24, 2015 at 12:01 AM, Mark Cave-Ayland <
mark.cave-ayland@ilande.co.uk> wrote:

> On 24/11/15 03:28, Programmingkid wrote:
>
> >> I've just done some testing here on my 9.2.2 ISO and I've found the
> >> following:
> >>
> >> - Removing "Apple Audio Extension" appears to prevent some kind of
> >> corruption which allows MacsBugs to give non-corrupt stack traces
> >>
> >> - The resulting stack trace points at "AINI 8042 05AE Startup ASLM PPC"
> >>
> >> - Further removing "Open Transport ASLM Modules" allows boot to proceed
> >> nearly all the way except for a hang just before the progress bar
> >> reaches the end
> >>
> >> - Finally removing "Multiprocessing" allows boot to proceed all the way
> >> to the desktop
> >>
> >> Alfonso/John can you confirm whether removing these 3 extensions works
> >> for your images too? If you are able to run the OS 9 installer all the
> >> way through and manually mount the hd images to remove them by hand
> >> before the next boot, do you end up with a bootable OS 9 HD image?
> >
> > Which version of Macsbug are you using? Do you have an 9.2.2 image file
> > available for download that has macsbug installed? I tried installing
> Macsbug
> > 6.6.3 into my iso file, but Mac OS 9 always stops booting right before
> the debugger
> > message is suppose to appear.
>
> One other thing I forgot to mention: if you install MacsBugs onto your
> ISO, you need to provide some mouse or keyboard input around the time
> when the happy mac icon appears (I normally capture the mouse and move
> it around a little), otherwise as you mention you see a freeze just
> before "Debugger Installed" appears.
>
> My guess is that MacsBugs is trying to work out whether to use ADB or
> USB for keyboard, so unless the OS 9 ADB driver gets any input then it
> can't decide and hangs on boot. Then again this could be another bug
> somewhere in the QEMU ADB emulation...
>
>
> ATB,
>
> Mark.
>
>
Mark,

You are correct about booting MacsBug and mouse or keyboard input during
happy mac icon!  Also, Programmingkid, you hit the nail on the head
regarding those extensions.  Removing those 4 extensions and
Multiprocessing Folder does indeed allow boot to desktop.

In my testing tonight, I was able to successfully patch the System file to
allow the System Folder from the installation cd to boot off the hard disk
image, before it was throwing an error after happy mac icon saying the
media had been copied and would not boot.  I achieved this by editing the
System file and removing the resource "xboo". This resource apparently
checks whether the boot volume is a locked HFS volume or not, and denies
boot accordingly.

I have included MacsBug 6.6.3 in the System Folder, and right before I get
to desktop, MacsBug opens with a "PowerPC Illegal Instruction at 00000000",
but I am able to type ES (escape to shell) to successfully boot into the
desktop.

Next, when running either the 9.2.1 OR 9.2.2 installer, MacsBug throws,
"PowerPC unmapped memory exception at AAFE0700".  I am then able to escape
to shell and resume the Finder.  I have tried copying the installer to
another disk image, increase memory allocation, to no avail.  The same
error persists.

I was also unable to find a method to boot any installed System File.  I
attempted to use an existing 9.2.2 System Folder found on macintoshgarden,
which would crash QEMU completely.  Next, extracting the "Big System
Morsels" file from the 9.2.2 installation cd (which should be the System
file, just renamed and with a different creator code) and setting the
Creator and Type Codes, throwing it in the System Folder and rebooting,
results in an Illegal Instruction and or Bus Error during boot.

Seems we still have some work to do...

I'm uploading a disk image y'all can use to boot to OS9.2.2CDSYSTEM for
further testing, I will forward the link when its ready to download.

-Alfonso

[-- Attachment #2: Type: text/html, Size: 5288 bytes --]

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:

> On 22/11/15 17:39, Programmingkid wrote:
> 
>>>>> Hi Alfonso,
>>>>> 
>>>>> Has there been any progress at all as to which extensions may be causing
>>>>> the crashes?
>>>> 
>>>> Remove these extensions from the Extensions folder and Mac OS 9 will boot to the desktop:
>>>> 
>>>> Apple Audio Extension
>>>> Apple Enet
>>>> Multiprocessing folder
>>>> Open Transport aslm modules
>>>> Text Encoding Converter
>>>> 
>>>> Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.
>>> 
>>> Now this is definitely helpful. Just to confirm that the presence of any
>>> *one* of these modules causes boot to fail?
>> 
>> Yes. That is correct. 
> 
> I've just done some testing here on my 9.2.2 ISO and I've found the
> following:
> 
> - Removing "Apple Audio Extension" appears to prevent some kind of
> corruption which allows MacsBugs to give non-corrupt stack traces
> 
> - The resulting stack trace points at "AINI 8042 05AE Startup ASLM PPC"
> 
> - Further removing "Open Transport ASLM Modules" allows boot to proceed
> nearly all the way except for a hang just before the progress bar
> reaches the end
> 
> - Finally removing "Multiprocessing" allows boot to proceed all the way
> to the desktop
> 
> Alfonso/John can you confirm whether removing these 3 extensions works
> for your images too? If you are able to run the OS 9 installer all the
> way through and manually mount the hd images to remove them by hand
> before the next boot, do you end up with a bootable OS 9 HD image?

It does work for me, but an illegal instruction error took place when the
desktop showed up. I could not do anything after the crash. Mac OS 9 does
hang sometimes earlier in the boot process,  so the above results are not consistent. 

My info:
Image: Mac OS 9.2.1 (Cormac's image)
Macsbug 6.6.3
Host: Mac OS 10.6

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Alfonso Gamboa]

[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]

On Mon, Nov 23, 2015 at 7:28 PM, Programmingkid <programmingkidx@gmail.com>
 wrote:

>
> On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:
>
> > On 22/11/15 17:39, Programmingkid wrote:
> >
> >>>>> Hi Alfonso,
> >>>>>
> >>>>> Has there been any progress at all as to which extensions may be
> causing
> >>>>> the crashes?
> >>>>
> >>>> Remove these extensions from the Extensions folder and Mac OS 9 will
> boot to the desktop:
> >>>>
> >>>> Apple Audio Extension
> >>>> Apple Enet
> >>>> Multiprocessing folder
> >>>> Open Transport aslm modules
> >>>> Text Encoding Converter
> >>>>
> >>>> Note: I used Cormac's Mac OS 9.2.1 iso file to do my testing.
> >>>
> >>> Now this is definitely helpful. Just to confirm that the presence of
> any
> >>> *one* of these modules causes boot to fail?
> >>
> >> Yes. That is correct.
> >
> > I've just done some testing here on my 9.2.2 ISO and I've found the
> > following:
> >
> > - Removing "Apple Audio Extension" appears to prevent some kind of
> > corruption which allows MacsBugs to give non-corrupt stack traces
> >
> > - The resulting stack trace points at "AINI 8042 05AE Startup ASLM PPC"
> >
> > - Further removing "Open Transport ASLM Modules" allows boot to proceed
> > nearly all the way except for a hang just before the progress bar
> > reaches the end
> >
> > - Finally removing "Multiprocessing" allows boot to proceed all the way
> > to the desktop
> >
> > Alfonso/John can you confirm whether removing these 3 extensions works
> > for your images too? If you are able to run the OS 9 installer all the
> > way through and manually mount the hd images to remove them by hand
> > before the next boot, do you end up with a bootable OS 9 HD image?
>
> Which version of Macsbug are you using? Do you have an 9.2.2 image file
> available for download that has macsbug installed? I tried installing
> Macsbug
> 6.6.3 into my iso file, but Mac OS 9 always stops booting right before the
> debugger
> message is suppose to appear.


Here are some links I packaged for the emaculation forum, included is an
image with macsbug installed already.  I had success booting to desktop.

Note:  it seems as time goes by, booting several times using the ISO images
corrupts them, resulting in failed boots with crashes at the boot splash
screen.  Crashes will continue until you replace them with fresh ones from
the zip files.  Reasons as to why are unknown at this time.

Resedit, Stuffit, Toast, Disk Copy, utilities in an ISO to mount within
QEMU:
http://bebop.gtxent.com/qemu_os9_utilities.iso.zip

MacOS 9.2.2 bootable image(extensions all removed):
http://bebop.gtxent.com/os922_uni.iso.zip

MacOS 9.2.1 bootable image(extensions all removed):
http://bebop.gtxent.com/os92_test.iso.zip

MacOS 9.2.1 bootable image with macsbug (extensions all removed):
http://bebop.gtxent.com/os92_test_macsbug.iso.zip

[-- Attachment #2: Type: text/html, Size: 6956 bytes --]

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 24/11/15 05:23, Alfonso Gamboa wrote:

> Here are some links I packaged for the emaculation forum, included is an
> image with macsbug installed already.  I had success booting to desktop.  
> 
> Note:  it seems as time goes by, booting several times using the ISO
> images corrupts them, resulting in failed boots with crashes at the boot
> splash screen.  Crashes will continue until you replace them with fresh
> ones from the zip files.  Reasons as to why are unknown at this time.

Yeah I noticed when booting from a CDROM that my open windows are
remembered across sessions(!). This makes me think that OS 9 thinks the
HFS volume is a HD rather than a CDROM and so mounts it read/write on
boot. How would I find this out in OS9?

> Resedit, Stuffit, Toast, Disk Copy, utilities in an ISO to mount within
> QEMU:
> http://bebop.gtxent.com/qemu_os9_utilities.iso.zip
> 
> MacOS 9.2.2 bootable image(extensions all removed):
> http://bebop.gtxent.com/os922_uni.iso.zip
> 
> MacOS 9.2.1 bootable image(extensions all removed):
> http://bebop.gtxent.com/os92_test.iso.zip
> 
> MacOS 9.2.1 bootable image with macsbug (extensions all removed):
> http://bebop.gtxent.com/os92_test_macsbug.iso.zip

These images are definitely helpful, however what would be really useful
to know is exactly what the modules in question do:

- Multiprocessing (maybe uses a currently unimplemented CPU instruction
to facilitate faster multitasking?)

- Open Transport ASLM Modules (no idea what these do)

- Apple Audio Extension Module (is this just a standard sound driver or
other? I did get a backtrace once suggesting that it was trying to
access digital CDROM audio which is why it crashed. Then again if it
thinks that the CDROM is a HD then that's not going to help too much
here either).


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Alfonso Gamboa]

[-- Attachment #1: Type: text/plain, Size: 3050 bytes --]

On Tue, Nov 24, 2015 at 12:06 AM, Mark Cave-Ayland <
mark.cave-ayland@ilande.co.uk> wrote:

> On 24/11/15 05:23, Alfonso Gamboa wrote:
>
> > Here are some links I packaged for the emaculation forum, included is an
> > image with macsbug installed already.  I had success booting to desktop.
> >
> > Note:  it seems as time goes by, booting several times using the ISO
> > images corrupts them, resulting in failed boots with crashes at the boot
> > splash screen.  Crashes will continue until you replace them with fresh
> > ones from the zip files.  Reasons as to why are unknown at this time.
>
> Yeah I noticed when booting from a CDROM that my open windows are
> remembered across sessions(!). This makes me think that OS 9 thinks the
> HFS volume is a HD rather than a CDROM and so mounts it read/write on
> boot. How would I find this out in OS9?
>
> > Resedit, Stuffit, Toast, Disk Copy, utilities in an ISO to mount within
> > QEMU:
> > http://bebop.gtxent.com/qemu_os9_utilities.iso.zip
> >
> > MacOS 9.2.2 bootable image(extensions all removed):
> > http://bebop.gtxent.com/os922_uni.iso.zip
> >
> > MacOS 9.2.1 bootable image(extensions all removed):
> > http://bebop.gtxent.com/os92_test.iso.zip
> >
> > MacOS 9.2.1 bootable image with macsbug (extensions all removed):
> > http://bebop.gtxent.com/os92_test_macsbug.iso.zip
>
> These images are definitely helpful, however what would be really useful
> to know is exactly what the modules in question do:
>
> - Multiprocessing (maybe uses a currently unimplemented CPU instruction
> to facilitate faster multitasking?)
>
> - Open Transport ASLM Modules (no idea what these do)
>
> - Apple Audio Extension Module (is this just a standard sound driver or
> other? I did get a backtrace once suggesting that it was trying to
> access digital CDROM audio which is why it crashed. Then again if it
> thinks that the CDROM is a HD then that's not going to help too much
> here either).
>
>
> ATB,
>
> Mark.
>
>
​The "Multiprocessing" folder contains a file named "Apple CPU Plugins" of
type cpup. Looking at the resource "cpups", it seems to contain code to
supplement the OS to support various newer CPUs and architectures.  The
resources in the file are named (and contain):

PowerSurge2PPlugin:
"hammerhead" (old clone computers based off multiple PPC 604I believe)

G3Plugin:
Powerbook1,1

Core99Plugin:
uni-north
keylargo
PowerMac2,1
PowerMac2,2
PowerMac3,4
PowerMac3,5
PowerMac4,1
PowerBook3,3
PowerBook3,4

The "Open Transport ASLM Modules" file seem to be a collection of shared
libraries, since many programs, once this file is removed from the
extensions folder, refuses to run, for example Apple System Profiler.
OTLib$NBPScnr, OTLib$SerIAB are some examples of shared libraries contained
within this file.  This is verified from the book "Sad Macs, Bombs, and
Other Disasters: And what to Do about Them By Ted Landau
​, see https://goo.gl/TVm9Tt"​

I will do more research.

Thanks,
Alfonso

[-- Attachment #2: Type: text/html, Size: 5923 bytes --]

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 24/11/15 09:01, Alfonso Gamboa wrote:

>     These images are definitely helpful, however what would be really useful
>     to know is exactly what the modules in question do:
> 
>     - Multiprocessing (maybe uses a currently unimplemented CPU instruction
>     to facilitate faster multitasking?)
> 
>     - Open Transport ASLM Modules (no idea what these do)
> 
>     - Apple Audio Extension Module (is this just a standard sound driver or
>     other? I did get a backtrace once suggesting that it was trying to
>     access digital CDROM audio which is why it crashed. Then again if it
>     thinks that the CDROM is a HD then that's not going to help too much
>     here either).
> 
> ​The "Multiprocessing" folder contains a file named "Apple CPU Plugins"
> of type cpup. Looking at the resource "cpups", it seems to contain code
> to supplement the OS to support various newer CPUs and architectures. 
> The resources in the file are named (and contain):
> 
> PowerSurge2PPlugin:
> "hammerhead" (old clone computers based off multiple PPC 604I believe)
> 
> G3Plugin:
> Powerbook1,1
> 
> Core99Plugin:
> uni-north
> keylargo
> PowerMac2,1
> PowerMac2,2
> PowerMac3,4
> PowerMac3,5
> PowerMac4,1
> PowerBook3,3
> PowerBook3,4

Now the mac99 machine defines itself as "PowerMac3,1" so that might
suggest that it is something in the keylargo/uni-north code that is
causing the problem. Is there a way to somehow disable the individual
resources in the Core99Plugin in order to determine which one is the
culprit?

> The "Open Transport ASLM Modules" file seem to be a collection of shared
> libraries, since many programs, once this file is removed from the
> extensions folder, refuses to run, for example Apple System Profiler. 
> OTLib$NBPScnr, OTLib$SerIAB are some examples of shared libraries
> contained within this file.  This is verified from the book "Sad Macs,
> Bombs, and Other Disasters: And what to Do about Them By Ted Landau
> ​, see https://goo.gl/TVm9Tt"​ 
> 
> I will do more research.

A good starting point is the "Apple Audio Extension Module" since that
seems to cause havoc on load. Do you know any good tutorials on how to
debug an extension module on load i.e. how to step through its
initialisation? Unfortunately there doesn't seem to be much related
documentation around these days.


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] [Qemu-ppc] CUDA has problems with Mac OS 10.4

[Alfonso Gamboa]

[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]

On Tue, Nov 24, 2015 at 12:06 AM, Mark Cave-Ayland <
mark.cave-ayland@ilande.co.uk> wrote:

> On 24/11/15 05:23, Alfonso Gamboa wrote:
>
> > Here are some links I packaged for the emaculation forum, included is an
> > image with macsbug installed already.  I had success booting to desktop.
> >
> > Note:  it seems as time goes by, booting several times using the ISO
> > images corrupts them, resulting in failed boots with crashes at the boot
> > splash screen.  Crashes will continue until you replace them with fresh
> > ones from the zip files.  Reasons as to why are unknown at this time.
>
> Yeah I noticed when booting from a CDROM that my open windows are
> remembered across sessions(!). This makes me think that OS 9 thinks the
> HFS volume is a HD rather than a CDROM and so mounts it read/write on
> boot. How would I find this out in OS9?
>
> > Resedit, Stuffit, Toast, Disk Copy, utilities in an ISO to mount within
> > QEMU:
> > http://bebop.gtxent.com/qemu_os9_utilities.iso.zip
> >
> > MacOS 9.2.2 bootable image(extensions all removed):
> > http://bebop.gtxent.com/os922_uni.iso.zip
> >
> > MacOS 9.2.1 bootable image(extensions all removed):
> > http://bebop.gtxent.com/os92_test.iso.zip
> >
> > MacOS 9.2.1 bootable image with macsbug (extensions all removed):
> > http://bebop.gtxent.com/os92_test_macsbug.iso.zip
>
> These images are definitely helpful, however what would be really useful
> to know is exactly what the modules in question do:
>
> - Multiprocessing (maybe uses a currently unimplemented CPU instruction
> to facilitate faster multitasking?)
>
> - Open Transport ASLM Modules (no idea what these do)
>
> - Apple Audio Extension Module (is this just a standard sound driver or
> other? I did get a backtrace once suggesting that it was trying to
> access digital CDROM audio which is why it crashed. Then again if it
> thinks that the CDROM is a HD then that's not going to help too much
> here either).
>
>
> ATB,
>
> Mark.
>
>

This is a zip containing qemu-ppc, and a 2gb disk image file with macos
9.2.2 installed. The system folder was modified to allow it to boot from an
unlocked HFS volume. This image has lots of extensions and control panels
included and enabled.  Once you download qemu_easy.zip, extract it, and run
qemu_os9.command (this is just a batch file with arguments)

qemu will now load and boot from the disk image to OS9 desktop.  The disk
image included here is read/write enabled.  I have only tried this on
OS10.11, your success may vary.  MacsBug is included in the root directory,
but is not enabled.


http://bebop.gtxent.com/qemu_easy.zip

thanks,
Alfonso

[-- Attachment #2: Type: text/html, Size: 4096 bytes --]

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 11/11/15 21:32, Andreas Tobler wrote:

> On 11.11.15 19:55, Programmingkid wrote:
>>
>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>
>>> On 11/11/15 15:15, Programmingkid wrote:
>>>
>>>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my
>>>> Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA
>>>> problem. I did use the mac99 target. Here is the error message:
>>>>
>>>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION
>>>> TYPE AND ERROR
>>>>
>>>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d
>>>> -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>>>>
>>>> I think there is still something wrong with CUDA. But we might not
>>>> have to "fix" it. When we use the mac99 target, the PowerMac3,1
>>>> Macintosh system is what we are trying to emulate. My sources
>>>> indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is
>>>> used for ADB communications. Using it only on the BeigeG3 target
>>>> makes sense.
>>>>
>>>> My sources for the PowerMac3,1 system is this link:
>>>> http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>>>>
>>>>
>>>> and this device tree:
>>>>
>>>> PowerMac G4 device tree
>>>>
>>>> ff839ab8: /cpus
>>>> ff839ce8:   /PowerPC,G4@0
>>>> ff83a060:     /l2-cache
>>>> ff83ab58: /chosen
>>>> ff83ace8: /memory@0
>>>> ff83af00: /openprom
>>>> ff83b008:   /client-services
>>>> ff83c1a8: /rom@ff800000
>>>> ff83c330:   /boot-rom@fff00000
>>>> ff83c4a8:   /macos
>>>> ff83c528: /options
>>>> ff83c5a8: /aliases
>>>> ff83cec8: /packages
>>>> ff83cf30:   /deblocker
>>>> ff83d798:   /disk-label
>>>> ff83e198:   /obp-tftp
>>>> ff8439f0:   /mac-parts
>>>> ff844850:   /mac-files
>>>> ff847540:   /hfs-plus-files
>>>> ff84c1c8:   /fat-files
>>>> ff84def8:   /iso-9660-files
>>>> ff84eb00:   /bootinfo-loader
>>>> ff8507a0:   /xcoff-loader
>>>> ff8511b8:   /pe-loader
>>>> ff851b90:   /elf-loader
>>>> ff8531c0:   /usb-hid-class
>>>> ff8554d8:   /usb-ms-class
>>>> ff8576a8:   /sbp2-disk
>>>> ff858ac0:   /ata-disk
>>>> ff859cd8:   /atapi-disk
>>>> ff85b348:   /bootpath-search
>>>> ff861b68:   /terminal-emulator
>>>> ff861c00: /psuedo-hid
>>>> ff861c88:   /keyboard
>>>> ff862308:   /mouse
>>>> ff862820: /multiboot
>>>> ff86e7f0: /diagnostics
>>>> ff86e858: /tools-node
>>>> ff8704b8: /rtas
>>>> ff8706b8: /nvram@fff04000
>>>> ff871180: /uni-n@f8000000
>>>> ff8713c8:   /i2c@f8001000
>>>> ff871b10:     /cereal
>>>> ff8721c0: /pci@f0000000
>>>> ff898cd0:   /uni-north-agp@b
>>>> ff898f40:   /ATY,Rage128Ps@10
>>>> ff873268: /pci@f2000000
>>>> ff8742d8:   /pci-bridge@d
>>>> ff876368:     /mac-io@7
>>>> ff8773a0:       /interrupt-controller@40000
>>>> ff877548:       /gpio@50
>>>> ff877630:         /extint-gpio1
>>>> ff8777c8:         /programmer-switch
>>>> ff877900:       /escc-legacy@12000
>>>> ff877af8:         /ch-a@12004
>>>> ff877c78:         /ch-b@12000
>>>> ff877df8:       /escc@13000
>>>> ff878000:         /ch-a@13020
>>>> ff8789a8:         /ch-b@13000
>>>> ff8792c0:       /davbus@14000
>>>> ff879540:         /sound
>>>> ff879c40:       /timer@15000
>>>> ff879da8:       /via-pmu@16000
>>>> ff87ccf0:         /rtc
>>>> ff87d3e0:         /power-mgt
>>>> ff8bf378:           /usb-power-mgt
>>>> ff87d648:       /i2c@18000
>>>> ff87ded8:         /cereal
>>>> ff87e5a0:       /ata-4@1f000
>>>> ff880318:         /disk
>>>> ff8809e8:       /ata-3@20000
>>>> ff882760:         /disk
>>>> ff882da8:       /ata-3@21000
>>>> ff884b20:         /disk
>>>> ff8864c8:     /ethernet@4
>>>> ff888690:     /usb@8
>>>> ff88dd50:     /usb@9
>>>> ff8be3f0:       /hub@1
>>>> ff8be580:         /keyboard@1
>>>> ff893410:     /firewire@a
>>>> ff8752e8: /pci@f4000000
>>>> ff8bb128:   /ethernet@f
>>>
>>> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
>>> issues that broke OS X among other things) and posted it to the
>>> qemu-devel list at
>>> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
>>>
>>> The patchset posted works well for me here, and I suspect will fix the
>>> issues that you've been seeing. Note that you'll also need the separate
>>> OpenBIOS binary mentioned in the link above if you want to try booting
>>> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
>>> since it regresses other images.
>>
>> It looks like you are saying you wish to keep the CUDA device. Mac OS
>> 9 is most
>> likely hard coded to expect via-pmu instead of via-cuda on the mac99
>> target.
>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>> I will still try your patches. Do you have a repo that I could just
>> clone? It is a
>> lot less error prone than patches.

Currently we know that mac99 is a hybrid of several machine types, but
it just so happens that the OSs contain a large enough range of drivers
for the image to work, as they appear to do here.

>From my testing I don't see a problem with CUDA, and while it could be
that via-pmu may help things with OS 9, we need a specific patch to
demonstrate this with instructions that can be independently reproduced.

> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it.
> Unfortunately it still doesn't work ... but hope is still here ;)

If it helps, I've just noticed that the OS 9 patchset also fixes NetBSD
PPC boot (looking at the CUDA driver I suspect it is likely the I2C
parts) so I don't think FreeBSD will be too far off.

>From what I've seen of reports from OpenBSD (e.g.
http://virtuallyfun.superglobalmegacorp.com/2015/07/19/gsoc-bringing-macos-9-to-qemu/),
my first guess would be that a good starting point would be to check to
PCI host bridge properties generated in OpenBIOS.

> Mark, is your complete qemu patch available somewhere? Then I could test
> 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.

I've just pushed the rebased version to
https://github.com/mcayland/qemu/tree/ppc-os9-upstream for people
interested to test further.


ATB,

Mark.

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 11, 2015, at 6:05 PM, Mark Cave-Ayland wrote:

> On 11/11/15 21:32, Andreas Tobler wrote:
> 
>> On 11.11.15 19:55, Programmingkid wrote:
>>> 
>>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>> 
>>>> On 11/11/15 15:15, Programmingkid wrote:
>>>> 
>>>>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my
>>>>> Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA
>>>>> problem. I did use the mac99 target. Here is the error message:
>>>>> 
>>>>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION
>>>>> TYPE AND ERROR
>>>>> 
>>>>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d
>>>>> -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>>>>> 
>>>>> I think there is still something wrong with CUDA. But we might not
>>>>> have to "fix" it. When we use the mac99 target, the PowerMac3,1
>>>>> Macintosh system is what we are trying to emulate. My sources
>>>>> indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is
>>>>> used for ADB communications. Using it only on the BeigeG3 target
>>>>> makes sense.
>>>>> 
>>>>> My sources for the PowerMac3,1 system is this link:
>>>>> http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>>>>> 
>>>>> 
>>>>> and this device tree:
>>>>> 
>>>>> PowerMac G4 device tree
>>>>> 
>>>>> ff839ab8: /cpus
>>>>> ff839ce8:   /PowerPC,G4@0
>>>>> ff83a060:     /l2-cache
>>>>> ff83ab58: /chosen
>>>>> ff83ace8: /memory@0
>>>>> ff83af00: /openprom
>>>>> ff83b008:   /client-services
>>>>> ff83c1a8: /rom@ff800000
>>>>> ff83c330:   /boot-rom@fff00000
>>>>> ff83c4a8:   /macos
>>>>> ff83c528: /options
>>>>> ff83c5a8: /aliases
>>>>> ff83cec8: /packages
>>>>> ff83cf30:   /deblocker
>>>>> ff83d798:   /disk-label
>>>>> ff83e198:   /obp-tftp
>>>>> ff8439f0:   /mac-parts
>>>>> ff844850:   /mac-files
>>>>> ff847540:   /hfs-plus-files
>>>>> ff84c1c8:   /fat-files
>>>>> ff84def8:   /iso-9660-files
>>>>> ff84eb00:   /bootinfo-loader
>>>>> ff8507a0:   /xcoff-loader
>>>>> ff8511b8:   /pe-loader
>>>>> ff851b90:   /elf-loader
>>>>> ff8531c0:   /usb-hid-class
>>>>> ff8554d8:   /usb-ms-class
>>>>> ff8576a8:   /sbp2-disk
>>>>> ff858ac0:   /ata-disk
>>>>> ff859cd8:   /atapi-disk
>>>>> ff85b348:   /bootpath-search
>>>>> ff861b68:   /terminal-emulator
>>>>> ff861c00: /psuedo-hid
>>>>> ff861c88:   /keyboard
>>>>> ff862308:   /mouse
>>>>> ff862820: /multiboot
>>>>> ff86e7f0: /diagnostics
>>>>> ff86e858: /tools-node
>>>>> ff8704b8: /rtas
>>>>> ff8706b8: /nvram@fff04000
>>>>> ff871180: /uni-n@f8000000
>>>>> ff8713c8:   /i2c@f8001000
>>>>> ff871b10:     /cereal
>>>>> ff8721c0: /pci@f0000000
>>>>> ff898cd0:   /uni-north-agp@b
>>>>> ff898f40:   /ATY,Rage128Ps@10
>>>>> ff873268: /pci@f2000000
>>>>> ff8742d8:   /pci-bridge@d
>>>>> ff876368:     /mac-io@7
>>>>> ff8773a0:       /interrupt-controller@40000
>>>>> ff877548:       /gpio@50
>>>>> ff877630:         /extint-gpio1
>>>>> ff8777c8:         /programmer-switch
>>>>> ff877900:       /escc-legacy@12000
>>>>> ff877af8:         /ch-a@12004
>>>>> ff877c78:         /ch-b@12000
>>>>> ff877df8:       /escc@13000
>>>>> ff878000:         /ch-a@13020
>>>>> ff8789a8:         /ch-b@13000
>>>>> ff8792c0:       /davbus@14000
>>>>> ff879540:         /sound
>>>>> ff879c40:       /timer@15000
>>>>> ff879da8:       /via-pmu@16000
>>>>> ff87ccf0:         /rtc
>>>>> ff87d3e0:         /power-mgt
>>>>> ff8bf378:           /usb-power-mgt
>>>>> ff87d648:       /i2c@18000
>>>>> ff87ded8:         /cereal
>>>>> ff87e5a0:       /ata-4@1f000
>>>>> ff880318:         /disk
>>>>> ff8809e8:       /ata-3@20000
>>>>> ff882760:         /disk
>>>>> ff882da8:       /ata-3@21000
>>>>> ff884b20:         /disk
>>>>> ff8864c8:     /ethernet@4
>>>>> ff888690:     /usb@8
>>>>> ff88dd50:     /usb@9
>>>>> ff8be3f0:       /hub@1
>>>>> ff8be580:         /keyboard@1
>>>>> ff893410:     /firewire@a
>>>>> ff8752e8: /pci@f4000000
>>>>> ff8bb128:   /ethernet@f
>>>> 
>>>> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
>>>> issues that broke OS X among other things) and posted it to the
>>>> qemu-devel list at
>>>> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
>>>> 
>>>> The patchset posted works well for me here, and I suspect will fix the
>>>> issues that you've been seeing. Note that you'll also need the separate
>>>> OpenBIOS binary mentioned in the link above if you want to try booting
>>>> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
>>>> since it regresses other images.
>>> 
>>> It looks like you are saying you wish to keep the CUDA device. Mac OS
>>> 9 is most
>>> likely hard coded to expect via-pmu instead of via-cuda on the mac99
>>> target.
>>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>>> I will still try your patches. Do you have a repo that I could just
>>> clone? It is a
>>> lot less error prone than patches.
> 
> Currently we know that mac99 is a hybrid of several machine types, but
> it just so happens that the OSs contain a large enough range of drivers
> for the image to work, as they appear to do here.

Just checked this myself. Mac OS 9 does boot consistently to the "Mac OS
9" startup screen, so you do have a point. I'm surprised. 

> 
> From my testing I don't see a problem with CUDA, and while it could be
> that via-pmu may help things with OS 9, we need a specific patch to
> demonstrate this with instructions that can be independently reproduced.

I will see what I can do.

>> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it.
>> Unfortunately it still doesn't work ... but hope is still here ;)
> 
> If it helps, I've just noticed that the OS 9 patchset also fixes NetBSD
> PPC boot (looking at the CUDA driver I suspect it is likely the I2C
> parts) so I don't think FreeBSD will be too far off.
> 
> From what I've seen of reports from OpenBSD (e.g.
> http://virtuallyfun.superglobalmegacorp.com/2015/07/19/gsoc-bringing-macos-9-to-qemu/),
> my first guess would be that a good starting point would be to check to
> PCI host bridge properties generated in OpenBIOS.
> 
>> Mark, is your complete qemu patch available somewhere? Then I could test
>> 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.
> 
> I've just pushed the rebased version to
> https://github.com/mcayland/qemu/tree/ppc-os9-upstream for people
> interested to test further.

I had just  spent a lot of tedious effort copying and pasting all 13 patches
from the link you sent me. Thank goodness for the git repo. 

Just to note, your original set of patches did make a lot of progess. Only 
patch 8 had problems that required it to be applied by hand. I applied them
to QEMU 2.4.1 on Mac OS 10.6. 

Will start testing out the new version of patches. 

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Programmingkid]

On Nov 11, 2015, at 6:05 PM, Mark Cave-Ayland wrote:

> On 11/11/15 21:32, Andreas Tobler wrote:
> 
>> On 11.11.15 19:55, Programmingkid wrote:
>>> 
>>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>> 
>>>> On 11/11/15 15:15, Programmingkid wrote:
>>>> 
>>>>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my
>>>>> Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA
>>>>> problem. I did use the mac99 target. Here is the error message:
>>>>> 
>>>>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION
>>>>> TYPE AND ERROR
>>>>> 
>>>>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d
>>>>> -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>>>>> 
>>>>> I think there is still something wrong with CUDA. But we might not
>>>>> have to "fix" it. When we use the mac99 target, the PowerMac3,1
>>>>> Macintosh system is what we are trying to emulate. My sources
>>>>> indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is
>>>>> used for ADB communications. Using it only on the BeigeG3 target
>>>>> makes sense.
>>>>> 
>>>>> My sources for the PowerMac3,1 system is this link:
>>>>> http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>>>>> 
>>>>> 
>>>>> and this device tree:
>>>>> 
>>>>> PowerMac G4 device tree
>>>>> 
>>>>> ff839ab8: /cpus
>>>>> ff839ce8:   /PowerPC,G4@0
>>>>> ff83a060:     /l2-cache
>>>>> ff83ab58: /chosen
>>>>> ff83ace8: /memory@0
>>>>> ff83af00: /openprom
>>>>> ff83b008:   /client-services
>>>>> ff83c1a8: /rom@ff800000
>>>>> ff83c330:   /boot-rom@fff00000
>>>>> ff83c4a8:   /macos
>>>>> ff83c528: /options
>>>>> ff83c5a8: /aliases
>>>>> ff83cec8: /packages
>>>>> ff83cf30:   /deblocker
>>>>> ff83d798:   /disk-label
>>>>> ff83e198:   /obp-tftp
>>>>> ff8439f0:   /mac-parts
>>>>> ff844850:   /mac-files
>>>>> ff847540:   /hfs-plus-files
>>>>> ff84c1c8:   /fat-files
>>>>> ff84def8:   /iso-9660-files
>>>>> ff84eb00:   /bootinfo-loader
>>>>> ff8507a0:   /xcoff-loader
>>>>> ff8511b8:   /pe-loader
>>>>> ff851b90:   /elf-loader
>>>>> ff8531c0:   /usb-hid-class
>>>>> ff8554d8:   /usb-ms-class
>>>>> ff8576a8:   /sbp2-disk
>>>>> ff858ac0:   /ata-disk
>>>>> ff859cd8:   /atapi-disk
>>>>> ff85b348:   /bootpath-search
>>>>> ff861b68:   /terminal-emulator
>>>>> ff861c00: /psuedo-hid
>>>>> ff861c88:   /keyboard
>>>>> ff862308:   /mouse
>>>>> ff862820: /multiboot
>>>>> ff86e7f0: /diagnostics
>>>>> ff86e858: /tools-node
>>>>> ff8704b8: /rtas
>>>>> ff8706b8: /nvram@fff04000
>>>>> ff871180: /uni-n@f8000000
>>>>> ff8713c8:   /i2c@f8001000
>>>>> ff871b10:     /cereal
>>>>> ff8721c0: /pci@f0000000
>>>>> ff898cd0:   /uni-north-agp@b
>>>>> ff898f40:   /ATY,Rage128Ps@10
>>>>> ff873268: /pci@f2000000
>>>>> ff8742d8:   /pci-bridge@d
>>>>> ff876368:     /mac-io@7
>>>>> ff8773a0:       /interrupt-controller@40000
>>>>> ff877548:       /gpio@50
>>>>> ff877630:         /extint-gpio1
>>>>> ff8777c8:         /programmer-switch
>>>>> ff877900:       /escc-legacy@12000
>>>>> ff877af8:         /ch-a@12004
>>>>> ff877c78:         /ch-b@12000
>>>>> ff877df8:       /escc@13000
>>>>> ff878000:         /ch-a@13020
>>>>> ff8789a8:         /ch-b@13000
>>>>> ff8792c0:       /davbus@14000
>>>>> ff879540:         /sound
>>>>> ff879c40:       /timer@15000
>>>>> ff879da8:       /via-pmu@16000
>>>>> ff87ccf0:         /rtc
>>>>> ff87d3e0:         /power-mgt
>>>>> ff8bf378:           /usb-power-mgt
>>>>> ff87d648:       /i2c@18000
>>>>> ff87ded8:         /cereal
>>>>> ff87e5a0:       /ata-4@1f000
>>>>> ff880318:         /disk
>>>>> ff8809e8:       /ata-3@20000
>>>>> ff882760:         /disk
>>>>> ff882da8:       /ata-3@21000
>>>>> ff884b20:         /disk
>>>>> ff8864c8:     /ethernet@4
>>>>> ff888690:     /usb@8
>>>>> ff88dd50:     /usb@9
>>>>> ff8be3f0:       /hub@1
>>>>> ff8be580:         /keyboard@1
>>>>> ff893410:     /firewire@a
>>>>> ff8752e8: /pci@f4000000
>>>>> ff8bb128:   /ethernet@f
>>>> 
>>>> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
>>>> issues that broke OS X among other things) and posted it to the
>>>> qemu-devel list at
>>>> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
>>>> 
>>>> The patchset posted works well for me here, and I suspect will fix the
>>>> issues that you've been seeing. Note that you'll also need the separate
>>>> OpenBIOS binary mentioned in the link above if you want to try booting
>>>> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
>>>> since it regresses other images.
>>> 
>>> It looks like you are saying you wish to keep the CUDA device. Mac OS
>>> 9 is most
>>> likely hard coded to expect via-pmu instead of via-cuda on the mac99
>>> target.
>>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>>> I will still try your patches. Do you have a repo that I could just
>>> clone? It is a
>>> lot less error prone than patches.
> 
> Currently we know that mac99 is a hybrid of several machine types, but
> it just so happens that the OSs contain a large enough range of drivers
> for the image to work, as they appear to do here.
> 
> From my testing I don't see a problem with CUDA, and while it could be
> that via-pmu may help things with OS 9, we need a specific patch to
> demonstrate this with instructions that can be independently reproduced.
> 
>> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it.
>> Unfortunately it still doesn't work ... but hope is still here ;)
> 
> If it helps, I've just noticed that the OS 9 patchset also fixes NetBSD
> PPC boot (looking at the CUDA driver I suspect it is likely the I2C
> parts) so I don't think FreeBSD will be too far off.
> 
> From what I've seen of reports from OpenBSD (e.g.
> http://virtuallyfun.superglobalmegacorp.com/2015/07/19/gsoc-bringing-macos-9-to-qemu/),
> my first guess would be that a good starting point would be to check to
> PCI host bridge properties generated in OpenBIOS.
> 
>> Mark, is your complete qemu patch available somewhere? Then I could test
>> 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.
> 
> I've just pushed the rebased version to
> https://github.com/mcayland/qemu/tree/ppc-os9-upstream for people
> interested to test further.

I think I cloned your repo correctly. When I did a 'git log', the first patch was this one:

commit 8aeea0670f83c93e6b9716598123fee98282610e
Author: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Date:   Fri Oct 23 11:08:53 2015 +0100

    cuda.c: add delay to setting of SR_INT bit

Are the version 2 of your patches suppose to be in this repo?

Re: [Qemu-devel] [OpenBIOS] CUDA has problems with Mac OS 10.4

[Mark Cave-Ayland]

On 12/11/15 00:42, Programmingkid wrote:

> On Nov 11, 2015, at 6:05 PM, Mark Cave-Ayland wrote:
> 
>> On 11/11/15 21:32, Andreas Tobler wrote:
>>
>>> On 11.11.15 19:55, Programmingkid wrote:
>>>>
>>>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>>>
>>>>> On 11/11/15 15:15, Programmingkid wrote:
>>>>>
>>>>>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my
>>>>>> Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA
>>>>>> problem. I did use the mac99 target. Here is the error message:
>>>>>>
>>>>>> panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION
>>>>>> TYPE AND ERROR
>>>>>>
>>>>>> This is the command I used: ./ppc-softmmu/qemu-system-ppc -boot d
>>>>>> -cdrom ~/tiger.iso  -prom-env boot-args=-v -usb -M mac99
>>>>>>
>>>>>> I think there is still something wrong with CUDA. But we might not
>>>>>> have to "fix" it. When we use the mac99 target, the PowerMac3,1
>>>>>> Macintosh system is what we are trying to emulate. My sources
>>>>>> indicate that the PowerMac3,1 doesn't have a CUDA chip. This chip is
>>>>>> used for ADB communications. Using it only on the BeigeG3 target
>>>>>> makes sense.
>>>>>>
>>>>>> My sources for the PowerMac3,1 system is this link:
>>>>>> http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html
>>>>>>
>>>>>>
>>>>>> and this device tree:
>>>>>>
>>>>>> PowerMac G4 device tree
>>>>>>
>>>>>> ff839ab8: /cpus
>>>>>> ff839ce8:   /PowerPC,G4@0
>>>>>> ff83a060:     /l2-cache
>>>>>> ff83ab58: /chosen
>>>>>> ff83ace8: /memory@0
>>>>>> ff83af00: /openprom
>>>>>> ff83b008:   /client-services
>>>>>> ff83c1a8: /rom@ff800000
>>>>>> ff83c330:   /boot-rom@fff00000
>>>>>> ff83c4a8:   /macos
>>>>>> ff83c528: /options
>>>>>> ff83c5a8: /aliases
>>>>>> ff83cec8: /packages
>>>>>> ff83cf30:   /deblocker
>>>>>> ff83d798:   /disk-label
>>>>>> ff83e198:   /obp-tftp
>>>>>> ff8439f0:   /mac-parts
>>>>>> ff844850:   /mac-files
>>>>>> ff847540:   /hfs-plus-files
>>>>>> ff84c1c8:   /fat-files
>>>>>> ff84def8:   /iso-9660-files
>>>>>> ff84eb00:   /bootinfo-loader
>>>>>> ff8507a0:   /xcoff-loader
>>>>>> ff8511b8:   /pe-loader
>>>>>> ff851b90:   /elf-loader
>>>>>> ff8531c0:   /usb-hid-class
>>>>>> ff8554d8:   /usb-ms-class
>>>>>> ff8576a8:   /sbp2-disk
>>>>>> ff858ac0:   /ata-disk
>>>>>> ff859cd8:   /atapi-disk
>>>>>> ff85b348:   /bootpath-search
>>>>>> ff861b68:   /terminal-emulator
>>>>>> ff861c00: /psuedo-hid
>>>>>> ff861c88:   /keyboard
>>>>>> ff862308:   /mouse
>>>>>> ff862820: /multiboot
>>>>>> ff86e7f0: /diagnostics
>>>>>> ff86e858: /tools-node
>>>>>> ff8704b8: /rtas
>>>>>> ff8706b8: /nvram@fff04000
>>>>>> ff871180: /uni-n@f8000000
>>>>>> ff8713c8:   /i2c@f8001000
>>>>>> ff871b10:     /cereal
>>>>>> ff8721c0: /pci@f0000000
>>>>>> ff898cd0:   /uni-north-agp@b
>>>>>> ff898f40:   /ATY,Rage128Ps@10
>>>>>> ff873268: /pci@f2000000
>>>>>> ff8742d8:   /pci-bridge@d
>>>>>> ff876368:     /mac-io@7
>>>>>> ff8773a0:       /interrupt-controller@40000
>>>>>> ff877548:       /gpio@50
>>>>>> ff877630:         /extint-gpio1
>>>>>> ff8777c8:         /programmer-switch
>>>>>> ff877900:       /escc-legacy@12000
>>>>>> ff877af8:         /ch-a@12004
>>>>>> ff877c78:         /ch-b@12000
>>>>>> ff877df8:       /escc@13000
>>>>>> ff878000:         /ch-a@13020
>>>>>> ff8789a8:         /ch-b@13000
>>>>>> ff8792c0:       /davbus@14000
>>>>>> ff879540:         /sound
>>>>>> ff879c40:       /timer@15000
>>>>>> ff879da8:       /via-pmu@16000
>>>>>> ff87ccf0:         /rtc
>>>>>> ff87d3e0:         /power-mgt
>>>>>> ff8bf378:           /usb-power-mgt
>>>>>> ff87d648:       /i2c@18000
>>>>>> ff87ded8:         /cereal
>>>>>> ff87e5a0:       /ata-4@1f000
>>>>>> ff880318:         /disk
>>>>>> ff8809e8:       /ata-3@20000
>>>>>> ff882760:         /disk
>>>>>> ff882da8:       /ata-3@21000
>>>>>> ff884b20:         /disk
>>>>>> ff8864c8:     /ethernet@4
>>>>>> ff888690:     /usb@8
>>>>>> ff88dd50:     /usb@9
>>>>>> ff8be3f0:       /hub@1
>>>>>> ff8be580:         /keyboard@1
>>>>>> ff893410:     /firewire@a
>>>>>> ff8752e8: /pci@f4000000
>>>>>> ff8bb128:   /ethernet@f
>>>>>
>>>>> I've done quite a bit of work on Cormac's tree (primarily to fix CUDA
>>>>> issues that broke OS X among other things) and posted it to the
>>>>> qemu-devel list at
>>>>> https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05556.html.
>>>>>
>>>>> The patchset posted works well for me here, and I suspect will fix the
>>>>> issues that you've been seeing. Note that you'll also need the separate
>>>>> OpenBIOS binary mentioned in the link above if you want to try booting
>>>>> OS 9 since one of the OpenBIOS patches hasn't been applied to trunk
>>>>> since it regresses other images.
>>>>
>>>> It looks like you are saying you wish to keep the CUDA device. Mac OS
>>>> 9 is most
>>>> likely hard coded to expect via-pmu instead of via-cuda on the mac99
>>>> target.
>>>> Moving on to via-pmu might make QEMU more compatible with Mac OS 9.
>>>> I will still try your patches. Do you have a repo that I could just
>>>> clone? It is a
>>>> lot less error prone than patches.
>>
>> Currently we know that mac99 is a hybrid of several machine types, but
>> it just so happens that the OSs contain a large enough range of drivers
>> for the image to work, as they appear to do here.
>>
>> From my testing I don't see a problem with CUDA, and while it could be
>> that via-pmu may help things with OS 9, we need a specific patch to
>> demonstrate this with instructions that can be independently reproduced.
>>
>>> I'd like to keep the CUDA too, FreeBSD PowerPC (32-bit) relies on it.
>>> Unfortunately it still doesn't work ... but hope is still here ;)
>>
>> If it helps, I've just noticed that the OS 9 patchset also fixes NetBSD
>> PPC boot (looking at the CUDA driver I suspect it is likely the I2C
>> parts) so I don't think FreeBSD will be too far off.
>>
>> From what I've seen of reports from OpenBSD (e.g.
>> http://virtuallyfun.superglobalmegacorp.com/2015/07/19/gsoc-bringing-macos-9-to-qemu/),
>> my first guess would be that a good starting point would be to check to
>> PCI host bridge properties generated in OpenBIOS.
>>
>>> Mark, is your complete qemu patch available somewhere? Then I could test
>>> 32-bit PowerPC on FreeBSD which still hangs on adb... up to now.
>>
>> I've just pushed the rebased version to
>> https://github.com/mcayland/qemu/tree/ppc-os9-upstream for people
>> interested to test further.
> 
> I think I cloned your repo correctly. When I did a 'git log', the first patch was this one:
> 
> commit 8aeea0670f83c93e6b9716598123fee98282610e
> Author: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> Date:   Fri Oct 23 11:08:53 2015 +0100
> 
>     cuda.c: add delay to setting of SR_INT bit
> 
> Are the version 2 of your patches suppose to be in this repo?

V2 was applied to master, so you should now be good with a standard QEMU
checkout and the custom OpenBIOS binary included in the cover letter.


ATB,

Mark.