linux-fbdev-users — Generic mailing list for users of frame buffers

[Linux-fbdev-users] Blanking the screen : EZFB

[James L. <ja...@ak...>]

Is there a way to ask the GPU on the video card to wipe out the data in the
visible area of the screen?
I have found it takes WAY to long to memset zeros to every line and keeping
track of only those pixels that have changed seems like more work than it's
worth.

http://www.akrobiz.com/ezfb
http://www.akrobiz.com/laserboy

Thanks!
Take care.   ~James.   :o)

Re: [Linux-fbdev-users] Endianness issues using the framebuffer

[James L. <ja...@ak...>]

Check this out!

EZFB
http://www.akrobiz.com/ezfb/

Please let me know what you think!

~James.   :o)




----- Original Message ----- 
From: "Roger Leigh" <rl...@wh...>
To: <lin...@li...>
Sent: Monday, June 27, 2005 4:46 PM
Subject: [Linux-fbdev-users] Endianness issues using the framebuffer


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi folks,
>
> I'm looking into writing a program which will use the framebuffer to
> display rendered fonts and some graphics.  However, I've not yet found
> much in the way of programming documentation.  Is there anything you
> would recommend?
>
> (I've looked at SDL, directfb and GGI sources, but they are very
> complex.)
>
> Using the comments in <linux/fb.h> and some simple examples I found,
> I've written the sample code below.  However, none of the examples I
> saw made any use of the fb_bitfield information.  I ran into problems
> when I tried my (i386 tested) code on a PPC.  After fixing the code,
> it still doesn't work.  I have the bizarre situation that if I run it
> under X11 (using XF86_FBDev), I see the glyphs rendered fine, but if I
> run it on the console the colours are mucked up, and I can't see any
> change in the bitfield data.
>
> Are there any examples of painting simple RGB pixel data onto any
> arbitrary framebuffer device which also works on big and little endian
> systems.  I'm sure this is fairly simple once you know how!
>
> Additionally, is there any documentation about how colourmaps and the
> other framebuffer features work?
>
>
> Many thanks,
> Roger
>
>
> This program simply renders each ASCII character in turn and paints
> it.  You might need to change the fb device and font path.  It's
> currently hard-coded for RBG LCDs, but is simple to change for a CRT.
>
> Compile with
> c99 -o ft-lcd ft-lcd.c `freetype-config --cflags --libs`
>
> #include <unistd.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <fcntl.h>
> #include <linux/fb.h>
> #include <sys/ioctl.h>
> #include <sys/mman.h>
>
> #include <ft2build.h>
> #include FT_FREETYPE_H
>
> void fail (const char *reason)
> {
>   fprintf (stderr, "%s\n", reason);
>   exit (EXIT_FAILURE);
> }
>
> int
> main()
> {
>   int fbfd = 0;
>   struct fb_var_screeninfo vinfo;
>   struct fb_fix_screeninfo finfo;
>   long int screensize = 0;
>   char *fbp = 0;
>   int x = 0, y = 0;
>   long int location = 0;
>
>   // Open the file for reading and writing
>   fbfd = open("/dev/fb/0", O_RDWR);
>   if (fbfd < 0)
>     fail("Error: cannot open framebuffer device.");
>
>   // Get fixed screen information
>   if (ioctl(fbfd, FBIOGET_FSCREENINFO, &finfo))
>     fail("Error reading fixed information.");
>
>   // Get variable screen information
>   if (ioctl(fbfd, FBIOGET_VSCREENINFO, &vinfo))
>     fail("Error reading variable information.");
>
>   printf("%ux%u (%ux%u), %ubpp\n", vinfo.xres, vinfo.yres,
> vinfo.xres_virtual, vinfo.yres_virtual, vinfo.bits_per_pixel );
>   printf("offsets: x=%u, y=%u\n", vinfo.xoffset, vinfo.yoffset);
>   printf("red: o=%u, l=%u, mr=%u\n", vinfo.red.offset, vinfo.red.length,
vinfo.red.msb_right);
>   printf("green: o=%u, l=%u, mr=%u\n", vinfo.green.offset,
vinfo.green.length, vinfo.green.msb_right);
>   printf("blue: o=%u, l=%u, mr=%u\n", vinfo.blue.offset,
vinfo.blue.length, vinfo.blue.msb_right);
>   printf("transp: o=%u, l=%u, mr=%u\n", vinfo.transp.offset,
vinfo.transp.length, vinfo.transp.msb_right);
>
>   unsigned int red_max = 1 << vinfo.red.length;
>   unsigned int green_max = 1 << vinfo.green.length;
>   unsigned int blue_max = 1 << vinfo.blue.length;
>   unsigned int transp_max = 1 << vinfo.transp.length;
>
>   unsigned int red_mask = 0;
>   for (unsigned int i=0; i<vinfo.red.length; ++i)
>     red_mask |= 1 << (vinfo.red.offset + i);
>   unsigned int green_mask = 0;
>   for (unsigned int i=0; i<vinfo.green.length; ++i)
>     green_mask |= 1 << (vinfo.green.offset + i);
>   unsigned int blue_mask = 0;
>   for (unsigned int i=0; i<vinfo.blue.length; ++i)
>     blue_mask |= 1 << (vinfo.blue.offset + i);
>   unsigned int transp_mask = 0;
>   for (unsigned int i=0; i<vinfo.transp.length; ++i)
>     transp_mask |= 1 << (vinfo.transp.offset + i);
>
>
>   // Figure out the size of the screen in bytes
>   screensize = vinfo.xres * vinfo.yres * vinfo.bits_per_pixel / 8;
>
>   // Map the device to memory
>   fbp = (char *)mmap(0, screensize, PROT_READ | PROT_WRITE, MAP_SHARED,
>      fbfd, 0);
>   if ((int)fbp == -1)
>     fail("Error: failed to map framebuffer device to memory.\n");
>
>   // Now setup FreeType
>   FT_Library library;
>   FT_Face face;
>
>   int error = FT_Init_FreeType( &library );
>   if ( error )
>     {
>       fail ("Failed to initialise FreeType");
>     }
>
>   error = FT_New_Face( library,
"/usr/share/fonts/truetype/ttf-bitstream-vera/VeraMono.ttf", 0, &face );
>   if ( error == FT_Err_Unknown_File_Format )
>     {
>       fail ("Unsupported font format");
>     }
>   else if ( error )
>     {
>       fail ("Error reading font file");
>     }
>
>   error = FT_Set_Char_Size ( face,
>      0,
>      12 * 64,
>      100,
>      100 );
>   if (error)
>     {
>       fail ("Error setting char size");
>     }
>
>   // Display each ASCII printable char
>   for (FT_ULong n = 33; n < 127; ++n)
>     {
>       FT_UInt glyph_index = FT_Get_Char_Index (face, n);
>
>       FT_Load_Glyph (face,
>      glyph_index,
>      FT_LOAD_DEFAULT|FT_LOAD_TARGET_LCD);
>
>       error = FT_Render_Glyph (face->glyph,
>        FT_RENDER_MODE_LCD);
>
>       if (error)
> {
>   fail ("Error rendering glyph");
> }
>
>       if (n == '_')
> continue;
>
>       FT_Bitmap *bitmap = &face->glyph->bitmap;
>
>       //      printf ("Glyph '%c': %d * %d\n", (char) n, bitmap->width,
bitmap->rows);
>
>       //printf ("Bitmap top: %d\nBitmap left: %d\n",
face->glyph->bitmap_top,
>       //      face->glyph->bitmap_left);
>
>       for (y=0; y<200; ++y)
> for (x=0; x<200; ++x)
>   {
>     location = ((x + 0)+vinfo.xoffset) *
>       (vinfo.bits_per_pixel/8) +
>       ((y + 0)+vinfo.yoffset) * finfo.line_length;
>
>     if ( vinfo.bits_per_pixel == 32 ) {
>       unsigned int *pixel = (int *) (fbp + location);
>       *pixel = 0;
>     }
>   }
>
>       for (y=0; y<bitmap->rows; ++y)
> for (x=0; x< (bitmap->width / 3); ++x)
>   {
>     location = ((x + face->glyph->bitmap_left)+vinfo.xoffset) *
>       (vinfo.bits_per_pixel/8) +
>       ((y + face->glyph->bitmap_top)+vinfo.yoffset) * finfo.line_length;
>
>     unsigned int r = *(bitmap->buffer + (y * bitmap->pitch) + (x*3 + 0));
>     //     r *= (red_max /8);
>     unsigned int g = *(bitmap->buffer + (y * bitmap->pitch) + (x*3 + 1));
>     //     g *= (red_max /8);
>     unsigned int b = *(bitmap->buffer + (y * bitmap->pitch) + (x*3 + 2));
>     //     b *= (red_max /8);
>
>     // printf("r=%u, g=%u, b=%u\n", r, g, b);
>
>     if ( vinfo.bits_per_pixel == 32 ) {
>       unsigned int *pixel = (int *) (fbp + location);
>       *pixel = 0;
>
>       // This works when I run under X11_FBDev (i.e. the
>       // colours are correct), but if I run on the console, I
>       // get a mess and mostly blue colours...
>
>       *pixel |= ((r << vinfo.red.offset)   & red_mask);
>       *pixel |= ((g << vinfo.green.offset) & green_mask);
>       *pixel |= ((r << vinfo.blue.offset)  & blue_mask);
>
>     }
>   }
>
>       sleep (1);
>
>     }
>
>   return 0;
> }
>
>
> - -- 
> Roger Leigh
>                 Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
>                 Debian GNU/Linux        http://www.debian.org/
>                 GPG Public Key: 0x25BFB848.  Please sign and encrypt your
mail.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
>
> iD8DBQFCwGWTVcFcaSW/uEgRAkt1AJ9n98Nx0sFOCSQz6FKJ4mftcnijLACgiW6A
> Ew9wJRanhXh419I9x6PRgzU=
> =2YCz
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>

