-=da TRoXX=- wrote:
> and i don't get it, who accepts these parameters in the kernel then? i mean
> if i put them in lilo.conf at least SOME thing uses them to set the
> framebuffer right...
The tdfxfb code does. When compiled into the kernel, there is a function
(tdfxfb_setup) which the ke
> I used to compile-in my framebuffer-device in the kernel
> then i just appended "video=tdfxfb:1024x768-32@70" in lilo.conf and it
> worked..
> now i compiled it as a module, and want modprobe to start it up for me..
> how can this be done?
> modprobe tdfxfb 1024x768-32@70
That's a very good que
David Wragg wrote:
> Something like this would be better:
> if (mtrr_add(video_base, temp_size, MTRR_TYPE_WRCOMB, 1) == -EINVAL) {
> /* Find the largest power-of-two */
> while (temp_size & (temp_size - 1))
> temp_sze &= (temp_size - 1);
> mtrr_add(video_ba
Gerd Knorr wrote:
> Well, vesafb really depends on what the vesa bios says...
Exactly my problem. In my laptop, I have a NeoMagic 2160 which does not have use
the last 64k of video for sound buffer like the NeoMagic 256es do yet it still
reports that the memory is not video memory. Both XF
Alan Cox wrote:
> > 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
tem so be careful! Syntax is mem=XXX[kKmM]
Have fun!
@@ -156,3 +162,4 @@
Minor (mostly typo) changes
by Nico Schmoigl <[EMAIL PROTECTED]>
+mem option added by Bryan Mayland <[EMAIL PROTECTED]>
diff -urN linux-orig/drivers/video/vesafb.c linux/drivers/video/vesafb.c
--- linux-orig/driv
g ywrap
+ every time the end of the memory is reached. If you enter a
+ value here larger than you actually have, you will more than
+ likely lock your system so be careful! Syntax is mem=XXX[kKmM]
Have fun!
@@ -156,3 +162,4 @@
Minor (mostly typo) changes
by Nico Schmoigl <[EMAIL PROTEC
7 matches
Mail list logo
