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

[Linux-fbdev-users] Getting started

[William E. <mru...@po...>]

Hi guys,

  Would someone please point me to a 'Getting started' URL for framebuffer
support?

  I am running Fedora Core 4 and I have rebuilt the kernel to make sure
FB support is in the kernel.  I have a simple FB program that I have
compiled but everytime I try to run it, I get:

    Error: cannot open framebuffer device /dev/fb0. - No such device rc=-1

  The open code looks like this:

        // Open the file for reading and writing
        char*  FB   = "/dev/fb0";
        int    fbfd = 0;
        fbfd = open( FB, O_RDWR);
        if (fbfd < 0) {
          printf("Error: cannot open framebuffer device %s. - %s rc=%d\n",
                 FB, strerror(errno), fbfd);
            exit(1);
        }
        printf("The framebuffer device was opened successfully. - %d\n",
    fbfd );

  I have done the mkdir:

    [wre00@Shrek FB]$ ls -lrt /dev/fb*
    crwxrwxr-x  1 wre00 root 29, 0 Aug 17 10:05 /dev/fb0

  Any ideas/help??

-- 
  William Estrada 
<http://www.Mt-Umunhum-Wireless.net/resume/william_estrada.html>   --  
MrUmunhum at popdial dot com <mailto:MrU...@po...>  --  
408-997-0743
  Ymessenger ID: MrUmunhum
  HTTP://Mt-Umunhum-Wireless.net

[Linux-fbdev-users] Help sema_init

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

Hi,

I am trying to make a char driver, I found a scull.c and I try to work
in base of that one. Here they initialized the semaphore with the
function sema_init. When I used that function in the SDK terminal
appears this message:

"ttyJ0 at MMIO 0x81801920 (irq =3D 7) is a jtag_uart"

And this is the last message it display and didn=B4t let me do anything els=
e.

I dont know how to solve this problem and why it stop there.

I will really appreciate your help.

                      Yanzely

