Eric,
The same.
One Clue: Even I do the reverse scan, if I enable the hard_reset in the misc_control.c. After the reset and successful scan the 8131/8111, it will hang when scan the 8151.
Regards
YH
-----邮件原件----- 发件人: YhLu 发送时间: 2003年10月13日 20:00 收件人: ebiederman@lnxi.com 抄送: LinuxBIOS 主题: Re: [COMMIT] freebios2 How much have I broken?
One minute.
-----邮件原件----- 发件人: ebiederman@lnxi.com [mailto:ebiederman@lnxi.com] 发送时间: 2003年10月13日 20:07 收件人: YhLu 抄送: LinuxBIOS 主题: Re: 答复: [COMMIT] freebios2 How much have I broken?
YhLu YhLu@tyan.com writes:
I think Stephan will have trouble on it too.
For me, If I reverse scan in northbridge.c, and it will be OK.
A) the reverse scan works and that is good.
It seems that 8131/8111 need to initialize before others.
Why? This is what I am trying to understand. It doesn't make sense especially as I already did that, earlier. The resets to get the hypertransport settings to take effect. I can see those depending on the amd8111.
Have you tried the small subroutine change I sent?
Eric _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
YhLu YhLu@tyan.com writes:
Eric,
The same.
Does this mean when the code looks as the device on bus 1 it sees 0xffff for the vendor and device id.
One Clue: Even I do the reverse scan, if I enable the hard_reset in the misc_control.c. After the reset and successful scan the 8131/8111, it will hang when scan the 8151.
Hmm. Thanks for looking at this.
I wonder if we might not have link speed/width configuration issues.
The code should be computing it properly but...
That is certainly what the second case sounds like. I had forgotten that i need to delay the reset until we are done with all of the hypertransport chains.
Hmm. I wonder if I am tripping up an 8151 errata.
Eric