coreboot October 2004

coreboot@coreboot.org

45 participants
197 discussions

RE: Freebios2 recovery progress... pci64 mem optimization
by YhLu 21 Oct '04

21 Oct '04

Another case Align big allocation at first base1: 0xe0000000 limit1: 0xfebfffff size: 0x10000000 align: 28 base2: 0xf0000000 limit2: 0xfebfffff size: 0x06a00000 align: 26 base1: 0xd8000000 limit1: 0xdfffffff size: 0x06a00000 align: 26 base2: 0xe0000000 limit2: 0xfebfffff size: 0x10000000 align: 28 PCI_DOMAIN: 0000 00 <- [0x0000001000 - 0x0000005fff] io PCI_DOMAIN: 0000 01 <- [0x00e0000000 - 0x00efffffff] prefmem PCI_DOMAIN: 0000 02 <- [0x00d8000000 - 0x00de9fffff] mem Align small allocation at first base1: 0xe0000000 limit1: 0xfebfffff size: 0x10000000 align: 28 base2: 0xf0000000 limit2: 0xfebfffff size: 0x06a00000 align: 26 base1: 0xe0000000 limit1: 0xf7ffffff size: 0x10000000 align: 28 base2: 0xf8000000 limit2: 0xfebfffff size: 0x06a00000 align: 26 PCI_DOMAIN: 0000 00 <- [0x0000001000 - 0x0000005fff] io PCI_DOMAIN: 0000 01 <- [0x00e0000000 - 0x00efffffff] prefmem PCI_DOMAIN: 0000 02 <- [0x00f8000000 - 0x00fe9fffff] mem Maybe need to compare the base to find out which one first. -----Original Message----- From: YhLu Sent: Thursday, October 21, 2004 3:57 PM To: ebiederman(a)lnxi.com Cc: LinuxBIOS Subject: RE: Freebios2 recovery progress... pci64 mem optimization Eric, In northbridge.c Another typo error /* If so place the one with the most stringent alignment first */ if (mem2->align > mem1->align) { struct resource *tmp; tmp = mem1; mem1 = mem2; mem2 = mem1; } /* Now place the memory as high up as it will go */ mem2->base = resource_max(mem2); mem1->limit = mem2->base - 1; mem1->base = resource_max(mem1); ----> /* If so place the one with the most stringent alignment first */ if (mem2->align > mem1->align) { struct resource *tmp; tmp = mem1; mem1 = mem2; mem2 = tmp; } /* Now place the memory as high up as it will go */ mem2->base = resource_max(mem2); mem1->limit = mem2->base - 1; mem1->base = resource_max(mem1); Another question is Should do align big allocation at first or align small first. It seems you should do align big allocation. Align big first base1: 0xd0000000 limit1: 0xfebfffff size: 0x18800000 align: 28 base2: 0xec000000 limit2: 0xfebfffff size: 0x06b00000 align: 26 base1: 0xd8000000 limit1: 0xdfffffff size: 0x06b00000 align: 26 base2: 0xe0000000 limit2: 0xfebfffff size: 0x18800000 align: 28 PCI_DOMAIN: 0000 00 <- [0x0000001000 - 0x0000005fff] io PCI_DOMAIN: 0000 01 <- [0x00e0000000 - 0x00f87fffff] prefmem PCI_DOMAIN: 0000 02 <- [0x00d8000000 - 0x00deafffff] mem Align small first base1: 0xd0000000 limit1: 0xfebfffff size: 0x18800000 align: 28 base2: 0xec000000 limit2: 0xfebfffff size: 0x06b00000 align: 26 base1: 0xd0000000 limit1: 0xf7ffffff size: 0x18800000 align: 28 base2: 0xf8000000 limit2: 0xfebfffff size: 0x06b00000 align: 26 PCI_DOMAIN: 0000 00 <- [0x0000001000 - 0x0000005fff] io PCI_DOMAIN: 0000 01 <- [0x00d0000000 - 0x00e87fffff] prefmem PCI_DOMAIN: 0000 02 <- [0x00f8000000 - 0x00feafffff] mem

1 0

RE: Makefile changes for symbols
by Rodney.Kittleson＠bench.com 21 Oct '04

21 Oct '04

