80386 Early Start Memory Access
nand2mario.github.io
80386 Early Start Memory Access
1–10 of 10 posts
Re: 80386 Early Start Memory Access
#2Re: 80386 Early Start Memory Access
#3Re: 80386 Early Start Memory Access
#4I wonder what exactly stops windows from booting
Re: 80386 Early Start Memory Access
#5Re: 80386 Early Start Memory Access
#6I wonder how the logic worked in the previous version without early start. Was it relying upon the address calculation speed to settle the outputs really quickly? Was it inserting or stretching cycles?
Re: 80386 Early Start Memory Access
#7I wonder what exactly stops windows from booting
Re: 80386 Early Start Memory Access
#8Re: 80386 Early Start Memory Access
#9I wonder how the logic worked in the previous version without early start. Was it relying upon the address calculation speed to settle the outputs really quickly? Was it inserting or stretching cycles?
The memory pipeline just starts one cycle later than now. Effective address is calculated during the first cycle of the instruction. The microcode then waits for it to finish with the DLY (delay) micro-op, which releases one cycle later.