[Linux-fbdev-users] Endianness issues using the framebuffer

[Roger L. <rl...@wh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

I'm looking into writing a program which will use the framebuffer to
display rendered fonts and some graphics.  However, I've not yet found
much in the way of programming documentation.  Is there anything you
would recommend?

(I've looked at SDL, directfb and GGI sources, but they are very
complex.)

Using the comments in <linux/fb.h> and some simple examples I found,
I've written the sample code below.  However, none of the examples I
saw made any use of the fb_bitfield information.  I ran into problems
when I tried my (i386 tested) code on a PPC.  After fixing the code,
it still doesn't work.  I have the bizarre situation that if I run it
under X11 (using XF86_FBDev), I see the glyphs rendered fine, but if I
run it on the console the colours are mucked up, and I can't see any
change in the bitfield data.

Are there any examples of painting simple RGB pixel data onto any
arbitrary framebuffer device which also works on big and little endian
systems.  I'm sure this is fairly simple once you know how!

Additionally, is there any documentation about how colourmaps and the
other framebuffer features work?


Many thanks,
Roger


This program simply renders each ASCII character in turn and paints
it.  You might need to change the fb device and font path.  It's
currently hard-coded for RBG LCDs, but is simple to change for a CRT.

Compile with
c99 -o ft-lcd ft-lcd.c `freetype-config --cflags --libs`

#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <linux/fb.h>
#include <sys/ioctl.h>
#include <sys/mman.h>

#include <ft2build.h>
#include FT_FREETYPE_H

void fail (const char *reason)
{
  fprintf (stderr, "%s\n", reason);
  exit (EXIT_FAILURE);
}

int
main()
{
  int fbfd = 0;
  struct fb_var_screeninfo vinfo;
  struct fb_fix_screeninfo finfo;
  long int screensize = 0;
  char *fbp = 0;
  int x = 0, y = 0;
  long int location = 0;

  // Open the file for reading and writing
  fbfd = open("/dev/fb/0", O_RDWR);
  if (fbfd < 0)
    fail("Error: cannot open framebuffer device.");

  // Get fixed screen information
  if (ioctl(fbfd, FBIOGET_FSCREENINFO, &finfo))
    fail("Error reading fixed information.");

  // Get variable screen information
  if (ioctl(fbfd, FBIOGET_VSCREENINFO, &vinfo))
    fail("Error reading variable information.");

  printf("%ux%u (%ux%u), %ubpp\n", vinfo.xres, vinfo.yres,
	 vinfo.xres_virtual, vinfo.yres_virtual, vinfo.bits_per_pixel );
  printf("offsets: x=%u, y=%u\n", vinfo.xoffset, vinfo.yoffset);
  printf("red: o=%u, l=%u, mr=%u\n", vinfo.red.offset, vinfo.red.length, vinfo.red.msb_right);
  printf("green: o=%u, l=%u, mr=%u\n", vinfo.green.offset, vinfo.green.length, vinfo.green.msb_right);
  printf("blue: o=%u, l=%u, mr=%u\n", vinfo.blue.offset, vinfo.blue.length, vinfo.blue.msb_right);
  printf("transp: o=%u, l=%u, mr=%u\n", vinfo.transp.offset, vinfo.transp.length, vinfo.transp.msb_right);

  unsigned int red_max = 1 << vinfo.red.length;
  unsigned int green_max = 1 << vinfo.green.length;
  unsigned int blue_max = 1 << vinfo.blue.length;
  unsigned int transp_max = 1 << vinfo.transp.length;

  unsigned int red_mask = 0;
  for (unsigned int i=0; i<vinfo.red.length; ++i)
    red_mask |= 1 << (vinfo.red.offset + i);
  unsigned int green_mask = 0;
  for (unsigned int i=0; i<vinfo.green.length; ++i)
    green_mask |= 1 << (vinfo.green.offset + i);
  unsigned int blue_mask = 0;
  for (unsigned int i=0; i<vinfo.blue.length; ++i)
    blue_mask |= 1 << (vinfo.blue.offset + i);
  unsigned int transp_mask = 0;
  for (unsigned int i=0; i<vinfo.transp.length; ++i)
    transp_mask |= 1 << (vinfo.transp.offset + i);


  // Figure out the size of the screen in bytes
  screensize = vinfo.xres * vinfo.yres * vinfo.bits_per_pixel / 8;

  // Map the device to memory
  fbp = (char *)mmap(0, screensize, PROT_READ | PROT_WRITE, MAP_SHARED,
		     fbfd, 0);
  if ((int)fbp == -1)
    fail("Error: failed to map framebuffer device to memory.\n");

  // Now setup FreeType
  FT_Library library;
  FT_Face face;

  int error = FT_Init_FreeType( &library );
  if ( error )
    {
      fail ("Failed to initialise FreeType");
    }

  error = FT_New_Face( library, "/usr/share/fonts/truetype/ttf-bitstream-vera/VeraMono.ttf", 0, &face );
  if ( error == FT_Err_Unknown_File_Format )
    {
      fail ("Unsupported font format");
    }
  else if ( error )
    {
      fail ("Error reading font file");
    }

  error = FT_Set_Char_Size ( face,
			     0,
			     12 * 64,
			     100,
			     100 );
  if (error)
    {
      fail ("Error setting char size");
    }

  // Display each ASCII printable char
  for (FT_ULong n = 33; n < 127; ++n)
    {
      FT_UInt glyph_index = FT_Get_Char_Index (face, n);

      FT_Load_Glyph (face,
		     glyph_index,
		     FT_LOAD_DEFAULT|FT_LOAD_TARGET_LCD);

      error = FT_Render_Glyph (face->glyph,
			       FT_RENDER_MODE_LCD);

      if (error)
	{
	  fail ("Error rendering glyph");
	}

      if (n == '_')
	continue;

      FT_Bitmap *bitmap = &face->glyph->bitmap;

      //      printf ("Glyph '%c': %d * %d\n", (char) n, bitmap->width, bitmap->rows);

      //printf ("Bitmap top: %d\nBitmap left: %d\n", face->glyph->bitmap_top,
      //      face->glyph->bitmap_left);

      for (y=0; y<200; ++y)
	for (x=0; x<200; ++x)
	  {
	    location = ((x + 0)+vinfo.xoffset) *
	      (vinfo.bits_per_pixel/8) +
	      ((y + 0)+vinfo.yoffset) * finfo.line_length;

	    if ( vinfo.bits_per_pixel == 32 ) {
	      unsigned int *pixel = (int *) (fbp + location);
	      *pixel = 0;
	    }
	  }

      for (y=0; y<bitmap->rows; ++y)
	for (x=0; x< (bitmap->width / 3); ++x)
	  {
	    location = ((x + face->glyph->bitmap_left)+vinfo.xoffset) *
	      (vinfo.bits_per_pixel/8) +
	      ((y + face->glyph->bitmap_top)+vinfo.yoffset) * finfo.line_length;

	    unsigned int r = *(bitmap->buffer + (y * bitmap->pitch) + (x*3 + 0));
	    //	    r *= (red_max /8);
	    unsigned int g = *(bitmap->buffer + (y * bitmap->pitch) + (x*3 + 1));
	    //	    g *= (red_max /8);
	    unsigned int b = *(bitmap->buffer + (y * bitmap->pitch) + (x*3 + 2));
	    //	    b *= (red_max /8);

	    // printf("r=%u, g=%u, b=%u\n", r, g, b);

	    if ( vinfo.bits_per_pixel == 32 ) {
	      unsigned int *pixel = (int *) (fbp + location);
	      *pixel = 0;

	      // This works when I run under X11_FBDev (i.e. the
	      // colours are correct), but if I run on the console, I
	      // get a mess and mostly blue colours...

	      *pixel |= ((r << vinfo.red.offset)   & red_mask);
	      *pixel |= ((g << vinfo.green.offset) & green_mask);
	      *pixel |= ((r << vinfo.blue.offset)  & blue_mask);

	    }
	  }

      sleep (1);

    }

  return 0;
}


- -- 
Roger Leigh
                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                Debian GNU/Linux        http://www.debian.org/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFCwGWTVcFcaSW/uEgRAkt1AJ9n98Nx0sFOCSQz6FKJ4mftcnijLACgiW6A
Ew9wJRanhXh419I9x6PRgzU=
=2YCz
-----END PGP SIGNATURE-----

[Linux-fbdev-users] Help

[Yanzely Ng <yan...@gm...>]

Hi,

I send the figure with the errors yesterday, but I think the mail
doesn't reach to you, because I receive a mail back.

Well, I will send it again, but this time only the figure with the errors.

I have another question, how can I change the kernel version, now I am
using the kernel version 2.6.9.

Thanks for your help.

                      Yanzely

Re: [Linux-fbdev-users] Help framebuffer

[Geert U. <ge...@li...>]

On Tue, 7 Jun 2005, Yanzely Ng wrote:
> I am developing a system with Nios II, my system doesn't have a
> physical frame buffer device, and I want to add that on the uClinux.
> But when I select the option
> Device Driver -> Character Device -> Support Frame Buffer device on
> the Kernel configuration, and then I compile with that option the
> kernel display some errors.

Can you please post the errors, so we don't have to guess? Thx!

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

[Linux-fbdev-users] Help framebuffer

[Yanzely Ng <yan...@gm...>]

Hi,

I am developing a system with Nios II, my system doesn't have a
physical frame buffer device, and I want to add that on the uClinux.
But when I select the option
Device Driver -> Character Device -> Support Frame Buffer device on
the Kernel configuration, and then I compile with that option the
kernel display some errors.

I am a little confuse on how I should create a frame buffer device on
uClinux. Can somebody help me with some information.

Thanks a lot.

              Yanzely

[Linux-fbdev-users] Framebuffer on embedded system

[Einar G. <eig...@gm...>]

I'm doing an small project, and a want to modify a VGA controller core
to make it compatible with the VBE VESA estandar, either 2.0 o 3.0, so
I could use it with uClinux, but i'm not so sure which are the
requiremets to do it, besides that it should work with a frame buffer.
I've been reading the document of VBE from www.vesa.org but it's focus
on software programing...
Is there another way a could take advantage from the frame buffer to
make my vga controller works??

--=20
Einar I. Gonz=E1lez V.

Re: [Linux-fbdev-users] intelfb on 82852/855GM

[Sylvain M. <syl...@wo...>]

        Hi,

    vga=3D depends on the BIOS. Check which modes are possible with your=20
BIOS. Also, vesafb is it working for you ? If yes, you should stick with=20
it. I don't own a flat-panel, so I won't implement LFP support. I hope=20
somebody else will help for implementing it. I think it's not a very=20
difficult thing to do. But as i can't debug it, i won't try it.

Regards
Sylvain

themuse a =E9crit:

>hello,=20
>
>anybody have any clue why vga=3D... (as specified below) doesn't work
>either for me?  (If I press space after the "...undefined video mode"
>error, I get a list of available modes, but those are only text modes)
>Are there any chances/plans to get intelfb to work with video=3D...
>settings for local non-CRT devices (laptop LCDs)?
>
>regards,
>bernie
>
>Am Sonntag, den 01.05.2005, 23:56 +0200 schrieb themuse:
> =20
>
>>here you go...
>>
>>
>>default 0
>>timeout 30
>>
>>title=3DLinux
>>root (hd0,1)
>>kernel (hd0,1)/kernel-2.6.11-gentoo-r6 root=3D/dev/hda4 vga=3D791
>>
>>title=3DWindows
>>rootnoverify (hd0,0)
>>makeactive
>>chainloader +1
>>
>>
>>...which gives me the error mentioned earlier - so I'd be glad for any
>>enlightening comments...
>>
>>bernie
>>
>>
>>Am Donnerstag, den 28.04.2005, 07:30 -0400 schrieb Kurt Wall:
>>   =20
>>
>>>On Thursday 28 April 2005 04:20, themuse enlightened us thusly:
>>>     =20
>>>
>>>>hello again,
>>>>
>>>>i tried different modes (both decimal and hexadecimal) with vga=3D...
>>>>in the kernel command line in grub.conf, but I always got the "you
>>>>passed an undefined video mode" error message on bootup. soit seems
>>>>like i'm pretty much stuck here...
>>>>       =20
>>>>
>>>Please post the contents of /boot/grub/grub.conf.
>>>
>>>Kurt
>>>
>>>
>>>-------------------------------------------------------
>>>SF.Net email is sponsored by: Tell us your software development plans!
>>>Take this survey and enter to win a one-year sub to SourceForge.net
>>>Plus IDC's 2005 look-ahead and a copy of this survey
>>>Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=3D105hi=
x
>>>_______________________________________________
>>>Linux-fbdev-users mailing list
>>>Lin...@li...
>>>https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>>>
>>>     =20
>>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by: NEC IT Guy Games.
>>Get your fingers limbered up and give it your best shot. 4 great events=
, 4
>>opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
>>win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=3D20
>>_______________________________________________
>>Linux-fbdev-users mailing list
>>Lin...@li...
>>https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>>
>>   =20
>>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Yahoo.
>Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
>Search APIs Find out how you can build Yahoo! directly into your own
>Applications - visit http://developer.yahoo.net/?fr=3Doffad-ysdn-ostg-q2=
2005
>_______________________________________________
>Linux-fbdev-users mailing list
>Lin...@li...
>https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>
> =20
>

Re: [Linux-fbdev-users] intelfb on 82852/855GM

[themuse <th...@gm...>]

hello, 

anybody have any clue why vga=... (as specified below) doesn't work
either for me?  (If I press space after the "...undefined video mode"
error, I get a list of available modes, but those are only text modes)
Are there any chances/plans to get intelfb to work with video=...
settings for local non-CRT devices (laptop LCDs)?

regards,
bernie

Am Sonntag, den 01.05.2005, 23:56 +0200 schrieb themuse:
> here you go...
> 
> 
> default 0
> timeout 30
> 
> title=Linux
> root (hd0,1)
> kernel (hd0,1)/kernel-2.6.11-gentoo-r6 root=/dev/hda4 vga=791
> 
> title=Windows
> rootnoverify (hd0,0)
> makeactive
> chainloader +1
> 
> 
> ...which gives me the error mentioned earlier - so I'd be glad for any
> enlightening comments...
> 
> bernie
> 
> 
> Am Donnerstag, den 28.04.2005, 07:30 -0400 schrieb Kurt Wall:
> > On Thursday 28 April 2005 04:20, themuse enlightened us thusly:
> > > hello again,
> > >
> > > i tried different modes (both decimal and hexadecimal) with vga=...
> > > in the kernel command line in grub.conf, but I always got the "you
> > > passed an undefined video mode" error message on bootup. soit seems
> > > like i'm pretty much stuck here...
> > 
> > Please post the contents of /boot/grub/grub.conf.
> > 
> > Kurt
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Tell us your software development plans!
> > Take this survey and enter to win a one-year sub to SourceForge.net
> > Plus IDC's 2005 look-ahead and a copy of this survey
> > Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> > _______________________________________________
> > Linux-fbdev-users mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> 

[Linux-fbdev-users] Dual Monitor console with frame buffer

[Uncle B. <ih...@ya...>]

Hi, I am trying to get mplayer to play a v4l stream on
/dev/fb0 and another instance of mplayer to place a
v4l stream on /dev/fb1. fb0 works fine if it is
controlled by  vesafb, but not if its with rivafb
(mplayer returns an error about not being able to use
that video output). If I try to use fbset to match the
settings of the rivafb powered fb to the vesa powered
one, the system just locks. The second card is an ATI
Mach64 and when I try to run mplayer out to it I get
either the same error, or the system hangs. I'm sure
that if I can get a console on each monitor, mplayer
will co-operate.

I've been searching for days.

Thanks in advance

Rob


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/

[Linux-fbdev-users] PATCH: vga console tweak

[Jordan C. <jor...@am...>]

The attached patch puts a hard 32k ceiling on copies to and from
the VGA VRAM space.

This bug was discovered with a 1920x1440 framebuffer console - before
switching from VGA, the console is expanded to 240 cols x 90 rows, equaling
a screenbuf_size of 43200 bytes.  Since the VGA VRAM space is only 32k bytes
big, calling vgacon_save_screen during the console transfer copied in a good
chunk of the video BIOS living at 0xc0000 too, resulting in some very purty
colors and characters at the bottom of the new console.

-- 
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>

Re: [Linux-fbdev-users] fbset doesn't change resolution for all consoles

[James S. <jsi...@ww...>]

> > Also the other issue is what if the user only changes the color depth and
> > the VCs are at different resolution. Some resolutions can handle the new
> > depth but others can't. How do we handle this?
> 
> The way fbset -a works is that all vc's will have the var of the current display.

So all is really ALL. Then that is okay :-)

