coreboot

coreboot@coreboot.org

11 participants
39713 discussions

RE: PCI_DOMAIN ??
by YhLu 05 Nov '04

05 Nov '04

Create dummy device, and assign devfn to it, then.... YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Wednesday, November 03, 2004 2:59 PM To: Eric W. Biederman Cc: LinuxBIOS Subject: Re: PCI_DOMAIN ?? On Wed, 2004-11-03 at 15:51, Eric W. Biederman wrote: > So my immediate suggestion would be to call pci_set_method from the pci_domain's > scan_bus method before it does anything. We can worry about the rest later. > Isn't the root_dev::scan_bus() called before pci_domain::scan_bus() ? What if root_dev::scan_bus() wants to access PCI CS ? Ollie _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Eric, If the chip_ops has no .name, then should use if CONFIG_CHIP_NAME config chip.h end also .c include that chip_ops #if CONFIG_CHIP_NAME ...chip_ops defininition #endif Regards Such as norththbridge, socket, mainboard(root). YH -----Original Message----- From: YhLu Sent: Friday, November 05, 2004 10:50 AM To: ebiederman(a)lnxi.com Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? What does "config chip.h" in Config.lb use for? It seems it is not necessary? Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 10:31 AM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > Forget about that. Ok. > Why separate root_complex from amdk8/northbridge.c to > root_complex/root_complex.c I haven't because the code is to intertwined in northbridge.c and it would be likely be a maintenance problem to do so. Eric _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Static.c include comes from it. YH -----Original Message----- From: YhLu Sent: Friday, November 05, 2004 10:44 AM To: 'ebiederman(a)lnxi.com' Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? What does "config chip.h" in Config.lb use for? It seems it is not necessary? Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 10:31 AM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > Forget about that. Ok. > Why separate root_complex from amdk8/northbridge.c to > root_complex/root_complex.c I haven't because the code is to intertwined in northbridge.c and it would be likely be a maintenance problem to do so. Eric

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

What does "config chip.h" in Config.lb use for? It seems it is not necessary? Regards YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, November 05, 2004 10:31 AM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > Forget about that. Ok. > Why separate root_complex from amdk8/northbridge.c to > root_complex/root_complex.c I haven't because the code is to intertwined in northbridge.c and it would be likely be a maintenance problem to do so. Eric

1 0

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Forget about that. Why separate root_complex from amdk8/northbridge.c to root_complex/root_complex.c YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, November 04, 2004 8:53 PM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > No, debug_dev can be PCI_DOMAIN and APIC's sibling and one child dev_root in > link0. So why the question about dev_root link 1 and 2? Eric

2 1

RE: Removing device driver code in mainboard.c for Tyan boards?
by YhLu 05 Nov '04

05 Nov '04

Share get_fx_devs and f1_read_config32? YH -----Original Message----- From: YhLu Sent: Friday, November 05, 2004 10:17 AM To: ebiederman(a)lnxi.com Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? Forget about that. Why separate root_complex from amdk8/northbridge.c to root_complex/root_complex.c YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, November 04, 2004 8:53 PM To: YhLu Cc: Ronald G. Minnich; Li-Ta Lo; LinuxBIOS Subject: Re: Removing device driver code in mainboard.c for Tyan boards? YhLu <YhLu(a)tyan.com> writes: > No, debug_dev can be PCI_DOMAIN and APIC's sibling and one child dev_root in > link0. So why the question about dev_root link 1 and 2? Eric _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

8131 and 8151 in static.c
by Li-Ta Lo 05 Nov '04

05 Nov '04

Eric, Why there is no struct southbridge_amd_amd8131_config or struct southbridge_amd_amd8151_config in ter static.c although we have chip southbridge/amd/amd8131 and chip southbridge/amd/amd8151 in the Config.lb? There is no struct chip_operations southbridge_amd_amd8131_ops nor struct chip_operations southbridge_amd_amd8151_ops nether. Ollie

3 2

[RFC] linuxbios autobuild
by Stefan Reinauer 05 Nov '04

05 Nov '04

Hi, What's missing in the linuxbios autobuild tool? Regression Testing ------------------ We might want to regularly (or even on checkin?) use abuild.sh to check the LinuxBIOS repository for consistency and open building lots.. Shall we have a mail sent to the mailinglist/cvs list regularly/on checkin? We definitely also want a web page with this information, maybe the tool should optionally generate HTML/XML reports? ... ? Resulting ROM images -------------------- There needs to be a way to specify a per build or at least per platform payload. Otherwise no bootable images will result. Once the images have been proven stable we could offer prebuilt images (or have a webfrontend that creates an image from 2 payloads and 2 linuxbios romimages.. too lion-hearted? Development ----------- I would love to see the rest of the target config files go away for default builds, or have the abuild tool create them easily on the fly. This could be nice for testing different scenarios during development as well as for end users that don't want to go edit the default configuration but still want a different payload etc.. Ideas? What's missing? Stefan

2 1

Re: linuxbios autobuild / regression testing
by Stefan Reinauer 05 Nov '04

05 Nov '04

* Eric W. Biederman <ebiederman(a)lnxi.com> [041105 10:45]: > > It seems no mainboard says "use LD" at all yet. Some still don't > > "use CC" but this is minor.. > > Actually what you should be looking for is "uses CROSS_COMPILE" > Currently we don't seem to call LD directly so as long as gcc can > find the proper one we are ok. Oops. Misassumption on my side. I just saw the defines on the compile command line: -DLINUXBIOS_LINKER='"GNU ld version 2.14.90.0.5 20030722 (SuSE Linux)"' -DLINUXBIOS_ASSEMBLER='"GNU assembler version 2.14.90.0.5 (x86_64-suse-linux) using BFD version 2.14.90.0.5 20030722 (SuSE Linux)"' Are these compiled in per default? > > What's the usual naming convention for the cross compiler and cross > > linker of a given platform? We also need to cope with multiple payloads > > if we want to be able to use the resulting binaries... (in an ideal > > world the next step would be to automatically flash them) > > I suspect that we will want to have a simple Config.lb in targets that > we can start with and add cross compiling and other options to. Hm. We're setting a lot of default options in Options.lb and some in Config.lb for the mainboards.. Is there room to place defaults for these specifics in there? > > ./abuild.sh -at arima/hdama > -a and -t sound like useful additions. -at doesn't seem to work btw. -a -t does though.. whatever. > Just don't forget that ultimately if we can fix the dependencies in the > tree we both -a and my caching of what actually built successfully > should be trivial. so far I deleted the linuxbios-builds directory most of the time before each build to make sure nothing old is keeping things from building correctly because I saw a place or two where things did not get rebuild though something changed in the source tree. With the rebuild of all motherboards currently being around 10 minutes on this machine speed did not really care for generating the reports along. This is different if the tool is used actively in each cycle during development.. > Note: I had to tweak the parser so it would work when I specified where the > linuxbios tree was. It was putting single quotes around the pathname > nad ls was not really fond of './freebios2/'/src/mainboard .... Oh,.. I had that problem too with the -t option.. Thanks for fixing this. I will remove the stupid tr -d workaround I used. Stefan

1 0

Technologic ts5300???
by ebiederman＠lnxi.com 05 Nov '04

05 Nov '04

There is the beginnins of a port but there is no sc520 code. What is the status of this? With nothing checked into the tree I cannot fix it along with everything else. Eric

3 8

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