coreboot

coreboot@coreboot.org

11 participants
39714 discussions

13 Jan '05

PCI: 02:06.0 30 <- [0x00fff80000 - 0x00fff7ffff] rom It seems it can not be processed by pci_set_resource properly. YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, January 12, 2005 10:10 PM To: YhLu Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA On Wed, 2005-01-12 at 23:07, YhLu wrote: > You assign the value to the new resource. > > I wonder if it will confuse the resource allocator. Because the range is out > of touch of allocator. > I don't think so but I am not sure neither. The resource is flagged as FIXED and ASSIGNED. The resource allocator should leave that resource as is. If it does not work, we can just write dev->rom_address to PCI_ROM_ADDRESS directly in pci_get_rom_resource() and the pci_rom_probe() can still be unchanged. Could you try the code? Ollie > YH > > -----Original Message----- > From: Li-Ta Lo [mailto:ollie@lanl.gov] > Sent: Wednesday, January 12, 2005 9:48 PM > To: YhLu > Cc: Sagiv Yefet; LinuxBIOS > Subject: RE: Running with VGA > > On Wed, 2005-01-12 at 21:02, YhLu wrote: > > Committed. > > > > Also I added readme in /drivers/pci/onboard/onboard.c > > > > > > YH > > > > I made some modification which should utilize the resource allocation > code and minimize the impact of the embedded ROM image. I was doing > it blindly, please test it on your platform. > > Ollie >

2 1

RE: Running with VGA
by YhLu 13 Jan '05

13 Jan '05

Move /* for on board device with embedded ROM image, the ROM image is at * fixed address specified in the Config.lb, the dev->rom_address is * inited by driver_pci_onboard_ops::enable_dev() */ if ((dev->on_mainboard) && (dev->rom_address != 0)) { resource->base = dev->rom_address; resource->flags |= IORESOURCE_MEM | IORESOURCE_READONLY | IORESOURCE_ASSIGNED | IORESOURCE_FIXED; return; } To get_pci_rom_resource end. PCI: 02:06.0 30 <- [0x00fff80000 - 0x00fff9ffff] rom But PCI: 02:06.0 init pci_rom_probe, rom address for PCI: 02:06.0 = 1d300 pci_rom_probe, Incorrect Expansion ROM Header Signature 1fe8 I wonder if we can not store that value into PCI_ROM_ADDRESS YH -----Original Message----- From: YhLu Sent: Thursday, January 13, 2005 10:06 AM To: YhLu; Li-Ta Lo Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA I guess it can not get size correctly. So you need to change the pci_get_rom_resource to get the size for it. And then assign the base to it. YH -----Original Message----- From: YhLu Sent: Thursday, January 13, 2005 9:49 AM To: Li-Ta Lo Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA PCI: 02:06.0 30 <- [0x00fff80000 - 0x00fff7ffff] rom It seems it can not be processed by pci_set_resource properly. YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, January 12, 2005 10:10 PM To: YhLu Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA On Wed, 2005-01-12 at 23:07, YhLu wrote: > You assign the value to the new resource. > > I wonder if it will confuse the resource allocator. Because the range is out > of touch of allocator. > I don't think so but I am not sure neither. The resource is flagged as FIXED and ASSIGNED. The resource allocator should leave that resource as is. If it does not work, we can just write dev->rom_address to PCI_ROM_ADDRESS directly in pci_get_rom_resource() and the pci_rom_probe() can still be unchanged. Could you try the code? Ollie > YH > > -----Original Message----- > From: Li-Ta Lo [mailto:ollie@lanl.gov] > Sent: Wednesday, January 12, 2005 9:48 PM > To: YhLu > Cc: Sagiv Yefet; LinuxBIOS > Subject: RE: Running with VGA > > On Wed, 2005-01-12 at 21:02, YhLu wrote: > > Committed. > > > > Also I added readme in /drivers/pci/onboard/onboard.c > > > > > > YH > > > > I made some modification which should utilize the resource allocation > code and minimize the impact of the embedded ROM image. I was doing > it blindly, please test it on your platform. > > Ollie > _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Running with VGA
by YhLu 13 Jan '05

13 Jan '05

I guess it can not get size correctly. So you need to change the pci_get_rom_resource to get the size for it. And then assign the base to it. YH -----Original Message----- From: YhLu Sent: Thursday, January 13, 2005 9:49 AM To: Li-Ta Lo Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA PCI: 02:06.0 30 <- [0x00fff80000 - 0x00fff7ffff] rom It seems it can not be processed by pci_set_resource properly. YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, January 12, 2005 10:10 PM To: YhLu Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA On Wed, 2005-01-12 at 23:07, YhLu wrote: > You assign the value to the new resource. > > I wonder if it will confuse the resource allocator. Because the range is out > of touch of allocator. > I don't think so but I am not sure neither. The resource is flagged as FIXED and ASSIGNED. The resource allocator should leave that resource as is. If it does not work, we can just write dev->rom_address to PCI_ROM_ADDRESS directly in pci_get_rom_resource() and the pci_rom_probe() can still be unchanged. Could you try the code? Ollie > YH > > -----Original Message----- > From: Li-Ta Lo [mailto:ollie@lanl.gov] > Sent: Wednesday, January 12, 2005 9:48 PM > To: YhLu > Cc: Sagiv Yefet; LinuxBIOS > Subject: RE: Running with VGA > > On Wed, 2005-01-12 at 21:02, YhLu wrote: > > Committed. > > > > Also I added readme in /drivers/pci/onboard/onboard.c > > > > > > YH > > > > I made some modification which should utilize the resource allocation > code and minimize the impact of the embedded ROM image. I was doing > it blindly, please test it on your platform. > > Ollie > _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