Re: [Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[TAMAS G. <di...@mf...>]

Hi,

 > Your system did not assign base address to the videoram, and neither
 > kernel PCI subsystem did that.  Try complaining at
 > lin...@vg..., or maybe to your BIOS vendor.  Maybe
 > that `dmesg` output would reveal why BIOS/kernel failed to assign MMIO range
 > to your hardware due to insufficient resources.  If you have 'MMIO hole'
 > setting in the BIOS, try setting it to 2GB instead of 1GB you are (probably)
 > currently using.

Mobo is MSI K8N NEO with Phoenix/Award BIOS. Sadly there is no 'MMIO
hole' option in it.

But it was a BIOS problem. I flashed it with the latest one from MSI and
framebuffer is now working fine.

Thanks again for your help.
Gergely

[Linux-fbdev-users] Re: Problems with loading i810fb (/dev/fb0 missing)

[Ritesh R. S. <rit...@us...>]

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

Ritesh Raj Sarraf wrote:

> There's a code for VGA Console in the kernel called vgacon/vgaconfb.
> AFAIK without that you don't get a console under fb.

Or if not that, it should be fbcon.

rrs
- -- 
Ritesh Raj Sarraf
RESEARCHUT -- http://www.researchut.com
Gnupg Key ID: 04F130BC
"Stealing logic from one person is plagiarism, stealing from many is
research."
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC8RNK4Rhi6gTxMLwRAja/AJ9kkUCuicYWCoo0qEzZykmn/nmc6QCgmuD5
PISnmg6yKMyoTMP7tDx6VRw=
=ijdP
-----END PGP SIGNATURE-----

Re: [Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[Petr V. <van...@vc...>]

TAMAS Gergely wrote:
> Hi,
> 
>  > What 'lspci -vvv -s 01:00.0' reports ?
> 
> Sorry, here is the output again, run as root :
> 
> 0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) (prog-if 00 [VGA])
> 	Subsystem: Matrox Graphics, Inc. Millennium G550 Dual Head DDR 32Mb
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> 	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> 	Latency: 32 (4000ns min, 8000ns max), Cache Line Size: 0x08 (32 bytes)
> 	Interrupt: pin A routed to IRQ 3
> 	Region 0: Memory at <ignored> (32-bit, prefetchable)

Your system did not assign base address to the videoram, and neither
kernel PCI subsystem did that.  Try complaining at
lin...@vg..., or maybe to your BIOS vendor.  Maybe
that `dmesg` output would reveal why BIOS/kernel failed to assign MMIO range
to your hardware due to insufficient resources.  If you have 'MMIO hole'
setting in the BIOS, try setting it to 2GB instead of 1GB you are (probably)
currently using.

> 	Region 1: Memory at d8000000 (32-bit, non-prefetchable) [size=16K]
> 	Region 2: Memory at d9000000 (32-bit, non-prefetchable) [size=8M]
> 	Expansion ROM at db000000 [disabled] [size=128K]
> 	Capabilities: [dc] Power Management version 2
> 		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 	Capabilities: [f0] AGP version 2.0
> 		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
> 		Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1

								Petr Vandrovec

Re: [Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[TAMAS G. <di...@mf...>]

Hi,

Sorry, missed this one :

 > System?

Debian sarge.

Gergo

Re: [Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[TAMAS G. <di...@mf...>]

Hi,

 > What 'lspci -vvv -s 01:00.0' reports ?

Sorry, here is the output again, run as root :

0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) (prog-if 00 [VGA])
	Subsystem: Matrox Graphics, Inc. Millennium G550 Dual Head DDR 32Mb
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (4000ns min, 8000ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 3
	Region 0: Memory at <ignored> (32-bit, prefetchable)
	Region 1: Memory at d8000000 (32-bit, non-prefetchable) [size=16K]
	Region 2: Memory at d9000000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at db000000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [f0] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
		Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1

Gergely

Re: [Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[TAMAS G. <di...@mf...>]

Hi,

 > > > [...]
 > > > Kernel command line: root=/dev/hda2 ro video=matroxfb:vesa:0x18b
 > > > [...]
 > > > matroxfb: Matrox G550 detected
 > > > matroxfb: video RAM is not available in PCI address space, matroxfb disabled
 > > > matroxfb: probe of 0000:01:00.0 failed with error -1
 > > > [...]
 > >
 > >What does this mean?  Where can i find more information about this? I
 > >tried google but found no usable infos.
 > 
 > Kernel version?

2.6.13-rc5

 > System?
 > Processor?

AMD Athlon64 in 32bit mode

 > What 'lspci -vvv -s 01:00.0' reports ?

0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) (prog-if 00 [VGA])
	Subsystem: Matrox Graphics, Inc. Millennium G550 Dual Head DDR 32Mb
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (4000ns min, 8000ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 3
	Region 0: Memory at <ignored> (32-bit, prefetchable)
	Region 1: Memory at d8000000 (32-bit, non-prefetchable) [size=16K]
	Region 2: Memory at d9000000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at db000000 [disabled] [size=128K]
	Capabilities: <available only to root>

Gergely

Re: [Linux-fbdev-users] matroxfb and 2 matrox cards

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

Christoph Kaminski wrote:
> Hi!
> 
> I have a Problem with 2 Matrox Cards in the same PC and matroxfb
> I want to use the Millenium2 for console/X and the G450 for tv-out (directfb)
> 
> I can load the matroxfb module without any errors:
> 
> matroxfb: Matrox Millennium II (PCI) detected
> matroxfb: MTRR's turned on
> matroxfb: 640x480x8bpp (virtual: 640x13081)
> matroxfb: framebuffer at 0xDA000000, mapped to 0xf9080000, size 8388608
> Console: switching to colour frame buffer device 80x30
> kernel: fb0: MATROX frame buffer device
> kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
> kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [APC4] -> GSI 19 (level, 
> high) -> IRQ 193
> kernel: matroxfb: Matrox G450 detected
> kernel: matroxfb: MTRR's turned on
> kernel: matroxfb: 640x480x8bpp (virtual: 640x26214)
> kernel: matroxfb: framebuffer at 0xD8000000, mapped to 0xfa100000, size 
> 33554432
> kernel: fb1: MATROX frame buffer device
> kernel: fb1: initializing hardware
> kernel: matroxfb_crtc2: secondary head of fb1 was registered as fb2
> kernel: matroxfb: cannot set xres to 800, rounded up to 832
> 
> but if I start a Program what uses directfb (eg: mplayer or freevo) ond 
> the /dev/fb1 (G450) then it freezes the /dev/fb0 (millenium2/console)
> If I stop the application, then I can again use console (/dev/fb0)
> 
> why? how can I solve it?
> 

Currently, only one vt can be active at a time. Directfb applications
usually allocate a vt, then switch to it.  This leaves the other vt's
inactive.

Try to experiment with options like --dfb:no-vt-switch, vt-switching,
no-graphics-vt. Try to do it with directfb apps first, then find a way to
pass these options to mplayer.

Another way is to launch the directfb app while in X.  I have heard that this
setup works for a lot of people.

(Note: I haven't followed development of directfb for sometime, but I guess
those options are still there).

Tony

[Linux-fbdev-users] matroxfb and 2 matrox cards

[Christoph K. <ma...@gm...>]

Hi!

I have a Problem with 2 Matrox Cards in the same PC and matroxfb
I want to use the Millenium2 for console/X and the G450 for tv-out (directfb)

I can load the matroxfb module without any errors:

matroxfb: Matrox Millennium II (PCI) detected
matroxfb: MTRR's turned on
matroxfb: 640x480x8bpp (virtual: 640x13081)
matroxfb: framebuffer at 0xDA000000, mapped to 0xf9080000, size 8388608
Console: switching to colour frame buffer device 80x30
kernel: fb0: MATROX frame buffer device
kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [APC4] -> GSI 19 (level, 
high) -> IRQ 193
kernel: matroxfb: Matrox G450 detected
kernel: matroxfb: MTRR's turned on
kernel: matroxfb: 640x480x8bpp (virtual: 640x26214)
kernel: matroxfb: framebuffer at 0xD8000000, mapped to 0xfa100000, size 
33554432
kernel: fb1: MATROX frame buffer device
kernel: fb1: initializing hardware
kernel: matroxfb_crtc2: secondary head of fb1 was registered as fb2
kernel: matroxfb: cannot set xres to 800, rounded up to 832

but if I start a Program what uses directfb (eg: mplayer or freevo) ond 
the /dev/fb1 (G450) then it freezes the /dev/fb0 (millenium2/console)
If I stop the application, then I can again use console (/dev/fb0)

why? how can I solve it?

-- 
MfG
Christoph Kaminski

Re: [Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[Petr V. <van...@vc...>]

TAMAS Gergely wrote:
> Hi,
> 
>  > [...]
>  > Kernel command line: root=/dev/hda2 ro video=matroxfb:vesa:0x18b
>  > [...]
>  > matroxfb: Matrox G550 detected
>  > matroxfb: video RAM is not available in PCI address space, matroxfb disabled
>  > matroxfb: probe of 0000:01:00.0 failed with error -1
>  > [...]
> 
> What does this mean?  Where can i find more information about this? I
> tried google but found no usable infos.

Kernel version?  System?  Processor?  What 'lspci -vvv -s 01:00.0' reports ?

Function pci_resource_start() reported zero, and matroxfb believes that
it is illegal.  If you are using ia32/x86_64/ia64, it is almost definitely
illegal, with ppc/ppc64 maybe NULL pci_resource_start() is valid and in such
case just remove tests for ctrlptr_phys == NULL and video_base_phys == NULL
from drivers/vide/matrox/matroxfb_base.c.
								Petr

[Linux-fbdev-users] Re: Problems with loading i810fb (/dev/fb0 missing)

[Ritesh R. S. <rit...@us...>]

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

Henryk Fuks wrote:

> Hi all,
> 
> I am using 82852/855GM integrated graphics device on my Centrino Laptop,
> running kernel 2.6.11 and X.org 6.8.2.
> 
> I would like to have simultaneously two features:
> 1) be able to switch to console via Ctrl-Alt-F1
> 2) run X with framebuffer driver
> 
> I can run VESA framebuffer (using video=791 in lilo.conf), but it
> does not allow me to switch to console (I get black screen), and I cannot
> see boot messages either.
> So I tried i810fb, but I cannot make it work. On my system (Xandros Linux
> 3.02) , i810fb is compiled as kernel module. If I load it by modprobe
> i810fb,
> it appears to get loaded, and  lsmod | grep i810fb  gives the output:
> 
> i810fb                 31872  0
> vgastate               10624  1 i810fb
> agpgart                33576  4 i810fb,drm,intel_agp
> 
> Unfortunately, the device /dev/fb is missing, and fbset gives error:
> open /dev/fb0: No such file or directory
> 
> Am I doing something wrong? Or is there some other option I could
> explore to get the features I listed at the beginning? Any suggestions
> or pointer will be much appreciated.
> 
> Henryk
> 

There's a code for VGA Console in the kernel called vgacon/vgaconfb.
AFAIK without that you don't get a console under fb.

rrs
- -- 
Ritesh Raj Sarraf
RESEARCHUT -- http://www.researchut.com
Gnupg Key ID: 04F130BC
"Stealing logic from one person is plagiarism, stealing from many is
research."
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC76xT4Rhi6gTxMLwRAukhAKCkoSTr92b9OXPRD8Dbj51OsNbb4ACePi+8
8l6pP8wMoMTwIdgmLEq1H1E=
=ua1s
-----END PGP SIGNATURE-----

[Linux-fbdev-users] matrox g550 problem (video RAM is not available in PCI address space)

[TAMAS G. <di...@mf...>]

Hi,

 > [...]
 > Kernel command line: root=/dev/hda2 ro video=matroxfb:vesa:0x18b
 > [...]
 > matroxfb: Matrox G550 detected
 > matroxfb: video RAM is not available in PCI address space, matroxfb disabled
 > matroxfb: probe of 0000:01:00.0 failed with error -1
 > [...]

What does this mean?  Where can i find more information about this? I
tried google but found no usable infos.

Thanks in advance,
Gergely

Re: [Linux-fbdev-users] Problems with loading i810fb (/dev/fb0 missing)

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

Henryk Fuks wrote:
> Hi all,
> 
> I am using 82852/855GM integrated graphics device on my Centrino Laptop, 
> running kernel 2.6.11 and X.org 6.8.2.
> 

Use intelfb.  i810fb is for i810/i815 chipsets only.

Tony

[Linux-fbdev-users] Problems with loading i810fb (/dev/fb0 missing)

[Henryk F. <hf...@br...>]

Hi all,

I am using 82852/855GM integrated graphics device on my Centrino Laptop, 
running kernel 2.6.11 and X.org 6.8.2.

I would like to have simultaneously two features:
1) be able to switch to console via Ctrl-Alt-F1
2) run X with framebuffer driver

I can run VESA framebuffer (using video=791 in lilo.conf), but it
does not allow me to switch to console (I get black screen), and I cannot
see boot messages either.
So I tried i810fb, but I cannot make it work. On my system (Xandros Linux 
3.02) , i810fb is compiled as kernel module. If I load it by modprobe i810fb,
it appears to get loaded, and  lsmod | grep i810fb  gives the output:

i810fb                 31872  0
vgastate               10624  1 i810fb
agpgart                33576  4 i810fb,drm,intel_agp

Unfortunately, the device /dev/fb is missing, and fbset gives error:
open /dev/fb0: No such file or directory

Am I doing something wrong? Or is there some other option I could
explore to get the features I listed at the beginning? Any suggestions
or pointer will be much appreciated.

Henryk

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

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

Would someone send me a snipet of code that shows how to call the
accelerator functions in fb_ops? All of the fun stuff seems to be defined
inside of a #ifdef __KERNEL__ section. How do I get at this?

Thanks!                     James.   :o)



