S2885

YhLu YhLu at tyan.com
Tue Oct 26 15:28:01 CEST 2004


Comment out

//      resource->limit = info->mask | (step - 1);

In pnp_get_ioresource

Will make it works right.

Regards

YH

-----Original Message-----
From: YhLu 
Sent: Tuesday, October 26, 2004 1:12 PM
To: ebiederman at lnxi.com
Cc: Ronald G. Minnich; linuxbios at clustermatic.org
Subject: RE: S2885

You are right, after I comment out the superio section in Config.lb. it
allocate correct io range for device in amd8111 PCI bridge.

Regards

YH



-----Original Message-----
From: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
Sent: Tuesday, October 26, 2004 12:52 PM
To: YhLu
Cc: Ronald G. Minnich; linuxbios at clustermatic.org
Subject: Re: S2885

YhLu <YhLu at tyan.com> writes:

> Eric,
> 
> I find the device on amd8111 pci io allocation get werid. Please check
6:b.0
> and 6:c.0 io allocation. It comes from 0x0000, instead of 0x1000.

Agreed this is a bug.  

Currently the code updates the limit on bridges if all of the devices
behind the bridge cannot use that limit.  In theory that works
great in practice however it barely works.

With I/O devices typically the problem is typically superio chips
with a limit of 0xfff.
 
> It works well before you add set_subsystem.

set_subsystem has been there since somewhere the start of the merge.
Although all of the methods for the amd8111 and amd8131 were not.

I suspect this has more to do with the updated pnp device code,
which now correctly computes the limit address.  And thus messes
up the computation logic for everything else.  At least if the resource
is not set statically.

If this is what I think it is, except for hard coding the superio resources
I don't see a quick fix in the works.

Eric
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



More information about the coreboot mailing list