coreboot March 2005

coreboot@coreboot.org

51 participants
93 discussions

[LinuxBIOS] Help regarding compiling and building bios
by Ramesh Chhaba 23 Mar '05

23 Mar '05

Hi All , I am a newbie in the fiels of LinuxBios, I want to make linuxbios for the STPC Atlas , I know it is not supported in the freebios2 but it is supprted in the freebios (1). Bit I have found making of first version is diffrent from that of freebios2 . I want to use Etherboot as payload for this bios. Somebody plz do this favour for me that tell me exact steps 1. Downloading freebios version 1 (Usually when i download it misses some files) 2. Compiling etherboot as payload. 3. Compiling and building freeebios It is very odd ,i am not knowing anything :(( But I have been caught in few errors during compiling and dont know exavt steps I want final output as a rom image that i can burn into BIOS chip. Thanks in advance Ramesh Chander Yahoo! India Matrimony: Find your life partneronline.

2 3

RE: [LinuxBIOS] multiple devices in mainboard Config.lb
by Stephen.Kimball＠bench.com 21 Mar '05

21 Mar '05

YH, I found that moving my changes to the latest LinuxBIOS source makes a difference. Now the device tree entries magically are put on a more correct bus. But LinuxBIOS uses different busses depending on how I number the devices. If I number the PCI devices to power up defaults, then the device table uses bus 1 for the first CK804 and 3 for the second. If I number them with the bumped up device numbers given by incoherent.c then it uses busses 1 and 2. I would assume that the Config.lb file would use the device's power up default values? I'm dumping the device tree in device.c after "Devices initialized" with printk_info("Dev tree...\n"); for(dev = all_devices; dev; dev = dev->next) { bus = dev->bus; printk_info("%s bus %d link %d ", dev_path(dev), bus->secondary, bus->link); printk_info(" sibling %s ", dev_path(dev->sibling)); printk_info(" next %s\n", dev_path(dev->next)); printk_info(" vendor %x ", dev->vendor); printk_info(" on_mainboard %x ", dev->on_mainboard); printk_info(" enabled %x ", dev->enabled); printk_info(" have_resources %x ", dev->have_resources); printk_info(" initialized %x\n", dev->initialized); } printk_info("End of tree\n"); Thanks. Steve -----Original Message----- From: Kimball, Stephen Sent: Monday, March 21, 2005 8:05 AM To: yinghailu(a)gmail.com Cc: linuxbios(a)openbios.org Subject: RE: [LinuxBIOS] multiple devices in mainboard Config.lb OK, that makes sense. So how do I specify bus 1 and 3 in the Config file? Steve -----Original Message----- From: yhlu [mailto:yinghailu@gmail.com] Sent: Friday, March 18, 2005 5:28 PM To: Kimball, Stephen Cc: linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] multiple devices in mainboard Config.lb the first one is right. bus 2 is leave for bus under your master ck804 pci bus behind pci bridge 1:a.0 YH _______________________________________________ LinuxBIOS mailing list LinuxBIOS(a)openbios.org http://www.openbios.org/mailman/listinfo/linuxbios

1 0

Re: [LinuxBIOS] RE: How to flash the bios?
by Ronald G. Minnich 21 Mar '05

21 Mar '05

On Mon, 21 Mar 2005, Markus Wolters wrote: > Pm29F002T-90PC I think that should have worked. I suggest you try the flash_rom from freeebios2 -- it has more parts supported. ron

1 0

RE: [LinuxBIOS] multiple devices in mainboard Config.lb
by Stephen.Kimball＠bench.com 21 Mar '05

21 Mar '05

OK, that makes sense. So how do I specify bus 1 and 3 in the Config file? Steve -----Original Message----- From: yhlu [mailto:yinghailu@gmail.com] Sent: Friday, March 18, 2005 5:28 PM To: Kimball, Stephen Cc: linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] multiple devices in mainboard Config.lb the first one is right. bus 2 is leave for bus under your master ck804 pci bus behind pci bridge 1:a.0 YH

1 0

[LinuxBIOS] RE: How to flash the bios?
by Markus Wolters 21 Mar '05

21 Mar '05

> Once you have identified the part, let us know what it is exactly and if > we don't already have support for it in the flash_rom utility, we might > be able to add support for it. It's the original bios chip. It is labelled: PMC Flash MFCN5 0231 Pm29F002T-90PC

1 0

[LinuxBIOS] Re: "Options.lb 2 XML" the 2nd
by Florian Zeitz 21 Mar '05

21 Mar '05

Stefan Reinauer wrote: > Ok, I checked the script into the arch repository now, utils/optionlist. > >I changed the xsl sheet slightly so it works with my version of xsltproc >and saxon. Which xsl processor are you using? > >Thanks for your work > >Stefan > > > To be honest I tried so many different xsl processors that I really can't remember what I finally used. I think it was a good idea to make it XSLT 1.0 (again (I had it written in XSLT 1.0 first, too) as it seems a lot more processors can handle it. You might want to completely remove the xsl:choose stuff (so basically what is commented right now) it was a hack to get the xml (the unprocessed of course) to show correctly in firefox and is specific to XSLT 2.0 anyway because it uses xhtml as method.

