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

[Linux-fbdev-users] Re: [Linux-fbdev-devel] "remap_page_range" i810 compile time problem ..

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

On Thursday 10 March 2005 13:26, Mukund JB. wrote:
> Hi adaplas,
>
> > > I have problem with compiling the i810fb driver downloaded from
> > > Sourceforge site.
> > > I have D/W the i810fb patch "linux-i810fb-0.0.35.tar.bz2".
> > >
> > > When I run the make modules I get the following error
> >
> > Try the i810fb-lite driver.  If that does not work, let me know what
> > kernel version you are using.
>
> I got it.
> The " remap_page_range" API the i810fb driver is using is old & when I
> modifies the API with required parameters , I  compiled well & worked.
>
> When I inserted the module using the modprobe i.e
>
> Modprobe i810fb vram=2 xres=1024 bpp=16 hsync1=30 hsync2=55 vsync1=50
> vsync2=85 accel=1 rotate=1
>
> the screen rotated. GREAT.
>
> But when I try this without accel=1 rotation fails. Can u just narrate
> me what is accel accentually doing?

Because if accel is on, the driver is using it's own version of drawing
functions which are flexible enough that additional features can be added,
such as screen rotation.

If accel is off, the driver will use the generic functions which cannot do
screen rotation.  Of course, one can write a software version that can do
screen rotation.

>
> Also, the font I am getting looks linear & is not good? I do I modify
> the font format

Use setfont.

Tony

[Linux-fbdev-users] RE: [Linux-fbdev-devel] "remap_page_range" i810 compile time problem ..

[Mukund JB. <muk...@es...>]

Hi adaplas,

> > I have problem with compiling the i810fb driver downloaded from
> > Sourceforge site.
> > I have D/W the i810fb patch "linux-i810fb-0.0.35.tar.bz2".
> >
> > When I run the make modules I get the following error
>=20
> Try the i810fb-lite driver.  If that does not work, let me know what
> kernel version you are using.

I got it.
The " remap_page_range" API the i810fb driver is using is old & when I
modifies the API with required parameters , I  compiled well & worked.

When I inserted the module using the modprobe i.e=20

Modprobe i810fb vram=3D2 xres=3D1024 bpp=3D16 hsync1=3D30 hsync2=3D55 =
vsync1=3D50
vsync2=3D85 accel=3D1 rotate=3D1

the screen rotated. GREAT.

But when I try this without accel=3D1 rotation fails. Can u just narrate
me what is accel accentually doing?

Also, the font I am getting looks linear & is not good? I do I modify
the font format

Regards,
Mukund jampala



>=20

[Linux-fbdev-users] Re: [Linux-fbdev-devel] "remap_page_range" i810 compile time problem ..

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

On Wednesday 09 March 2005 19:14, Mukund JB. wrote:
> Hi all,
>
> I have problem with compiling the i810fb driver downloaded from
> Sourceforge site.
> I have D/W the i810fb patch "linux-i810fb-0.0.35.tar.bz2".
>
> When I run the make modules I get the following error

Try the i810fb-lite driver.  If that does not work, let me know what
kernel version you are using.

I haven't updated the driver for quite some time so it may be suffering
from bitrot.

Tony

[Linux-fbdev-users] "remap_page_range" i810 compile time problem ..

[Mukund JB. <muk...@es...>]

Hi all,

I have problem with compiling the i810fb driver downloaded from
Sourceforge site.
I have D/W the i810fb patch "linux-i810fb-0.0.35.tar.bz2".

When I run the make modules I get the following error

i810_main.c: 643: warning: passing arg 1 of 'remap_page_range_R2baf18f2'
makes pointer from integer without a cast
i810_main.c: 643: incompatible type for argument 4 of
'remap_page_range_R2baf18f2'
i810_main.c: 643: too few arguments to function
'remap_page_range_R2baf18f2'
Make[3]: *** [I810_main.c] Error 1
........
......

The call to "remap_page_range()" is as follows:-

return (io_remap_page_range(vma->vm_start, off, vma->vm_end -
vma->vm_start, vma->vm_page_prot)) ? -EAGAIN : 0;

I am running Redhat 9 Linux.

Regards,
Mukund jampala

RE: [Linux-fbdev-users] RE: Crosstool for EBD9312..

[Mukund JB. <muk...@es...>]

Hi adalpas,

Thanks for the 810fb info.

