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

[Linux-fbdev-users] Radeon Mobility M9 with external TFT-monitor

[<lyn...@fr...>]

Hallo!


I have a Laptop with a Radeon Mobility M9 graphics card that has an external vga
connector.  I  got a new TFT-Monitor with 1280x1024 resolution and would like to
use its full resolution with a console framebuffer so that  I  have  160x64  for
text  with the laptop monitor switched off. The problem I got is that the laptop
monitor is only 1024x768 and when  radeonfb  probes everything it is taking this
smaller  resolution  from  the  bios  panel even if the laptop monitor is off. I
tried to change it with video=radeonfb:1280x1024@75  for  the  kernel  but  that
yielded  a  1280x1024 with a view port of only 1024x768. With that I mean on the
left and bottom the parts bigger than 1024x768 are not shown. This  is  only  on
the first console. On the others I have just a usual 1024x768.
I  also  tried video=vesafb:ywrap,mtrr vga=0x31A but then the external is saying
"freq. out of range" which should be 75Hz I think but vesafb is always at  60Hz.
The laptop monitor has a grayening effect...
I   had   a   look   in   the  sources  but  do  not  understand  much.  Is  the
video=radeonfb:1280x1024@75 right for the  radeon  driver?  I  took  the  aty128
readme  because  there is none for the radeon driver. Is there a way to override
the bios panel data so that I finally get what I want?
Under X I can get a resolution of 1280x1024 on the external and 1024x768 on  the
internal  monitor  so from that I think I can assume my graphics card can handel
the higher resolution.
I tried also to change the mode with "fbset -v lynx" to:
mode "lynx"
    # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
    geometry 1280 1024 1280 1024 8
    timings 7812 216 40 48 2 64 4  # 128 MHz, 80.0 kHz, 74.2 Hz
endmode

timings are from videogen -fb but fbset -i shows that nothing changed.

In  the  framebuffer HOWTO I read about getting the external monitor showing a
different tty than the internal with con2fb. I'd really love that but I  don't
know  how to get the external connector being assosiated with /dev/fb1 as it's
all just one graphics-card. Can that be achiefed some how?

My System: LFS 5.1.1 or SuSE 8.1

Thanks a lot for any help or hints
Lynx

RE: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Gil B. <co...@ba...>]

Okay, I made some very important progress:

I hard-coded the correct values into dsp_config and dsp_on_off. Presto - =
no
more disruption.
But the code does seem to boot when using quik. Which means that when OF
initializes the card, it sets some values that are not being touched =
later
on, or at least used to generate the (bogus) dsp_config and dsp_on_off.
Since the BIOS probe code entered, maybe the driver was cleaned of =
forced
programming of registers, which macs depended on for correct operation.

Gil Bahat,
System Administrator.

-----Original Message-----
From: lin...@li...
[mailto:lin...@li...] On Behalf Of Gil
Bahat
Sent: Saturday, November 05, 2005 7:15 PM
To: lin...@li...
Subject: RE: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and
Beige G3

Hello,

I have now decoded and mapped the register differences as they appeared =
in
http://patchwork.ozlabs.org/linuxppc/patch?id=3D1268. However, I have =
went
through the code path and cannot explain most of the reasons for the
changes, nor can I estimate their effect. That's where the list might =
come
handy :)

So, after applying the patch:

BUS_CNTL changes from 7b23a040 to 7b23a050. this is due to the code =
section
that enables auxillary aperture to enable access to 8mb memory cards.

CRTC_GEN_CNTL changes from 03000200 to 0b000200. I have noticed the code =
in
mach64_ct.c has removed a particular bit masking when assigning =
GEN_CNTL,
but I have no idea why.

DSP_CONFIG also changes. It becomes 004805FA instead of 004808e2. no =
idea
why - the code that generates it looks the same to me.

DSP_ON_OFF also changes. It becomes 00B4043B instead of 009C0666. ditto =
for
the reasoning.

PLL is also different in its first 24 bytes:
ADD52414 instead of ADD52144
A80382D1 instead of E80382D1
8E829601 instead of 8E9E9814
I don't know how to decode this yet.

Can anyone have a look at mach64_ct.c and maybe notice what I haven't
noticed regarding the DSP programming?

Thanks,

Gil Bahat,
System Administrator.



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. =
Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Linux-fbdev-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users