[Linux-fbdev-users] new system for heavy framebuffer user: ati or nvidia?

[Jurriaan <thu...@xs...>]

I'm going to buy a new linux system, which will be used for mail, news
and film-watching.

Since it's going to have a pci-e slot and no agp slot, I can't take my
Ati 9600 with me.

So it'll probably be either an Ati X300, X600 or a Nvidia 6600 (or the
one below without shared memory).

Which of those cards works best with open source drivers, a 1600x1200
framebuffer and a 1600x1200 X and a good, working Xv extension?

I frequently switch from X to the console and back, and use mplayer,
ogle and vlc to watch movies. I haven't been able to find any reviews
about these combinations, and I don't see many people posting problems
here with these combinations. That may not mean there aren't any....

How good is the new nvidiafb driver? Does it work just find with XFree
or X.org?

Thanks,
Jurriaan
-- 
But he spoke first, forestalling the accusation in her eyes.
"I have come," he said, kneeling for the first time, "to discharge
the debt I owe the Arkosa Voyani."
	Michelle West - The Riven Shield
Debian (Unstable) GNU/Linux 2.6.12-rc3-mm3 2x6139 bogomips load 0.07

Re: [Linux-fbdev-users] fbset doesn't change resolution for all consoles

[Antonino A. D. <ad...@ho...>]