I have D/W the i810fb patch "linux-2.4.20-i810fb.diff".
These were some rejects & I found some ".ref" in linux, video & i810
directories when I tried patched it to the kernel tree. I just tried to
see if it works apart form the rejects & make bzImage was successful and
"make modules" command FAILED saying:-

i810_main.c: 643: warning: passing arg 1 of 'remap_page_range_R2baf18f2'
makes pointer from integer without a cast
i810_main.c: 643: incompatible type for argument 4 of
'remap_page_range_R2baf18f2'
i810_main.c: 643: too few arguments to function
'remap_page_range_R2baf18f2'
Make[3]: *** [I810_main.c] Error 1
........
......

I am looking into code, I thought mailing u this will be helpful.
What could be the problem?
I am running redhat 9 Linux.

Regards,
Mukund jampala

Re: [Linux-fbdev-users] RE: Crosstool for EBD9312..

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

On Monday 07 March 2005 21:36, Mukund JB. wrote:
> Hi all,
>
> I also have a doubt regarding Accelarated Display driver.
> Would u define an Accelerated display driver?

An accelerated driver means that most of the drawing is done by
the GPU (the processor of the graphics card) while an unaccelerated driver
implies that drawing is done by the main CPU.

>
> Is it the driver to a Accelerated display card?

The driver is implementing the features of the card.

>
> 			Or
>
> Is it like accelerated display driver has a different meaning. I mean,
> it has the set features which will not be there on a normal driver for
> the same card?
>

The effect of software versus accelerated is the same.  The main difference
is that the GPU does the work if accelerated, the CPU if not.  And the CPU
version will be slower because it has to do other work besides drawing, and
the data that is processed by the CPU has to go to and from the bus.  The
GPU has no such constraints.

> How can I implement a accelerated driver?

You need to know the details of the particular chipset you are working on.

> Can I use the existing code of a framebuffer driver & do that? I heard

Yes, if the framebuffer driver implements console acceleration.

> in the groups saying framebuffer driver is not an accelerated driver.
>

Yes, the framebuffer driver only implements acceleration for the console.

> Please take the pain of explaining how a framebuffer driver is different
> form accelerated driver?

Essentially, a framebuffer driver only exposes the video memory to its
clients, period.  You can read from or write to this memory, but you have
to use the CPU to do this.  In order to implement acceleration, you need
to know how to talk to the GPU.

Tony

Re: [Linux-fbdev-users] RE: rotate the screen on ARM board

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

On Thursday 03 March 2005 20:28, Mukund JB. wrote:
> Hello komal,
>
> Is it a must that hardware should support the screen rotation. Can't we
> handle that in an fb driver? And, if possible do explain me that like
> How & where the fb driver allows changes to support screen rotation.

It doesn't.

>
> Please suggest me how can I activate the frambuffer on RedHat 9. It is
> not active on my system. When I say fbset -i, it responds saying
> open /dev/fb0: No such device
>
> I have a Intel Corp. 82810E DC-133 Graphic controller on my system. Is a
> fb driver specific to this. Does the generic fbdev work with this
> controller?

vesafb does not work for the i810.  You have to enable the specific driver
for it, i810fb, in your kernel config.  The i810fb is only available for 2.6
kernels, but you can grab an old patch for 2.4 in

http://i810fb.sf.net

Grab the latest one, and it should apply to any recent 2.4 kernel.  You might
get hunk failures but it should be easy to fix.

Tony

BTW, the i810 does not support hardware rotation. It can be done in software,
if you enable the fbdev driver for X.

RE: [Linux-fbdev-users] RE: rotate the screen on ARM board

[Mukund JB. <muk...@es...>]

Hi komal,=20

> > Is it a must that hardware should support the screen rotation. Can't
we
> > handle that in an fb driver? And, if possible do explain me that
like
> > How & where the fb driver allows changes to support screen rotation.
>=20
> No you don't need the rotation support. It is a add on and it is a per
> driver thing.

U mean fb driver does not have the screen rotation support. Right?

> > Please suggest me how can I activate the frambuffer on RedHat 9. It
is
> > not active on my system. When I say fbset -i, it responds saying
> > open /dev/fb0: No such device
> >
> > I have a Intel Corp. 82810E DC-133 Graphic controller on my system.
Is a
> > fb driver specific
>=20
> What is your config?

--------------Below is my XF86Config file --------------

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
	InputDevice    "DevInputMice" "AlwaysCore"
EndSection

