Sure, but even though Peter knows how to use DAs, he unfortunately can't stop a 26bit-mode processor and operating system putting flags in the most significant bits of the program counter. You can't demand a particular address from the OS as a userspace program.
If you have code executing in high memory areas, where the virtual address requires bits 26-31, this will clash with the status flags. Execution will jump wildly to the wrong addresses, and the browser will crash - frustrating the user.
We've seen this before when the Select Filer's DA is high up in memory and its virtual address would clash with the flags bits in R1 of OS_HeapSort. Users with lots of DAs and 128MB+ of RAM would see this. Because the A9home's 32bit-mode cpu and OS can safely execute code high up in memory, I presume this is why Peter hasn't ruled out an A9home port.
I've emailed Peter, but he refused to confirm what I've said or explain why the Firefox will be Iyonix-only (unless an A9home por comes later on). This is because he feels the article headline and sub-headline are inaccurate, and won't talk unless I correct it.
He said: "Both these statements made in the head and subhead are inaccurate, as evidenced by wording on the actual page. When drobe puts more stock in accuracy, above wording simply designed to get a reaction (including, but not limited to the quotes you have from me which appear on the frontpage), I'll be happy to answer your questions further."