coreboot November 2004

coreboot@coreboot.org

31 participants
183 discussions

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

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

04 Nov '04

I modified some debug func. chip drivers/generic/debug device pnp 0.0 on end # print parent name device pnp 0.1 off end # print PCI regs device pnp 0.2 off end # print mem device pnp 0.3 on end # print msr ? end but it only can be put under device with scan_static_bus calling. Such as dev_root and lpc. Regards YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, November 04, 2004 4:09 PM To: YhLu Cc: LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? On Thu, 2004-11-04 at 17:13, YhLu wrote: > Then every device will need do scan_static_bus. > > Also the debug device need to find his parent.... > Why ?? Ollie

1 0

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

04 Nov '04

OK for me. Some line I want to use print mem or pci at the end of LinuxBIOS can not be used now. Eric removed the CHIP_PASS.... Regards YH -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, November 04, 2004 9:07 AM To: YhLu; LinuxBIOS Subject: Removing device driver code in mainboard.c for Tyan boards? YhLu, Now we have a totally new device driver architecture, could we remove those #if 0 #endf code in the mainboard.c for Tyan board? Ollie

4 3

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

04 Nov '04

Actually, Eric another link to dev_root and it's init will be called after all under dev_root link0. Regards YH -----Original Message----- From: Ronald G. Minnich [mailto:rminnich@lanl.gov] Sent: Thursday, November 04, 2004 12:27 PM To: YhLu Cc: Li-Ta Lo; LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? On Thu, 4 Nov 2004, YhLu wrote: > Some line I want to use print mem or pci at the end of LinuxBIOS can not be > used now. Eric removed the CHIP_PASS.... it was no longer needed I think. ron

2 1

Board hangs after soft_reset() in auto.c
by Liu Tao 04 Nov '04

04 Nov '04

Hello, My K8 board hangs after "ht reset -" is printed, the post card at 0x80 is reseted to 0xff, so I think 8111 has performed the RESET_L and LDTRST_L signal. On my board the LDTRST_L signal drives to the RESET_L pin of K8 and RESET# pin of 8131, is this routing OK? Does the RESET_L signal of K8 updates the ht freq/width during reseting the CPU? Is this a cold/hard reset to CPU? Regards, Liu Tao

2 2

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

04 Nov '04

Do you mean chip southbridge/amd/amd8111 chip drivers/generic/debug device pnp 0.0 on end # print parent .name amd8111 SB device pnp 0.1 on end # print parent PCI CS... device pnp 0.2 on end # othe debug... end device pci 0.0 on device pci 0.0 on end device pci 0.1 on end device pci 0.2 off end device pci 1.0 off end end device pci 1.0 on ...... -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, November 04, 2004 4:09 PM To: YhLu Cc: LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? On Thu, 2004-11-04 at 17:13, YhLu wrote: > Then every device will need do scan_static_bus. > > Also the debug device need to find his parent.... > Why ?? Ollie

2 1

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

04 Nov '04

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... YH CVS: ---------------------------------------------------------------------- CVS: Enter Log. Lines beginning with `CVS:' are removed automatically CVS: CVS: Committing in . CVS: CVS: Modified Files: CVS: src/mainboard/tyan/s2735/mainboard.c CVS: src/mainboard/tyan/s2850/mainboard.c CVS: src/mainboard/tyan/s2875/mainboard.c CVS: src/mainboard/tyan/s2880/mainboard.c CVS: src/mainboard/tyan/s2881/mainboard.c CVS: src/mainboard/tyan/s2882/mainboard.c CVS: src/mainboard/tyan/s2885/Config.lb CVS: src/mainboard/tyan/s2885/mainboard.c CVS: src/mainboard/tyan/s4880/mainboard.c CVS: src/mainboard/tyan/s4882/mainboard.c CVS: Added Files: CVS: src/drivers/generic/debug/Config.lb CVS: src/drivers/generic/debug/chip.h CVS: src/drivers/generic/debug/debug_dev.c CVS: ---------------------------------------------------------------------- -----Original Message----- From: Li-Ta Lo [mailto:ollie@lanl.gov] Sent: Thursday, November 04, 2004 1:35 PM To: YhLu Cc: LinuxBIOS Subject: RE: Removing device driver code in mainboard.c for Tyan boards? On Thu, 2004-11-04 at 14:22, YhLu wrote: > I want to print PCI regs after PCI device initialization. > > Where need to put the calling print_pci_regs_all? In hardwaremain ??? > Why don't you put the debug device into device/generic/debug ? And in the mainboard Config.lb you added chip device/generic/debug as the last chip. The device emuleration will call the methods of the debug device last. And you probably can dump PCI CS registers in different stages of the enumeration. Ollie

2 1

Just for Fun: 01/12/01 submission
by David Nicol 04 Nov '04

04 Nov '04

Just for Fun: 01/12/01: Submit your ideas for the best use of all the useless factory flash parts we've got laying around. Thesis: Glue on fishhooks and sell as lures Antithesis: Donate to elementary schools as a craft supply Synthesis: Outsource assembly of the fishing lures to child laborers -- David L Nicol "How cool is that?" -- Elgie

1 0

← Newer
1
...
10
11
12
13
14
15
16
...
19
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 November 2004