Section "Files"
# RgbPath is the location of the RGB database.  Note, this is the name
of the=20
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

	RgbPath      "/usr/X11R6/lib/X11/rgb"
	FontPath     "unix/:7100"
EndSection

Section "Module"
	Load  "dbe"
	Load  "extmod"
	Load  "fbdevhw"
	Load  "glx"
	Load  "record"
	Load  "freetype"
	Load  "type1"
	Load  "dri"
EndSection

Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#	Option	"Xleds"		"1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.
#	Option	"XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#	Option	"XkbModel"	"pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#	Option	"XkbModel"	"microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#	Option	"XkbLayout"	"de"
# or:
#	Option	"XkbLayout"	"de"
#	Option	"XkbVariant"	"nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#	Option	"XkbOptions"	"ctrl:swapcaps"
# Or if you just want both to be control, use:
#	Option	"XkbOptions"	"ctrl:nocaps"
#
	Identifier  "Keyboard0"
	Driver      "keyboard"
	Option	    "XkbRules" "xfree86"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "PS/2"
	Option	    "Device" "/dev/psaux"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "no"
EndSection

Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
	Identifier  "DevInputMice"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "no"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Samsung Samtron 45B(n)"
	DisplaySize  270	200
	HorizSync    30.0 - 55.0
	VertRefresh  50.0 - 120.0
	Option	    "dpms"
EndSection

#mukund defined device
Section "Device"
	Identifier  "VESA Framebuffer"
	Driver      "fbdev"
	VendorName  "Videocard vendor"
	# BoardName   "Intel 810"
	VideoRam    16384
	Option	    "UseFBDev"
	Option	    "ShadowFB" "ON"
	Option	    "Rotate" "CCW"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "VESA Framebuffer"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Depth     24
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "DRI"
	Group        0
	Mode         0666
EndSection

[Linux-fbdev-users] RE: Crosstool for EBD9312..

[Mukund JB. <muk...@es...>]

Hello Burian,

> The framebuffer implementation you get in the unofficial cirrus tree
> (ep93xx-2.6) is not accelerated. The latest cirrus release (for
> linux-2.4.21-rmk1) seems acclerated. Diff the source for details.
>=20
> Note that the unaccelerated 2.6 driver and the accelerated
> 2.4.21-rmk1-crus-whatever driver do not have a common anchestor,
> the 2.6. was implemented from scratch, using fb-skeleton.c
>=20

OK.

> To explain it short:
>=20
> if hardware acceleration is not available you'll have to emulate the
> missing features in software (always possible), which is usually slow.

Yes, right. This will be painful (performance wise).