RE: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Gil B. <co...@ba...>]

Hello,

I have now decoded and mapped the register differences as they appeared in
http://patchwork.ozlabs.org/linuxppc/patch?id=1268. However, I have went
through the code path and cannot explain most of the reasons for the
changes, nor can I estimate their effect. That's where the list might come
handy :)

So, after applying the patch:

BUS_CNTL changes from 7b23a040 to 7b23a050. this is due to the code section
that enables auxillary aperture to enable access to 8mb memory cards.

CRTC_GEN_CNTL changes from 03000200 to 0b000200. I have noticed the code in
mach64_ct.c has removed a particular bit masking when assigning GEN_CNTL,
but I have no idea why.

DSP_CONFIG also changes. It becomes 004805FA instead of 004808e2. no idea
why - the code that generates it looks the same to me.

DSP_ON_OFF also changes. It becomes 00B4043B instead of 009C0666. ditto for
the reasoning.

PLL is also different in its first 24 bytes:
ADD52414 instead of ADD52144
A80382D1 instead of E80382D1
8E829601 instead of 8E9E9814
I don't know how to decode this yet.

Can anyone have a look at mach64_ct.c and maybe notice what I haven't
noticed regarding the DSP programming?

Thanks,

Gil Bahat,
System Administrator.

[Linux-fbdev-users] Re: virtual frame buffer

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

Yan,

  Don't know if this will help or in fact it is what you really want to do:

    http://mt-umunhum-wireless.net/hacks/multiple_wm.html#Remote

  I use this procedure all the time and it works very well even over a 
wireless bridge.
You will need to install an X server on the embedded system.

  Good luck.

>Message: 1
>Date: Wed, 12 Oct 2005 07:26:34 -0700
>From: Yan Seiner <ya...@se...>
>To: lin...@li...
>Subject: [Linux-fbdev-users] virtual frame buffer
>Reply-To: lin...@li...
>

>I am trying to set up a graphical system on an embedded system with no 
>video hardware at all.  I am using nano-x (http://www.microwindows.com) 
>The output is into the virtual frame buffer, and then I am trying to use 
>vnc to remote the display to another computer.
>


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

RE: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Gil B. <co...@ba...>]

Sorry for the late reply, But i've been getting a lot of internal =
compiler
errors on my powermac and it's slow to compile kernels on. Only when I =
found
out it was due to not enabling swap space, did compiling go smoother. =
While
it did seem to be able to completely compile both patches, neither of =
them
worked - the phenomena is still there and the kernel crashes almost =
right
after loading the aty framebuffer.=20
Maybe some testing with a more stable box is in order... but that's all =
I
have. I'll continue looking.=20

Thanks,

Gil Bahat

Re: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Ville <sy...@sc...>]

On Mon, Oct 31, 2005 at 09:07:32AM +0200, Gil Bahat wrote:
> Hello,
>=20
> =20
>=20
> I suspect I have found the reason for the breakage I reported earlier i=
n the
> driver - but I'd be very happy if someone was confirming that my attemp=
t
> wouldn't mess up my hardware before I set off to test it.
>=20
> =20
>=20
> This addition:
>=20
> =20
>=20
> +   /* according to ATI, we should use clock 3 for acelerated mode */
> +   par->clk_wr_offset =3D 3;
>=20
> =20
>=20
> comes up right after a nice piece of code that actually tries to mask
> clk_wr_offset:
>=20
> =20
>=20
> +   if (!(aty_ld_le32(CRTC_GEN_CNTL, par) & CRTC_EXT_DISP_EN))
> +      par->clk_wr_offset =3D (inb(R_GENMO) & 0x0CU) >> 2;
> +   else
> +      par->clk_wr_offset =3D aty_ld_8(CLOCK_CNTL, par) & 0x03U;
>=20
> =20
>=20
> and so makes this code redundant with a static value that "seems" to co=
me
> out of nowhere.

clk_wr_offset just decides which VCLK "preset slot" we use to store the=20
VCLK settings. It won't make any real difference which one is used. It's=20
just some standard to use the last slot. I guess the lower slots are=20
typically used for storing VGA clock settings or something like that.

> Furthermore, looking at atyfb.h, this particular register has overloade=
d
> meaning (by its comment) so it may cause the unexpected results I'm see=
ing.

I think that just means that it's used with GX chips as an actual write
offset. With CT chips it's used as a clock id which is actaully the same
thing as the preset slot thin I said earlier. In other words it has=20
nothing to do with your case.

Did you try the dsp_loop_latency patch I sent earlier?

--=20
Ville Syrj=E4l=E4
sy...@sc...
http://www.sci.fi/~syrjala/

Re: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Gil B. <co...@ba...>]

Hello,

=20

I suspect I have found the reason for the breakage I reported earlier in =
the
driver - but I'd be very happy if someone was confirming that my attempt
wouldn't mess up my hardware before I set off to test it.

=20

This addition:

=20

+   /* according to ATI, we should use clock 3 for acelerated mode */
+   par->clk_wr_offset =3D 3;

=20

comes up right after a nice piece of code that actually tries to mask
clk_wr_offset:

=20

+   if (!(aty_ld_le32(CRTC_GEN_CNTL, par) & CRTC_EXT_DISP_EN))
+      par->clk_wr_offset =3D (inb(R_GENMO) & 0x0CU) >> 2;
+   else
+      par->clk_wr_offset =3D aty_ld_8(CLOCK_CNTL, par) & 0x03U;

=20

and so makes this code redundant with a static value that "seems" to =
come
out of nowhere.

Furthermore, looking at atyfb.h, this particular register has overloaded
meaning (by its comment) so it may cause the unexpected results I'm =
seeing.

But. these 4 lines of code replace an even bigger PLL calculation =
routine,
and I do not know if they are correct or are just an attempt to read the
value that got "commented out" because it was not complete.

=20

So I ripped out the first two lines and count on the next 4 lines to
initialize clk_wr_offset.

I already compiled the appropriate kernel, but since my understanding of =
all
the hidden subtleties of the mach64 registers is far from complete, and =
my
only mac is an all-in-one machine where damage to the crt by wrong =
clocking
will render the entire box useless, I would appreciate it if you tell me =
at
least what you think and if I am putting my hardware at any risk.

=20

Thanks,

=20

Gil Bahat,

System Administrator.

Re: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Ville <sy...@sc...>]

On Fri, Oct 28, 2005 at 10:18:36PM +0200, Geert Uytterhoeven wrote:
> On Fri, 28 Oct 2005, coutal coutal wrote:
> > i am using the atyfb driver on my powermac 5500 (ati rage II 215GT). =
after
> > upgrading the kernel, three vertical bands of visible distortion appe=
ared in
> > my console. they are not videomode-tied (tried almost all my card sup=
ports)
> > and thus i suspect some breakage in the driver.
>=20
> Which kernel version worked fine? Which one caused the regression?
>=20
> > can anyone please have a look at it?
> > moreover, what could cause such an effect? would it be memory clock o=
r pll
> > programming? please enlighten me a bit, i am curious.
>=20
> This looks more like a problem with the display FIFO programming (DSP_*
> registers): some RAGE chips have 24 entries in the display FIFO, others=
 have
> 32.

One thing that sticks out is dsp_loop_latency. This patch changes the=20
calculation to be more like the old way. It's still a bit different since=
=20
the new code takes more memory types into consideration. Completely=20
untested on any hardware...

--- mach64_ct.c.orig	2005-10-29 14:05:40.000000000 +0300
+++ mach64_ct.c	2005-10-29 14:10:37.000000000 +0300
@@ -425,8 +425,10 @@
=20
 	if (M64_HAS(FIFO_32)) {
 		pll->ct.fifo_size =3D 32;
+		pll->ct.dsp_loop_latency =3D 2;
 	} else {
 		pll->ct.fifo_size =3D 24;
+		pll->ct.dsp_loop_latency =3D 0;
 		pll->ct.xclkpagefaultdelay +=3D 2;
 		pll->ct.xclkmaxrasdelay +=3D 3;
 	}
@@ -434,35 +436,35 @@
 	switch (par->ram_type) {
 	case DRAM:
 		if (info->fix.smem_len<=3DONE_MB) {
-			pll->ct.dsp_loop_latency =3D 10;
+			pll->ct.dsp_loop_latency +=3D 8;
 		} else {
-			pll->ct.dsp_loop_latency =3D 8;
+			pll->ct.dsp_loop_latency +=3D 6;
 			pll->ct.xclkpagefaultdelay +=3D 2;
 		}
 		break;
 	case EDO:
 	case PSEUDO_EDO:
 		if (info->fix.smem_len<=3DONE_MB) {
-			pll->ct.dsp_loop_latency =3D 9;
+			pll->ct.dsp_loop_latency +=3D 7;
 		} else {
-			pll->ct.dsp_loop_latency =3D 8;
+			pll->ct.dsp_loop_latency +=3D 6;
 			pll->ct.xclkpagefaultdelay +=3D 1;
 		}
 		break;
 	case SDRAM:
 		if (info->fix.smem_len<=3DONE_MB) {
-			pll->ct.dsp_loop_latency =3D 11;
+			pll->ct.dsp_loop_latency +=3D 9;
 		} else {
-			pll->ct.dsp_loop_latency =3D 10;
+			pll->ct.dsp_loop_latency +=3D 8;
 			pll->ct.xclkpagefaultdelay +=3D 1;
 		}
 		break;
 	case SGRAM:
-		pll->ct.dsp_loop_latency =3D 8;
+		pll->ct.dsp_loop_latency +=3D 6;
 		pll->ct.xclkpagefaultdelay +=3D 3;
 		break;
 	default:
-		pll->ct.dsp_loop_latency =3D 11;
+		pll->ct.dsp_loop_latency +=3D 9;
 		pll->ct.xclkpagefaultdelay +=3D 3;
 		break;
 	}

--=20
Ville Syrj=E4l=E4
sy...@sc...
http://www.sci.fi/~syrjala/

RE: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

[Gil B. <co...@ba...>]

One tiny important detail left out :)

According to information on the net
(http://patchwork.ozlabs.org/linuxppc/patch?id=3D1268) the precise =
regression
moment was between 2.6.10-rc1-bk3 and 2.6.10-rc1-bk8.
I have it confirmed between 2.6.8 and 2.6.13.4 myself.

-----Original Message-----
From: ge...@so... [mailto:ge...@so...] On Behalf Of Geert
Uytterhoeven
Sent: Friday, October 28, 2005 10:19 PM
To: lin...@li...
Subject: Re: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and
Beige G3

On Fri, 28 Oct 2005, coutal coutal wrote:
> i am using the atyfb driver on my powermac 5500 (ati rage II 215GT). =
after
> upgrading the kernel, three vertical bands of visible distortion =
appeared
in
> my console. they are not videomode-tied (tried almost all my card
supports)
> and thus i suspect some breakage in the driver.

Which kernel version worked fine? Which one caused the regression?

> can anyone please have a look at it?
> moreover, what could cause such an effect? would it be memory clock or =
pll
> programming? please enlighten me a bit, i am curious.

This looks more like a problem with the display FIFO programming (DSP_*
registers): some RAGE chips have 24 entries in the display FIFO, others =
have
32.

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

Re: [Linux-fbdev-users] atyfb: brokenness on PowerMac 5500 and Beige G3

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

On Fri, 28 Oct 2005, coutal coutal wrote:
> i am using the atyfb driver on my powermac 5500 (ati rage II 215GT). after
> upgrading the kernel, three vertical bands of visible distortion appeared in
> my console. they are not videomode-tied (tried almost all my card supports)
> and thus i suspect some breakage in the driver.

Which kernel version worked fine? Which one caused the regression?

> can anyone please have a look at it?
> moreover, what could cause such an effect? would it be memory clock or pll
> programming? please enlighten me a bit, i am curious.

This looks more like a problem with the display FIFO programming (DSP_*
registers): some RAGE chips have 24 entries in the display FIFO, others have
32.

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] atyfb: brokenness on PowerMac 5500 and Beige G3

[coutal c. <co...@ba...>]

Hello,

i am using the atyfb driver on my powermac 5500 (ati rage II 215GT). after upgrading the kernel, three vertical bands of visible distortion appeared in my console. they are not videomode-tied (tried almost all my card supports) and thus i suspect some breakage in the driver.

can anyone please have a look at it?
moreover, what could cause such an effect? would it be memory clock or pll programming? please enlighten me a bit, i am curious.

thanks a lot,

Gil Bahat

Re: [Linux-fbdev-users] fb driver for intel 82915G

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

