Re: [COMMIT] freebios2 How much have I broken?

[YhLu]

Eric,

Still can not enumerate 8151.

Regards

YH

LinuxBIOS-1.1.52.0_Fallback Tue Oct 14 01:39:52 EDT 2003 booting...
Finding PCI configuration type.
PCI: Using configuration type 1
Enumerating: AMD K8 Northbridge
Enumerating: AMD K8 Northbridge
Enumerating: AMD K8
Enumerating: AMD K8
Enumerating: AMD 8111
Enumerating buses...PCI: pci_scan_bus for bus 0
PCI: 00:18.0 [1022/1100] enabled
PCI: 00:18.1 [1022/1101] enabled
PCI: 00:18.2 [1022/1102] enabled
PCI: 00:18.3 [1022/1103] ops
PCI: 00:18.3 [1022/1103] enabled
PCI: 00:19.0 [1022/1100] enabled
PCI: 00:19.1 [1022/1101] enabled
PCI: 00:19.2 [1022/1102] enabled
PCI: 00:19.3 [1022/1103] ops
PCI: 00:19.3 [1022/1103] enabled
amdk8_scan_chains max: 0 starting...
Hyper transport scan link: 0 max: 1
Missing static device: PCI: 01:00.0
PCI: pci_scan_bus for bus 1
PCI: 01:00.0 [ffff/ffff/00ffff] has unknown header type ff, ignoring.
PCI: 01:00.0 No device operations
PCI: 01:01.0 [ffff/ffff/00ffff] has unknown header type ff, ignoring.
PCI: 01:01.0 No device operations
PCI: pci_scan_bus returning with max=01
Hyper transport scan link: 0 new max: 1
Hypertransport scan link done
Hyper transport scan link: 2 max: 2
PCI: 02:01.0 [1022/7450] enabled next_unitid: 0003
PCI: 02:03.0 [1022/7460] enabled next_unitid: 0007
PCI: pci_scan_bus for bus 2
PCI: 02:01.0 [1022/7450] bus ops
PCI: 02:01.0 [1022/7450] enabled
PCI: 02:01.1 [1022/7451] ops
PCI: 02:01.1 [1022/7451] enabled
PCI: 02:02.0 [1022/7450] bus ops
PCI: 02:02.0 [1022/7450] enabled
PCI: 02:02.1 [1022/7451] ops
PCI: 02:02.1 [1022/7451] enabled
PCI: 02:03.0 [1022/7460] enabled
PCI: 02:04.0 [1022/7468] bus ops
PCI: 02:04.0 [1022/7468] enabled
PCI: 02:04.1 [1022/7469] ops
PCI: 02:04.1 [1022/7469] enabled
PCI: 02:04.2 [1022/746a] enabled
PCI: 02:04.3 [1022/746b] ops
PCI: 02:04.3 [1022/746b] enabled
PCI: 02:04.5 [1022/746d] enabled
amd8111_enable dev: PCI: 02:04.6 lpc_dev: PCI: 02:04.0 index: 6 reg: ffff ->
ffbf done
PCI: 02:04.6 [ffff/ffff] disabled
PCI: pci_scan_bus for bus 3
PCI: 03:09.0 [14e4/16a7] ops
PCI: 03:09.0 [14e4/16a7] enabled
PCI: pci_scan_bus returning with max=03
PCI: pci_scan_bus for bus 4
PCI: pci_scan_bus returning with max=04
PCI: pci_scan_bus for bus 5
PCI: 05:00.0 [1022/7464] ops
PCI: 05:00.0 [1022/7464] enabled
PCI: 05:00.1 [1022/7464] ops
PCI: 05:00.1 [1022/7464] enabled
PCI: 05:00.2 [1022/7463] ops
PCI: 05:00.2 [1022/7463] enabled
amd8111_enable dev: PCI: 05:01.0 lpc_dev: PCI: 02:04.0 index: 9 reg: ffbf ->
fdbf done
PCI: 05:01.0 [ffff/ffff] disabled
PCI: 05:0b.0 [1095/3114] ops
PCI: 05:0b.0 [1095/3114] enabled
PCI: 05:0c.0 [104c/8023] ops
PCI: 05:0c.0 [104c/8023] enabled
PCI: pci_scan_bus returning with max=05
PCI: pci_scan_bus returning with max=05
Hyper transport scan link: 2 new max: 5
Hypertransport scan link done
amdk8_scan_chains max: 5 done
amdk8_scan_chains max: 5 starting...
amdk8_scan_chains max: 5 done
PCI: pci_scan_bus returning with max=05
done

-----邮件原件-----
发件人: [e-mail] [mailto:[e-mail]] 
发送时间: 2003年10月13日 18:57
收件人: YhLu
抄送: LinuxBIOS
主题: Re: [COMMIT] freebios2 How much have I broken?

YhLu  writes:
> Eric,
>
> After changed to following,
>    PCI_ADDR(0, 0x18, 1, 0xE0), 0x0000FC88, 0x00000003,
>    PCI_ADDR(0, 0x18, 1, 0xE4), 0x0000FC88, 0x00000000,
>    PCI_ADDR(0, 0x18, 1, 0xE8), 0x0000FC88, 0x00000000,
>    PCI_ADDR(0, 0x18, 1, 0xEC), 0x0000FC88, 0x00000000,

Make that:
> PCI_ADDR(0, 0x18, 1, 0xE0), 0x0000FC88, 0x00000203,
>    PCI_ADDR(0, 0x18, 1, 0xE4), 0x0000FC88, 0x00000000,
>    PCI_ADDR(0, 0x18, 1, 0xE8), 0x0000FC88, 0x00000000,
>    PCI_ADDR(0, 0x18, 1, 0xEC), 0x0000FC88, 0x00000000,

So it still goes out link 2 to the amd8111.

Eric

[COMMIT] freebios2 How much have I broken?

YhLu  writes:
> Eric,
>
> Still can not enumerate 8151.

Ok.  Well at least it worked well enough to initialize memory.
Thanks for looking at this.

I just really want to understand why you have trouble with the 8151.
If I can find a reasonable explanation on why you need to do it in a
special magic order I don't mind.  But without that I am a very
nervous about putting in any kind of bug fix.

I am still hopeful that it is a routing issue and my less hackish
fix will handle it.  But it does not seem especially likely at the moment.

Eric