>=20
> if hardware acceleration is available but the driver does not use it
> (emulates it as if it wasn't there) you still have a software-only
driver.
=20
You mean if the existing driver support is not accelerated, we need to
emulate it in software again. But Why, can't we rewrite the driver at
some places & make it work?

> if hardware acceleration is available and the driver makes use of
> it you've got a "accelerated" driver. In the ep93xx's case
> the "raster engine" is used then.

What is the raster engine? I goggled it, but did not find any thing
strong enough.
=20
My actual requirement is to rotate the screen by 90 degrees. Maillists
ask me to use Xfree86 as it already has such kind of a support to rotate
the screen.=20

Are there any side affects if I make use of the X server & rotate the
screen. I mean is there any application that makes use of the video
buffer directly without using X server and may fail to rotate the screen
as we are rotating the screen at X server level and not at fb level.

Also, if my device uses the console the screen rotation at X server
level will not work. I mean if.

Thanks & Regards,
mukund jampala

Re: [Linux-fbdev-users] RE: rotate the screen on ARM board

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

> Hello komal,
> 
> Is it a must that hardware should support the screen rotation. Can't we
> handle that in an fb driver? And, if possible do explain me that like
> How & where the fb driver allows changes to support screen rotation.

No you don't need the rotation support. It is a add on and it is a per 
driver thing.
 
> Please suggest me how can I activate the frambuffer on RedHat 9. It is
> not active on my system. When I say fbset -i, it responds saying 
> open /dev/fb0: No such device
> 
> I have a Intel Corp. 82810E DC-133 Graphic controller on my system. Is a
> fb driver specific 

What is your config?

[Linux-fbdev-users] RE: Crosstool for EBD9312..

[Mukund JB. <muk...@es...>]

Hi all,

I also have a doubt regarding Accelarated Display driver.=20
Would u define an Accelerated display driver?

Is it the driver to a Accelerated display card?

			Or

Is it like accelerated display driver has a different meaning. I mean,
it has the set features which will not be there on a normal driver for
the same card?

How can I implement a accelerated driver?
Can I use the existing code of a framebuffer driver & do that? I heard
in the groups saying framebuffer driver is not an accelerated driver.=20

Please take the pain of explaining how a framebuffer driver is different
form accelerated driver?

Regards,
Mukund jampala

[Linux-fbdev-users] RE: rotate the screen on ARM board

[Mukund JB. <muk...@es...>]

Hello komal,

Is it a must that hardware should support the screen rotation. Can't we
handle that in an fb driver? And, if possible do explain me that like
How & where the fb driver allows changes to support screen rotation.

Please suggest me how can I activate the frambuffer on RedHat 9. It is
not active on my system. When I say fbset -i, it responds saying=20
open /dev/fb0: No such device

I have a Intel Corp. 82810E DC-133 Graphic controller on my system. Is a
fb driver specific to this. Does the generic fbdev work with this
controller?

Thanks & regards,
Mukund jampala

Re: [Linux-fbdev-users] rotate the screen on ARM board

[Komal S. <kom...@ya...>]

--- "Mukund JB." <muk...@es...>
wrote:

> Hello all,

Hi,

> 
> I have query about how to rotate the screen on an
> ARM board i.e EDB9312
> which I recently brought.
> 
> I want rotate it by 90 degree.

As you are talking about the hardware rotation, I hope
your hardware supports that. I had not worked on the
edb9312, but generally it might be possible to do
rotation directly in memory (sdram/sram) or through
specialized engine. You might have to program few
variables with equations and change the mode, pixclock
accoradingly. You can talk to edb9312-arm-linux
maintainers probably (I guess Ray' can help you ).  

_or_ checkout cirrus support on that arm-linux
versions for your board.



=====
---Komal Shah


	
		
__________________________________ 
Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web 
http://birthday.yahoo.com/netrospective/

[Linux-fbdev-users] rotate the screen on ARM board

[Mukund JB. <muk...@es...>]

Hello all,

=20

Hello to Open Linux Community.

=20

I have query about how to rotate the screen on an ARM board i.e EDB9312
which I recently brought.

I want rotate it by 90 degree.

=20

Thanks for all of yours continuous support.

=20

Regards,

Mukund jampala

=20

[Linux-fbdev-users] unsubscribe

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

unsubscribe

-- 
  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] Apple M9179LL/A 30" Widescreen LCD with rv280

[Esben S. <b0...@es...>]

I'm planning on getting the M9179LL/A; it's a Apple 30" Widescreen
LCD, http://www.apple.com/displays/ - probably Samsung or Viewsonic
OEM. If anyone knows please tell.

I intend to run this with a rv280 gpu, Radeon 9250 on GNU/Linux. This
card features a single link DVI which is not sufficient to run the LCD
in native resolution, 2560x1600. I will run in 1280x800/1920x1200
until a card is out that is supported with libre software. I have seen
this monitor operate at 1280x800/1920x1200 and it's blurryness is
acceptable for a short term solution.

I am interested in the aspects relating to boot up "out of sync" reports.

All the monitor adjustements are done in software. Is it possible to
adjust this monitor with libre software?. I guess I have xgamma(1). 

There is a report, 

http://www.geek.com/news/geeknews/2004Jun/bma20040630025789.htm

.. that older revisions of this monitor had some problems with the
monitor going "out of sync" making it impossible to access bios or
even use until it was initialized in native resolution. The newer
revisions of this monitor have this issue resolved, or so they
say. Anyone have any experience?

Anyone have any experience with this display or other inputs?.

Also, what would the bios initialize this card with?. How would it
show up?. 

I can't seem to find any widescreen vesa modes in the kernel
documentation, but I guess I will have to give video=radeon:1280x800
to it.

-- 
Esben Stien is b0...@es...
http://www.esben-stien.name
irc://irc.esben-stien.name/%23contact
[sip|iax]:b0...@es...

Re: AW: [Linux-fbdev-users] rivafb results in black screen

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

On Friday 11 February 2005 22:26, Sebastian Michel wrote:
> I have no problem, when I attach my LCD to the standard VGA-Port! But why?
> I just want to use DVI.

rivafb has problems with digital output (DVI).  I'll send a new driver for nvidia
chipsets within this week for testing.

Tony

AW: [Linux-fbdev-users] rivafb results in black screen

[Sebastian M. <ins...@gm...>]

I have no problem, when I attach my LCD to the standard VGA-Port! But why? I
just want to use DVI.

Sebastian

[Linux-fbdev-users] rivafb results in black screen

[Sebastian M. <ins...@gm...>]

Hello,

I have a Geforce Ti4200 with a LCD attached to the DVI-Connector. My
computer is running Debian with kernel 2.6.10. I compiled the =
rivafb-driver
into the kernel. But when I boot, I see only a black screen.

debian:~# dmesg | grep rivafb
Kernel command line: root=3D/dev/sda2 ro video=3Drivafb
rivafb: nVidia device/chipset 10DE0253
rivafb: nVidia Corporation NV25 [GeForce4 Ti 4200]
rivafb: Detected CRTC controller 0 being used
rivafb: RIVA MTRR set to ON
rivafb: setting virtual Y resolution to 104857
rivafb: PCI nVidia NV25 framebuffer ver 0.9.5b (64MB @ 0xE8000000)


debian:~# fbset -i -fb /dev/fb0

mode "640x480-60"
=A0=A0=A0 # D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz
=A0=A0=A0 geometry 640 480 640 32767 8
=A0=A0=A0 timings 39721 40 24 32 11 96 2
=A0=A0=A0 rgba 8/0,8/0,8/0,0/0
endmode

Frame buffer device information:
=A0=A0=A0 Name=A0=A0=A0=A0=A0=A0=A0 : NV25
=A0=A0=A0 Address=A0=A0=A0=A0 : 0xe8000000
=A0=A0=A0 Size=A0=A0=A0=A0=A0=A0=A0 : 67108864
=A0=A0=A0 Type=A0=A0=A0=A0=A0=A0=A0 : PACKED PIXELS
=A0=A0=A0 Visual=A0=A0=A0=A0=A0 : PSEUDOCOLOR
=A0=A0=A0 XPanStep=A0=A0=A0 : 1
=A0=A0=A0 YPanStep=A0=A0=A0 : 1
=A0=A0=A0 YWrapStep=A0=A0 : 0
=A0=A0=A0 LineLength=A0 : 640
=A0=A0=A0 MMIO Address: 0xfd000000
=A0=A0=A0 MMIO Size=A0=A0 : 16777216
=A0=A0=A0 Accelerator : No


debian:~# fbset -i -fb /dev/fb1

mode "640x480-59"
=A0=A0=A0 # D: 25.176 MHz, H: 31.469 kHz, V: 59.489 Hz
=A0=A0=A0 geometry 640 480 640 480 4
=A0=A0=A0 timings 39721 48 16 39 8 96 2
=A0=A0=A0 rgba 6/0,6/0,6/0,0/0
endmode

Frame buffer device information:
=A0=A0=A0 Name=A0=A0=A0=A0=A0=A0=A0 : VGA16 VGA
=A0=A0=A0 Address=A0=A0=A0=A0 : 0xa0000
=A0=A0=A0 Size=A0=A0=A0=A0=A0=A0=A0 : 65536
=A0=A0=A0 Type=A0=A0=A0=A0=A0=A0=A0 : VGA 16 colors in 4 planes
=A0=A0=A0 Visual=A0=A0=A0=A0=A0 : PSEUDOCOLOR
=A0=A0=A0 XPanStep=A0=A0=A0 : 8
=A0=A0=A0 YPanStep=A0=A0=A0 : 1
=A0=A0=A0 YWrapStep=A0=A0 : 0
=A0=A0=A0 LineLength=A0 : 80
=A0=A0=A0 Accelerator : No

debian:~# cat /proc/fb
0 NV25
1 VGA16 VGA



So where is my problem?

Sebastian

RE: [Linux-fbdev-users] Intel 830M and conexant cx2587x (cx25873)

[Dely N. <Nic...@th...>]

Hi,

>The intel 830M should be functional. I'm a bit busy now, but i'll try =
to=20
>add a basic documentation soon. Now, you should look directly at the=20
>code to know about the options.

I've tried many different configurations, the best one comes from vesafb =
1024x768 depth 8 bits. The same configuration works with intelfb but the =
screen looks ugly.

These modes: 16, 24 depth are unknown on boot command line in 1024x768 =
and 800x600. Is it possible to get 1024x768 and 24 bits depth on intel =
830 ?

the next lines are my lspci output:

0000:00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev =
04)
0000:00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset =
Graphics Controller] (rev 04)
0000:00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics =
Controller]