----- Original Message ----- 
From: "James Lehman" <ja...@ak...>
To: <lin...@li...>
Sent: Friday, July 01, 2005 10:17 PM
Subject: Re: [Linux-fbdev-users] Blanking the screen : EZFB


> OK. I've looked at the code quite a bit and I've done some searching...
> Sorry if I'm getting into this and it has already been discussed, but are
> there any online docs about what changed in the new 2.6 frame buffer vs.
> 2.4? I see there is a thing called fb_info and it has a structure of
> function pointers in it that look like they do some fabulous things. All I
> create in my code is a user version of fix and var and a memmap to the
video
> ram. Are there some examples of instantiating an fb_info with fix and var
> encapsulated inside of it? Please note: I've been into computers most of
my
> life for one reason only... For art. I really want to get this right. I
just
> got a Matrox G400 with 32MB ram. I can double buffer a screen of 1600x1200
@
> 32. Even with a waist of time like memsetting zeros to every pixel on the
> screen for a wipe, it SMOKES! (in a good way). I also really want to get a
> mouse pointer working. Is all this stuff I see about "cursor" relevant to
> that or is that just character cell terminal block letter stuff?
>
> http://www.akrobiz.com/ezfb
> http://www.akrobiz.com/laserboy
>
> Thanks!    James.   :o)
>
>
>
>
> ----- Original Message ----- 
> From: "James Simmons" <jsi...@ww...>
> To: <lin...@li...>
> Sent: Tuesday, June 28, 2005 5:02 PM
> Subject: Re: [Linux-fbdev-users] Blanking the screen : EZFB
>
>
> >
> >
> > In 2.6.X the kernel side supports fillrect. Do a fillrect the size of
the
> > display with the color black.
> >
> > On Mon, 27 Jun 2005, James Lehman wrote:
> >
> > > 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)
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > 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
> > >
> >
> >
> > -------------------------------------------------------
> > 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
> >
>
>
>
> -------------------------------------------------------
> 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
>