3 2

[LinuxBIOS] How to flash the bios?
by Markus Wolters 20 Mar '05

20 Mar '05

Hello, I have compiled and build freebios and everything went ok. The romimage is at /usr/src/freebios/build. My mainboard is a K7SEM. When I do flash_rom, this error message appears : 2f is 0xfd EEPROM not found I'm not sure what I'm doing wrong. How do I have to flash the image? Thanks Markus

1 0

[LinuxBIOS] multiple devices in mainboard Config.lb
by Stephen.Kimball＠bench.com 18 Mar '05

18 Mar '05

I'm trying to write the mainboard Config.lb file to support a CK804 and an IO4 on one Opteron. I can write a mainboard Config.lb file that will boot the system from an IDE device, but that's only because new device table entries are created for the IDE device. So I'm not using the static on_mainboard=1 entries. I can write a Config.lb file to use the CK804, but incoherent.c bumps up the device numbers and northbridge.c moves the device to bus 1. Then I get the PCI bus configured like this Bus# 00, Dev# 18, Func# 0 ---> Vendor ID = 1022 Device ID = 1100 Bus# 00, Dev# 18, Func# 1 ---> Vendor ID = 1022 Device ID = 1101 Bus# 00, Dev# 18, Func# 2 ---> Vendor ID = 1022 Device ID = 1102 Bus# 00, Dev# 18, Func# 3 ---> Vendor ID = 1022 Device ID = 1103 Bus# 00, Dev# 19, Func# 0 ---> Vendor ID = 1022 Device ID = 1100 Bus# 00, Dev# 19, Func# 1 ---> Vendor ID = 1022 Device ID = 1101 Bus# 00, Dev# 19, Func# 2 ---> Vendor ID = 1022 Device ID = 1102 Bus# 00, Dev# 19, Func# 3 ---> Vendor ID = 1022 Device ID = 1103 Bus# 01, Dev# 01, Func# 0 ---> Vendor ID = 10DE Device ID = 005E Bus# 01, Dev# 02, Func# 0 ---> Vendor ID = 10DE Device ID = 0051 Bus# 01, Dev# 02, Func# 1 ---> Vendor ID = 10DE Device ID = 0052 Bus# 01, Dev# 02, Func# 2 ---> Vendor ID = 10DE Device ID = 005F Bus# 01, Dev# 03, Func# 0 ---> Vendor ID = 10DE Device ID = 005A Bus# 01, Dev# 03, Func# 1 ---> Vendor ID = 10DE Device ID = 005B Bus# 01, Dev# 05, Func# 0 ---> Vendor ID = 10DE Device ID = 0059 Bus# 01, Dev# 05, Func# 1 ---> Vendor ID = 10DE Device ID = 0058 Bus# 01, Dev# 07, Func# 0 ---> Vendor ID = 10DE Device ID = 0053 Bus# 01, Dev# 08, Func# 0 ---> Vendor ID = 10DE Device ID = 0054 Bus# 01, Dev# 09, Func# 0 ---> Vendor ID = 10DE Device ID = 0055 Bus# 01, Dev# 0A, Func# 0 ---> Vendor ID = 10DE Device ID = 005C Bus# 01, Dev# 0B, Func# 0 ---> Vendor ID = 10DE Device ID = 0056 Bus# 01, Dev# 0C, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 01, Dev# 0D, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 01, Dev# 0E, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 01, Dev# 0F, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 03, Dev# 01, Func# 0 ---> Vendor ID = 10DE Device ID = 005E Bus# 03, Dev# 02, Func# 0 ---> Vendor ID = 10DE Device ID = 00D3 Bus# 03, Dev# 02, Func# 1 ---> Vendor ID = 10DE Device ID = 0052 Bus# 03, Dev# 02, Func# 2 ---> Vendor ID = 10DE Device ID = 005F Bus# 03, Dev# 08, Func# 0 ---> Vendor ID = 10DE Device ID = 0054 Bus# 03, Dev# 09, Func# 0 ---> Vendor ID = 10DE Device ID = 0055 Bus# 03, Dev# 0B, Func# 0 ---> Vendor ID = 10DE Device ID = 0056 Bus# 03, Dev# 0C, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 03, Dev# 0D, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 03, Dev# 0E, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 03, Dev# 0F, Func# 0 ---> Vendor ID = 10DE Device ID = 005D If I add "device pci_domain" statements before the devices, I get this Bus# 00, Dev# 18, Func# 0 ---> Vendor ID = 1022 Device ID = 1100 Bus# 00, Dev# 18, Func# 1 ---> Vendor ID = 1022 Device ID = 1101 Bus# 00, Dev# 18, Func# 2 ---> Vendor ID = 1022 Device ID = 1102 Bus# 00, Dev# 18, Func# 3 ---> Vendor ID = 1022 Device ID = 1103 Bus# 00, Dev# 19, Func# 0 ---> Vendor ID = 1022 Device ID = 1100 Bus# 00, Dev# 19, Func# 1 ---> Vendor ID = 1022 Device ID = 1101 Bus# 00, Dev# 19, Func# 2 ---> Vendor ID = 1022 Device ID = 1102 Bus# 00, Dev# 19, Func# 3 ---> Vendor ID = 1022 Device ID = 1103 Bus# 01, Dev# 00, Func# 0 ---> Vendor ID = 10DE Device ID = 005E Bus# 01, Dev# 01, Func# 0 ---> Vendor ID = 10DE Device ID = 0051 Bus# 01, Dev# 01, Func# 1 ---> Vendor ID = 10DE Device ID = 0052 Bus# 01, Dev# 01, Func# 2 ---> Vendor ID = 10DE Device ID = 005F Bus# 01, Dev# 02, Func# 0 ---> Vendor ID = 10DE Device ID = 005A Bus# 01, Dev# 02, Func# 1 ---> Vendor ID = 10DE Device ID = 005B Bus# 01, Dev# 04, Func# 0 ---> Vendor ID = 10DE Device ID = 0059 Bus# 01, Dev# 04, Func# 1 ---> Vendor ID = 10DE Device ID = 0058 Bus# 01, Dev# 06, Func# 0 ---> Vendor ID = 10DE Device ID = 0053 Bus# 01, Dev# 07, Func# 0 ---> Vendor ID = 10DE Device ID = 0054 Bus# 01, Dev# 08, Func# 0 ---> Vendor ID = 10DE Device ID = 0055 Bus# 01, Dev# 09, Func# 0 ---> Vendor ID = 10DE Device ID = 005C Bus# 01, Dev# 0A, Func# 0 ---> Vendor ID = 10DE Device ID = 0056 Bus# 01, Dev# 0B, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 01, Dev# 0C, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 01, Dev# 0D, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 01, Dev# 0E, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 02, Dev# 00, Func# 0 ---> Vendor ID = 10DE Device ID = 005E Bus# 02, Dev# 01, Func# 0 ---> Vendor ID = 10DE Device ID = 00D3 Bus# 02, Dev# 01, Func# 1 ---> Vendor ID = 10DE Device ID = 0052 Bus# 02, Dev# 01, Func# 2 ---> Vendor ID = 10DE Device ID = 005F Bus# 02, Dev# 07, Func# 0 ---> Vendor ID = 10DE Device ID = 0054 Bus# 02, Dev# 08, Func# 0 ---> Vendor ID = 10DE Device ID = 0055 Bus# 02, Dev# 0A, Func# 0 ---> Vendor ID = 10DE Device ID = 0056 Bus# 02, Dev# 0B, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 02, Dev# 0C, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 02, Dev# 0D, Func# 0 ---> Vendor ID = 10DE Device ID = 005D Bus# 02, Dev# 0E, Func# 0 ---> Vendor ID = 10DE Device ID = 005D So why does incoherent.c need to bump up the device numbers when the devices are on different busses? There should be no device number conflicts? No matter what I do, LinuxBIOS always creates new device table entries, because my Config.lb file has the devices on the wrong bus - 0. The config file doesn't specify a device's bus and it doesn't assume a bus from the domain statement. How is this suppose to work? Attached is my Config.lb file. Thanks for the help. Steve Kimball