In order to test fb device I've had few lines in XFConfig-4 which use =
fbdev driver, is oit correct? My goal is to provide directfb for the UI. =


Could someone give me some advice to succeed ?

Re: [Linux-fbdev-users] Intel 830M and conexant cx2587x (cx25873)

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

  Hi,

The intel 830M should be functional. I'm a bit busy now, but i'll try to=20
add a basic documentation soon. Now, you should look directly at the=20
code to know about the options.
For the conexant cx25873, i don't know about it, the datasheet doesn't=20
seem to be freely available. But if you find some info and want to code=20
tv output, i did it for a chrontel 7011. My code wasn't accepted as is=20
in the linux kernel but maybe it's time to open a discussion about how=20
implement such a feature (and TFT support too) into a fbdev driver. The=20
tv encoder can used after an intel, nvidia or other graphic chip and i=20
think we could find a generic api between an fbdev driver and a tv/tft=20
encoder.

Regards
Sylvain

Dely Nicolas a =E9crit:

>Hi,
>
>I would like to know which is the status of intel 830M frame buffer ther=
e is=20
>no help in linux/Documentation about this driver in 2.6 kernel.=20
>
>Moreover, I'm a newbie in s-video and composite output on Linux. So I do=
n't=20
>know how to find help about conexant cx2587x (cx25873). Are there some s=
oft=20
>in order to test these outputs ? Is there a generic driver in the kernel=
 to