Re: [Linux-fbdev-users] 2.6.13-rc2-mm2 -- vesafb mode and mtrr questions

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

On Thursday 14 July 2005 08:16, Miles Lane wrote:
> I am using Grub and have this in my kernel arguments:
> video=vesafb:ywrap,mtrr,vram:128 vga=792
>
> I have a 1280x768 laptop display.
>
> My Xorg.log contains:
>
> (II) I810(0): VESA VBE PanelID read successfully
> (II) I810(0): PanelID returned panel resolution : 1280x768
> (II) I810(0): VESA VBE DDC supported
> (II) I810(0): VESA VBE DDC Level 2
> *Mode: 7e (1280x768)
>         BitsPerPixel: 32
>
> Does this mean there is a way for me to tell vesafb to use this mode?
> I would like to have the consoles display in 1280x768.

Probably not.  1280x768 is not a standard vesa mode, so there is no
identifier for it.  It is possible though that the BIOS has an OEM id for
it.

Try scanning for the id.  Use vga=ask in your boot parameter.  Then
try each modes until you get the desired resolution.  If not, then you
have to use intelfb.

Tony

[Linux-fbdev-users] 2.6.13-rc2-mm2 -- vesafb mode and mtrr questions

[Miles L. <mil...@gm...>]

I am using Grub and have this in my kernel arguments:
video=3Dvesafb:ywrap,mtrr,vram:128 vga=3D792

