From: Michel <da...@re...> - 2000-11-20 19:03:57
|
Alan Buxey wrote: > #define APUS_PROGRESS(_a) \ > lis r3,0xfff0; > \ > > ori r3,r3,0xeff0; \ > > lis r4,0x1234; \ > > ori r4,r4,(_a); \ > > stw r4,0x0(r3); \ > > dcbf 0,r3; \ > > sync; \ > > isync > > > > > > So it's 0xeff01234 . > > just to confirm.....if I use a tool like MemoryX under AmigaOS, I will > find the number from APUS_PROGRESS calls at memory location > $eff01234 - correct, or is the memory mapping difference under > Linux/AmigaOS going to mean the info is actually at some other location? APUS_PROGRESS only makes sense when the MMU is off, which means all addresses are physical, like in AmigaOS. So it's 0xeff01234 . AFAIR when the MMU is turned on, things should be more or less set up for dmesg debugging to work. BTW Alan, what about committing your code now so others can join your experiments? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project |