On Fri, Jun 23, 2006 at 01:35:49AM +0200, Andi Kleen wrote:
> On Thu, Jun 22, 2006 at 07:23:58PM -0400, Jeff Garzik wrote:
> > Andrew Morton wrote:
> > >I don't think Jeff has sent us an example .config, but I hit this a few
> > >times too, before we fixed it. I think this was all triggered by a Kconfig
> > >change in the AGP tree, so you wouldn't have seen it, but -mm did.
> >
> > 'make allmodconfig' on x86-64. You can create this .config yourself :)
> >
> > I think the tree suffers [sometimes due to me :(] when 'allyesconfig'
> > and 'allmodconfig' stop working.
>
> Yes, but they work in 2.6.17 right?
worked for me, it only broke as of .17-git2 or so.
> And nothing should have changed since 2.6.17 so far.
> But apparently something did. What was it?
(for the 3rd time today) INTEL_FB now builds on x86-64,
and selects AGP, so if INTEL_FB=m, AGP becomes =m too,
which breaks the select AGP which GART_IOMMU wants.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
