On Sun, 21 Jul 2019, Mark Cave-Ayland wrote:
Finally one other thing: I'm finding this thread really hard to follow - too much information is spread across too many emails, and the subject line isn't really helping me understand what topic we're following or where I can find related information. May I suggest that it makes sense to break this down into a series of smaller, more concise threads?
As a reminder here's what the word from FCode ROM is trying to do that I'm trying to get working (it works with SLOF):
8552: new-token ati-map-io \ 0x926 8555: b(:) 8556: my-address 8558: b(lit) 0x1000014 8563: my-space 8565: + 8566: const_0x100 8568: b(") ( len=6 ) " map-in" 8576: ati-call-parent 8578: b(to) var_mapped_io_base 8581: b(lit) 0x4 8586: my-space 8588: + 8589: dup 8590: b(") ( len=9 ) " config-b@" 8601: ati-call-parent 8603: 1 8604: or 8605: swap 8606: b(") ( len=9 ) " config-b!" 8617: ati-call-parent 8619: b(;)
This would map BAR1 and enable IO access (Command reg bit 0) in config space if I got that right. So we need map-in and config-b[!@] words for this. Currently trying to get past map-in.
Regards, BALATON Zoltan