On Friday 29 April 2005 06:28, James Simmons wrote:
> > > This was done because sometimes the user entered a bad mode which the
> > > driver could not handle. As a result all the VCs went blank and became
> > > useless. The only fix was to reboot the box.
> >
> > One of the reasons why /dev/fb should be root-access only.
> >
> > Anyway, if that happens, one can always blindly type fbset commands that
> > can restore the fb console. And if incorrectly using fbset renders the
> > console permanently useless that the only fix is to reboot the box, then
> > it doesn't really matter if one uses fbset with or without the  '--all'
> > argument.
>
> Also the other issue is what if the user only changes the color depth and
> the VCs are at different resolution. Some resolutions can handle the new
> depth but others can't. How do we handle this?

The way fbset -a works is that all vc's will have the var of the current display.

Tony

[Linux-fbdev-users] Re: intelfb on 82852/855GM and cursor problem

[Stanislav S. <sse...@cs...>]

Hi

>> I think you don"t have to set it by hand but enable in menuconfig Device Driver
>> / Graphics Support / Console Display driver support / Video mode selection
>> support.

Agree, but I have this turned on:

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

It doesn't help

>> the cursor was killed - restore it !!
>> 
>> and there is no cursor in console (without X started). I tried turning off 
>> hardware cursor support, didn"t help, could you suggest what to do next?
>> 
> It"s caused by X which silently change the hw cursor (and don"t reinit it) . If
> you turn off hw cursor the message will go off. And yes there a cursor in console,
> the blinking underscore at the bottom of your window :-)