Steve, What version of Source point are you using? The symbols are coming in but SourcePoint doesn't allow me to reference the source files. I mapped the linuxbios directory on my Win2000 system for SourcePoint to access. (I have samba running on my linux system) I just need to get SourcePoint working. Thanks, Rod -----Original Message----- From: Kimball, Stephen Sent: Wednesday, October 20, 2004 1:04 PM To: Kittleson, Rodney C.; linuxbios(a)clustermatic.org Cc: Jeff_Pitts(a)arium.com Subject: RE: Makefile changes for symbols The file under your target in normal/linuxbios_c.o seems to have all the symbols if you add "-gdwarf-2" to the $CFLAGS in the Makefile. Then when you open the first C module the SourcePoint software asks where the file exists, after you tell SourcePoint it seems to find the rest by itself. I recreated the same Linux directory structure on Windows. Thanks Rod! Steve -----Original Message----- From: Kittleson, Rodney C. Sent: Wednesday, October 20, 2004 11:47 AM To: Kimball, Stephen; linuxbios(a)clustermatic.org Subject: RE: Makefile changes for symbols Linuxbios_c, from the build directory, can be sucked into Sourcepoint to extract the symbols. This allows the disassembled instructions to display the symbols inline. It makes it easier to set breakpoints and follow the code, but it's a far cry from source level debugging. I haven't attempted to link the source with sourcepoint yet. I may try it later this week, let me know if you have any success. Rod -----Original Message----- From: Kimball, Stephen Sent: Tuesday, October 19, 2004 3:33 PM To: linuxbios(a)clustermatic.org Subject: Makefile changes for symbols Can someone give me the Makefile changes to make a LinuxBIOS with symbols? I tried adding "-gdwarf-2" to CFLAGS, but I'm not sure where the unstripped output would be. Are there any features in the code that are useful in debugging LinuxBIOS? Any defines that should change as well? Someone must have some experience with source code level debugging of LinuxBIOS with an American Arium ECM-50. Thanks. Steve Kimball Benchmark Electronics Hudson, NH _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Freebios2 recovery progress...
by YhLu 21 Oct '04

21 Oct '04

It's OK. PCI: 04:01.0 bridge ctrl <- 0003 PCI: 04:01.0 cmd <- 146 PCI: 05:04.0 cmd <- 142 PCI: 04:01.1 subsystem <- 10f1/2895 PCI: 04:01.1 cmd <- 146 PCI: 04:02.0 bridge ctrl <- 0003 PCI: 04:02.0 cmd <- 147 PCI: 06:06.0 cmd <- 143 PCI: 06:06.1 cmd <- 143 -----Original Message----- From: YhLu Sent: Thursday, October 21, 2004 12:11 PM To: 'ebiederman(a)lnxi.com' Cc: LinuxBIOS Subject: RE: Freebios2 recovery progress... I will test that on s2885. I suspect that will need MEM enable too. YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, October 21, 2004 11:39 AM To: YhLu Cc: LinuxBIOS Subject: Re: Freebios2 recovery progress... YhLu <YhLu(a)tyan.com> writes: > You can not test that in arima board. Because all device on 8131 is using > ioapic in amd8111. I can't test that it works but I can test that the bits are getting set by running lspci. And that is how I tested. The bus master bit is still getting set. I just move the location. Eric

1 0

RE: Tyan 488x
by YhLu 21 Oct '04

21 Oct '04

My fault. Need to change to 4. YH -----Original Message----- From: Stefan Reinauer [mailto:stepan@openbios.org] Sent: Thursday, October 21, 2004 12:52 PM To: YhLu Cc: 'LinuxBIOS' Subject: Tyan 488x In the Tyan 488x Option.lb files the maximum number of CPUs is set to 2. Is this on purpose? Stefan

1 0

Tyan 488x
by Stefan Reinauer 21 Oct '04

21 Oct '04

In the Tyan 488x Option.lb files the maximum number of CPUs is set to 2. Is this on purpose? Stefan

1 0

RE: FYI: Merge in progress...
by YhLu 21 Oct '04

21 Oct '04

Why just set subsystem id, in amd_8111.c enable_dev function? That would more easy. Need one switch case to figure out different reg position. Regards YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, October 21, 2004 11:18 AM To: Eric W. Biederman Cc: YhLu; 'Ronald G. Minnich'; 'LinuxBIOS' Subject: Re: FYI: Merge in progress... On Thu, 2004-10-21 at 12:00, Eric W. Biederman wrote: > At this point we should be able to look at the device tree and > see if we need to use and io range register or the RdRam WrDram bits. > Are you talking somthing in my mind ? I hope in the mtrr.c for K8 instead of hack with the mem_map we have: setup_mtrr() { if (search_for_vga_device_on_the_tree() == FOUND) { enable_rd_wr_mem_in_fixed_mtrr(); clear_rd_wr_mem_for_legacy_vga_buffer(); set_IORR_to_AGP_aperture(); } else { disable_rd_wr_mem(); } do_some_other_thigs(); } And the code is executed on each processors. Ollie

