Re: Overlaping IO resource for AMD K8
Li-Ta Lo [EMAIL PROTECTED] writes: On Tue, 2005-01-11 at 16:52, Ronald G. Minnich wrote: Ollie, you did it! We should thank SciTech for their wonderful emulator. Yes. Ollie just took a big stack of video cards, some AGP and some PCI, and booted linuxbios one at a time and showed how each video card came up. It's fantastic. I think the current code should support most VGA cards available in the market. I have tried VGA cards from Nvidia, ATI, Matrox and Cirrus. I found that the VBIOS on S3 cards don't have correct ROM header. The company is dead anyway. In what sense do they have a bad ROM header? I can easily see them not supporting new pci features. Unless we can show that something is broken beyond repair we should not give up on supporting it. We don't know what brain damage will show up next. Eric ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
On Tue, 2005-01-18 at 04:54, Eric W. Biederman wrote: Li-Ta Lo [EMAIL PROTECTED] writes: On Tue, 2005-01-11 at 16:52, Ronald G. Minnich wrote: Ollie, you did it! We should thank SciTech for their wonderful emulator. Yes. Ollie just took a big stack of video cards, some AGP and some PCI, and booted linuxbios one at a time and showed how each video card came up. It's fantastic. I think the current code should support most VGA cards available in the market. I have tried VGA cards from Nvidia, ATI, Matrox and Cirrus. I found that the VBIOS on S3 cards don't have correct ROM header. The company is dead anyway. In what sense do they have a bad ROM header? I can easily see them not supporting new pci features. Unless we can show that something is broken beyond repair we should not give up on supporting it. We don't know what brain damage will show up next. Some of them don't have correct 0x55aa signature. All of them have wrong Class code. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
* Li-Ta Lo [EMAIL PROTECTED] [050118 17:14]: Some of them don't have correct 0x55aa signature. All of them have wrong Class code. Then it is not a pci option rom as described by the standard. Do they have the other pci option rom structs? ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
It is weird that fuctory bios can still use them. There's gotta be a hack in fuctory bios, I would guess, something like: if (the pci card is a vga there is an option rom) callit(); i.e. I betcha that fuctory bioses will call an option rom on vga even if it violates the spec. I wonder if we really want to do this, the S3 cards are antiques anyway. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
On Tue, 2005-01-18 at 09:29, Ronald G. Minnich wrote:
It is weird that fuctory bios can still use them.
There's gotta be a hack in fuctory bios, I would guess, something like:
if (the pci card is a vga there is an option rom)
callit();
i.e. I betcha that fuctory bioses will call an option rom on vga even if
it violates the spec.
I wonder if we really want to do this, the S3 cards are antiques anyway.
ron
YhLu,
Why did you remove the class code check ?
if (dev-class != ((rom_data-class_hi 8) | rom_data-class_lo)) {
printk_err(Class Code mismatch ROM %08x, dev %08x\n,
(rom_data-class_hi 8) | rom_data-class_lo,
dev-class);
// return NULL;
}
Ollie
___
Linuxbios mailing list
Linuxbios@clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
It is weird that fuctory bios can still use them. There's gotta be a hack in fuctory bios, I would guess, something like: if (the pci card is a vga there is an option rom) callit(); i.e. I betcha that fuctory bioses will call an option rom on vga even if it violates the spec. I wonder if we really want to do this, the S3 cards are antiques anyway. Ollie how are you ripping the vbios bios from the S3 card? Did you pop the chip and use a programmer? If not you may be suffering from the nuke the rom header issue I was talking about earlier. -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
On Tue, 2005-01-18 at 10:06, Richard Smith wrote: It is weird that fuctory bios can still use them. There's gotta be a hack in fuctory bios, I would guess, something like: if (the pci card is a vga there is an option rom) callit(); i.e. I betcha that fuctory bioses will call an option rom on vga even if it violates the spec. I wonder if we really want to do this, the S3 cards are antiques anyway. Ollie how are you ripping the vbios bios from the S3 card? Did you pop the chip and use a programmer? If not you may be suffering from the nuke the rom header issue I was talking about earlier. I can enable rom load but disable execution in LinuxBIOS. After the system is up, I dumped the memory content. Actually, the rom load refuse to download it because its header is incorrect. It is not the nuke problem, it is simply incorrect header. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
i.e. I betcha that fuctory bioses will call an option rom on vga even if it violates the spec. I doubt that.. I've scrubbed the 0xAA55 from several VGA cards so I could plug them into a factory bios system and not have the VGA enabled. None of them ever went ahead and ran the bios. I can enable rom load but disable execution in LinuxBIOS. After the system is up, I dumped the memory content. Actually, the rom load refuse to download it because its header is incorrect. It is not the nuke problem, it is simply incorrect header. Without a correct header I don't see how it could have ever worked in a factory system. I have several S3 cards and they don't seem broken to me. -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
Ollie, I fixed one bug in the class code ...in pci_rom.c. please check it. ... YH ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
On Tue, 2005-01-18 at 11:13, YhLu wrote: Ollie, I fixed one bug in the class code ...in pci_rom.c. please check it. ... YH Did you check in ? Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
Yes. I swap the class_hi and class_lo in pci_rom.h YH -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 10:31 AM To: YhLu Cc: Eric W. Biederman; Ronald G. Minnich; LinuxBIOS Subject: Re: Overlaping IO resource for AMD K8 On Tue, 2005-01-18 at 11:13, YhLu wrote: Ollie, I fixed one bug in the class code ...in pci_rom.c. please check it. ... YH Did you check in ? Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
On Tue, 18 Jan 2005, Stefan Reinauer wrote: Also, the 0x55aa sequence has to be at any 4k boundary within the rom. Before that any data may occur. IIRC the standard does not say that the option rom image has to start at the beginning of the physical chip. I never saw that requirement adhered to in practice. In fact some vga bioses we have seen have several bios versions in one chip. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
On Tue, 2005-01-18 at 12:58, Ronald G. Minnich wrote: On Tue, 18 Jan 2005, Stefan Reinauer wrote: Also, the 0x55aa sequence has to be at any 4k boundary within the rom. Before that any data may occur. IIRC the standard does not say that the option rom image has to start at the beginning of the physical chip. I never saw that requirement adhered to in practice. In fact some vga bioses we have seen have several bios versions in one chip. ron Is there a way to get those cards back from salvage? Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
Ollie, I recall sth about mtrr setting, I wonder if I enable the NC could affect your code. Please check cpu/x86/mtrr/mtrr.c about enable NC below 4G. YH -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 11, 2005 10:21 AM To: LinuxBIOS; Eric Biederman Subject: Overlaping IO resource for AMD K8 Eric, Why I got the overlaping IO resources in the 18:0 ? PCI: 00:18.0 1ba - [0x00f400 - 0x00f5ff] prefmem node 0 link2 PCI: 00:18.0 1c2 - [0x001000 - 0x001fff] io node 0 link 2 PCI: 00:18.0 1d8 - [0x002000 - 0x001fff] io node 0 link 0 PCI: 00:18.0 1b0 - [0x00e000 - 0x00efff] prefmem node 0 link0 PCI: 00:18.0 1a8 - [0x00f630 - 0x00f63f] mem node 0 link 0 PCI: 00:18.0 1a2 - [0x00f600 - 0x00f62f] mem node 0 link 2 Shouldn't the 1d8 be 0x2000 to 0x2? Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
On Tue, 2005-01-11 at 11:56, YhLu wrote: Ollie, I recall sth about mtrr setting, I wonder if I enable the NC could affect your code. Please check cpu/x86/mtrr/mtrr.c about enable NC below 4G. I think there is some problem with the resource allocation. If the vga card has PCI IO resource then there will be no overlaping. If it does not have PCI IO resource then there will be overlaping. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
On Tue, 2005-01-11 at 12:02, Li-Ta Lo wrote: On Tue, 2005-01-11 at 11:56, YhLu wrote: Ollie, I recall sth about mtrr setting, I wonder if I enable the NC could affect your code. Please check cpu/x86/mtrr/mtrr.c about enable NC below 4G. I think there is some problem with the resource allocation. If the vga card has PCI IO resource then there will be no overlaping. If it does not have PCI IO resource then there will be overlaping. There is really a but in the resource allocation. Please take a look at the attached log files. The ATI card has PCI IO resource so there is no bogus resource in the northbridge. As the Nvidia card it does not have PCI IO resource so we got the 2 to 1 thing. Ollie LinuxBIOS-1.1.72.0_Fallback Tue Jan 11 11:22:28 MST 2005 starting... setting up resource mapdone. (0,1) link=01 (1,0) link=01 02 nodes initialized. SBLink=02 NC node/link=00 busn=06 NC node/link=02 ht reset - LinuxBIOS-1.1.72.0_Fallback Tue Jan 11 11:22:28 MST 2005 starting... setting up resource mapdone. (0,1) link=01 (1,0) link=01 02 nodes initialized. SBLink=02 NC node/link=00 busn=06 NC node/link=02 Ram1.00 Ram1.01 Ram2.00 Ram2.01 Ram3 Initializing memory: done Initializing memory: done Clearing initial memory region: done Ram4 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.72.0_Fallback Tue Jan 11 11:22:28 MST 2005 booting... Enumerating buses... PCI_DOMAIN: enabled APIC_CLUSTER: 0 enabled PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] bus ops PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [1022/1100] bus ops PCI: 00:19.0 [1022/1100] enabled PCI: 00:19.1 [1022/1101] enabled PCI: 00:19.2 [1022/1102] enabled PCI: 00:19.3 [1022/1103] ops PCI: 00:19.3 [1022/1103] enabled PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004 HyperT reset not needed PCI: pci_scan_bus for bus 1 PCI: 01:01.0 [1022/7454] ops PCI: 01:01.0 [1022/7454] enabled PCI: 01:02.0 [1022/7455] bus ops PCI: 01:02.0 [1022/7455] enabled PCI: pci_scan_bus for bus 2 PCI: 02:00.0 [1002/4e48] enabled PCI: 02:00.1 [1002/4e68] enabled PCI: pci_scan_bus returning with max=02 PCI: pci_scan_bus returning with max=02 PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003 PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007 HyperT reset not needed PCI: pci_scan_bus for bus 3 PCI: 03:01.0 [1022/7450] bus ops PCI: 03:01.0 [1022/7450] enabled PCI: 03:01.1 [1022/7451] ops PCI: 03:01.1 [1022/7451] enabled PCI: 03:02.0 [1022/7450] bus ops PCI: 03:02.0 [1022/7450] enabled PCI: 03:02.1 [1022/7451] ops PCI: 03:02.1 [1022/7451] enabled PCI: 03:03.0 [1022/7460] bus ops PCI: 03:03.0 [1022/7460] enabled PCI: 03:04.0 [1022/7468] bus ops PCI: 03:04.0 [1022/7468] enabled PCI: 03:04.1 [1022/7469] ops PCI: 03:04.1 [1022/7469] enabled PCI: 03:04.2 [1022/746a] bus ops PCI: 03:04.2 [1022/746a] enabled PCI: 03:04.3 [1022/746b] bus ops PCI: 03:04.3 [1022/746b] enabled PCI: 03:04.5 [1022/746d] enabled PCI: 03:04.6 No device operations PCI: pci_scan_bus for bus 4 PCI: 04:09.0 [14e4/16a7] enabled PCI: pci_scan_bus returning with max=04 PCI: pci_scan_bus for bus 5 PCI: pci_scan_bus returning with max=05 PCI: pci_scan_bus for bus 6 PCI: 06:00.0 [1022/7464] enabled PCI: 06:00.1 [1022/7464] enabled PCI: 06:00.2 No device operations PCI: 06:01.0 No device operations PCI: 06:0c.0 [104c/8023] enabled PCI: pci_scan_bus returning with max=06 PNP: 002e.0 enabled PNP: 002e.1 disabled PNP: 002e.2 enabled PNP: 002e.3 enabled PNP: 002e.5 enabled PNP: 002e.6 disabled PNP: 002e.7 disabled PNP: 002e.8 disabled PNP: 002e.9 disabled PNP: 002e.a disabled PNP: 002e.b enabled I2C: 50 enabled I2C: 51 enabled I2C: 52 enabled I2C: 53 enabled I2C: 54 enabled I2C: 55 enabled I2C: 56 enabled I2C: 57 enabled PCI: pci_scan_bus returning with max=06 PCI: pci_scan_bus returning with max=06 CPU: APIC: 00 enabled CPU: APIC: 01 enabled done Allocating resources... Reading resources... PCI: 03:01.0 1c - [0x00f000 - 0x00efff] bus 4 io PCI: 03:01.0 24 - [0xfff0 - 0xffef] bus 4 prefmem PCI: 03:02.0 1c - [0x00f000 - 0x00efff] bus 5 io PCI: 03:02.0 24 - [0xfff0 - 0xffef] bus 5 prefmem PCI: 03:02.0 20 - [0x00fff0 - 0x00ffef] bus 5 mem PCI: 03:03.0 1c - [0x00f000 - 0x00efff] bus 6 io PCI: 03:03.0 24 - [0x00fff0 - 0x00ffef] bus 6 prefmem Done reading resources. Allocating VGA resource PCI: 02:00.0 Setting PCI_BRIDGE_CTK_VGA for bridge PCI: 01:02.0 Setting PCI_BRIDGE_CTK_VGA for bridge PCI: 00:18.0 Setting PCI_BRIDGE_CTK_VGA for bridge PCI_DOMAIN: Setting PCI_BRIDGE_CTK_VGA for bridge Root Device Setting resources... amdk8_create_vga_resource: link 0 has VGA device PCI: 00:18.0 1ba - [0x00f450 - 0x00f44f] prefmem node 0 link 2 PCI: 00:18.0 1c2 - [0x001000 - 0x001fff] io node 0 link 2 PCI: 00:18.0 1d8 - [0x002000 - 0x002fff] io node
RE: Overlaping IO resource for AMD K8
Complie error You missed sth? Tue Jan 11 10:17:11 PST 2005 FAILED! Log excerpt: /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c: In function `setup_system_bios': /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:219: warning: implicit declaration of function `memset' /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c: At top level: /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:232: error: conflicting types for 'reset_int_vect' /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:179: error: previous implicit declaration of 'reset_int_vect' was here /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c: In function `run_bios': /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:289: warning: implicit declaration of function `X86EMU_setMemBase' make[1]: *** [biosemu.o] Error 1 -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 11, 2005 11:13 AM To: YhLu Cc: LinuxBIOS; Eric Biederman Subject: RE: Overlaping IO resource for AMD K8 On Tue, 2005-01-11 at 12:02, Li-Ta Lo wrote: On Tue, 2005-01-11 at 11:56, YhLu wrote: Ollie, I recall sth about mtrr setting, I wonder if I enable the NC could affect your code. Please check cpu/x86/mtrr/mtrr.c about enable NC below 4G. I think there is some problem with the resource allocation. If the vga card has PCI IO resource then there will be no overlaping. If it does not have PCI IO resource then there will be overlaping. There is really a but in the resource allocation. Please take a look at the attached log files. The ATI card has PCI IO resource so there is no bogus resource in the northbridge. As the Nvidia card it does not have PCI IO resource so we got the 2 to 1 thing. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
As the Nvidia card it does not have PCI IO resource so we got the 2 to 1 thing. It mean it doesn't allocate resource to it. Limitstart YH -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 11, 2005 11:13 AM To: YhLu Cc: LinuxBIOS; Eric Biederman Subject: RE: Overlaping IO resource for AMD K8 On Tue, 2005-01-11 at 12:02, Li-Ta Lo wrote: On Tue, 2005-01-11 at 11:56, YhLu wrote: Ollie, I recall sth about mtrr setting, I wonder if I enable the NC could affect your code. Please check cpu/x86/mtrr/mtrr.c about enable NC below 4G. I think there is some problem with the resource allocation. If the vga card has PCI IO resource then there will be no overlaping. If it does not have PCI IO resource then there will be overlaping. There is really a but in the resource allocation. Please take a look at the attached log files. The ATI card has PCI IO resource so there is no bogus resource in the northbridge. As the Nvidia card it does not have PCI IO resource so we got the 2 to 1 thing. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
On Tue, 2005-01-11 at 12:37, YhLu wrote: Complie error You missed sth? I don't think so. Those function are not actually used. You can try to mark them. Ollie Tue Jan 11 10:17:11 PST 2005 FAILED! Log excerpt: /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c: In function `setup_system_bios': /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:219: warning: implicit declaration of function `memset' /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c: At top level: /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:232: error: conflicting types for 'reset_int_vect' /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:179: error: previous implicit declaration of 'reset_int_vect' was here /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c: In function `run_bios': /home/yhlu/xx/xx/freebios2/src/devices/emulator/biosemu.c:289: warning: implicit declaration of function `X86EMU_setMemBase' make[1]: *** [biosemu.o] Error 1 -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 11, 2005 11:13 AM To: YhLu Cc: LinuxBIOS; Eric Biederman Subject: RE: Overlaping IO resource for AMD K8 On Tue, 2005-01-11 at 12:02, Li-Ta Lo wrote: On Tue, 2005-01-11 at 11:56, YhLu wrote: Ollie, I recall sth about mtrr setting, I wonder if I enable the NC could affect your code. Please check cpu/x86/mtrr/mtrr.c about enable NC below 4G. I think there is some problem with the resource allocation. If the vga card has PCI IO resource then there will be no overlaping. If it does not have PCI IO resource then there will be overlaping. There is really a but in the resource allocation. Please take a look at the attached log files. The ATI card has PCI IO resource so there is no bogus resource in the northbridge. As the Nvidia card it does not have PCI IO resource so we got the 2 to 1 thing. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
On Tue, 2005-01-11 at 12:39, YhLu wrote: As the Nvidia card it does not have PCI IO resource so we got the 2 to 1 thing. It mean it doesn't allocate resource to it. Limitstart But why it set the resource to the HW registers? Doesn't it cause some ill side effect? Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Overlaping IO resource for AMD K8
Li-Ta Lo [EMAIL PROTECTED] writes: Eric, Why I got the overlaping IO resources in the 18:0 ? PCI: 00:18.0 1ba - [0x00f400 - 0x00f5ff] prefmem node 0 link2 PCI: 00:18.0 1c2 - [0x001000 - 0x001fff] io node 0 link 2 PCI: 00:18.0 1d8 - [0x002000 - 0x001fff] io node 0 link 0 PCI: 00:18.0 1b0 - [0x00e000 - 0x00efff] prefmem node 0 link0 PCI: 00:18.0 1a8 - [0x00f630 - 0x00f63f] mem node 0 link 0 PCI: 00:18.0 1a2 - [0x00f600 - 0x00f62f] mem node 0 link 2 Shouldn't the 1d8 be 0x2000 to 0x2? I'm not quite certain but it appears to be my code for disabling bridge resources when there is nothing behind it. start end creates a resource that doesn't decode anything. Do you have any I/O resources on that link? Does the resource allocator see those resources? Eric ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
On Tue, 2005-01-11 at 13:16, YhLu wrote: It works on S2895 + NV (Vendor 10de, Device 00fd) card. You did a great job. Please disable the printk_debug instruction biosemu.c. YH I am still debugging PCI cards. Once I have PCI cards working I will disable these messages. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
Ollie, you did it! Ollie just took a big stack of video cards, some AGP and some PCI, and booted linuxbios one at a time and showed how each video card came up. It's fantastic. now, Stefan, time for openbios payload. Then we have a desktop PC that prints an Open Boot prompt :-) ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Overlaping IO resource for AMD K8
On Tue, 2005-01-11 at 16:52, Ronald G. Minnich wrote: Ollie, you did it! We should thank SciTech for their wonderful emulator. Ollie just took a big stack of video cards, some AGP and some PCI, and booted linuxbios one at a time and showed how each video card came up. It's fantastic. I think the current code should support most VGA cards available in the market. I have tried VGA cards from Nvidia, ATI, Matrox and Cirrus. I found that the VBIOS on S3 cards don't have correct ROM header. The company is dead anyway. now, Stefan, time for openbios payload.Then we have a desktop PC that prints an Open Boot prompt :-) After 5 years, we are finally at the point to be able to compete with factory BIOS on all market sectors. Ollie ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
