[OpenBIOS] Back at it again( PCI Passthrough )
Jd Lyons
lyons_dj at yahoo.com
Sat May 12 05:24:33 CEST 2018
Yes, along with some of the other config* words:
new-token 0xa00
b(defer)
new-token 0xa01
b(defer)
new-token 0xa02
b(defer)
new-token 0xa03
b(:)
my-space
or
b(") ( len=0x12 [18 bytes] )
" assigned-addresses"
get-my-property
invert
b?branch 0x0033 ( =dec 51)
rot
>r
b(<mark)
dup
b?branch 0x0029 ( =dec 41)
decode-phys
b(lit) 0xff
and
r@
b(lit) 0xff
and
=
b?branch 0x000a ( =dec 10)
2swap
2drop
r>
exit
bbranch 0x0005 ()
b(>resolve)
2drop
b(>resolve)
decode-int
drop
decode-int
drop
bbranch 0xffd8 ( =dec -40)
b(>resolve)
2drop
r>
b(>resolve)
>r
my-address
r>
b(;)
new-token 0xa04
b(:)
b(") ( len=6 )
" map-in"
$call-parent
b(;)
new-token 0xa05
b(:)
b(") ( len=7 )
" map-out"
$call-parent
b(;)
new-token 0xa06
b(:)
b(") ( len=9 )
" config-w@"
$call-parent
b(;)
new-token 0xa07
b(:)
b(") ( len=9 )
" config-w!"
$call-parent
b(;)
new-token 0xa08
b(:)
b(") ( len=9 )
" config-l@"
$call-parent
b(;)
new-token 0xa09
b(:)
b(") ( len=9 )
" config-l!"
$call-parent
b(;)
new-token 0xa0a
b(:)
(unnamed-fcode) [0x9a3]
+
rb@
b(;)
new-token 0xa0b
b(:)
(unnamed-fcode) [0x9a3]
+
rb!
b(;)
new-token 0xa0c
b(:)
swap
(unnamed-fcode) [0xa0b]
b(;)
new-token 0xa0d
b(:)
(unnamed-fcode) [0x9a3]
+
rl@
b(;)
new-token 0xa0e
b(:)
(unnamed-fcode) [0x9a3]
+
rl!
b(;)
new-token 0xa0f
b(:)
(unnamed-fcode) [0x9a3]
+
rl!
b(;)
> On May 11, 2018, at 11:31 AM, Mark Cave-Ayland <mark.cave-ayland at ilande.co.uk> wrote:
>
> On 11/05/18 12:46, Jd Lyons via OpenBIOS wrote:
>
>> Thanks Mark, now I’m down to stepping through the ddf word.
>> Are map-in and map-out implemented in forth?
>> Seems the nVidia roms use them, as most option roms would.
>
> From memory PCI map-in is supported, map-out isn't but could be implemented fairly easily. Do you see that in the NVidia ROM image?
>
>
> ATB,
>
> Mark.
More information about the OpenBIOS
mailing list