Hi!
On Fri, Nov 26, 2021 at 09:34:44AM +0100, Cédric Le Goater wrote:
> On 11/25/21 10:38, Segher Boessenkool wrote:
> >On Thu, Nov 25, 2021 at 01:45:00AM +0100, BALATON Zoltan wrote:
> >>As for guests, those running on the said PowerMac G4 should have support
> >>for
Hi!
On Thu, Nov 25, 2021 at 01:45:00AM +0100, BALATON Zoltan wrote:
> As for guests, those running on the said PowerMac G4 should have support
> for these CPUs so maybe you can try some Mac OS X versions (or maybe
OSX uses hardware pagetables.
> MorphOS but that is not the best for debugging a
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/pmu9
Your code can change MSR[IP]; there is also a strapping pin that is
sampled on HRESET (and copied to MSR[IP]).
Wouldn't this mean that when the reset is issued by hardware, MSR[IP]
is always 1 (to boot from ROM) but with software reset it can take
software defined values?
Yes, that is what i
It is explained in [e300CORERM] at chapters 5.2.3, 5.5.1.1 and 8.3.3.
Clearly, the vector offset is 0x100 and the exception prefix can
be 0 or
0xFFF0, depending of the MSR[IP] bit.
So, yes, I'm sure the value of hreset_vector must be 0x100.
But hreset_excp_prefix can change. It could be an
970 may be a bad example in that it can't actually bring itself up --
it requires an external controller to configure it at power-up. So
whatever the external controller programs into the PC is where it
starts.
970 always starts at HIOR|0x00100.
I don't see any mention of an initial PC value i
When I read Avi's TODO, I basically thought about getting rid of the
long command lines I had to store in scripts. I wanted to write that
command line once, and then forgetting about it, until I needed to
change it.
Instead of inventing great and wonderfully complicated schemes, the
most sensibl
