[lkml]   [2001]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init
> 1)  The amount of video memory is being incorrectly reported my the VESA call
> used in arch/i386/video.S (INT 10h AX=4f00h). My Dell Inspiron 3200 (NeoMagic
> video) returns that it has 31 64k blocks of video memory, instead of the
> correct 32. This means that vesafb thinks that I've got 1984k of video ram,

You have 31. The last one is used for audio buffering

> 2) When the vesafb goes to mtrr_add its range (with the incorrect 1984k size)
> mtrr_add fails with -EINVAL. The code in vesafb_init then goes into a while
> loop with no exit, as each size mtrr fails.
> while (mtrr_add(video_base, temp_size, MTRR_TYPE_WRCOMB,
> 1)==-EINVAL) {
> temp_size >>= 1;
> }

Ok that one is the bug.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.080 / U:1.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site