:-) If it was so easy...
I don't start X at all and I tried turning off the hardware cursor - how can it be
caused by X if it never starts? There is no cursor from the very booting.

Re: [Linux-fbdev-users] intelfb on 82852/855GM

[themuse <th...@gm...>]

here you go...


default 0
timeout 30

title=Linux
root (hd0,1)
kernel (hd0,1)/kernel-2.6.11-gentoo-r6 root=/dev/hda4 vga=791

title=Windows
rootnoverify (hd0,0)
makeactive
chainloader +1


...which gives me the error mentioned earlier - so I'd be glad for any
enlightening comments...

bernie


Am Donnerstag, den 28.04.2005, 07:30 -0400 schrieb Kurt Wall:
> On Thursday 28 April 2005 04:20, themuse enlightened us thusly:
> > hello again,
> >
> > i tried different modes (both decimal and hexadecimal) with vga=...
> > in the kernel command line in grub.conf, but I always got the "you
> > passed an undefined video mode" error message on bootup. soit seems
> > like i'm pretty much stuck here...
> 
> Please post the contents of /boot/grub/grub.conf.
> 
> Kurt
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> 

[Linux-fbdev-users] Help me please with Radeonfb. (fwd)

[Geert U. <ge...@li...>]

LS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0tLS0tLS0tDQpEYXRlOiBTYXQsIDMw
IEFwciAyMDA1IDExOjQzOjQ4ICswNDAwDQpGcm9tOiBhbl9hY2NpZGVudGFsX21hbkBlLW1h
aWwucnUNClRvOiBnZWVydEBsaW51eC1tNjhrLm9yZw0KU3ViamVjdDogSGVscCBtZSBwbGVh
c2Ugd2l0aCBSYWRlb25mYi4NCg0KSGVsbG8gR2VlcnQuDQpNYXliZSB5b3UgY291bGQgaGVs
cCBtZT8NCkkndmUgZ290IFJhZGVvbiA5MTAwIGNvbm5lY3RlZCB0byBMQ0QgbW9uaXRvciBv
dmVyIERWSS4NCkFmdGVyIGNvbXBpbGluZyAyLjYuMTEga2VybmVsIHdpdGggbmV3IHJhZGVv
bmZiIGVuYWJsZWQNCmkgc2VlIGJsYW5rIHNjcmVlbiwgdGhvdWdoIHN5c3RlbSBib290cyBP
Sy4NCkkgc2F3IGluIGRpZmZlcmVudCBwb3N0cyBpbiBXRUIgdGhhdCBvdGhlciBwZW9wbGUg
aGFkDQpzYW1lIHByb2JsZW0uIENhbiBpIHNvbWVob3cgc29sdmUgdGhpcyBpc3N1ZT8gVGhh
bnguDQpTZXJnZWkuDQpodHRwOi8vd3d3LmUtbWFpbC5ydQ0K1MXExdDAy9zNwN8gz87X0s7C
wN8g0cvTxsHAIEUtTUFJTC5SVQ0KaHR0cDovL3d3dy5lLW1haWwucnUNCg0K0u7r/OruIOTu
IDMwIODv8OXr/yDq7uzv4O3o/yAiyuv+9yDP6+Dx8sru7fHy8PPq8u7wIiDv8OXk6+Dj4OXy
IPHq6OTq6CDk7iAyMCUg7eAg7+vg8fLo6u7i++Ug7urt4CDoIOTi5fDoISDH4u7t6PLlIPHl
6ffg8S4NClRlbC9mYXg6ICgwOTUpIDc4NC02NC04NA0KVVJMOiBodHRwOi8vd3d3Lmtway5y
dQ==

[Linux-fbdev-users] Getting hands on FrameBuffer, Linux Display System

[Vishal L. <vis...@gm...>]

Dear all,

I am trying to work/study on Linux Display System,  All my work for
the last 10 days is to reach to this milestone.

All i would like to achieve is to somehow control the flow of data
which XServer is passing it to the Display Driver.

I wanaa reach to that level, As in.. whenever the video data is passed
frm XServer to Display driver..  like i will develop kindaa module
which can modify this data... kindaa filter driver...

I am doing everything possible...  http://kerneltrap.org/blog/8787

Setting up remote kernel debugging testbed/trying to locate the
functions which are actually responsible for writing/drawing on the
screen.

Your inputs on this would be highly appreciated.

I am using kernel 2.6.8
Have Nvidia and Intel cards with me.
Os is Fedora Core 3.

Thanx & Regards,
Vishal.

Re: [Linux-fbdev-users] fbset doesn't change resolution for all consoles

[Grzegorz A. H. <gr...@ti...>]

On 2005-04-28, James Simmons <jsi...@pe...> wrote:
> Also the other issue is what if the user only changes the color
> depth and the VCs are at different resolution. Some resolutions
> can handle the new depth but others can't. How do we handle this?

Fail like fbset fails to set an unknown mode for the current
console. fbset would print an error for all the consoles which
could not be changed and return nonzero on exit.

Re: [Linux-fbdev-users] fbset doesn't change resolution for all consoles

[James S. <jsi...@ww...>]

> > This was done because sometimes the user entered a bad mode which the
> > driver could not handle. As a result all the VCs went blank and became
> > useless. The only fix was to reboot the box.
> >
> 
> One of the reasons why /dev/fb should be root-access only.
> 
> Anyway, if that happens, one can always blindly type fbset commands that
> can restore the fb console. And if incorrectly using fbset renders the
> console permanently useless that the only fix is to reboot the box, then it
> doesn't really matter if one uses fbset with or without the  '--all'
> argument.

Also the other issue is what if the user only changes the color depth and 
the VCs are at different resolution. Some resolutions can handle the new 
depth but others can't. How do we handle this?

Re: [Linux-fbdev-users] intelfb on 82852/855GM

[Kurt W. <kw...@ku...>]

On Thursday 28 April 2005 04:20, themuse enlightened us thusly:
> hello again,
>
> i tried different modes (both decimal and hexadecimal) with vga=...
> in the kernel command line in grub.conf, but I always got the "you
> passed an undefined video mode" error message on bootup. soit seems
> like i'm pretty much stuck here...

Please post the contents of bootgrubgrub.conf.

Kurt

Re: [Linux-fbdev-users] intelfb on 82852/855GM

[themuse <th...@gm...>]

hello again, 

i tried different modes (both decimal and hexadecimal) with vga=... in
the kernel command line in grub.conf, but I always got the "you passed
an undefined video mode" error message on bootup. soit seems like i'm
pretty much stuck here...

bernie