Configuration for motherboard
by Andreas Bach Aaen (AH/TED) 13 Jan '05

13 Jan '05

Hi linuxbios developers, I am new to this list and BIOS concepts in general. However I have worked with Linux for over 10 years, but I am sure you can learn me something new anyhow:-) I have a motherboard which gives me the following output from lspci: ------- 0000:00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01) 0000:00:00.1 Class ff00: Intel Corp. E7000 Series Host RASUM Controller (rev 01) 0000:00:02.0 PCI bridge: Intel Corp. E7000 Series Hub Interface B PCI-to-PCI Bridge (rev 01) 0000:00:02.1 Class ff00: Intel Corp. E7000 Series Hub Interface B RASUM Controller (rev 01) 0000:00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 82) 0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02) 0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 IDE Controller (rev 02) 0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) 0000:02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) 0000:02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) 0000:02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) 0000:02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) 0000:03:02.0 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03) 0000:03:02.1 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03) 0000:03:03.0 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03) 0000:03:03.1 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet Controller (rev 03) 0000:03:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz Ultra3 SCSI Adapter (rev 01) -------- The superIO chip is NSC PC87417 which don't seen to be supported, but I only need access to one of the serial ports in BIOS. Is this possible? I can see that my base should be freebios2 and not freebios. Which motherboard/configuration would be my best starting point? I would like to flash a linux kernel 2.4.x in BIOS which later on could boot a linux 2.6.x from either harddisk or net. How does the one kernel hand over the control to the other? Regards, -- Andreas Bach Aaen System Developer, M. Sc. Ericsson Telebit A/S tel: +45 89 38 51 00 Skanderborgvej 232 fax: +45 89 38 51 01 8260 Viby J Denmark andreas.bach.aaen(a)ericsson.com

2 3

RE: problem with booting SMP linux kernel
by YhLu 13 Jan '05

13 Jan '05

Every MB's mptable.c is different. YH -----Original Message----- From: Gin [mailto:ginlin@nexcom.com.tw] Sent: Wednesday, January 12, 2005 6:55 PM To: 'Ronald G. Minnich' Cc: linuxbios(a)clustermatic.org Subject: RE: problem with booting SMP linux kernel >bad mp table would be my guess. I think the I/O APICs are incorrectly assigned to buses. From the kernel messages, devices on bus 0 are transformed to high IRQs. Can anyone one confirm that the mptable.c under src/tyan/s2735 is a good one to boot SMP linux kernel? I might need to manually construct the MP table for my board according to a good one. Thanks, gin _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

[OT] Tyan dual opteron motherboards
by Amaury Jacquot 13 Jan '05

13 Jan '05

considering how AMD64 is NUMA based, is it possible to use processors with a different operating frequency ?

1 0

RE: Running with VGA
by YhLu 12 Jan '05

12 Jan '05

You assign the value to the new resource. I wonder if it will confuse the resource allocator. Because the range is out of touch of allocator. YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, January 12, 2005 9:48 PM To: YhLu Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA On Wed, 2005-01-12 at 21:02, YhLu wrote: > Committed. > > Also I added readme in /drivers/pci/onboard/onboard.c > > > YH > I made some modification which should utilize the resource allocation code and minimize the impact of the embedded ROM image. I was doing it blindly, please test it on your platform. Ollie

2 1

RE: Running with VGA
by YhLu 12 Jan '05

12 Jan '05

You may write the value into the PCI_ROM_REGISTER instead of create one resource for it. Also it's better to let pci_probe_rom to double check the signature is more safe. YH -----Original Message----- From: YhLu Sent: Wednesday, January 12, 2005 9:56 PM To: 'Li-Ta Lo' Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA You assign the value to the new resource. I wonder if it will confuse the resource allocator. Because the range is out of touch of allocator. YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, January 12, 2005 9:48 PM To: YhLu Cc: Sagiv Yefet; LinuxBIOS Subject: RE: Running with VGA On Wed, 2005-01-12 at 21:02, YhLu wrote: > Committed. > > Also I added readme in /drivers/pci/onboard/onboard.c > > > YH > I made some modification which should utilize the resource allocation code and minimize the impact of the embedded ROM image. I was doing it blindly, please test it on your platform. Ollie

1 0

RE: Running with VGA
by YhLu 12 Jan '05

12 Jan '05

Committed. Also I added readme in /drivers/pci/onboard/onboard.c YH

2 1

RE: mptable.c
by YhLu 12 Jan '05

12 Jan '05

Enable apic ext id committed. Changes Auto.c nodeid = lapicid() & 0xf; #if ENABLE_APIC_EXT_ID == 1 enable_apic_ext_id(nodeid); lapic_write(LAPIC_ID, ( lapic_read(LAPIC_ID) | (APIC_ID_OFFSET<<24) ) ); // CPU apicid is from 0x10 #endif if (cpu_init_detected(nodeid)) { asm volatile ("jmp __cpu_reset"); } distinguish_cpu_resets(nodeid); also reset_test.c change cpu_init_detected and distinguish_cpu_resets to take node id. YH -----Original Message----- From: Ronald G. Minnich [mailto:rminnich@lanl.gov] Sent: Tuesday, January 04, 2005 7:29 AM To: Stefan Reinauer Cc: linuxbios(a)clustermatic.org Subject: Re: mptable.c On Tue, 4 Jan 2005, Stefan Reinauer wrote: > I can have a look, if you can point me to some documentation. Is the > utility supposed to through out a working mptable? The code it creates > looks fundamentally different from the opteron boards' mptables.c > versions. It will toss out C code with the proper options. It's been so long since anyone has used it that I don't remember how to run it! ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot