> yywrap is a hack rather than generally safe feature and its not guaranteed that > your videoram wraps neatly. Really the driver should have spotted the hole I > guess. Well, vesafb really depends on what the vesa bios says... That's why it has all may-have-problems features turned off by default: no ywrap, no mtrr. At least it was this way last time I touched it. Gerd -- Get back there in front of the computer NOW. Christmas can wait. -- Linus "the Grinch" Torvalds, 24 Dec 2000 on linux-kernel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init Bryan Mayland
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on ini... Alan Cox
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on... Chris Kloiber
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... Steven Walter
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... David Wragg
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... Gerd Knorr
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on... Bryan Mayland
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... Alan Cox
- Re: [PATCH] VESA framebuffer w/ MTRR locks ... Gerd Knorr
- Re: [PATCH] VESA framebuffer w/ MTRR l... Bryan Mayland
- Re: [PATCH] VESA framebuffer w/MTRR locks 2.4.0 on ... David Wragg
- Re: [PATCH] VESA framebuffer w/MTRR locks 2.4.0... Bryan Mayland
- Re: Framebuffer as a module Bryan Mayland
- Re: Framebuffer as a module Bryan Mayland