> So what do you say. Can we use my patch to allow the user to override the VESA > detected memory size... or does anyone else have a better plan? It seems a passable solution. The mtrr bug is real either way and wants a fix. If the 2Mb reporting is wrong perhaps they will fix the bios ;) - 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