Messages in this thread | | | Subject | Re: [BUG]: agpgart for i810 chipsets broken in 2.5.51 | From | Antonino Daplas <> | Date | 10 Dec 2002 22:34:46 +0500 |
| |
On Tue, 2002-12-10 at 19:03, Dave Jones wrote: > On Tue, Dec 10, 2002 at 09:47:24PM +0500, Antonino Daplas wrote: > > btw, iirc you were the guy who wanted agpgart initialised sooner > due to the way the i810 framebuffer worked ? Yes.
> How much sooner are we talking ? What puzzles me, is looking Here's part of dmesg:
fb: Intel(R) 810 Framebuffer Device v0.9.0, Tony Daplas Video RAM : 4096K Mode : 1024x768-8bpp@67Hz Acceleration : enabled MTRR : enabled External VGA : disabled Video Timings : VESA GTF (US) Console: switching to colour frame buffer device 128x48 pty: 256 Unix98 ptys configured Real Time Clock Driver v1.11 Non-volatile memory driver v1.2 Linux agpgart interface v0.99 (c) Dave Jones agpgart: Detected an Intel i810 Chipset. agpgart: Maximum main memory to use for agp memory: 149M agpgart: AGP aperture is 64M @ 0xe8000000
> at the link order in the makefiles, agpgart should already be > getting initialised before the framebuffer code, but doesn't > seem to be for reasons unknown.. > I'm also not sure why, and even in .built-in.o.cmd, drivers/char is before drivers/video. Perhaps the early console_init()? I'll try to rebuild my kernel without the framebuffer console and let you know. > Another issue on this same case, is that for this to work out, > we'll need some kconfig magick so that if the framebuffer is 'Y' > rather than 'M' the i810 gart module must be forced to 'Y' too. > Yes, FB_I810 depends on AGP_INTEL, so the i810fb option is disabled if agpgart is disabled.
Tony
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |