coreboot

coreboot@coreboot.org

25 participants
39548 discussions

"best" supported hardware
by Zachary Miller 30 Sep '03

30 Sep '03

hi all, i'm new to this list although i have some experience with linuxbios. about a year ago (somewhere in the 2.4.12 kernel era) i got everything working no problem on a matsonic/ms7308e motherboard, with a disk-on-chip filesystem and all. my boot time from power off is about 6 seconds until the mp3 player kicks in. i must say i'm very impressed! it seems that many more types of motherboards are now listed as stable since i last checked. sure, i could go and look up the specs of every single one, and i probably will, but i thought i would suggest putting some basic specs for each on the status page or perhaps an entry in the faq that answers my basic question: which of the "stable" motherboards supports the fastest processor? cheers, -zach

2 1

static_devices.c
by Stefan Reinauer 30 Sep '03

30 Sep '03

Hi, the amd64 boards all have the "static_devices.c" file but it is not used by any of them, instead the resulting object file is commented out in the config file. Can it safely be removed, or will this code come back to life? I also saw there are some old config method files lying around. Using the old config method is discouraged. Is there anything speaking against removing these files? Keeping no obsolete files in the tree makes it a lot easier to get into the code for new developers. Thus, if there are no major reasons against this, I will drop those files in a while. Stefan -- Architecture Team SuSE Linux AG

3 3

V2 committers
by ron minnich 30 Sep '03

30 Sep '03

I notice a lot of see-sawing on Config.lb files. Please consider having multiple Config files for a given target. So, for example, you could have arima/hdama/Config.etherboot.lb arima/hdama/Config.kernel.lb and so on. Each Config tool should build to a different target directory, to make multiple concurrent builds easy. The the buildtarget tool can default to <target>/Config.lb, but a user can also specify (in future) <target>/<some-config> ron

1 0

V2 EPIA FIXED!
by ron minnich 30 Sep '03

30 Sep '03

Here's what I had to do. First, though, let me say: the new linuxbios architecture, while hard to get the hang of (learning curve) is very powerful. You can have a mainboard-specific pci scan function, and that's what I needed. I may put this as a generic thing into the pci device code. See below for how it works. Basically, for your mainboard, you provide a function that scans the root of the "mainboard PCI" tree. ron Here goes ================ #include <console/console.h> #include <device/device.h> #include <device/pci.h> #include <device/pci_ids.h> #include <device/pci_ops.h> #include <arch/io.h> #include <device/chip.h> #include "chip.h" static int mainboard_scan_bus(device_t root, int maxbus) { int retval; printk_spew("%s: root %p maxbus %d\n", __FUNCTION__, root, maxbus); retval = pci_scan_bus(root->bus, 0, 0xff, maxbus); printk_spew("DONE %s: return %d\n", __FUNCTION__, maxbus); return maxbus; } static struct device_operations mainboard_operations = { .read_resources = root_dev_read_resources, .set_resources = root_dev_set_resources, .enable_resources = enable_childrens_resources, .init = 0, .scan_bus = mainboard_scan_bus, .enable = 0, }; static void enumerate(struct chip *chip) { struct chip *child; dev_root.ops = &mainboard_operations; chip->dev = &dev_root; chip->bus = 0; for(child = chip->children; child; child = child->next) { child->bus = &dev_root.link[0]; } } struct chip_control mainboard_via_epia_control = { .enumerate = enumerate, .name = "VIA EPIA mainboard ", };

3 4

v2 epia
by ron minnich 29 Sep '03

29 Sep '03

this is bad: Read config 32 bus 1,devfn 0x0,reg 0x18,val 0xffffffff 1:0.0 register 18.l is all ffffffff. Very bad, it should be 010100 Stefan, what was that about hardware bugs again? ron

2 2

V2 issue
by ron minnich 29 Sep '03

29 Sep '03

not sure why yet but ... all functions other than 0 are not having their OPS set correctly. ron

2 4

Re: config tool + tree enumeration
by YhLu 29 Sep '03

29 Sep '03

Alan, K8 support is in freebios2 instead. Regards YH. -----邮件原件----- 发件人: Alan Mimms [mailto:a.mimms@f5.com] 发送时间: 2003年9月29日 11:14 收件人: YhLu; ron minnich 抄送: Stefan Reinauer; Eric W. Biederman; linuxbios(a)clustermatic.org 主题: RE: config tool + tree enumeration Hello Lu, Is there anything in CVS yet for K8 CPU support? I didn't see anything a week or so ago. The AMD folks say it's there and "production level". ? Thanks. Alan Mimms, Senior Architect F5 Networks, Inc. Spokane Development Center Liberty Lake, Washington v: 509-343-3524 f: 509-343-3501

1 0

RE: config tool + tree enumeration
by Alan Mimms 29 Sep '03

29 Sep '03

Hello Lu, Is there anything in CVS yet for K8 CPU support? I didn't see anything a week or so ago. The AMD folks say it's there and "production level". ? Thanks. Alan Mimms, Senior Architect F5 Networks, Inc. Spokane Development Center Liberty Lake, Washington v: 509-343-3524 f: 509-343-3501 -----Original Message----- From: YhLu [mailto:YhLu@tyan.com] Sent: Monday, September 29, 2003 10:06 AM To: ron minnich Cc: Stefan Reinauer; Eric W. Biederman; linuxbios(a)clustermatic.org Subject: Re: config tool + tree enumeration Ron, In s2880, If I don't change the 0 to 1. I will get two copy of bus1 devices in the Linux. In S2885, it is OK, if I don't change it. In Arima, You still can not see bus1 device now? Regards Yinghai Lu -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年9月29日 10:00 收件人: YhLu 抄送: Stefan Reinauer; Eric W. Biederman; linuxbios(a)clustermatic.org 主题: Re: config tool + tree enumeration On Mon, 29 Sep 2003, YhLu wrote: > Stefan, > > >It's bus 1, that LinuxBIOS and OpenBIOS > >find really well, only Linux refuses to see it. > > Do you update the irq_table.c's interrupt router bus no. from to "0" to "1"? that's not the problem. The problem is that linux does not see bus 1 at all. ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

Re: config tool + tree enumeration
by YhLu 29 Sep '03

29 Sep '03

Ron, In s2880, If I don't change the 0 to 1. I will get two copy of bus1 devices in the Linux. In S2885, it is OK, if I don't change it. In Arima, You still can not see bus1 device now? Regards Yinghai Lu -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年9月29日 10:00 收件人: YhLu 抄送: Stefan Reinauer; Eric W. Biederman; linuxbios(a)clustermatic.org 主题: Re: config tool + tree enumeration On Mon, 29 Sep 2003, YhLu wrote: > Stefan, > > >It's bus 1, that LinuxBIOS and OpenBIOS > >find really well, only Linux refuses to see it. > > Do you update the irq_table.c's interrupt router bus no. from to "0" to "1"? that's not the problem. The problem is that linux does not see bus 1 at all. ron

2 1

V2 and epia
by ron minnich 29 Sep '03

29 Sep '03

I really think that if you are working on EPIA-*, you should make the cut to V2. I need the help. The port is going to be a much better job, and we won't have to keep fighting hacks in assembly code. Things that need looking at right now: - vt8231 early spd code - pci bus set up - northbridge and southbridge enumeration I feel very strongly that if we get EPIA done, EPIA-M will be pretty easy. So please consider making the move. ron

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot