linux-fbdev-users Mailing List for Linux Frame Buffer Device Development (Page 33)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I cannot get the agp/framebuffer code in the linuxppc 2.5 tree to 
compile.
Is anyone working on this?

	Miles

it still does not work :(

do you know where i can get info about radeonfb?

mfg
leif gensert

On 24 Feb 2003 05:34:05 +0800
Antonino Daplas <ad...@po...> wrote:

> On Sun, 2003-02-23 at 20:33, leif gensert wrote:
> > i have a ati radeon 8500 and i want to use radeonfb for my framebuffer
> > 
> > it actually works with the atyfb module and lilo.conf lines "vga=792" and append="video=atyfb:mode:1024x768,font:SUN12x22" vesafb also works.
> > 
> > ok first stupid question:
> > does it make sense to use radeonfb
> 
> atyfb and radeonfb seems to have overlapping device support (R100's,
> R200's and RV200's at least).  Choose which works best for you.
> 
> > 
> > when i use radeonfb i framebuffer starts but i only get 640x480 on my console. what am i doing wrong? i tried everything "video=radeonfb:mode:1024x768,font:SUN12x22" does not work without append it does not work and "video=atyfb:mode:1024x768,font:SUN12x22" doesn't work neither.
> > 
> 
> The mode: parameter is not needed.  Try:
> 
> "video=radeonfb":font:SUN12x22,1024x768
> 
> Tony
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
> The most comprehensive and flexible code editor you can use.
> Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
> www.slickedit.com/sourceforge
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> 

On Sun, 2003-02-23 at 20:33, leif gensert wrote:
> i have a ati radeon 8500 and i want to use radeonfb for my framebuffer
> 
> it actually works with the atyfb module and lilo.conf lines "vga=792" and append="video=atyfb:mode:1024x768,font:SUN12x22" vesafb also works.
> 
> ok first stupid question:
> does it make sense to use radeonfb

atyfb and radeonfb seems to have overlapping device support (R100's,
R200's and RV200's at least).  Choose which works best for you.

> 
> when i use radeonfb i framebuffer starts but i only get 640x480 on my console. what am i doing wrong? i tried everything "video=radeonfb:mode:1024x768,font:SUN12x22" does not work without append it does not work and "video=atyfb:mode:1024x768,font:SUN12x22" doesn't work neither.
> 

The mode: parameter is not needed.  Try:

"video=radeonfb":font:SUN12x22,1024x768

Tony

i have a ati radeon 8500 and i want to use radeonfb for my framebuffer

it actually works with the atyfb module and lilo.conf lines "vga=792" and append="video=atyfb:mode:1024x768,font:SUN12x22" vesafb also works.

ok first stupid question:
does it make sense to use radeonfb

when i use radeonfb i framebuffer starts but i only get 640x480 on my console. what am i doing wrong? i tried everything "video=radeonfb:mode:1024x768,font:SUN12x22" does not work without append it does not work and "video=atyfb:mode:1024x768,font:SUN12x22" doesn't work neither.

can you help me

mfg
leifg

On Sun, 2003-02-23 at 19:31, Antonino Daplas wrote:
>
> Yes, I saw that.  What I meant was XFBDev (and most fb-based
> applications) requires that video memory is mappable to userspace,
> otherwise the driver will only work within the console.  If you need to
> have these apps work, then you have to find a way to map the video
> memory.  Also fix->smem_start requires a physical address, so you need
> the virt_to_phys() macro.
> 
> You can try this in xxxfb_encode_fix():
> 
> fix->smem_start = virt_to_phys(info.vmemory)
> 
> If you're very lucky, vmalloc() might have given you a chunk of memory
> that is linear.  Do not rely on vmalloc() though, try __get_free_pages()
> instead.
> 

BTW: If you do intend to use __get_free_pages(), it will also return a
virtual pointer. So you still have to use virt_to_bus() or
virt_to_phys(). __get_free_pages() will probably give you around
128-512K of linear memory, possibly more, it depends on the machine
architecture.

Tony

On Sat, 2003-02-22 at 03:22, he...@ar... wrote:
> Thanks for sugesstions!
> 
> "STATIC_PSEUDOCOLOR" I will check. Problem: My Display have no hardware palette registers. So I can not handle this. It is a fix hardware monochrome black or white. What should I do, if Xserver calls me as "set color palette register"?
> 
If the hardware can only support black and white, then you have to
export the visual as FB_VISUAL_MONO01 (1 - black, 0 - white) or
FB_VISUAL_MONO10 (0 - black, 1 - white).  It's possible for a black and
white hardware to have 8 bpp (which means it will only accept 0x00/0xff
for black/white).  However, the logo drawing function assumes 1bpp only,
so monochrome 8-bpp hardware will not have the logo drawn correctly.

If your hardware does support 256 colors, but has no hardware registers,
then you must export it as STATIC_PSEUDOCOLOR.  A correctly-behaving
application should recognize that and not attempt to set the color
registers.  Your driver must however be capable of giving the calling
application the default colormap.

> Memory is ok.
> It's a special trick! Display have no physical memory. Can not mepped this. So a Interval Timer compare with a second shadow buffer and utpade differences to Screen Hardware. It's not good but have no other way.
> 
> In boot process is all ok. FB Text console works. FB logo is also ok.
> But how the Xserver Kdrive write only 0x00 into my video RAM? This clear only the full screen.
> 

Yes, I saw that.  What I meant was XFBDev (and most fb-based
applications) requires that video memory is mappable to userspace,
otherwise the driver will only work within the console.  If you need to
have these apps work, then you have to find a way to map the video
memory.  Also fix->smem_start requires a physical address, so you need
the virt_to_phys() macro.

You can try this in xxxfb_encode_fix():

fix->smem_start = virt_to_phys(info.vmemory)

If you're very lucky, vmalloc() might have given you a chunk of memory
that is linear.  Do not rely on vmalloc() though, try __get_free_pages()
instead.

Tony

Thanks for sugesstions!

"STATIC_PSEUDOCOLOR" I will check. Problem: My Display have no hardware palette registers. So I can not handle this. It is a fix hardware monochrome black or white. What should I do, if Xserver calls me as "set color palette register"?

Memory is ok.
It's a special trick! Display have no physical memory. Can not mepped this. So a Interval Timer compare with a second shadow buffer and utpade differences to Screen Hardware. It's not good but have no other way.

In boot process is all ok. FB Text console works. FB logo is also ok.
But how the Xserver Kdrive write only 0x00 into my video RAM? This clear only the full screen.

Henry

----------------------------------------------------------------------------
Schlagen Sie sofort zu - mit Arcor und eBay
Viele Artikel zum Sofort Kaufen!
http://www.arcor.de/auk/ebay_sk.php
-----------------------------------------------------------------------

On Fri, 2003-02-21 at 20:24, he...@ar... wrote:
> Hello Andre!
> 
> I have also problem to with SED1335 controller on BW LCD. I'm using my self writing driver based on fbcon-*.c
> 
> If booting with bpp=1 the linux logo is ok, text console is ok, but Xserver/Kdrive/Xfbdev don't work. In bpp=8 console text ok, but linux logo is black only, XServer shows only a empty screen.
> 
> So I'm think it is a palette problem. In my fact: I have no palette. I have only black or white.
> I don't know how handle functions ...encode_fix, ...decode_var, ...encode_var, ...get_par and ...set_par?
> 
> ftp://ssv-embedded.de/ssv/products/trm916/sample/x86/linux/fbdev/linux-2.4.20-fb916-20.patch.gz
> 
> Henry
> 
> 

Hi,

I checked your setcolreg() function and I don't see it setting the
hardware color registers.  The logo needs index 32 to index 255 to
display the logo.  One way or another you have to set this, unless your
hardware cannot set/hardwires the color registers (in which case you
need to use STATIC_PSEUDOCOLOR).

Secondly (but I'm not sure about this), you are using virtual memory
(vmalloc) for your screen_base (vmemory).  Then you use the same value
for fix->smem_start in encode_fix.  fix->smem_start requires a physical
address, not the virtual address.  Another problem is using the
virt_to_phys() or virt_to_bus() macro with a virtual pointer may not
work, since memory allocated by vmalloc is not guaranteed to be linear,
unless you're lucky.  So, your video memory may not be mappable to
user_space and apps which uses mmap, like XFBdev, may not work.

So if you want these kinds of apps to work  you might want to consider
another method of allocating video memory.  You can try __get_free_pages
but this is too expensive and the size you get is limited (pagesize *
2^page_order)  I don't know the maximum page order but I'm pretty sure
it's not a large amount.  Perhaps another solution is to create a
scatter-gather buffer.

Tony

Hello Andre!

I have also problem to with SED1335 controller on BW LCD. I'm using my self writing driver based on fbcon-*.c

If booting with bpp=1 the linux logo is ok, text console is ok, but Xserver/Kdrive/Xfbdev don't work. In bpp=8 console text ok, but linux logo is black only, XServer shows only a empty screen.

So I'm think it is a palette problem. In my fact: I have no palette. I have only black or white.
I don't know how handle functions ...encode_fix, ...decode_var, ...encode_var, ...get_par and ...set_par?

ftp://ssv-embedded.de/ssv/products/trm916/sample/x86/linux/fbdev/linux-2.4.20-fb916-20.patch.gz

Henry

----------------------------------------------------------------------------
Schlagen Sie sofort zu - mit Arcor und eBay
Viele Artikel zum Sofort Kaufen!
http://www.arcor.de/auk/ebay_sk.php
-----------------------------------------------------------------------

Well I have pretty much just given up. A BIOS issue is of course possible
but I wouldn't know how to tell. As for a native fbdev driver, I have a
GeForce 4 ti4600 so I think the rivafb would be the right one. I have
tried that however and it has the same results.

-Matt n.

On Wed, 12 Feb 2003, James Simmons wrote:

>
> Any luck? For teh life of me I can't figure it out. It could be a bug in
> the BIOS. Is there a native fbdev driver for that card?
>
> > No luck.  I have ACPI compiled as modules so I tried having them not load.
> > This didn't work so I recompiled with no power management at all. This
> > also had no effect.
> >
> > If I need to supply any additional information I would be happy to do so.
> >
> > Thanks for the suggestion it was something I had not thought to test.
> >
> > -Matt N.
> >
> > On Tue, 28 Jan 2003, James Simmons wrote:
> >
> > >
> > > > I guess I shouild have mentioned that this was the first thing I tried. My
> > > > kernel is compiled with support for 4GB of memory.
> > > >
> > > > Any other ideas?
> > >
> > > Do you have ACPI turned on? If you do try turning it off.
> > >
> > >
> > >
> > >
> >
> >
>
>
>

I have some new patches that I will post soon.

> hi all. 
> i have a (little) problem with X11. my mouse pointer is a funny coloured rectangle that changes when the mouse pointer should change. i believe this is a problem of rivafb module (2.5.59+riva.diff.gz patch). is there some piece of configuration i need to add? should i change something? somebody does know why my pointer seems so funny? thanks in advance.
> 
> 

Any luck? For teh life of me I can't figure it out. It could be a bug in 
the BIOS. Is there a native fbdev driver for that card?

> No luck.  I have ACPI compiled as modules so I tried having them not load.
> This didn't work so I recompiled with no power management at all. This
> also had no effect.
> 
> If I need to supply any additional information I would be happy to do so.
> 
> Thanks for the suggestion it was something I had not thought to test.
> 
> -Matt N.
> 
> On Tue, 28 Jan 2003, James Simmons wrote:
> 
> >
> > > I guess I shouild have mentioned that this was the first thing I tried. My
> > > kernel is compiled with support for 4GB of memory.
> > >
> > > Any other ideas?
> >
> > Do you have ACPI turned on? If you do try turning it off.
> >
> >
> >
> >
> 
> 

hi all. 
i have a (little) problem with X11. my mouse pointer is a funny coloured rectangle that changes when the mouse pointer should change. i believe this is a problem of rivafb module (2.5.59+riva.diff.gz patch). is there some piece of configuration i need to add? should i change something? somebody does know why my pointer seems so funny? thanks in advance.

-- 
Ivo Bellin Salarin
------------------
Email: iag...@io...
Jabber: ia...@ti...
Web: http://iago.ods.org

--- Hi! I'm a Signature virus! Please, copy me into your ~/.signature! ---

No luck.  I have ACPI compiled as modules so I tried having them not load.
This didn't work so I recompiled with no power management at all. This
also had no effect.

If I need to supply any additional information I would be happy to do so.

Thanks for the suggestion it was something I had not thought to test.

-Matt N.

On Tue, 28 Jan 2003, James Simmons wrote:

>
> > I guess I shouild have mentioned that this was the first thing I tried. My
> > kernel is compiled with support for 4GB of memory.
> >
> > Any other ideas?
>
> Do you have ACPI turned on? If you do try turning it off.
>
>
>
>

I posted this to the devel mailing list. I think I may have been in error
having done so. Therefor a am posting it here in hopes someone can help.

I was running debian with a 2.4.20(-3 I believe) with vesafb with no
problems with 512MB ram. I upgraded to 1GB and immediately I could not
boot. I get as far as the LILO prompt, but as soon as I hit enter the
screen goes black, the caps lock and scroll lock keyboard LEDs flash, and
nothing save hitting the reset button has any affect.

I can append 'mem=768M' to the kernel command line and everything boots
like normal except of course that then it think I have only 768MB RAM. If
I tell the kernel not to use vesafb by removing the 'vga=' line in my
lilo.conf then everything boots fine and my RAM is recognized.

I also have a second install of debian with kernel 2.4.19 on the same
machine. With this kernel it actually boots, however the screen stays
black. I can log in blindly and issue commands and dmesg reported the
following:

"vesafb: abort, cannot ioremap video memory 0x8000000 @ 0xd8000000"

This kernel also behaves normally if I specify 'mem=768M' on the kernel
command line or if I specify vga=normal (overriding my normal vga=792 from
lilo.conf). With 'mem=768M' set dmesg shows:

 vesafb: framebuffer at 0xd8000000, mapped to 0xf080e000, size 131072k
 vesafb: mode is 1024x768x32, linelength=4096, pages=1
 vesafb: protected mode interface info at c000:e350
 vesafb: scrolling: redraw
 vesafb: directcolor: size=8:8:8:8, shift=24:16:8:0
 Console: switching to colour frame buffer device 128x48
 fb0: VESA VGA frame buffer device

with 2.4.20 and 'mem=768M'

 vesafb: framebuffer at 0xd8000000, mapped to 0xf0800000, size 131072k
 vesafb: mode is 1024x768x32, linelength=4096, pages=1
 vesafb: protected mode interface info at c000:e350
 vesafb: scrolling: redraw
 vesafb: directcolor: size=8:8:8:8, shift=24:16:8:0
 Console: switching to colour frame buffer device 128x48
 fb0: VESA VGA frame buffer device

In testing I have found that I can go as high as 'mem=880M' with no
problem but 'mem=881M' ends in the same results as described above.

I don't know if this is a bug or something I may have overlooked or failed
to do. Hope someone can understand whats happening and parhaps offer a
possible solution..

Thanks and regards,
Matt N.

> I have just tried booting linux on my pegasos board, which contains a
> powerpc processor on a Mai Logic chipset (following the POP design from
> IBM). I use my old PCI Matrox Millenium II board. Linux boots fine (i
> can type stuff, and write to the harddisk), but i have no video output.
> I didn't manage yet to get any kind of boot log message, so i don't
> really know what the problem is, and typing blindly is not all that
> easy. So, my question is if you have reports of matroxfb working on
> powerpc or something such ? The board works fine in OF. I am using
> 2.4.18 + the POP patches 0.9.2 + a few pegasos specific changes which
> should not have any influence on the fbdev output.

Only if I had a PPC. 

P.S

   How is the pm3fb driver coming?

> Hi all,
> I've just installed on my computer a "new" Matrtox G400 dual-head and I 
> would like to run framebuffer on it.
> in my GRUB configuration I passed like a kernel argument 'vga=792'(this 
> works with my Riva TNT2 and with a Matrox G200)and at boot i saw this:
> _____
> You passed an undefined mode number.
> press <RETURN> to see video modes avaliable, <SPACE> to continue or wait 
> 30 secs.
> Video adapter: VESA VGA
> 
> MODE:        COLS X ROWS
> 0   0F00         80x25
> 1   0F01         80x50
> 2   0F02         80x43
> 3   0F03         80x28
> 4   0F05         80x30
> 5   0F06         80x34
> 6   0F07         80x60
> 7   0F0A        132x43
> 
> Enter mode number or 'scan':
> _____
> 
> I have this problem on linux 2.4.19 and 2.5.51
> I tried to use matroxfb(on 2.4.19), i tried to use vga=318,  like 
> explained in vesafb.txt, but i have always the same output.
> How can I enable fb with my Matrox G400 d-h?
 You are better off using the modedb stuff. Take a look at modedb.txt in 
Documentation/fb

Hello, ...

I have just tried booting linux on my pegasos board, which contains a
powerpc processor on a Mai Logic chipset (following the POP design from
IBM). I use my old PCI Matrox Millenium II board. Linux boots fine (i
can type stuff, and write to the harddisk), but i have no video output.
I didn't manage yet to get any kind of boot log message, so i don't
really know what the problem is, and typing blindly is not all that
easy. So, my question is if you have reports of matroxfb working on
powerpc or something such ? The board works fine in OF. I am using
2.4.18 + the POP patches 0.9.2 + a few pegasos specific changes which
should not have any influence on the fbdev output.

Friendly,

Sven Luther

Hi all,
I've just installed on my computer a "new" Matrtox G400 dual-head and I 
would like to run framebuffer on it.
in my GRUB configuration I passed like a kernel argument 'vga=792'(this 
works with my Riva TNT2 and with a Matrox G200)and at boot i saw this:
_____
You passed an undefined mode number.
press <RETURN> to see video modes avaliable, <SPACE> to continue or wait 
30 secs.
Video adapter: VESA VGA

MODE:        COLS X ROWS
0   0F00         80x25
1   0F01         80x50
2   0F02         80x43
3   0F03         80x28
4   0F05         80x30
5   0F06         80x34
6   0F07         80x60
7   0F0A        132x43

Enter mode number or 'scan':
_____

I have this problem on linux 2.4.19 and 2.5.51
I tried to use matroxfb(on 2.4.19), i tried to use vga=318,  like 
explained in vesafb.txt, but i have always the same output.
How can I enable fb with my Matrox G400 d-h?

Se you

    Moreno

On Tue, Dec 24, 2002 at 09:01:28PM +0100, Jurriaan wrote:
> I'd like to upgrade my kernel from 2.5.50, but then my matrox
> framebuffer stops compiling. It isn't yet upgraded to the new
> framebuffer model.
> 
> Unfortunatly, it's quite a big and complicated driver, and looking at
> the diff for the tdfxfb driver doesn't give me enough insight to fix the
> matrox driver.
> 
> Has someone already been busy with that and is there a patch to test?

There is nothing to test. I'm still investigating whether I should cripple
my driver and remove some functionality (text mode and fast putcs) from it 
to make it fit into the new API, or whether I should write complete console 
layer which will look like pre-2.5.51 fbcon... Or whether I should just
add old hooks to the new fbdev, so drivers will have much better chance
to work if they have some non-zero acceleration in hardware, not like
vesafb or radeonfb (sorry for picking that one, I was upgrading it to
2.5.50 API to have working display on my laptop, and to my surprise
there is no accel used there)...

Originally I thought that I'll have something before christmas, but
as you can see, there is still nothing, and I do not expect that it
will change this year.

Sorry. Either use vesafb, or pre-2.5.51 kernel like I do.
						Best regards,
							Petr Vandrovec

I'd like to upgrade my kernel from 2.5.50, but then my matrox
framebuffer stops compiling. It isn't yet upgraded to the new
framebuffer model.

Unfortunatly, it's quite a big and complicated driver, and looking at
the diff for the tdfxfb driver doesn't give me enough insight to fix the
matrox driver.

Has someone already been busy with that and is there a patch to test?

Thanks,
Jurriaan
-- 
"As we all know, cats now rule the world."
	John R. F. Breen 
GNU/Linux 2.5.50 SMP/ReiserFS 2x2752 bogomips load av: 0.00 0.00 0.00

André Stierenberg wrote:
> Hello,
> 
> I want to use a bigger font in the framebuffer, but I can´t find a font 
> of size 16x16 pixels... Where can I get these font or how can I create 
> it myself? I know that there fonts in the drivers/video directory in .c 
> - files, but how can I create it?

Does it have to be 16x16? If not, the biggest font in the kernel is
sun12x22.

I don't think I've ever seen a true 16x16 font. Once you get bigger
than 8x8 you tend to reserve more room for the descent (the space
below the baseline for chars like 'g', etc.) which results in
non-square char boxes. You could use xmbdfed to create a font
or modify one.

I have a patched xmbdfed to export to a .c file at home. I can try
to dig it up...

Cheers,
-- 
Frank Becker - Intrinsyc Software, Inc. - http://www.intrinsyc.com/
Need a break? http://criticalmass.sf.net/

Hello,

I want to use a bigger font in the framebuffer, but I can´t find a font 
of size 16x16 pixels... Where can I get these font or how can I create 
it myself? I know that there fonts in the drivers/video directory in .c 
- files, but how can I create it?

Andre

Hello,

i have some problems with a framebuffer. I´m using a PXA Processor and 
using a moncrom display.

If I want to write something the charakters are mirrored and isn´t 
displayed correctly, only parts. I can´t run bpp=1 so my display runs at 
bpp=4. If I swap the  definitions at the beginning of fbcon-cfb4.c for 
the ENDIANS the characters are display correctly, but the contrast 
between the backgrund and the charakters are not good. What can I do?

Could it be that the reason is the fact that I´m using bpp=4	instead of 
bpp=1?

Andre

Hello,

now my BW Display on the PXA Prozessor runs. But I´m not happy about the 
result. The problem is the following. If I run my 1-bit per pixel 
display with the pxafb driver in 1-bit per pixel mode, I can´t see 
anything. It is dark flickering the screen.
But if I use bpp=4 or bpp=8 I have no problem. I can see the charakters. 
But I don´t understand why I can´t run my display in monocrom mode. At 
some places in the drivers I have now problems because I´m using bpp>1 
instead of Black and White (e.g. in the parts for the linux logo... the 
kernel now uses a coloured image and therefore the result of the image 
on the screen are terrible).

I want to use my display with bpp=1! What can be the reason for my 
problem and how can I solve it?

Andre

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

linux-fbdev-users Mailing List for Linux Frame Buffer Device Development (Page 33)

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