Am Sonntag, den 24.04.2005, 23:35 +0200 schrieb Sylvain Meyer: 
>         Hi,
>    
>     Local Flat Panel support isn't fully implemented in intelfb. Only 
> CRT output is.  The workaround is to use the BIOS to program the graphic 
> chip at boot time using the 'vga=' option. One restriction is the driver 
> cannot change video modes.
> 
> Regards
> Sylvain
> 
> themuse a écrit:
> 
> >Hello, 
> >
> >I'm trying to get intelfb compiled into kernel 2.6.11(-gentoo-r5) with 
> >
> >video=intelfb:1024x768-16@60 
> >
> >in my grub.conf kernel command line to work with my fujitsu-siemens
> >lifebook (with intel 82852855GM graphics) and keep getting the
> >following in dmesg:
> >
> >intelfb: Framebuffer driver for Intel(R) 830M845G852GM855GM865G
> >chipsets
> >intelfb: Version 0.9.2
> >intelfb: 00:02.0: Intel(R) 855GM, aperture size 128MB, stolen memory
> >8060kB
> >intelfb: Non-CRT device is enabled ( LVDS port ).  Disabling mode
> >switching.
> >intelfb: Video mode must be programmed at boot time.
> >
> >And I'm left with the text console. I've also tried
> >other modes (theoretically, the system supports 1400x1050-24@60), but
> >with no success so far. (Research in Gentoo forums makes me think I'm
> >not the only person getting these error messages, but I didn't find
> >anything usable there.) Any help would be welcome, I'd help gladly with
> >testing fixes (if it's the driver's and not my fault). 
> >
> >Greetings
> >themuse
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: New Crystal Reports XI.
> >Version 11 adds new functionality designed to reduce time involved in
> >creating, integrating, and deploying reporting solutions. Free runtime info,
> >new features, or free trial, at: http:www.businessobjects.comdevxi728
> >_______________________________________________
> >Linux-fbdev-users mailing list
> >Lin...@li...
> >https:lists.sourceforge.netlistslistinfolinux-fbdev-users
> >
> >  
> >
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http:ads.osdn.com?ad_ide95&alloc_id396&op=click
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https:lists.sourceforge.netlistslistinfolinux-fbdev-users
> 

Re: [Linux-fbdev-users] fbset doesn't change resolution for all consoles

[Antonino A. D. <ad...@ho...>]

On Wednesday 27 April 2005 20:25, Grzegorz Adam Hankiewicz wrote:
> On 2005-04-25, Petr Vandrovec <van...@vc...> wrote:

> I'm shocked. Is he going to ban changing color depth at all in the
> future? Right now I boot into some vesa mode and need fbset to set
> the same resolution with hardware acceleration to avoid it being
> so sluggish. Is there a way to do this with stty rather than fbset?

fbset has been working for 2-3 kernel versions already, well, except for
the fbset -a part, which for some time I've known not to work.  I decided to
fix it only if someone complains.

Tony

Re: [Linux-fbdev-users] fbset doesn't change resolution for all consoles

[Antonino A. D. <ad...@ho...>]

On Wednesday 27 April 2005 04:42, James Simmons wrote:
> > > Matrox g450 support built into the kernel as well as fbcon. Standing
> > > on a console I try running "fbset -a resolution" or "fbset
> > > --all resolution" where resolution is one of the modes listed
> > > in /etc/fb.modes. However, only the current console's resolution
> > > is changed.
> > >
> > > Is this a bug in fbset? Is there any new version of this software? I
> > > remember using fbset on a 2.4.x kernel with the same video card
> > > without problems.
> >
> > Not a bug in fbset, but is due to changes in fbcon code from 2.4->2.6.
> > Now, only the visible console will respond to fbset requests.
> >
> > I'll see what I can do about this bug.
>
> This was done because sometimes the user entered a bad mode which the
> driver could not handle. As a result all the VCs went blank and became
> useless. The only fix was to reboot the box.
>

One of the reasons why /dev/fb should be root-access only.

Anyway, if that happens, one can always blindly type fbset commands that
can restore the fb console. And if incorrectly using fbset renders the
console permanently useless that the only fix is to reboot the box, then it
doesn't really matter if one uses fbset with or without the  '--all'
argument.

Tony

Re: [Linux-fbdev-users] intelfb on 82852/855GM and cursor problem

[Sylvain M. <syl...@wo...>]

    Hi Stanislav,

Stanislav Semakin a =E9crit:

>Hello,
>
>For those who are on the:
>
> intelfb: Non-CRT device is enabled ( LVDS port ).  Disabling mode switc=
hing.
> intelfb: Video mode must be programmed at boot time.
>
>stage read this: http://www.xfree86.org/~dawes/intelfb.html
>and svga.txt in the kernel source documentation. I managed to start
>video mode needed, but with tricks: I had to define this
>
>#define CONFIG_FB_VESA_STD
>
    I think you don't have to set it by hand but enable in menuconfig=20
Device Driver / Graphics Support / Console Display driver support /=20
Video mode selection support.

>
>in the beginning of the arch/i386/boot/video.S file. Without it I couldn=
't
>start video mode via "vga=3D" or etc. though I played a lot with all
>that stuff described in svga.txt, the definition I used is not mentioned
>in svga.txt. What was wrong?
>
>Ok, now I have it running but my dmesg is full of
>
>the cursor was killed - restore it !!
>
>and there is no cursor in console (without X started). I tried turning o=
ff hardware
>cursor support, didn't help, could you suggest what to do next?
>
    It's caused by X which silently change the hw cursor (and don't=20
reinit it) . If you turn off hw cursor the message will go off. And yes=20
there a cursor in console, the blinking underscore at the bottom of your=20
window :-)

>
>Thanks in advance
>
>Regards,
>Stas
>
Regards
Sylvain