2 1

[LinuxBIOS] Problems Setting The Opteron Address Map (resourcemap.c)
by Jeff Stevens 18 Mar '05

18 Mar '05

I am trying to understand the Opteron Address Map, and am having some problems. I'm pretty sure I understand everything but the PCI I/O section, but I have few questions about the other sections also. If there is a good document to help one setup the address map, other than the "AMD BIOS and Kernel Developer's Guide", please let me know. I have a Quad-Opteron system, with an AMD 8131 and AMD 8111 hanging off of CPU 0, and another AMD 8131 hanging off of CPU 1. Each CPU has 4 DIMM slots for DDR memory. 1. Does the DRAM map section pertain to the DDR SDRAM, or is there an ability on the Opteron (as on some other PPC processors I have dealt with) to hang standard DRAM off of the local bus of the processor? If this is for DDR SDRAM, if I leave them all disabled, do these get configured later when the BIOS reads the SPD PROM for the DDR? Or do I have to configure a Window for each processor's maximum allowable DDR SDRAM? 2. It seems that the Memory Mapped I/O section is mainly to map the AMD 8111 and 8131s IO-APIC address ranges (which seem to be 64KB in size). Is this correct, and is there anything else that should go there (maybe PCI space)? 3. The PCI I/O section is my main problem. I haven't dealt with PCI too much in depth. I don't understand how it uses only 13 bits for the PCI I/O Base and Limit addresses? I thought that you need a 32-bit address? Please help me understand exactly what the I/O base address is! The only examples in the LinuxBIOS tree have the AMD 8111 & 8131s hanging off of one CPU, and therefor just steer all of the address range to that HT link. Thanks you in advance! Jeff Stevens __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

[LinuxBIOS] CVS or TLA
by Li-Ta Lo 18 Mar '05

18 Mar '05

Stephan, What is the current status of the revision control system? Are we going to use the tla now? Ollie

4 6

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot March 2005