coreboot

coreboot@coreboot.org

11 participants
39713 discussions

RE: Board hangs after soft_reset() in auto.c
by YhLu 05 Nov '04

05 Nov '04

Which stage auto.c E0: 0xff010003 --> 0x06000003 E4: 0x09070103 --> 0x09070103 E8: --> 0x0c0a0203 YH -----Original Message----- From: Liu Tao [mailto:liutao@safe-mail.net] Sent: Thursday, November 04, 2004 8:31 PM To: YhLu Cc: Eric W. Biederman; LinuxBIOS Subject: Re: Board hangs after soft_reset() in auto.c I mean when enumerating HT0 e0 is set to 0xff010003, while e4 matains 0x09070103, so e4 overlaps with e0? Regards, Liu Tao YhLu wrote: >That only used by auto.c (in_conherent.c) > >And it is ok to be overlapped in c parts. ( hardwaremain)? > >To do that, only let cpu can see different BUS in auto.c stage. >

2 1

make -j4 ?
by Stefan Reinauer 05 Nov '04

05 Nov '04

Hi, just noticed on my way to bed.. it seems make -j does work fine for the single linuxbios images (fallback / normal) but not for the concatenated final one because of a wrong dependency: ------------------------------ 8< ----------------------------- all: fallback-rom normal-rom buildroms fallback-rom: if (cd fallback; \ make linuxbios.rom)\ then true; else exit 1; fi; normal-rom: if (cd normal; \ make linuxbios.rom)\ then true; else exit 1; fi; buildroms: cat normal/linuxbios.rom fallback/linuxbios.rom > ./amd_quartet.rom ------------------------------ 8< ----------------------------- should look like: all: buildroms [..] buildroms: fallback-rom normal-rom Otherwise make assumes it can build all three of fallback-rom, normal-rom and buildroms in parallel Stefan

2 1

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

04 Nov '04

No, debug_dev can be PCI_DOMAIN and APIC's sibling and one child dev_root in link0. YH -----Original Message----- From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] Sent: Thursday, November 04, 2004 8:29 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: > Great. That will be very clear. > > Then > chip northbridge/amd/amk8/root_complex > > .. > > End # ----> dev_root link0 > chip northbridge/amd/amk8/root_complex > > .. > > End # ----> dev_root link1 > > chip northbridge/amd/amk8/root_complex > > .. > > End # ----> dev_root link2 And what do you want on link1 and link2 for the root_device? Among other things I'm not certain config.g currently supports that. Is this just for placing the debug devices far away? Eric

2 1

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

04 Nov '04

Great. That will be very clear. Then chip northbridge/amd/amk8/root_complex .. End # ----> dev_root link0 chip northbridge/amd/amk8/root_complex .. End # ----> dev_root link1 chip northbridge/amd/amk8/root_complex .. End # ----> dev_root link2

2 1

RE: Board hangs after soft_reset() in auto.c
by YhLu 04 Nov '04

04 Nov '04

That only used by auto.c (in_conherent.c) And it is ok to be overlapped in c parts. ( hardwaremain)? To do that, only let cpu can see different BUS in auto.c stage. Regards YH -----Original Message----- From: Liu Tao [mailto:liutao@safe-mail.net] Sent: Thursday, November 04, 2004 8:05 PM To: YhLu Cc: Eric W. Biederman; LinuxBIOS Subject: Re: Board hangs after soft_reset() in auto.c Can this cause configuration regions overlap with each other during device enumeration? In amdk8_scan_chains() the subordinate/limit field of current register is set to 0xff before hypertransport_scan_chain(), while other following registers are not touched yet, so they overlay with current register? Regards, Liu Tao > > PCI_ADDR(0, 0x18, 1, 0xE0), 0x0000FC88, 0x06000203, // AMD 8131/8111 on >link0 of CPU 0 > PCI_ADDR(0, 0x18, 1, 0xE4), 0x0000FC88, 0x09070003, // AMD 8131 on link1 >of CPU 0 > PCI_ADDR(0, 0x18, 1, 0xE8), 0x0000FC88, 0x0c0a0003, // AMD 8131 on link2 >of CPU 0 > PCI_ADDR(0, 0x18, 1, 0xEC), 0x0000FC88, 0x00000000, >

2 1

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

04 Nov '04