>activate theses features?
>
>Thanks
>
>Nanouck
>
>HW=A6j)b=B2=CAh?=CA+y=D6=F2N=17?L=FA=E8v=E7-=1A=E8?y=17?v=1A'z=CB\jwbv=B7=
=AF?=EC,=A2xn?=DA=DEv=CA=1F!3=EB=A1=DB?=B6=C7=EB=A2j=DEj[=ACz=BB=03?=C7(=BD=
=EA=F0?'!=A6=BA=1D=B9=CBl=B6=BB=A5=CAX=AFz=EAm=A2=D8^?*^J=D6=AB=B6=B7?v)=E0=
??!=B6=DA?=FD=A7l=A2=C7gr?=BFi=D8?=03=AE=E5=A9e=A1=C8?=03^=F7=AA)=01=C9rB=
=E2?=EC_m=D7=AF=BA=C7=AB=B2f=A2?)=E0?+-.)=EE=C5=F6=DDz=FB=ACz=BB%?=CBl=B2=
?=ABq=E7=E8=AE=07=A7z=D8m=B6??=FEX=AC=B6=CB(=BA=B7=1E~?=E0zw=AD=FEX=AC=B6=
=CF=E5?=CBb?=FA??)=EE=C5=F6=DDz=FB=ACers=3D
>

[Linux-fbdev-users] Intel 830M and conexant cx2587x (cx25873)

[Dely N. <Nic...@th...>]

SGksDQoNCkkgd291bGQgbGlrZSB0byBrbm93IHdoaWNoIGlzIHRoZSBzdGF0dXMgb2YgaW50ZWwg
ODMwTSBmcmFtZSBidWZmZXIgdGhlcmUgaXMgDQpubyBoZWxwIGluIGxpbnV4L0RvY3VtZW50YXRp
b24gYWJvdXQgdGhpcyBkcml2ZXIgaW4gMi42IGtlcm5lbC4gDQoNCk1vcmVvdmVyLCBJJ20gYSBu
ZXdiaWUgaW4gcy12aWRlbyBhbmQgY29tcG9zaXRlIG91dHB1dCBvbiBMaW51eC4gU28gSSBkb24n
dCANCmtub3cgaG93IHRvIGZpbmQgaGVscCBhYm91dCBjb25leGFudCBjeDI1ODd4IChjeDI1ODcz
KS4gQXJlIHRoZXJlIHNvbWUgc29mdCANCmluIG9yZGVyIHRvIHRlc3QgdGhlc2Ugb3V0cHV0cyA/
IElzIHRoZXJlIGEgZ2VuZXJpYyBkcml2ZXIgaW4gdGhlIGtlcm5lbCB0bw0KYWN0aXZhdGUgdGhl
c2VzIGZlYXR1cmVzPw0KDQpUaGFua3MNCg0KTmFub3Vjaw0KDQo=

[Linux-fbdev-users] DirectFB radeon output

[Torgeir V. <to...@po...>]

