Alex,
What is your chipset ? Your can find some partial documentation on
the intel website. You can start with i810/i815 datasheet (the last
chipset intel give full documentation). i830 and higher are just
evolutions of these chips, so a lot of info are still ok for them.
To resume, the intel chipset can output data in analog format for
VGA output (internal DACs) or output in digital with a parallel protocol
- these output are named DVO. For example there are 3 DVOs in a i845. A
last output is named LVDS. For local LCD, i think it's the one you have
to concentrate on. I don't know if it outputs data in lvds format or
with the same protocol than DVO to a lvds converter. If there are a lvds
converter, you have to determine what is this chip and how to program it.
For my board, tv-out support is done with a Chrontel ch7011
connected to DVOC and programmed via a I2C bus connected to the i845. I
can send you my tv-out patch to see what i did and if you have an
external LVDS converter to program, i think my i2c code (using the
kernel i2c infrastructure) will be useful to you. Luckily for me the
ch7011 has a full datasheet on the chrontel website which really
simplify the coding process.
Good luck
Sylvain
Alex Lau a écrit:
Sylvain Meyer wrote:
The lack of LCD support is firtly nobody has dig into it. I did
the port of intelfb from kernel 2.4 to kernel 2.6. I added TV-Out
support for CH7011 tv-out encoder (rejected in official kernel tree).
But i don't own LCD, so i can't do it. I think it should not be very
difficult if you can find the datasheet of your TMDS encoder.
I'm using the buildin LCD should I get a LVDS specification instead?
Sylvain what do you think I should do to start this process?
is there any sample code of what have been done before? ( sample code
from other driver? maybe? )
Thanks
Regards
Sylvain
Dave Airlie a écrit:
The intelfb driver can't modeset on non-CRT outputs as it requires
using
the video BIOS to do it, this is due to the chip specs not being
available
for all the different external TMDS and TV-out chips...
Not sure what you can do really...
Dave.
On Sun, 10 Jul 2005, Alex Lau wrote:
Try add more info into my intelfb problem.
I think the problem is when I'm using LCD, intelfb get to
be fixed mode ( any one can explain to me why? I don't fully
understand ) so when I init directfb it just won't change to
the correct setting.
I take alot at the kernel driver, with intelfb fix mode it should
take the {kernel-source}/driver/video/modedb.c mdoe line then
apply it .... however at run time my reading from fbset is a little
bit different from all the modedb setting
In the directfb init debug message ... it fail in the Graphic
and show the modeline not find ( even I put that exact mode line
into the /etc/fb.modes
and also stay the pixelformat 8/16, 8/8, 8/0, 8/24
I try ggi also ... it fail with mode change also ...
so I think it is the driver problem... anyone get some idea where
should I look into this mode problem?
Thanks
Alex Lau wrote:
Hi all
I'm using a samsung laptop Q20,
kernel using 2.6.12.2
intelfb able to install with the
follow kernel parm
video=intelfb:[EMAIL PROTECTED],accel=1,mtrr,vram=128,fixed,hwcursor=0
vga=792
since it is LCD ... by default it won't allow mode change
and I have to specifly vga=XXX for fixed mode
playing the cvs version of directfb
and I won't able to init core it say fb.mode not find
and this is my mode line output
mode "1024x768-60"
# D: 62.360 MHz, H: 47.530 kHz, V: 60.013 Hz
geometry 1024 768 1024 768 32
timings 16036 128 32 16 4 128 4
accel true
rgba 8/16,8/8,8/0,8/24
endmode
of course I can redirect to SDL layer and it will work ok ..
but is there any reason it can't get the mode?
any hints?
Thanks
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