2 1

RE: Freebios2 recovery progress...
by YhLu 21 Oct '04

21 Oct '04

I will test that on s2885. I suspect that will need MEM enable too. YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, October 21, 2004 11:39 AM To: YhLu Cc: LinuxBIOS Subject: Re: Freebios2 recovery progress... YhLu <YhLu(a)tyan.com> writes: > You can not test that in arima board. Because all device on 8131 is using > ioapic in amd8111. I can't test that it works but I can test that the bits are getting set by running lspci. And that is how I tested. The bus master bit is still getting set. I just move the location. Eric

1 0

RE: Freebios2 recovery progress...
by YhLu 21 Oct '04

21 Oct '04

No., Onboard scsi subsystem id should be same to others. -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, October 21, 2004 11:21 AM To: Eric W. Biederman Cc: YhLu; LinuxBIOS Subject: Re: Freebios2 recovery progress... On Thu, 2004-10-21 at 11:56, Eric W. Biederman wrote: > > The .set_subsystem simply exists because there is not > a standard way to set that value. The almost generic > version is in src/devices/pci_device.c but I can use > it only occasionally. > > > device pci 0.0 on > > vendor 0x1234 > > device 0x5678 > > end > > > > or > > > > device pci 0.0 on > > register "subsystem_vendor_id" = "0x1234" > > register "subsystem_device_id" = "0x5678" > > end > > I don't see the benefit of those methods over having > an Option if you have exactly 1 subsystem vendor_id+device_id that > need to be set. > YhLu's intention is to set subsystem ID differently for each devices on the mainboard. It is totally the opposite to what you want and doing. Ollie

2 1

RE: Freebios2 recovery progress...
by YhLu 21 Oct '04

21 Oct '04

Driver add < static void lpci_set_subsystem(device_t dev, unsigned vendor, unsigned device) < { < pci_write_config32(dev, 0x2c, < ((device & 0xffff) << 16) | (vendor & 0xffff)); < } < < static struct pci_operations lops_pci = { < .set_subsystem = lpci_set_subsystem, < }; -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, October 21, 2004 9:31 AM To: Eric W. Biederman Cc: LinuxBIOS Subject: Re: Freebios2 recovery progress... On Thu, 2004-10-21 at 05:08, Eric W. Biederman wrote: > I have managed to get another chunk of merging and bug fixing > done tonight. > > I now have pci subsystem vendor and subsystem id's being set on > the arima hdama, so the board is now identifiable with lspci. > How did you do that ? Where do you put those IDs ? Ollie _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

4 5

RE: Freebios2 recovery progress...
by YhLu 21 Oct '04

21 Oct '04

You may remove .enable = amd8111_enable, It will be called twice. One in enable_dev. -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, October 21, 2004 10:46 AM To: YhLu; Li-Ta Lo Cc: LinuxBIOS Subject: Re: Freebios2 recovery progress... Li-Ta Lo <ollie(a)lanl.gov> writes: > How did you do that ? Where do you put those IDs ? YhLu <YhLu(a)tyan.com> writes: > You changes all mb config for AMD/Iwill/IBM....that took some time. > > If there is on board scsi, I want to set subsystem id, I need to put that in > Config.lb? Or more likely src/mainboarod/???/???/Options.lb src/devices/pci_device.c:pci_dev_enable_resources() calls dev->ops->pci_ops->set_subsystem() when the device dev->on_mainboard is true. In turn config.g sets that in static.c for all devices in the static tree. I believe those are the correct semantics. That the subsystem is essentially an identifier for the board the chips are sitting on. The values are come from: Look at MAINBOARD_PCI_SUBSYSTEM_VENDOR_ID and MAINBOARD_SUBSYSTEM_DEVICE_ID. So for the onboard scsi case you likely need to have a driver for the onboard scsi device that implements the set_subsystem method because there is not a generic way of doing that. Eric

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
20
Older →

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 October 2004