> There is a mistake in the Makefile of drivers/char/agp, the line concerning
> i7x05-agp support does not match the one in the Kconfig, thus e7x05 support
> is never compiled, be it as a module or in the kernel.
I'm really amazed. This has been broken for months, and no-one noticed.
The day I fixed it in the agpgart bk tree, I got a half dozen reports,
and now I'm getting one daily. Truly bizarre.
> The last problem is more important and I have yet to find a solution. It seems
> like the driver stores device 0 in his agp_bridge->dev (0x255d for E7205,
> 0x2550 for E7505) but it uses registers from device 1 (0x2552) thus the
> chipset cannot be configured properly. The fetch_size function fails to
> determine aperture size.
Yep, the other issues (compile problems) are fixed up and will be going
to Linus real soon now, this problem though is something that is being
looked at by Matt (i7x05 gart driver author) right now.
Hopefully that'll also get fixed up with the changes being readied for 2.5.67
The reason i7x05 does things differently is that the generic-3.0 code
looks at the devices hanging of the device 0 (in that case, agp gfx cards).
I realised last week that the generic code is broken, as every other
agp chipset has the agp cards as secondaries of the agp bridge, not the
host bridge. Rather than fudge things like this, it looks like a lot
of the generic-3.0 stuff will be ripped out. It doesn't really work
properly, and is of questionable use.
> Sorry if this is redundant and is already being looked at.
No problem 8-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/