Actually the irqtable entries is only for peer root pci bus scan when mptable is used.
So you need to make sure mptable is right, and put entries for hypertransport chain other than on bus0.
YH
________________________________
From: vincente.tsou@gmail.com [mailto:vincente.tsou@gmail.com] On Behalf Of Vincente Tsou Sent: Tuesday, June 20, 2006 7:05 PM To: Lu, Yinghai Cc: Stefan Reinauer; linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] New guy in LinuxBios
Dear YH,
excuse me, how about the irq_tables.c?
should I modify it like tyan/s2882 did.
printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 }; pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); pirq_info++; slot_num++;
2006/6/20, Lu, Yinghai yinghai.lu@amd.com:
You need to update the entries at mptable.c for your slots or onboard pci device.
YH
Dear YH,
got it.
Thanks for the information and your help.
2006/6/21, Lu, Yinghai yinghai.lu@amd.com:
Actually the irqtable entries is only for peer root pci bus scan when mptable is used.
So you need to make sure mptable is right, and put entries for hypertransport chain other than on bus0.
YH
*From:* vincente.tsou@gmail.com [mailto:vincente.tsou@gmail.com] *On Behalf Of *Vincente Tsou *Sent:* Tuesday, June 20, 2006 7:05 PM *To:* Lu, Yinghai *Cc:* Stefan Reinauer; linuxbios@linuxbios.org
*Subject:* Re: [LinuxBIOS] New guy in LinuxBios
Dear YH,
excuse me, how about the irq_tables.c?
should I modify it like tyan/s2882 did.
printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 }; pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, 0x2,
0xdef8, 0, 0, 0, 0, 0, 0); pirq_info++; slot_num++;
2006/6/20, Lu, Yinghai yinghai.lu@amd.com:
You need to update the entries at mptable.c for your slots or onboard pci device.
YH
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
Hi YH,
Thanks again for your help.
Now I can active all devices in my LinuxBios, it almost done except VGA function.
I appended a 36k VGA option rom to LinuxBios, and enable Options about VGA.
And I got the halt_sys message:
PCI: 04:02.0 init rom address for PCI: 04:02.0 = fff80000 copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes entering emulator halt_sys: file /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, line 4387 PCI: 01:04.0 init
then, I can see something output, but the output is like snow screen and I can't read anything. I think it is working in the wrong mode.
When I made a blind type 'root' and password, I can login the Linux, and then the screen became clear. (work fine)
I wonder how to fix the problem? is the halt_sys message normal ?
I also got another question, could it possible boot to MS-DOS floppy/USB disk. The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to support it?
2006/6/21, Vincente Tsou vincentetsou@nexcom.com.tw:
Dear YH,
got it.
Thanks for the information and your help.
2006/6/21, Lu, Yinghai yinghai.lu@amd.com:
Actually the irqtable entries is only for peer root pci bus scan when mptable is used.
So you need to make sure mptable is right, and put entries for hypertransport chain other than on bus0.
YH
*From:* vincente.tsou@gmail.com [mailto:vincente.tsou@gmail.com] *On Behalf Of *Vincente Tsou *Sent:* Tuesday, June 20, 2006 7:05 PM *To:* Lu, Yinghai *Cc: *Stefan Reinauer; linuxbios@linuxbios.org
*Subject:* Re: [LinuxBIOS] New guy in LinuxBios
Dear YH,
excuse me, how about the irq_tables.c?
should I modify it like tyan/s2882 did.
printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0
}; pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); pirq_info++; slot_num++;
2006/6/20, Lu, Yinghai <yinghai.lu@amd.com >:
You need to update the entries at mptable.c for your slots or onboard pci device.
YH
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
the snow screen only happened when I was debugging the onboard VGA support. So i move the CPU init before other pci device init call. That is something related to mtrr setting around [0xa0000-0xb0000) the font buffer. the halt_sys display is normal...it means the vga option rom is executed successfully. you can use filo in etherboot to boot from usb stick.
YH
On 6/25/06, Vincente Tsou vincentetsou@nexcom.com.tw wrote:
Hi YH,
Thanks again for your help.
Now I can active all devices in my LinuxBios, it almost done except VGA function.
I appended a 36k VGA option rom to LinuxBios, and enable Options about VGA.
And I got the halt_sys message:
PCI: 04:02.0 init rom address for PCI: 04:02.0 = fff80000 copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes entering emulator halt_sys: file /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, line 4387 PCI: 01:04.0 init
then, I can see something output, but the output is like snow screen and I can't read anything. I think it is working in the wrong mode.
When I made a blind type 'root' and password, I can login the Linux, and then the screen became clear. (work fine)
I wonder how to fix the problem? is the halt_sys message normal ?
I also got another question, could it possible boot to MS-DOS floppy/USB disk. The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to support it?
2006/6/21, Vincente Tsou vincentetsou@nexcom.com.tw:
Dear YH,
got it.
Thanks for the information and your help.
2006/6/21, Lu, Yinghai yinghai.lu@amd.com:
Actually the irqtable entries is only for peer root pci bus scan when
mptable is used.
So you need to make sure mptable is right, and put entries for
hypertransport chain other than on bus0.
YH
From: vincente.tsou@gmail.com [mailto:vincente.tsou@gmail.com] On Behalf
Of Vincente Tsou
Sent: Tuesday, June 20, 2006 7:05 PM To: Lu, Yinghai Cc: Stefan Reinauer; linuxbios@linuxbios.org
Subject: Re: [LinuxBIOS] New guy in LinuxBios
Dear YH,
excuse me, how about the irq_tables.c?
should I modify it like tyan/s2882 did.
printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0
};
pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8,
0x2, 0xdef8, 0, 0, 0, 0, 0, 0);
pirq_info++; slot_num++;
2006/6/20, Lu, Yinghai <yinghai.lu@amd.com >:
You need to update the entries at mptable.c for your slots or onboard
pci device.
YH
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/ -- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
Hi,
Excuse me....
I don't know how to move the CPU init before other pci device init call.... sorry.
I have tried to find it, but .... :(
2006/6/26, yhlu yinghailu@gmail.com:
the snow screen only happened when I was debugging the onboard VGA support. So i move the CPU init before other pci device init call. That is something related to mtrr setting around [0xa0000-0xb0000) the font buffer. the halt_sys display is normal...it means the vga option rom is executed successfully. you can use filo in etherboot to boot from usb stick.
YH
On 6/25/06, Vincente Tsou vincentetsou@nexcom.com.tw wrote:
Hi YH,
Thanks again for your help.
Now I can active all devices in my LinuxBios, it almost done except VGA function.
I appended a 36k VGA option rom to LinuxBios, and enable Options about
VGA.
And I got the halt_sys message:
PCI: 04:02.0 init rom address for PCI: 04:02.0 = fff80000 copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes entering emulator halt_sys: file /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, line 4387 PCI: 01:04.0 init
then, I can see something output, but the output is like snow screen and
I
can't read anything. I think it is working in the wrong mode.
When I made a blind type 'root' and password, I can login the Linux, and then the screen became clear. (work fine)
I wonder how to fix the problem? is the halt_sys message normal ?
I also got another question, could it possible boot to MS-DOS floppy/USB disk. The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to
support
it?
2006/6/21, Vincente Tsou vincentetsou@nexcom.com.tw:
Dear YH,
got it.
Thanks for the information and your help.
2006/6/21, Lu, Yinghai yinghai.lu@amd.com:
Actually the irqtable entries is only for peer root pci bus scan
when
mptable is used.
So you need to make sure mptable is right, and put entries for
hypertransport chain other than on bus0.
YH
From: vincente.tsou@gmail.com [mailto:vincente.tsou@gmail.com] On
Behalf
Of Vincente Tsou
Sent: Tuesday, June 20, 2006 7:05 PM To: Lu, Yinghai Cc: Stefan Reinauer; linuxbios@linuxbios.org
Subject: Re: [LinuxBIOS] New guy in LinuxBios
Dear YH,
excuse me, how about the irq_tables.c?
should I modify it like tyan/s2882 did.
printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0,
0
};
pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8,
0x2, 0xdef8, 0, 0, 0, 0, 0, 0);
pirq_info++; slot_num++;
2006/6/20, Lu, Yinghai <yinghai.lu@amd.com >:
You need to update the entries at mptable.c for your slots or
onboard
pci device.
YH
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/
-- Best Regards, Vincente Tsou
Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou@nexcom.com.tw Web: http://www.nexcom.com.tw/ -- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
* Vincente Tsou vincentetsou@nexcom.com.tw [060626 08:57]:
Hi,
Excuse me....
I don't know how to move the CPU init before other pci device init call.... sorry.
I have tried to find it, but .... :(
Other question: How did you produce your vga bios image? you should extract it from the vendor bios image, not from memory, as some modify themselfes.
And, no, sorry, booting MSDOS is not possible at the moment (except maybe with ADLO, which has not been developed in a long time)
Hello Stefan,
Yeah, the VGA BIOS is extract from vendor bios image.
Thanks for your update of MS-DOS.
2006/6/26, Stefan Reinauer stepan@coresystems.de:
- Vincente Tsou vincentetsou@nexcom.com.tw [060626 08:57]:
Hi,
Excuse me....
I don't know how to move the CPU init before other pci device init
call....
sorry.
I have tried to find it, but .... :(
Other question: How did you produce your vga bios image? you should extract it from the vendor bios image, not from memory, as some modify themselfes.
And, no, sorry, booting MSDOS is not possible at the moment (except maybe with ADLO, which has not been developed in a long time)
-- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/