DirectFB output with VDR & softdevice plugin works ok with an mga card,
but I'm struggling with radeon output. The screen goes all black, and
the strange thing is that if I start up the Xorg server after this, the
Xv output windows is also completely black, but with OSD shown. Any
ideas?

[root@vigor10 softdevice]# cat /etc/directfbrc
mode=720x576
depth=32

[root@vigor10 softdevice]# dfbinfo
(*) DirectFB/Config: Parsing config file '/etc/directfbrc'.

       ---------------------- DirectFB v0.9.21 ---------------------
             (c) 2000-2002  convergence integrated media GmbH
             (c) 2002-2004  convergence GmbH
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2005-01-24 13:32)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 5494)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802]
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5495)...
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: ATI Radeon 0.2 (Michel Dnzer)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)


Screen (00) Radeon Primary Screen           (primary screen)
   Caps: VSYNC POWER_MANAGEMENT

     Layer (00) FBDev Primary Layer             (primary layer)
        Type:    GRAPHICS
        Caps:    SURFACE BRIGHTNESS CONTRAST SATURATION

     Layer (01) Radeon Overlay
        Type:    GRAPHICS VIDEO STILL_PICTURE
        Caps:    SURFACE OPACITY ALPHACHANNEL SCREEN_LOCATION
SRC_COLORKEY DST_COLORKEY


Input (01) IMPS/2 Mouse                    (primary mouse)
   Type: MOUSE
   Caps: AXES BUTTONS

Input (00) Keyboard                        (primary keyboard)
   Type: KEYBOARD
   Caps: KEYS

[root@vigor10 VDR]# ./rundfb
[softdevice] processing args
[softdevice]   argv [0] = softdevice
[softdevice]   argv [1] = -vo
arg: /dev/cdrom
[setup-softdevice] alsa device set to: hw:0,2
[setup-softdevice] A/V Offset set to (-8)
[setup-softdevice] cropping mode set to 0 (none)
[setup-softdevice] deinterlace method set to 1 lavc
[softdevice] picture mirroring set to 0 (off)
[setup-softdevice] pixel format set to (YUV2)
[setup-softdevice] startup aspect set to (16:9 wide)
[softdevice] initializing Plugin
[softdevice] Initializing Video Out
[softdevice] ffmpeg version(0.4.9-pre1) build(4736)
[dfb] init
(*) DirectFB/Config: Parsing config file '/etc/directfbrc'.

       ---------------------- DirectFB v0.9.21 ---------------------
             (c) 2000-2002  convergence integrated media GmbH
             (c) 2002-2004  convergence GmbH
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2005-01-24 13:32)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 5505)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802]
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5506)...
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: ATI Radeon 0.2 (Michel Dnzer)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
[dfb] RAM: 67108864 bytes
[dfb] Accellerated Functions: FillRectange DrawRectange DrawLine Blit
All
[dfb] Drawing Flags: none
[dfb] Surface Blitting Flags: SrcColorkey
[dfb] Supported video Modes are: 640x480@8 640x480@8 640x480@8 640x480@8
640x480@8 800x600@8 800x600@8 800x600@8 800x600@8 800x600@8 800x600@8
800x600@8 800x600@8 1024x768@8 1024x768@8 1024x768@8 1024x768@8
1024x768@8 1024x768@8 1024x768@8 1152x864@8 1152x864@8 1152x864@8
1152x864@8 1152x864@8 1152x864@8 1024x1024@8 1280x1024@8 1280x1024@8
1280x1024@8 1280x1024@8 1280x1024@8 1600x1200@8 1600x1200@8 1600x1200@8
1280x720@16 1280x720@32 720x576@32
[dfb] Enumeratig display Layers
Layer 0 FBDev Primary Layer  Type: graphics
  Caps: brightness contrast saturation surface
Layer 1 Radeon Overlay  Type: graphics picture video
  Caps: alphachannel dst_colorkey opacity screen_location src_colorkey
surface
[dfb] width = 720, height = 576
[dfb] got fmt = 0x00400c03 bpp = 32
[dfb] Using this layer for OSD: (FBDev Primary Layer - [720x576])
osdSurface::
 - videoonly
 - flipping
videoSurface::
 - videoonly
