Then, the setup scripts tool should include that support and should have support for auto.c too.
YH
-----邮件原件----- 发件人: Stefan Reinauer [mailto:stepan@suse.de] 发送时间: 2003年8月29日 4:48 收件人: YhLu 抄送: linuxbios@clustermatic.org 主题: Re: Unified setup...
* YhLu YhLu@tyan.com [030828 23:36]:
PS:
PCI_ADDR(0, 0x18, 0, 0x94), 0xff0000ff, 0x00ff0000,
PCI_ADDR(0, 0x18, 0, 0x94), 0xff0000ff, 0x00050000,
[..]
PCI_ADDR(0, 0x18, 0, 0xd4), 0xff0000ff, 0x00000000,
PCI_ADDR(0, 0x18, 0, 0xd4), 0xff0000ff, 0x00030000,
should be there. It defines the bus number behind the links. It will be
used
when enumerating the non-coherent devices.
I agree. But maybe we find a nicer way of describing this.
Are these "hard coded" in hardware? The motherboard configuration should then probably contain a busnumber value for each ht bridge that implements a pci bus
southbridge amd/amd8131 "amd8131" register "bus0" = "5" end
southbridge amd/amd8151 "amd8151" register "bus0" = "3" end
Or should this be handled distinct from the bridges with options like option BUS1=99 option BUS2=5 ?
Stefan
* YhLu YhLu@tyan.com [030902 18:18]:
Then, the setup scripts tool should include that support and should have support for auto.c too.
YH
southbridge amd/amd8131 "amd8131" register "bus0" = "5" end
southbridge amd/amd8151 "amd8151" register "bus0" = "3" end
currently the code that is generated (static.c) consists all of global structs that are not directly usable with romcc code. looking at the needs of auto.c it might be worth it adding a new writeromccstructs definition that dumps into the right files and is only called "on architectures that have romcc support" ;)
When i.e. generating hypertransport routing tables it would be nice to have those directly generated in config.g. but then again, this adds up a lot of cpu dependent magic to the config tool. What about having part specific configuration output in src/<type>/<vendor>/<id>/config.py i.e. have the opteron northbridge specific code that creates ht tables and writes auto.c's mem_controller struct in src/northbridge/amd/amdk8/Config.py. That would keep the configuration utility reasonably small and enhancable while have the actual config file creator for each of the components at the same place as the other code parts belonging to that component.
Stefan