From: Gildas Bayard <gil...@gm...>
Date: Fri, Oct 28, 2005 at 10:38:47AM +0200
> Hello,
> 
> I'd like to use the fb on my (quite) new dell optiplex sx280 computer
> but the nvidiafb does not work (can't claim fb mem region)
> 
> lspci -v tells me that my controler is a intel 82915G.
> looking into /sys/bus/pci I found that the device ID for my card is 0x2782
> => so I checked in kernel sources (driver/video/intelfb/intelfb.h) and
> I noticed that my device ID is not supported
> in the sources Intel 915G is device ID 0x2582
> I guess my intel 915G is a new kind of 915G with slightly different
> caracteristics.
> 
One of the first things to try is to add that pci-id to the existing
driver, and see if it works.

Good luck,
Jurriaan
-- 
Evil Grin no. 13: <<<<<GRIN>>>>>
Debian (Unstable) GNU/Linux 2.6.14-rc2-mm2 2x4804 bogomips 1.34

[Linux-fbdev-users] fb driver for intel 82915G

[Gildas B. <gil...@gm...>]

Hello,

I'd like to use the fb on my (quite) new dell optiplex sx280 computer
but the nvidiafb does not work (can't claim fb mem region)

lspci -v tells me that my controler is a intel 82915G.
looking into /sys/bus/pci I found that the device ID for my card is 0x2782
=3D> so I checked in kernel sources (driver/video/intelfb/intelfb.h) and
I noticed that my device ID is not supported
in the sources Intel 915G is device ID 0x2582
I guess my intel 915G is a new kind of 915G with slightly different
caracteristics.

If the adaptation to my card is not too hard to do I'd be happy to do
it but I will need some explanations

Gildas

Re: [Linux-fbdev-users] trying to start using nvidiafb

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

Gildas Bayard wrote:
> Hello,
> 
> I'm quite new to the framebuffer but I've been using the vesa fb driver
> for several weeks and launched X on it with success
> 
> I would like to try nvidiafb now but I have the following problems:
> I can see for a very brief instant a page that looks like the penguin we
> all know with some normal console messages but it vanishes immediately
> and then nothing is displayed...
> 
> Are there some parameters I could have wrong?
> There is no nvidiafb file in the kernel Documentation directory so
> is there a place to know options for the nvidia fb driver?
> 
> finally I could boot a console with nvidiafb by specifying
> video=nvidiafb:800x600 at startup but
> - it still doesn't work on other resolutions
> - if I change resolution from 800 600 to 1024 768 with fbset it does
> something but the result is bad. If I precise depth 32 it's better but
> the screen is cut in half

Check if you have a /etc/fb.modes.  Then use fbset by doing

fbset 1024x768-60 # where 1024x768-60 can be an entry in fb.modes

> 
> BTW, I'm using vanilla kernel 2.6.13.4, my card (as reported by lspci)
> is a GE force FX Go5200 and I'm on a laptop (with lcd screen then)

If you can, try using linux-2.6.14-rc5-mm1, as there are a bunch of nvidiafb
fixes that might be related to your problem.

Tony

[Linux-fbdev-users] trying to start using nvidiafb

[Gildas B. <gil...@gm...>]

Hello,

I'm quite new to the framebuffer but I've been using the vesa fb driver
for several weeks and launched X on it with success

I would like to try nvidiafb now but I have the following problems:
I can see for a very brief instant a page that looks like the penguin we
all know with some normal console messages but it vanishes immediately
and then nothing is displayed...

Are there some parameters I could have wrong?
There is no nvidiafb file in the kernel Documentation directory so
is there a place to know options for the nvidia fb driver?

finally I could boot a console with nvidiafb by specifying
video=nvidiafb:800x600 at startup but
- it still doesn't work on other resolutions
- if I change resolution from 800 600 to 1024 768 with fbset it does
something but the result is bad. If I precise depth 32 it's better but
the screen is cut in half

BTW, I'm using vanilla kernel 2.6.13.4, my card (as reported by lspci)
is a GE force FX Go5200 and I'm on a laptop (with lcd screen then)

Gildas

[Linux-fbdev-users] Re: Doubt...Urgent sir

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

On Mon, 24 Oct 2005, Chandramouli P wrote:
> At present, Iam working on Framebuffer. I have a doubt sir. Please solve
> this.
> 
> *How to display a string or a character in Frame buffer in C language?
> *What is the library file used to do all I/O function manipulations like
> printing, reading, opening in a file and display that file in frame
> buffer...?

By drawing the characters to the frame buffer.

> Here, Iam using SuSe Linux 9.3 and gcc compiler. Can i need any extra
> libraries to implement the task? This is urgent requirement sir. Please do
> needful. I will be wait for your reply. Thank you.

There exist several libraries for that, e.g. DirectFB.

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

Re: [Linux-fbdev-users] virtual frame buffer

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

Yan Seiner wrote:
> 
>> Vfb behaves like a real frame buffer device, except that you cannot
>> mmap() it
>> to userspace (resulting behavior is undefined). But that should be
>> fixable by
>> letting vfb provide its own fb_mmap() routine, if anyone cares to
>> implement.
>>
>> Gr{oetje,eeting}s,
>>
>>                         Geert
>>  
>>
> Well, that explains why vncserver won't work right.  It gives me hope
> that everything else I've done works.
> 
> OK, I've had a look at the various kernel source xxfb_mmap functions... 
> If I were to try and write one for the vfb, where do I find some docs or
> info on where to start?
> 
> And/or what's the closest one I can copy from driver/video?  Is there
> one that is simple and well documented which explains what xxfb_mmap is
> supposed to do and how?
> 

You can start by changing vfb to use __get_free_pages() to allocate the
videomemory instead of vmalloc.

Then just copy the fb_mmap() function in drivers/video/fbmem.c to
vfb.c as vfb_mmap and then mark vm->vm_flags as VM_RESERVED also. Then make sure that
you point fb_mmap in vfb_ops to your vfb_mmap() function.

If you're using linux-2.6, you also have to add this before register_framebuffer():

info->fix.smem_len = videomemorysize;
info->fix.smem_start = virt_to_phys(videomemory) & PAGE_MASK;

Tony

[Linux-fbdev-users] Using of a nonstandard hardware with fb

[<vi...@ma...>]

Hi

  I'm trying to use framebuffer with some device, that is not a video
adaptor. It can receive a 24 bit RGB frames (pictures) as byte stream
and don't know anything about some kind of timings, etc. The speed of
output is about 25 fps. So I need to catch a completed frames
asynchronously and send it to this device.

  Is it possible to use fb with this device at all? Should I use vfb for
this task or write my own fb driver? Where can I find any documentation
and/or examples of using a vfb or writing an fb driver if need? In
kernel sourse I hasn't found anything about asynchronous output.

Thank you.

--- 
  br
Victor

Re: [Linux-fbdev-users] virtual frame buffer

[Yan S. <ya...@se...>]

>Vfb behaves like a real frame buffer device, except that you cannot mmap() it
>to userspace (resulting behavior is undefined). But that should be fixable by
>letting vfb provide its own fb_mmap() routine, if anyone cares to implement.
>
>Gr{oetje,eeting}s,
>
>						Geert
>  
>
Well, that explains why vncserver won't work right.  It gives me hope 
that everything else I've done works.

OK, I've had a look at the various kernel source xxfb_mmap functions...  
If I were to try and write one for the vfb, where do I find some docs or 
info on where to start?

And/or what's the closest one I can copy from driver/video?  Is there 
one that is simple and well documented which explains what xxfb_mmap is 
supposed to do and how?

--Yan

Re: [Linux-fbdev-users] virtual frame buffer

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

On Wed, 12 Oct 2005, Yan Seiner wrote:
> OK, this is a long shot since the kernel virtual frame buffer isn't really
> part of the fbdev development....  (that I know of?  Maybe it is....)
> 
> Is it possible to use the virtual frame buffer as a real device?  The one that
> says 'for testing only' in the menuconfig?
> 
> I am trying to set up a graphical system on an embedded system with no video
> hardware at all.  I am using nano-x (http://www.microwindows.com) The output
> is into the virtual frame buffer, and then I am trying to use vnc to remote
> the display to another computer.
> 
> The nano-x client apps can see mouse events from vncviewer, but vncviewer only
> shows total blackness.
> 
> Is the virtual frame buffer just a black hole? Or should vnc work with it?
> IIRC vnc reads the video memory and then sends it to the viewer.  Obviously,
> if the virtual frame buffer is just a black hole that won't work....
> 
> From looking at the source, it seems like the vfb really allocates memory for
> framebuffer use.... And vncserver is mmap'ing it correctly.  So that would
> lead me to believe that it should work....

Vfb behaves like a real frame buffer device, except that you cannot mmap() it
to userspace (resulting behavior is undefined). But that should be fixable by
letting vfb provide its own fb_mmap() routine, if anyone cares to implement.

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] virtual frame buffer

[Yan S. <ya...@se...>]

OK, this is a long shot since the kernel virtual frame buffer isn't 
really part of the fbdev development....  (that I know of?  Maybe it is....)

Is it possible to use the virtual frame buffer as a real device?  The 
one that says 'for testing only' in the menuconfig?

I am trying to set up a graphical system on an embedded system with no 
video hardware at all.  I am using nano-x (http://www.microwindows.com) 
The output is into the virtual frame buffer, and then I am trying to use 
vnc to remote the display to another computer.

The nano-x client apps can see mouse events from vncviewer, but 
vncviewer only shows total blackness.

Is the virtual frame buffer just a black hole? Or should vnc work with 
it?  IIRC vnc reads the video memory and then sends it to the viewer.  
Obviously, if the virtual frame buffer is just a black hole that won't 
work....

 From looking at the source, it seems like the vfb really allocates 
memory for framebuffer use.... And vncserver is mmap'ing it correctly.  
So that would lead me to believe that it should work....

--Yan

[Linux-fbdev-users] urgent: dhcpd not running

[umashankar l. <the...@re...>]

 =A0  =0A hi all, =0A =0Awe are trying to make our server as gateway, which=
 runs on FreeBSD. =0Athe problem arising is when i run dhcpd thro the comma=
nd: =0A =0A# sh /usr/local/etc/rc.d/isc-dhcpd.sh start =0A =0Athe promt sim=
ply returns. when i check status i get message : =0A =0A"the dhcpd is not r=
unning" =0A =0Aexternal ip address i have 65.195.95.200. internal ip i want=
 to use =0A192.168.10.1 =0Aall necessary changes in rc.conf is made. NAT se=
rvice: basically i =0Awant to run a dhcp server and enable NAT make this co=
mputer as =0Agateway. =0A =0Awhat should i do? =0A=0AUmashankar.L=0A

Re: [Linux-fbdev-users] Newbie in Frame Buffer world

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

Ri...@so... wrote:
> Hi all,
> 
> I am new to frame buffer drivers. Where can I get information about
> frame buffer abstraction and design, low level driver interface, so that
> I can write my own display driver?
> 

There are really no docs for the 2.6 framebuffer layer.  But you
can see drivers/video/skeletonfb.c for a template.  You can also
use any of the updated drivers in the same directory.

Writing a driver for fbdev is relatively easy.  As long as you
know how to set the hardware to the correct video mode, everything
just falls into place.

Tony

Re: [Linux-fbdev-users] radeonfb problem

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

Tomek Kuchta wrote:
> Hello,
> I have 19" lcd display, which native resolution is 1280x1024.
> I have been trying to turn on framebuffer under that resolution, but I
> wasn't able to do that.
> All I can do is :
> 1) set 1024x768 resolution, by adding vga=0x317 to my grub.conf

Don't use vga= option, it's for vesafb only.

> 2) set 1280x1024 by typing "modprobe radeonfb", after the framebuffer is
> on by vga=0x317
> I've tried to add :
> vga=0x307 video=radeonfb:1280x1024-24@60
> but it didn't worked.
> When I try to get my native resolution the screen is black, and I can't
> even turn on display's OSD menu.
> I would be grateful for your help,

What kernel version are you using?  What does dmesg say.

Tony

[Linux-fbdev-users] radeonfb problem

[Tomek K. <to...@po...>]

Hello,
I have 19" lcd display, which native resolution is 1280x1024.
I have been trying to turn on framebuffer under that resolution, but I 
wasn't able to do that.
All I can do is :
1) set 1024x768 resolution, by adding vga=0x317 to my grub.conf
2) set 1280x1024 by typing "modprobe radeonfb", after the framebuffer is 
on by vga=0x317
I've tried to add :
vga=0x307 video=radeonfb:1280x1024-24@60
but it didn't worked.
When I try to get my native resolution the screen is black, and I can't 
even turn on display's OSD menu.
I would be grateful for your help,
 
                         Tomek


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.7/112 - Release Date: 2005-09-26