I have a 1280x768 laptop display.

My Xorg.log contains:

(II) I810(0): VESA VBE PanelID read successfully
(II) I810(0): PanelID returned panel resolution : 1280x768
(II) I810(0): VESA VBE DDC supported
(II) I810(0): VESA VBE DDC Level 2
*Mode: 7e (1280x768)
        BitsPerPixel: 32

Does this mean there is a way for me to tell vesafb to use this mode?
I would like to have the consoles display in 1280x768.

Also, when I boot I see that there are problems with overlapping
mtrr regions.  I have read:
http://www.rage3d.com/board/showthread.php?t=3D33821469
but this doesn't give me enough information to understand my
current mtrr configuration:

cat /proc/mtrr
reg00: base=3D0x00000000 (   0MB), size=3D1024MB: write-back, count=3D1
reg01: base=3D0x3df00000 ( 991MB), size=3D   1MB: uncachable, count=3D1
reg02: base=3D0x3e000000 ( 992MB), size=3D  32MB: uncachable, count=3D1
reg03: base=3D0xe8000000 (3712MB), size=3D  16MB: write-combining, count=3D=
1

I only have 1Gig of RAM, so I don't know what this 3712MB could be=20
refering to.

mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x1000000
[drm] Initialized i915 1.1.0 20040405 on minor 0: Intel Corporation
82852/855GM Integrated Graphics Device
mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x1000000
[drm] Initialized i915 1.1.0 20040405 on minor 1: Intel Corporation
82852/855GM Integrated Graphics Device (#2)

vesafb: framebuffer at 0xe8000000, mapped to 0xf8880000, using 6144k,
total 32576k
vesafb: mode is 1024x768x32, linelength=3D4096, pages=3D9
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: Truecolor: size=3D8:8:8:8, shift=3D24:16:8:0

mtrr: base(0xe8020000) is not aligned on a size(0x3c0000) boundary
mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x1000000

0000:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM
Integrated Graphics Device (rev 02) (prog-if 00 [VGA])
        Subsystem: Hewlett-Packard Company: Unknown device 3080
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e8000000 (32-bit, prefetchable) [size=3D128M]
        Memory at e0000000 (32-bit, non-prefetchable) [size=3D512K]
        I/O ports at 1800 [size=3D8]
        Capabilities: [d0] Power Management version 1

0000:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated
Graphics Device (rev 02)
        Subsystem: Hewlett-Packard Company: Unknown device 3080
        Flags: bus master, fast devsel, latency 0
        Memory at f0000000 (32-bit, prefetchable) [disabled] [size=3D128M]
        Memory at e0080000 (32-bit, non-prefetchable) [disabled] [size=3D51=
2K]
        Capabilities: [d0] Power Management version 1

The system information says the video card has access to 128M of memory,
yet my Xorg log doesn't say that is getting used:

(--) I810(0): Chipset: "852GM/855GM"
(--) I810(0): Linear framebuffer at 0xE8000000
(--) I810(0): IO registers at addr 0xE0000000
(II) I810(0): 2 display pipes available.
(II) I810(0): detected 32636 kB stolen memory.
(II) I810(0): I830CheckAvailableMemory: 929788 kB available
(II) I810(0): Checking Lid status enabled
(--) I810(0): Pre-allocated VideoRAM: 32636 kByte
(=3D=3D) I810(0): VideoRAM: 32768 kByte
(=3D=3D) I810(0): video overlay key set to 0x101fe
(**) I810(0): page flipping disabled
(=3D=3D) I810(0): Display is using Pipe B
(--) I810(0): Maximum frambuffer space: 32600 kByte

What is going on?

How do I best optimize my vesafb and Xorg configurations?

          Miles

Re: [Linux-fbdev-users] Redirect the framebuffer /dev/fb0 to a DVB-Card

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

I'm not familiar with the exact hardware you have, but usually, a composite
video or s-video output from a conventional video card just works. All of
the magic of converting the computer monitor display to a TV compatible
signal is done on the video card. Have you tried any other application that
is designed to use the frame buffer? Perhaps it is only a matter of choosing
the right one. If there is more than one video output on a system, there
will be /dev/fb0, /dev/fb1, /dev/fb2, etc... The fb's that actually have
drivers to hardware behind them will be valid and may be opened for read and
write.

Take a look at this:
http://www.akrobiz.com/ezfb/

It might compile and run on your system. If so, it will most likely tell you
something about your video situation.
Let me know what happens.

Good Luck!       James.   :o)


