-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: |> Wow no it's news to me. Qi treats steppingstone as always accessible. |> that would definitely kill it since a bunch of low level stuff like |> strcpy() is linked to be in steppingstone even in "phase 2". | | Ah, then we have it. Yeah, Samsung were indeed too cheap to latch | those OM lines. | | This is also something that gets in the way of interrupts. I fixed | this once for u-boot by remapping the 0x0... address range: | remap-vec.patch, commit 2df49277c9a8c0b2b7c57597162578ef5de80861
Thanks for the pointer, I just found it here: http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=2df49277c9a8c0b2b7c57597162578ef5de80861 It appears there is a simpler solution to this, despite what the docs claim in fact the steppingstone is actually permanently mapped at 0x40000000 regardless of OM[] state. It's only the incarnation of it down at 0x0 that is swapped in and out according to OM[]. I found that changing the linker script to get us up to the 0x40000000 copy fixes the AUX thing in GTA02 qi. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkv4qMACgkQOjLpvpq7dMoqyACeJ0sB5t+P+eeaCn5QP+maagej QVYAnjihx5RXTokIgCFcBJuvLwh7ABvG =c7Pe -----END PGP SIGNATURE-----
