[Windows Phone 7 Development and Hacking] ntonhd2:
Cotulla,

thinking of going this way (first 3):

http://www.openfirmware.info/Building_OFW_for_ARM

http://www.coreboot.org/SeaBIOS

http://www.coreboot.org/Payloads

also interesting here:

http://www.openfirmware.info/BeginAgain

http://www.coreboot.org/Etherboot

http://rom-o-matic.net/gpxe/gpxe-1.0.1/contrib/rom-o-matic/ (any these be made magldr compatible :D ?)

Need to hack which sections of the memory and IO map are probed for devices (disabling support for finding anything like non-supported-SuperIO chips and legacy controllers, buses, pci, ACPI power???, because these will cause a BlueScreenOfDeath without the bluescreen= just DEATH.)

I will hack which parts of the PCI bus space are scanned and need to look at hd2 buses for support here instead maybe eventually bring in ROOT device. PCI bus scan 0.00.1 or 0.00.2 will cause DEATH.

DEATH!

You do not need a BIOS I realize this as only osloader/NTLDR requires BIOS services and not many: like ones you mentioned Cotulla above.... LDR gets into protected mode quickly. But I will create a new loader to get the kernel, HAL, disk driver, registry and the everything else including all appropriate virtual address space mappings set up....

Problem with NT is although the kernel needs and uses no BIOS services it will attempt accesses to devices via the (non-exsitent-on-arm-hd2) PCI bus space (see HAL ROOT object/device also). so lot of hacks here will be required obviously.

It is a LOT easier fro my perspective to strap up in a closest to PC environment though and if possible would like to have a go at simulating bios using KEXEC type method of kernel>kernel jump off... so, all this just ultimately means:

spl>magldr>linux>coreboot>PAYLOAD(SeaBIOS)>MYCODE... or, if possible, preferably CE7 or WP7 then PAYLOAD & MYCODE!

PXE over USB would be fun & maybe linkable with KITL :p but keeping on track:

Magldr,Linux= SPL, Magldr, onto zimage/initrd made with COREBOOT and SeaBIOS full-BIOS-service PAYLOAD. once this is done im good: so hopefully can start there. I will go completely CLEAN but wouldnt mind trying to get ARMLLB as meant to be running after this just to see how it goes then pass it onto a hackedup osloader.exe which working@ now.

or

Magldr,WPH/CE7= except for support for platform-builder to debug etc, rebuild the imgfs, my code as NK.EXE

Maybe try both :D?

I know this is more *COMPLEX* but it works a lot better from my end :). out of WPH/CE7 (mycode@nk.exe with KITL for PlatformBuilder) or COREBOOT zimage>SeaBios>Mycode, which is more doable and what issues are there you think?

Can include full KITL, Debug, USB support from day zero- PlatformBuilder maybe?

The whole NK.EXE or COREBOOT(zimage) methods can be *removed* as project comes to an end: it is more about the way I am seeing the big picture and where we are at here and need for KITL or some kind of usb or eth or serial debug.

Worth a try even if a big challenge :). If anyone can do it you can ;). I will have no problem once at this point- out of malgdr and got OpenFirmware setup running. That first link at top look doable for QD-ARM (OFW for ARM)? Must TRY coreboot :). Either way it looks very doable now: with this payload up and running I will be able to and will create HD2 running full native hd2 ARM NTOSKRNL.EXE!