----- Original Message ----- 
From: "jabiruh" <ja...@gm...>
To: <lin...@li...>
Sent: Sunday, July 10, 2005 3:29 PM
Subject: [Linux-fbdev-users] Redirect the framebuffer /dev/fb0 to a DVB-Card


> Hello,
> My linvdr (Mini-Distri for VDR) system has got two DVB-Cards and only a TV
> attatched to it (no other Monitor).
> Now I would like to install the webbrowser links2 which uses the
framebuffer
> to run graphic mode.
> Is there any possibility to redirect the output of the browser to TV over
the
> DVB-Card? Do I have to convert the framebuffer to mpeg first, so that
MPlayer
> can show it like other videos on TV?
> I already tried several mailing lists (MPlayer, ImageMagic and mjpeg) to
find
> a solution, but nobody knows how to do this).
> Reiner
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by
HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>

Re: [Linux-fbdev-users] Redirect the framebuffer /dev/fb0 to a DVB-Card

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

On Sun, 10 Jul 2005, jabiruh wrote:
> My linvdr (Mini-Distri for VDR) system has got two DVB-Cards and only a TV 
> attatched to it (no other Monitor).
> Now I would like to install the webbrowser links2 which uses the framebuffer 
> to run graphic mode.
> Is there any possibility to redirect the output of the browser to TV over the 
> DVB-Card? Do I have to convert the framebuffer to mpeg first, so that MPlayer 
> can show it like other videos on TV?
> I already tried several mailing lists (MPlayer, ImageMagic and mjpeg) to find 
> a solution, but nobody knows how to do this).