[dfb] Configuring CooperativeLevel for Overlay
[dfb] Configuring ColorKeying
[dfb] Configuring CooperativeLevel for OSD
[dfb] Using this layer for OSD: FBDev Primary Layer
[dfb] Using this layer for Video out: Radeon Overlay
[dfb] (re)configuring Videolayer to 720 x 576 (720x576)
[dfb] creating new surface
[dfb] (re)configured 0x00200806
[softdevice] Video Out seems to be OK
[softdevice] Initializing Audio Out
[softdevice] Audio out seems to be OK
[softdevice] A/V devices initialized, now initializing MPEG2 Decoder
cSoftDevice::MakePrimaryDevice
 (!!!)  *** ONCE [only copying/scaling blits supported for YUV in
software] *** [generic.c:3998 in gAcquire()]
[softdevice] allocating picture buffer for resolution 720x576
[dfb] (re)configuring Videolayer to 720 x 576 (720x576)
[dfb] creating new surface
[dfb] (re)configured 0x00200806



-- 
Torgeir Veimo <to...@po...>

[Linux-fbdev-users] Re: [directfb-users] Re: 1400x1050 not possible with ATI M9?

[Torgeir V. <to...@po...>]

On Sat, 2005-01-22 at 19:26 -0500, Taoufik Zammou wrote:
> On Fri, 21 Jan 2005 15:32:44 +0000, Torgeir Veimo <to...@po...> wrote:
> > 
> > What does fbset -i tell you?
> > 

> - When recompiling DirectFB without multi-app support (fusion),
> DirectFB works in 1400x1050.
> - When compiled with multi-app, DirectFB crashes on 1400x1050...
> whatever the refreshrate is. I've tried 1400x1050@62 and 1400x1050@75.
> Both worked good with fbset (console). Running DirectFB with the last
> one gave screen for a half a second, there after i get the "Caught
> signal 7" error. Running DirectFB with the fist one, DirectFB exists
> immediatly with the "Caught signal 7" error.
> 
> So it seems it has something to do with the fusion kernel module.
> 
> fbset -i tells this:
> 
> mode "1400x1050-62"
>     # D: 108.003 MHz, H: 65.856 kHz, V: 61.778 Hz
>     geometry 1400 1050 1400 1050 8
>     timings 9259 88 40 13 0 112 3
>     hsync high
>     vsync high
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : ATI Radeon Lf
>     Address     : 0xe8000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : PSEUDOCOLOR
>     XPanStep    : 8
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 1408
>     MMIO Address: 0xfcff0000
>     MMIO Size   : 16384
>     Accelerator : No

You probably need to patch the radeon fb driver to explicitly set an
accelerator id to get directfb working properly. What is the output of
running dfbinfo?

[root@vigor10 aty]# diff radeon_base.c radeon_base.c-orig
1783,1784d1782
<       else
<               info->fix.accel = FB_ACCEL_ATI_RADEON;

-- 
Torgeir Veimo <to...@po...>

[Linux-fbdev-users] aty128fb and ADC connector

[Charles L. <cl...@gm...>]

I have a Rage 128 in a G4 cube, and I'm having some trouble getting it
to send display to the ADC video port. If I use 'video=ofonly', I can
use an ADC monitor (a 17" ADC CRT), but as far as I can tell, that
bypasses the aty128fb driver. (The FBdev X server doesn't work with
'video=ofonly', but that's another story.)

If I use 'video=aty128fb', I can drive a VGA monitor hooked to the VGA
port (but my VGA monitor isn't doing so well these days). The
suggested 'video=aty128fb:vmode:14' didn't seem to have any effect
(seen on a YDL list, among others).

Here's the aty128fb output from dmesg (kernel 2.6.9 w/ Debian patches):

aty128fb: Invalid ROM signature 1110 should be 0xaa55
aty128fb: BIOS not located, guessing timings.
aty128fb: Rage128 PF PRO AGP [chip rev 0x1] 16M 128-bit SDR SGRAM (1:1)

Other card info:

# lspci -v -s 0:10.0 # [numeric PCI ID: 1002:5046]
0000:00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128
PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
        Flags: bus master, stepping, 66MHz, medium devsel, latency 255, IRQ 48
        Memory at 94000000 (32-bit, prefetchable) [size=64M]
        I/O ports at 802400 [size=256]
        Memory at 90000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [50] AGP version 2.0
        Capabilities: [5c] Power Management version 2

Suggestions? Should I look at some of the development code instead of
the mainline kernel drivers? If the Rage128 registers are readable, I
can try to modify the driver probe routine to see how OF set the
registers up to enable the ADC port (vs VGA).

thanks for reading this far,

-- 
- Charles Lepple