I'm using QDIA6T MB based on vt8601/vt82c686. Now I can boot it using DOC IPL. I can copy linuxbios from DOC to RAM at 0x8000:0. But when linuxbios executed "data32 ljmp $ROM_CODE_SEG, $__protected_start" statement. The MB halted. help! zhu
__________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail
* zhu shi song zhushisongzhu@yahoo.com [040819 15:42]:
I'm using QDIA6T MB based on vt8601/vt82c686. Now I can boot it using DOC IPL. I can copy linuxbios from DOC to RAM at 0x8000:0. But when linuxbios executed "data32 ljmp $ROM_CODE_SEG, $__protected_start" statement. The MB halted. help! zhu
Seems your RAM is not initialized correctly?! Any room for debugging output in docipl?
Stefan
I have made one romimage , it can copy linuxbios into RAM and execute it from there. That means raminit.inc init sdram ok. I have ported the init code in raminit.inc to ipl.S. The only difference of them is that ipl.S init sdram in real mode and raminit.inc init sdram in protected mode. After IPL.s initialization of sdram, IPL.s can copy code from doc to RAM at 0x8000:0000 and execute some statements. That means at least sdram can be read and written. Should I enter proteced mode before initializing sdram? Who has the experience of initializing sdram correctly in real mode using vt8601? tks zhu
--- Stefan Reinauer stepan@openbios.org wrote:
- zhu shi song zhushisongzhu@yahoo.com [040819
15:42]:
I'm using QDIA6T MB based on vt8601/vt82c686. Now
I
can boot it using DOC IPL. I can copy linuxbios
from
DOC to RAM at 0x8000:0. But when linuxbios
executed
"data32 ljmp $ROM_CODE_SEG,
$__protected_start"
statement. The MB halted. help! zhu
Seems your RAM is not initialized correctly?! Any room for debugging output in docipl?
Stefan
_______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush
-
Stefan Reinauer -
zhu shi song