Menu
▾
▴
linux-fbdev-users — Generic mailing list for users of frame buffers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
(10) |
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(5) |
Aug
(7) |
Sep
(15) |
Oct
(4) |
Nov
(3) |
Dec
(7) |
| 2003 |
Jan
(5) |
Feb
(30) |
Mar
(5) |
Apr
(13) |
May
(12) |
Jun
(11) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(7) |
| 2004 |
Jan
(4) |
Feb
(9) |
Mar
(16) |
Apr
(42) |
May
(5) |
Jun
(11) |
Jul
(3) |
Aug
(39) |
Sep
(5) |
Oct
(32) |
Nov
(27) |
Dec
|
| 2005 |
Jan
(11) |
Feb
(8) |
Mar
(22) |
Apr
(26) |
May
(9) |
Jun
(10) |
Jul
(7) |
Aug
(43) |
Sep
(23) |
Oct
(18) |
Nov
(15) |
Dec
(15) |
| 2006 |
Jan
(7) |
Feb
(16) |
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
(8) |
Jul
(3) |
Aug
(35) |
Sep
(7) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2007 |
Jan
(2) |
Feb
(30) |
Mar
(6) |
Apr
(7) |
May
(5) |
Jun
|
Jul
(15) |
Aug
(12) |
Sep
(22) |
Oct
(48) |
Nov
(9) |
Dec
(7) |
| 2008 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(5) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: James S. <jsi...@in...> - 2002-11-19 21:04:24
|
> I'm trying to compile framebuffer support into the 2.5.46 kernel. > I have > Video mode selection support > VESA VGA graphics console > Advanced low level driver options > 8 bpp packed pixels support > 24 bpp packed pixels support > > I've tried different modes, including 640x480 x24/x8 and 1280x1024 > x24/x8 but all I get is a black screen (the system starts up ok, just no > screen output). > I noticed that, compared to 2.4.18 (which I used before), there is no > "VGA characters/attributes support" option in 2.5.46 - I recall getting a black > screen on the 2.4.18 without this option... The VESA framebuffer driver has been ported over to the new fbdev api. You have to use Hardware Acceleration under Advance low level driver options. It will work after that. |
|
From: Jack <ja...@td...> - 2002-11-10 14:03:51
|
I'm trying to compile framebuffer support into the 2.5.46 kernel. I have Video mode selection support VESA VGA graphics console Advanced low level driver options 8 bpp packed pixels support 24 bpp packed pixels support I've tried different modes, including 640x480 x24/x8 and 1280x1024 x24/x8 but all I get is a black screen (the system starts up ok, just no screen output). I noticed that, compared to 2.4.18 (which I used before), there is no "VGA characters/attributes support" option in 2.5.46 - I recall getting a black screen on the 2.4.18 without this option... -- Jack Joergensen <jackj@/nospam/tdcadsl.dk> "\end{document} :wq" |
|
From: James S. <jsi...@ph...> - 2002-11-09 01:06:10
|
> have any of you out there got the ATI Radeon Mobility up and running > with framebuffer (radeonfb)? > > I've tried for days now, and the only thing that I can get to work is > the VESA fb. > > All help will be highly appreciated... Which kernel and whcih chipset? Also can you post your dmesg. |
|
From: Frode T. <ft...@ki...> - 2002-10-31 14:20:47
|
Hi all, have any of you out there got the ATI Radeon Mobility up and running with framebuffer (radeonfb)? I've tried for days now, and the only thing that I can get to work is the VESA fb. All help will be highly appreciated... Regards Frode Trydal |
|
From: James S. <jsi...@in...> - 2002-10-18 16:44:31
|
> I have been hoping to see this driver become usable again > and would like to see a ported driver before the 2.5 > feature freeze. I can give it a shot. I still have some of the code around when I did port it over. |
|
From: Miles L. <mil...@at...> - 2002-10-16 04:53:38
|
I have been hoping to see this driver become usable again and would like to see a ported driver before the 2.5 feature freeze. Miles |
|
From: Meelis R. <mr...@li...> - 2002-10-12 22:07:54
|
Short summary: offb works with one graphics card but not with another. I have a PowerMac 7300. It has abuiltin Control framebuffer device and a PCI s3virge device (Formac GA6). Using controlfb on /chaos/control is fine, so let's forget it for now (the control device has one bad bit when writing to its memory). Using offb on /chaos/control is OK too. Using offb on s3virge (/bandit/formacga6) is not OK - it produces strange filesystem locking oopses on disk load (posted on LKML recently). This was tested when using the config option 'Support for early boot text console (BootX or OpenFirmware only)'. When this option was turned off, no picture was shown on the screen (MacOS desktop image stayed) but the keyboard worked and probably the dummy console was used. OFfb was not activated (seen from dmesg and /proc/fb) and the machine was stable under load. So it seems that OFfb works with Control but not with s3virge. I want to use the s3virge device because of the bad bit in Control. Any ideas where to start debugging the instability? -- Meelis Roos (mr...@li...) |
|
From: Kalyan C. D. <ka...@sa...> - 2002-09-27 07:22:29
|
Hi,
I am using Linux 2.4.8 with necessary patches for ARM processor. I
am using SA-1110 processor running at 206 MHz, with a 640x480 Hitachi
8-bit color LCD. I am trying to display a logo at boot up time.
I am replacing the penguin logo header file with the header file
of the image which I want to display, with appropriate changes for the
LOGO_H and LOGO_W. I tried the same method with LCD's of 320x240 size and
I am able to display logo's of size of 320x240 both mono chrome and
color with out any problem. On the 640x480 LCD, I am able
to display penguin logo and other logo's of size upto 320x240. If I try to
display an image of size 640x480 kernel panics while booting. Is there any
limitation on the size of the logo that can be displayed while booting? Is
there any fix provided if the limitation is there?
Any pointers will be helpful,
thanks,
kalyan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kalyan C Dasari
IAS-BlackRose
Sasken Communication Technologies Limited
Bangalore
Phone -- (o)- 53 555 01 / 53 555 03 extn: 3322
(R)- 5542448
E-mail ka...@sa...
_____________________________________________________________________
CONFIDENTIALITY INFORMATION AND DISCLAIMER
---------------------------------------------------------------------
"This communication sent by Sasken Communication Technologies Limited is
privileged and confidential, and is directed to and for the use of the
addressee only. If this message reaches anyone other than the intended
recipient, we request the reader not to reproduce, copy, disseminate or in
any manner distribute it. We further request such recipient to notify us
immediately by return email and delete the original message.
Sasken does not guarantee the security of any information transmitted
electronically and is not liable for the proper, timely and complete
transmission thereof. Opinions, conclusions and other information in this
communication that do not relate to the official business of Sasken shall
be understood as neither given nor endorsed by it."
_____________________________________________________________________
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
From: Aradhana P. <ara...@wi...> - 2002-09-26 12:21:03
|
Hallo, I have a SA1110 based board with linux-2.5.6-rmk1 running on it. On this = board I am trying to make an ALPS monochrome LCD work, whose resolution = is 240X320 and has 4Bpp. The problem: If I configure the LCD for 320X240 mode, I get two screens, the first = one being of length 240 pixels and the next one being 120 pixels and two = logos along with 2 cursors blinking, with a good contrast. Since the LCD is portrait type i.e 240X320, so when I make the changes = to drivers/video/sa1100fb.c for this resolution, the penguin logo comes = alongwith the cursor but within 5-10 seconds the logo fades away and the = cursor becomes invisible. I have struggled a lot to find the reason behind it and am stuck up on = this for a number of weeks on this. I get the timing calculations for = 320X240 only @ 70Hz but not for 240X320 @ 70Hz.=20 Can somebody please give me pointers as to what I should look into. Thanks and Regards....Aradhana DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to = Wipro Limited and is intended for use only by the individual or entity = to which it is addressed, and may contain information that is = privileged, confidential or exempt from disclosure under applicable law. = If this is a forwarded message, the content of this E-MAIL may not have = been sent with the authority of the Company. If you are not the intended = recipient, an agent of the intended recipient or a person responsible = for delivering the information to the named recipient, you are notified = that any use, distribution, transmission, printing, copying or = dissemination of this information in any way or in any manner is = strictly prohibited. If you have received this communication in error, = please delete this mail & notify us immediately at mai...@wi... |
|
From: Geert U. <ge...@li...> - 2002-09-25 08:37:25
|
On Tue, 24 Sep 2002, Frank Wang wrote:
> I wonder if anybody know the mmap() works for the frame buffer devices in
> general? I have tried to do mmap() on the virtual frame buffer deivce
> (drivers/video/vfb.c driver) and it doesn't seem to map out the correct
> address to the memory allocated in the device driver. Any clue will be
> greatly appreciated.
You found one of the few exceptions :-) Vfb doesn't support mmap() of the
frame buffer. Almost all other frame buffer devices do.
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
|
|
From: Frank W. <fr...@at...> - 2002-09-24 22:59:03
|
Hi, I wonder if anybody know the mmap() works for the frame buffer devices in general? I have tried to do mmap() on the virtual frame buffer deivce (drivers/video/vfb.c driver) and it doesn't seem to map out the correct address to the memory allocated in the device driver. Any clue will be greatly appreciated. Thanks. Frank Wang @ Advanced Technology Video Inc. |
|
From: T S. <ts...@id...> - 2002-09-23 22:11:01
|
Hi, I am using the kernel 2.4.6-rmk1-rayl1 on edb89712. I need a lcd frame buffer device driver. Does anyboby have experience how to configure the kernel with frame buffer support? Thanks in advance. T. Song Iders Incorporated 600A Clifton St. Winnipeg, Manitoba Canada R3G 2X6 ph: 204 779 5400 x45 fax: 204 779 5444 http:\\www.iders.ca |
|
From: <kn...@ma...> - 2002-09-23 06:23:22
|
> From: "Munjun Kang" <ma...@ee...> > To: <lin...@li...> > Date: Mon, 16 Sep 2002 22:06:36 +0900 > Subject: [Linux-fbdev-users] Can I get the savage4 frame buffer driver? > "savagefb.c" > You can download kernel patch including savage4 fb driver from www.directfb.org in section patches __________________________________ 12MB-POP3-WAP-SMS---TOBA-E-mail.bG ---------------------------------- " Ako uckame u Bue agpec B mail.bg ugeme myk: http://www.mail.bg/new/ " |
|
From: Munjun K. <ma...@ee...> - 2002-09-16 13:06:51
|
SGVsbG8uDQpJJ20gbmV3YmllIGluIGZyYW1lIGJ1ZmZlciBkcml2ZXIuDQpDYW4gSSBnZXQgdGhl IHNhdmFnZTQgZnJhbWUgYnVmZmVyIGRyaXZlcj8gInNhdmFnZWZiLmMiDQpQbHouIHJlcGx5Lg0K VGhhbmtzIGZvciByZWFkaW5nLg0KUmVnYXJkcywNCk1hbGFzDQoNCg== |
|
From: Saurabh N. <na...@ii...> - 2002-09-12 06:22:45
|
okay, I got the point rivafb and vesafb together is a bad thing to do. So i compiled two new kernel (2.4.19) (i) with only rivafb - this one gives me only 640x480@(8/16/24) (ii) with only vesafb - this one gives me all the resolutions I want. Now I come to my next woe... setting up the XF86-FBDev I am attaching my XF86Config file and the output by the XServer when it fails to start. Does rivafb support more that 640x480?? One more problem (might not be appropriate to ask here) - when i use mplayer with -vo fbdev the picture doesn't get full screen. Any pointers?? Thanx in advance. Saurabh Nanda |
|
From: Jurriaan <thu...@xs...> - 2002-09-12 05:28:55
|
From: Saurabh Nanda <na...@ii...> Date: Thu, Sep 12, 2002 at 08:54:01AM +0530 > Hi, > Been trying to get my system work with the framebuffer but have some > troubles. > I compiled 2.4.19 with the > * VGA Text Console > * Video Mode Selection Support > * Support for frame buffer devices > * nVidia Riva Support > * VESA VGA Graphics Console > > I have a Riva TNT2 32MB. > When I try to go into the video mode "314" (or any other mode) I always > get /dev/fb0 with the following resolution: > > mode "640x480-60" > # D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz > geometry 640 480 640 480 8 > timings 39721 40 24 32 11 96 2 > accel true > rgba 8/0,8/0,8/0,0/0 > endmode > > Frame buffer device information: > Name : nVidia RIVA-VTNT > Address : 0xde000000 > Size : 33554432 > Type : PACKED PIXELS > Visual : PSEUDOCOLOR > XPanStep : 1 > YPanStep : 1 > YWrapStep : 0 > LineLength : 640 > MMIO Address: 0xdc000000 > MMIO Size : 16777216 > Accelerator : Unknown (28) > > And /dev/fb1 with the following: > mode "800x600-75" > # D: 48.001 MHz, H: 46.876 kHz, V: 75.121 Hz > geometry 800 600 800 600 16 > timings 20833 96 32 16 4 96 4 > rgba 5/11,6/5,5/0,0/0 > endmode > > Frame buffer device information: > Name : VESA VGA > Address : 0xde000000 > Size : 33554432 > Type : PACKED PIXELS > Visual : TRUECOLOR > XPanStep : 0 > YPanStep : 0 > YWrapStep : 0 > LineLength : 1600 > Accelerator : No > > I do not understand what is happening. > I have also attached my dmesg output along with this message. > > rivafb: RIVA MTRR set to ON > Console: switching to colour frame buffer device 80x30 > rivafb: PCI nVidia NV4 framebuffer ver 0.9.3 (RIVA-VTNT2, 32MB @ 0xDE000000) > vesafb: abort, cannot reserve video memory at 0xde000000 It looks like you have compiled in both rivafb and vesafb into your kernel. rivafb starts first, vesafb second and vesafb then complains rivafb has taken all memory. vesafb then can only use a very low-grade resolution. Recompile your kernel without vesafb, would be my suggestion. Good luck, Jurriaan -- Remember, Unix on some machines is nUxi. GNU/Linux 2.4.19-ac4 SMP/ReiserFS 2x1402 bogomips load av: 0.22 1.24 1.49 |
|
From: Saurabh N. <na...@ii...> - 2002-09-12 03:26:23
|
Hi,
Been trying to get my system work with the framebuffer but have some
troubles.
I compiled 2.4.19 with the
* VGA Text Console
* Video Mode Selection Support
* Support for frame buffer devices
* nVidia Riva Support
* VESA VGA Graphics Console
I have a Riva TNT2 32MB.
When I try to go into the video mode "314" (or any other mode) I always
get /dev/fb0 with the following resolution:
mode "640x480-60"
# D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz
geometry 640 480 640 480 8
timings 39721 40 24 32 11 96 2
accel true
rgba 8/0,8/0,8/0,0/0
endmode
Frame buffer device information:
Name : nVidia RIVA-VTNT
Address : 0xde000000
Size : 33554432
Type : PACKED PIXELS
Visual : PSEUDOCOLOR
XPanStep : 1
YPanStep : 1
YWrapStep : 0
LineLength : 640
MMIO Address: 0xdc000000
MMIO Size : 16777216
Accelerator : Unknown (28)
And /dev/fb1 with the following:
mode "800x600-75"
# D: 48.001 MHz, H: 46.876 kHz, V: 75.121 Hz
geometry 800 600 800 600 16
timings 20833 96 32 16 4 96 4
rgba 5/11,6/5,5/0,0/0
endmode
Frame buffer device information:
Name : VESA VGA
Address : 0xde000000
Size : 33554432
Type : PACKED PIXELS
Visual : TRUECOLOR
XPanStep : 0
YPanStep : 0
YWrapStep : 0
LineLength : 1600
Accelerator : No
I do not understand what is happening.
I have also attached my dmesg output along with this message.
Thanks in advance...
Saurabh Nanda
|
|
From: Steve <st...@sh...> - 2002-09-08 10:43:34
|
(My apologies if this has been posted twice)
Hi,
I'm running the 2.4.19 kernel with atyfb on a Mach64VT card.
This all works fine:-
/usr/src/linux# fbset -v
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven
Opening frame buffer device `/dev/fb0'
Using current video mode from `/dev/fb0'
mode "640x400-70"
# D: 25.157 MHz, H: 31.446 kHz, V: 69.879 Hz
geometry 640 400 640 3251 8
timings 39751 40 24 39 9 96 2
accel true
rgba 8/0,8/0,8/0,0/0
endmode
but I cannot switch interlaced video on:-
/usr/src/linux# fbset -laced true
ioctl FBIOPUT_VSCREENINFO: Invalid argument
Checking the newsgroups I see other people have similar problems.
Any ideas?
Steve.
|
|
From: <Pl...@se...> - 2002-09-08 10:35:54
|
Hi,
I'm running the 2.4.19 kernel with atyfb on a Mach64VT card.
This all works fine:-
/usr/src/linux# fbset -v
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven
Opening frame buffer device `/dev/fb0'
Using current video mode from `/dev/fb0'
mode "640x400-70"
# D: 25.157 MHz, H: 31.446 kHz, V: 69.879 Hz
geometry 640 400 640 3251 8
timings 39751 40 24 39 9 96 2
accel true
rgba 8/0,8/0,8/0,0/0
endmode
but I cannot switch interlaced video on:-
/usr/src/linux# fbset -laced true
ioctl FBIOPUT_VSCREENINFO: Invalid argument
Checking the newsgroups I see other people have similar problems.
Any ideas?
Steve.
|
|
From: <jo...@br...> - 2002-09-06 22:35:33
|
> > What graphics card? > With a matrox you can do almost anything you want :-) > No its a SIS630 ST=20 and I am using the vesafb with kernel 2.2.20 (cant use kernel 2.4 on my l= aptop=20 because it crashes :( ) Joern --=20 http://joern.bratzke.net -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GS d- s: a-- C++ UL++ P+ L++ E- W++ N++ o? K? w-- O? M- V? PS PE Y? PGP+ t+ 5 X R+ tv+ b+ DI D+ G++ e h+ r++ y+ ------END GEEK CODE BLOCK------ |
|
From: Jurriaan <thu...@xs...> - 2002-09-06 19:51:47
|
From: J?rn Bratzke <jo...@br...> Date: Fri, Sep 06, 2002 at 07:35:32PM +0200 > Hello list! > > I need to set up a framebuffer with 1024x600 > because it isnt a Vesa standart resolution i cant set it up at boottime and > fbset wont let me change the resolution... can anyone help me?? What graphics card? With a matrox you can do almost anything you want :-) Jurriaan -- It might look like I'm doing nothing, but at the cellular level I'm really quite busy. Hans Haas GNU/Linux 2.4.20-pre4-ac2 SMP/ReiserFS 2x1402 bogomips load av: 1.14 1.34 1.17 |
|
From: <jo...@br...> - 2002-09-06 17:35:37
|
Hello list! I need to set up a framebuffer with 1024x600 because it isnt a Vesa standart resolution i cant set it up at boottime a= nd=20 fbset wont let me change the resolution... can anyone help me?? greets Joern --=20 http://joern.bratzke.net -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GS d- s: a-- C++ UL++ P+ L++ E- W++ N++ o? K? w-- O? M- V? PS PE Y? PGP+ t+ 5 X R+ tv+ b+ DI D+ G++ e h+ r++ y+ ------END GEEK CODE BLOCK------ |
|
From: <wil...@al...> - 2002-08-28 13:02:47
|
Hi,
I have a SBC with a MediaGX graphics card. I run Redhat 6.2 on it. My
application is written using Qt embedded.
I can select modes from the fb.modes file (Mach64 ATI).
I want to drive an LCD display and need to change the resolution to
480x234.
How to I calculate (tune) the timings for that resolution?
When I try to change the geometry to anything different than standard video
modes I get the following error:
Cannot Support Requested CRTMode 480x234 8 (39722, 60), 3
ioctl FBIOPUT_VSCREENINFO: Invalid argument.
This is an example from the fb.modes file:
# 640x480, 60 Hz, Non-Interlaced (25.175 MHz dotclock)
#
# Horizontal Vertical
# Resolution 640 480
# Scan Frequency 31.469 kHz 59.94 Hz
# Sync Width 3.813 us 0.064 ms
# 12 chars 2 lines
# Front Porch 0.636 us 0.318 ms
# 2 chars 10 lines
# Back Porch 1.907 us 1.048 ms
# 6 chars 33 lines
# Active Time 25.422 us 15.253 ms
# 80 chars 480 lines
# Blank Time 6.356 us 1.430 ms
# 20 chars 45 lines
# Polarity negative negative
#
mode "640x480-60"
# D: 25.175 MHz, H: 31.469 kHz, V: 59.94 Hz
geometry 640 480 640 480 8
timings 39722 48 16 33 10 96 2
endmode
Thank you for your help.
Wilhelm Leichtfried
wil...@al...
|
|
From: Gul J. <jon...@ma...> - 2002-08-26 11:37:10
|
Ok, the problem is this. I would like to set up a display by writing to the VGA registers. Before working through the (very verbose) documentation i found on the net, i would like to know if anyone who had done that before had some code to share. I've had a look at the Tweak utility for DOS and tried to mimick its behaviour, but i seem to have overlooked something, because, it won't work :( To be precise, i just took the values for BIOS mode 13h and wrote them to the registers, which blanked the screen, but mmapping the default VGA page (at 0xA0000) and writing to it didn't have any effect. -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup |
|
From: Hermes <he...@rd...> - 2002-08-25 20:53:13
|
Hello, I noticed that I am not having any framebuffer options in my kernel (2.4.19) under Console Drivers => I only have : - Vga text console - Video mode selection support Should I patch my kernel in order to be able to use the framebuffer ? I want to use 1024/768 @ 16 bit console. Thanks, Pieterjan -- Pieterjan Heyse E-Mail: He...@rd... ICQ: 43037479 GSM: 0496/755987 http://www.rds-clan.be Sent with The Bat! v1.51 |
6 messages has been excluded from this view by a project administrator.