and Mainboard on ..... End Mainboard on ... End To put them into dev_root links YH -----Original Message----- From: YhLu Sent: Thursday, November 04, 2004 8:01 PM 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? chip northbridge/amd/amdk8 device pci_domain 0 on device pci 18.0 on # LDT0 . .... End .... chip northbridge/amd/amdk8 device pci 19.0 end ... End End # PCI domain .....acpic... End # NB K8 It looks strang, Why not thang that to followings? device pci_domain 0 on chip northbridge/amd/amdk8 device pci 18.0 on # LDT0 . .... End .... End #NB K8 chip northbridge/amd/amdk8 device pci 19.0 end ... End End # PCI domain .....apic.... _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

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

04 Nov '04

chip northbridge/amd/amdk8 device pci_domain 0 on device pci 18.0 on # LDT0 . .... End .... chip northbridge/amd/amdk8 device pci 19.0 end ... End End # PCI domain .....acpic... End # NB K8 It looks strang, Why not thang that to followings? device pci_domain 0 on chip northbridge/amd/amdk8 device pci 18.0 on # LDT0 . .... End .... End #NB K8 chip northbridge/amd/amdk8 device pci 19.0 end ... End End # PCI domain .....apic....

2 1

RE: Board hangs after soft_reset() in auto.c
by YhLu 04 Nov '04

04 Nov '04

It seems that you only have one CPU. Then without ht_optimize_link in in_conherent.c you even don't need to do soft_reset. What's the value in you resource_map.c? You need update that to PCI_ADDR(0, 0x18, 1, 0xE0), 0x0000FC88, 0x06000203, // AMD 8131/8111 on link0 of CPU 0 PCI_ADDR(0, 0x18, 1, 0xE4), 0x0000FC88, 0x09070003, // AMD 8131 on link1 of CPU 0 PCI_ADDR(0, 0x18, 1, 0xE8), 0x0000FC88, 0x0c0a0003, // AMD 8131 on link2 of CPU 0 PCI_ADDR(0, 0x18, 1, 0xEC), 0x0000FC88, 0x00000000, In the auto.c static const struct ht_chain ht_c[] = { { /* Link 0 of CPU0 */ .devreg = 0xe0, /* Preset bus num in resource map */ }, { /* Link 1 of CPU0 */ .devreg = 0xe4, /* Preset bus num in resource map */ }, { /* Link 2 of CPU0 */ .devreg = 0xe8, /* Preset bus num in resource map */ }, }; Regards YH -----Original Message----- From: Liu Tao [mailto:liutao@safe-mail.net] Sent: Thursday, November 04, 2004 6:11 PM To: Eric W. Biederman Cc: LinuxBIOS Subject: Re: Board hangs after soft_reset() in auto.c Thanks, after remove the ht_optimize_link() in ht_setup_chainx() the board soft resets OK. Eric W. Biederman wrote: > >The short answer is that optimizing the hypertransport speed and frequency >is an optimization. So you can disable the reset and see how far you board >gets otherwise. That should give you a little more time to debug the reset path. > Regards, Liu Tao _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 2

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

04 Nov '04

Then every device will need do scan_static_bus. Also the debug device need to find his parent.... YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, November 04, 2004 3:26 PM To: YhLu Cc: LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? On Thu, 2004-11-04 at 15:44, YhLu wrote: > debug device added > > chip drivers/generic/debug > device pnp 0.0 on end > end > > debug device will be sibling to PCI_DOMAIN and APIC_CLUSTER... > Cool, that is exactly what I want. Actually by defining different debug devices, we can construct different 'probes' into the device space. We can either probe software data structures or the real hardware and we can do it at different phases of the device enumeration as we want. For example, the current debug device (pnp 0.0) dumps the PCI CS registers at the end of device enumeration. We can define another debug device to show the topology of the device tree or just print the famous .name field ;-). The best thing about the debug device is it totally extensible and plug/unplugable. We don't have to add any code to the existing device driver nor the hardwaremain(). It is decoupled from the rest of LinuxBIOS. The operations we need to act on the (normal) devices are encapsulated in the debug device. Ollie

3 2

PCI_DOMAIN ??
by Li-Ta Lo 04 Nov '04

04 Nov '04

Eric, >From my memory of the LXNI visit, the pci_domain represents different ways to access PCI CS (0xcf8, 0xcfc). So the very low level of PCI access method will be different depends on the domain. Now the question is why not the pci_set_method() a device method of the PCI_DOMAIN device ? It is in the hardwarmain() now. Ollie

3 10

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