If your DVB card has a fullscreen OSD mode (some only support a limited number
of very small OSD windows), you can write a frame buffer device for the OSD
plane. Then you can have a text console, X, links2, ... in the OSD plane, and
video in the video plane underneath (controllable through an alpha/transparency
parameter).

This is a common approach in Set Top Boxes.

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] Redirect the framebuffer /dev/fb0 to a DVB-Card

[jabiruh <ja...@gm...>]

Hello,
My linvdr (Mini-Distri for VDR) system has got two DVB-Cards and only a TV 
attatched to it (no other Monitor).
Now I would like to install the webbrowser links2 which uses the framebuffer 
to run graphic mode.
Is there any possibility to redirect the output of the browser to TV over the 
DVB-Card? Do I have to convert the framebuffer to mpeg first, so that MPlayer 
can show it like other videos on TV?
I already tried several mailing lists (MPlayer, ImageMagic and mjpeg) to find 
a solution, but nobody knows how to do this).
Reiner

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

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

OK. I've looked at the code quite a bit and I've done some searching...
Sorry if I'm getting into this and it has already been discussed, but are
there any online docs about what changed in the new 2.6 frame buffer vs.
2.4? I see there is a thing called fb_info and it has a structure of
function pointers in it that look like they do some fabulous things. All I
create in my code is a user version of fix and var and a memmap to the video
ram. Are there some examples of instantiating an fb_info with fix and var
encapsulated inside of it? Please note: I've been into computers most of my
life for one reason only... For art. I really want to get this right. I just
got a Matrox G400 with 32MB ram. I can double buffer a screen of 1600x1200 @
32. Even with a waist of time like memsetting zeros to every pixel on the
screen for a wipe, it SMOKES! (in a good way). I also really want to get a
mouse pointer working. Is all this stuff I see about "cursor" relevant to
that or is that just character cell terminal block letter stuff?

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

Thanks!    James.   :o)




----- Original Message ----- 
From: "James Simmons" <jsi...@ww...>
To: <lin...@li...>
Sent: Tuesday, June 28, 2005 5:02 PM
Subject: Re: [Linux-fbdev-users] Blanking the screen : EZFB


>
>
> In 2.6.X the kernel side supports fillrect. Do a fillrect the size of the
> display with the color black.
>
> On Mon, 27 Jun 2005, James Lehman wrote:
>
> > 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)
> >
> >
> >
> >
> > -------------------------------------------------------
> > 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
> >
>
>
> -------------------------------------------------------
> 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
>

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

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

In 2.6.X the kernel side supports fillrect. Do a fillrect the size of the 
display with the color black.

On Mon, 27 Jun 2005, James Lehman wrote:

> 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)
> 
> 
> 
> 
> -------------------------------------------------------
> 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
> 

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

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

Interesting idea. Is this a pure software application? The writing suggest 
you modified the kernel. I haven't looked at the code.


On Mon, 27 Jun 2005, James Lehman wrote:

> 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
> >
> 
> 
> 
> -------------------------------------------------------
> 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
> 

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

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

On Mon, 27 Jun 2005, Roger Leigh wrote:
> 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!

http://www.sf.net/projects/linux-fbdev/ CVS module fbtest

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