On Tue, 2009-06-30 at 00:25 +0800, Jesse Barnes wrote:
> On Sun, 28 Jun 2009 15:42:17 -0700
> Keith Packard wrote:
>
> > Convert many printk calls to DRM_DEBUG calls to reduce kernel log
> > noise for normal activities. Switch other printk calls to DRM_ERROR
> > or DRM_INFO.
> >
> > Signed-off-b
Hi, All
When the system is booted with KMS enabled, the xrandr tool will get
less modes than in UMS mode. And it seems that this is a top KMS gap.
Many laptops will be affected by this issue.
I worked on this issue and gave two proposals for this issue. One is
realized in user space(
On Wed, 2009-06-10 at 06:45 +0800, Eric Anholt wrote:
> On Mon, 2009-05-11 at 10:52 +0800, yakui_zhao wrote:
> > Hi, All
> >
> > This is the patch set to add the CVT/GTF algorithm in kernel space.
> > They are based on
> > the CVT/GTF function in xserver. But
On Wed, 2009-06-10 at 06:35 +0800, Jesse Barnes wrote:
> On Tue, 09 Jun 2009 15:16:53 -0700
> Eric Anholt wrote:
>
> > On Mon, 2009-06-08 at 08:52 +0800, yakui_zhao wrote:
> > > On Fri, 2009-06-05 at 19:11 +0800, Eric Anholt wrote:
> > > > On Fri, 2009-06
On Wed, 2009-06-10 at 06:16 +0800, Eric Anholt wrote:
> On Mon, 2009-06-08 at 08:52 +0800, yakui_zhao wrote:
> > On Fri, 2009-06-05 at 19:11 +0800, Eric Anholt wrote:
> > > On Fri, 2009-06-05 at 15:45 +0800, yakui_zhao wrote:
> > > > It is useful to get the reg
On Mon, 2009-06-08 at 10:04 +0800, yakui_zhao wrote:
> Hi, All
> the following is the patch set that adds the default modes for LVDS in
> KMS
> mode. It is to solve the following bugs:
> http://bugs.freedesktop.org/show_bug.cgi?id=20801
> http://bu
On Tue, 2009-06-02 at 14:07 +0800, yakui_zhao wrote:
> Hi,
Hi,
Any comments on this patch set?
Is it convenient to get the debug info in KMS mode?
Thanks.
> When the X is started in UMS mode, we can see the info related with the
> mode
> setting in the
On Mon, 2009-06-08 at 10:18 +0800, yakui_zhao wrote:
> Hi,
Hi, Carl
How about this patch set?
I also send the KMS version of patch set for this issue. And this patch
set is already shipped.
Thanks.
Yakui
> The following is the patch set that use the SDVO
On Mon, 2009-06-08 at 10:04 +0800, yakui_zhao wrote:
> Hi, All
> the following is the patch set that adds the default modes for LVDS in
> KMS
> mode. It is to solve the following bugs:
> http://bugs.freedesktop.org/show_bug.cgi?id=20801
> http://bu
Hi, All
the following is the patch set that adds the default modes for LVDS in
KMS
mode.
Patch 1/3: Add a private data for LVDS
When the connector type is LVDS, it will add a private data
that
can be used to store the LVDS panel limit. For example: hdisplay, vdisp
Fix the EDID for the LVDS output device to add the default modes.This is
similar to what we have done in UMS mode.
a. When there exists the EDID, either find the DS_RANGES block or replace
a DS_VENDOR block, smashing it into a DS_RANGES block with open refresh
to match all the defaults modes.
b. W
Hi,
The following is the patch set that use the SDVO device info
parsed from general definition block to initialize the SDVO device.
It is to fix the following bug:
http://bugs.freedesktop.org/show_bug.cgi?id=20429
By parsing the general definition block of VBT w
Subject: GFX: Initialize the SDVO device based on the valid slave address
From: Zhao Yakui
When the slave address is found for the SDVO port, the SDVO device will
be initialzied.
When the slave address is not found for the SDVO port, it will return
the slave address by using the following flowch
On Fri, 2009-06-05 at 19:11 +0800, Eric Anholt wrote:
> On Fri, 2009-06-05 at 15:45 +0800, yakui_zhao wrote:
> > It is useful to get the register snapshot.
> > Add a debugfs I/F named "i915_reg" to dump the I915 register snapshot. And
> > this
> > is created
Add the private data when the connector type is LVDS.
We can use the private_data to store the LVDS panel limit.
For example: Hdisplay, Vdisplay
Signed-off-by: Zhao Yakui
---
src/drmmode_display.c | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
Index: xf86_vi
Hi, All
the following is the patch set that adds the default modes for LVDS in
KMS
mode. It is to solve the following bugs:
http://bugs.freedesktop.org/show_bug.cgi?id=20801
http://bugs.freedesktop.org/show_bug.cgi?id=21094
http://bugs.freedesktop.org/show_b
The size of general definition block varies on different platform/machines.
In such case the number of child device is also different.
And it will be better to get the number of child device in general definition
block dynamically.
The number of child device can be calculated by the following for
When the connector type is LVDS, it will traverse the mode list returned by KMS
kernel to
get the LVDS panel limit.
Then it will use the panel limit to check whether the given modeline is valid.
If the given modeline exceeds the LVDS panel limit, it will be invalid.
Signed-off-by: Zhao Yakui
---
This covers:
a. create the scaling mode property and attach it to LVDS
b. add the support of panel fitting property for LVDS
c. update the display mode according to the panel fitting mode
v2: the drm_calloc/drm_free is replaced by kzalloc/kfree based
on Eric's suggesti
The general definition block contains the child device tables, which include
the child device info. For example: device slave address, device dvo port,
device type.
We will get the info of SDVO device by parsing the general definition blocks.
Only when a valid slave address is found, it is regarded
It is useful to get the register snapshot.
Add a debugfs I/F named "i915_reg" to dump the I915 register snapshot. And this
is created under the dri/0/ of debugfs.
The output format is similar to what we have done in UMS mode.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/Makefile
Use the DRM_DEBUG_KMS macro definition to print the debug info for
the LVDS.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_lvds.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
Index: linux-2.6/drivers/gpu/drm/i915/intel_lvds.c
Now all the DRM debug info will be reported if the boot option of
"drm.debug=1" is added. Sometimes it is inconvenient to get the debug
info in KMS mode. We will get too much unrelated info.
This will separate several DRM debug levels and the debug level can be used
to print the different debug
Use the DRM_DEBUG_KMS/DEBUG_LOG_KMS to print the debug info for
SDVO device.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_sdvo.c | 67 +++---
1 file changed, 35 insertions(+), 32 deletions(-)
Index: linux-2.6/drivers/gpu/drm/i915/intel_sdvo.c
Replace the DRM_DEBUG with DRM_DEBUG_MODE macro to print the info in drm_mode.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/drm_modes.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
Index: linux-2.6/drivers/gpu/drm/drm_modes.c
=
Replace the DRM_DEBUG with the DRM_DEBUG_DRIVER to print the debug info
in i915 driver.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/i915_dma.c | 49 +++-
1 file changed, 29 insertions(+), 20 deletions(-)
Index: linux-2.6/drivers/gpu/drm/i915/i915_dma
Hi,
When the X is started in UMS mode, we can see the info related with the
mode
setting in the Xorg.log(For example: SDVO device command, modeline validation).
This is very helpful to analyze the issue related with modesetting.
When KMS is used, we have no such info. Maybe it is very
Hi,
The following is the patch set that use the SDVO device info
parsed from general definition block to initialize the SDVO device.
It is to fix the following bug:
http://bugs.freedesktop.org/show_bug.cgi?id=20429
By parsing the general definition block of VBT w
On Wed, 2009-05-27 at 23:28 +0800, Jesse Barnes wrote:
> On Fri, 15 May 2009 19:21:40 +1000
> Dave Airlie wrote:
>
> > > Now all the DRM debug info will be printed if the boot option of
> > > "drm.debug=1" is added. Sometimes it is inconvenient. We will get
> > > too much unrelated info.
> > >
>
When the connector type is LVDS, it will traverse the mode list returned by KMS
kernel to
get the LVDS panel limit.
Then it will use the panel limit to check whether the given modeline is valid.
If the given modeline exceeds the LVDS panel limit, it will be invalid.
Signed-off-by: Zhao Yakui
---
Hi,
The following is the patch set that use the SDVO device info
parsed from general definition block to initialize the SDVO device.
It is to fix the following bug:
http://bugs.freedesktop.org/show_bug.cgi?id=20429
By parsing the general definition block of VBT w
The size of general definition block varies on different platform/machines.
In such case the number of child device is also different.
And it will be better to get the number of child device in general definition
block dynamically.
The number of child device can be calculated by the following for
The general definition block contains the child device tables, which include
the SDVO device info. For example: device slave address, device dvo port,
device type.
We will get the info of SDVO device by parsing the general definition blocks.
Only when a valid slave address is found, it is regarded
Add the private data when the connector type is LVDS.
We can use the private_data to store the LVDS panel limit.
For example: Hdisplay, Vdisplay
Signed-off-by: Zhao Yakui
---
src/drmmode_display.c | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
Index: xf86_vi
The general definition block contains the child device tables, which include
the child device info. For example: device slave address, device dvo port,
device type.
We will get the info of SDVO device by parsing the general definition blocks.
Only when a valid slave address is found, it is regarded
When the slave address is found for the SDVO port, the slave address will
use to initialize the SDVO device.
When the slave address is not found for the SDVO port, it will use the
the slave address returned by using the following flowchart to initialize
the SDVO device.
a. If the SDVO device info
Add the private data when the connector type is LVDS.
We can use the private_data to store the LVDS panel limit.
For example: Hdisplay, Vdisplay
Signed-off-by: Zhao Yakui
---
src/drmmode_display.c | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
Index: xf86_vi
When the slave address is found for the SDVO port, the SDVO device will
be initialzied.
When the slave address is not found for the SDVO port, it will return
the slave address by using the following flowchart:
a. If the SDVO device info is found for another SDVO port, it will return
the slave addre
Fix the EDID for the LVDS output device to add the default modes.This is
similar to what we have done in UMS mode.
a. When there exists the EDID, either find the DS_RANGES block or replace
a DS_VENDOR block, smashing it into a DS_RANGES block with open refresh
to match all the defaults modes.
b. W
Hi, All
the following is the patch set that adds the default modes for LVDS in
KMS
mode. It is to solve the following bugs:
http://bugs.freedesktop.org/show_bug.cgi?id=20801
http://bugs.freedesktop.org/show_bug.cgi?id=21094
http://bugs.freedesktop.org/show_b
Add the definition of child_device_config. And the general definition is
updated by using child_device_config.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_bios.h | 101 ++
1 file changed, 93 insertions(+), 8 deletions(-)
Index: linux-2.6/drivers
When the slave address is found for the SDVO port, the SDVO device will
be initialzied. Otherwise it will be skipped.
http://bugs.freedesktop.org/show_bug.cgi?id=20429
Signed-off-by: Zhao Yakui
---
src/i830_sdvo.c | 49 ++---
1 file changed, 46 ins
Hi,
The following is the patch set that use the SDVO device info
parsed from general definition block to initialize the SDVO device.
By parsing the general definition block of VBT we can get the
relationship between the DVO port and slave address. For example: the
SDVO wiring, the
The size of general definition block varies on different platform/machines.
In such case the number of child device is also different.
And it will be better to get the number of child device in general definition
block dynamically.
The number of child device can be calculated by the following fo
The general definition block contains the child device tables, which include
the child device info. For example: device slave address, device dvo port,
device type.
We will get the info of SDVO device by parsing the general definition blocks.
Only when a valid slave address is found, it is regarded
On Thu, 2009-05-21 at 14:45 +0800, yakui_zhao wrote:
> This covers:
> a. create the scaling mode property and attach it to LVDS
> b. add the support of panel fitting property for LVDS
> c. update the display mode according to the panel fitting mode
>
>
Hi, All
the following is the patch set that adds the default modes for LVDS in
KMS
mode.
Patch 1/3: Add a private data for LVDS
When the connector type is LVDS, it will add a private data
that
can be used to store the LVDS panel limit. For example: hdisplay, vdisp
Add the private data when the connector type is LVDS.
We can use the private_data to store the LVDS panel limit.
For example: Hdisplay, Vdisplay
Signed-off-by: Zhao Yakui
---
src/drmmode_display.c | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
Index: xf86_vi
When the connector type is LVDS, it will traverse the mode list returned by KMS
kernel to
get the LVDS panel limit.
Then it will use the panel limit to check whether the given modeline is valid.
If the given modeline exceeds the LVDS panel limit, it will be invalid.
Signed-off-by: Zhao Yakui
---
Fix the EDID for the LVDS output device to add the default modes.This is
similar to what we have done in UMS mode.
a. When there exists the EDID, either find the DS_RANGES block or replace
a DS_VENDOR block, smashing it into a DS_RANGES block with open refresh
to match all the defaults modes.
b. W
On Fri, 2009-05-15 at 17:21 +0800, Dave Airlie wrote:
> > Now all the DRM debug info will be printed if the boot option of
> > "drm.debug=1" is added. Sometimes it is inconvenient. We will get too much
> > unrelated info.
> >
> > This will separate several DRM debug levels and the debug level can b
Now all the DRM debug info will be printed if the boot option of
"drm.debug=1" is added. Sometimes it is inconvenient. We will get too much
unrelated info.
This will separate several DRM debug levels and the debug level can be used
to print the different debug info. And the debug level is control
Add the GTF algorithm in kernel space. And this function can be called to
generate the required modeline.
I copy it from the file of xserver/hw/xfree86/modes/xf86gtf.c. What I have
done is to translate it by using integer calculation. This is to avoid
the float-point calculation in kernel space.
A
Hi, All
This is the patch set to add the CVT/GTF algorithm in kernel space.
They are based on
the CVT/GTF function in xserver. But the CVT/GTF algorithm in xserver is
realized by using float-point
calculation. And the float-point calculation had better be avoided in kernel
space. I tran
Add the CVT algorithm in kernel space. And this function can be called to
generate the required modeline.
I copy it from the file of xserver/hw/xfree86/modes/xf86cvt.c. What I have
done is to translate it by using integer calculation. This is to avoid
the float-point calculation in kernel space.
On Thu, 2009-05-07 at 06:01 +0800, Eric Anholt wrote:
> On Tue, 2009-05-05 at 15:19 +0800, yakui_zhao wrote:
> > Add the CVT algorithm in kernel space. And this function can be called to
> > generate the required modeline.
> >
> > Signed-off-by: Zhao Yakui
>
> T
On Wed, 2009-05-06 at 02:17 +0800, Ian Romanick wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> yakui_zhao wrote:
> > Add the CVT algorithm in kernel space. And this function can be called to
> > generate the required modeline.
> >
> > Signed-off-
Hi, All
This is the patch set to add the CVT/GTF algorithm in kernel space.
They are based on
the CVT/GTF function in xserver. But the CVT/GTF algorithm in xserver is
realized by using float-point
calculation. And the float-point calculation had better be avoided in kernel
space. I tran
Add the CVT algorithm in kernel space. And this function can be called to
generate the required modeline.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/drm_modes.c | 210
include/drm/drm_crtc.h |3
2 files changed, 213 insertions(+)
Index:
Add the GTF algorithm in kernel space. And this function can be called to
generate the required modeline.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/drm_modes.c | 188
include/drm/drm_crtc.h |3
2 files changed, 191 insertions(+)
Index:
A. Hi, Eric
It is not very good to add the giant tables of modelines. It will be
perfect if the modeline is generated by using CVT/GTF algorithm.
Then I use the CVT/GTF to get the mode and find that the mode
generated by CVT/GTF is different with the default mode in Xserver.
For
Hi, Kaleb
From the git log I know that the two files of vesamodes/extramodes
are created by you. And the default modes will be generated by two
scripts. In the two files there define the parameters for the different
modelines. For example: hdisplay, vdisplay, htotal, vtotal, pclk.
My q
This covers:
a. create the scaling mode property and attach it to LVDS
b. add the support of panel fitting property for LVDS
c. update the display mode according to the panel fitting mode
v2: the drm_calloc/drm_free is replaced by kzalloc/kfree based
on Eric's suggesti
On Wed, 2009-04-08 at 18:17 +0800, Thomas Renninger wrote:
> Hi,
>
> We have these interfaces:
> - vendor specific implementation
> (mostly in drivers/platform/x86/vendor-laptop.c)
> - ACPI generic backlight only
> - Opregion (this is the KMS/i915 interface you are talking about
> or
On Tue, 2009-04-07 at 15:38 +0800, Matthew Garrett wrote:
> On Tue, Apr 07, 2009 at 03:25:23PM +0800, yakui_zhao wrote:
> > On Tue, 2009-04-07 at 13:57 +0800, Matthew Garrett wrote:
> > > No, since in UMS mode the X server handles the backlight registers.
> > If so, ther
On Tue, 2009-04-07 at 16:48 +0800, Zhang, Rui wrote:
> CC Thomas, Len and linux-acpi mail list.
>
> On Tue, 2009-04-07 at 16:22 +0800, Matthew Garrett wrote:
> > On Tue, Apr 07, 2009 at 04:20:34PM +0800, Zhang Rui wrote:
> >
> > > All subsystems can register a set of callbacks for backlight contr
On Tue, 2009-04-07 at 13:57 +0800, Matthew Garrett wrote:
> On Tue, Apr 07, 2009 at 11:45:11AM +0800, yakui_zhao wrote:
> > On Sat, 2009-04-04 at 00:29 +0800, Matthew Garrett wrote:
> > > Right. I'd imagine it as i915 loading and calling is_acpi_backlight().
> > >
On Sat, 2009-04-04 at 00:29 +0800, Matthew Garrett wrote:
> On Fri, Apr 03, 2009 at 09:24:08AM -0700, Jesse Barnes wrote:
> > I'd rather not have a native kernel backlight property (i.e. a property
> > on the LVDS output) exposed at all. I chatted with Matthew about this
> > a little, and I think
Hi, All
When the kernel is booted with KMS enabled, the backlight brightness
can't be changed by xrandr tool. This issue is caused by that the native
kernel backlight I/F is not exposed to userland. In such case there is
no backlight property in xrandr tool. Of course the brightness can't be
c
This covers:
Check whether the INTERLACE/DBLSCAN is supported by output device. If
not, the mode containing the flag of INTERLACE/DBLSCAN will be marked
as unsupported.
v2: Fix the code-style and several minor issues based on Eric's suggestion
Signed-off-by: Zhao Yakui
---
d
On Thu, 2009-04-02 at 04:16 +0800, Eric Anholt wrote:
> On Mon, 2009-03-23 at 11:15 +0800, yakui_zhao wrote:
> > Subject: [DRM/I915]: Sync the mode validation for INTERLACE/DBLSCAN
> > From: Zhao Yakui
> >
> > Sync the mode validation for INTERLACE/D
This covers:
Check whether the INTERLACE/DBLSCAN is supported by output device. If
not, the mode containing the flag of INTERLACE/DBLSCAN will be marked
as unsupported.
v2: Fix the code-style and several minor issues based on Eric's suggestion
Signed-off-by: Zhao Yakui
---
d
On Thu, 2009-04-02 at 13:22 +0800, Zhao, Yakui wrote:
Hi, Eric
this time the email is sent by using git-send-email. But after
saving the message from email and running checkpatch.pl, it seems that
the patch is still mangled.
I don't know what I should do.
thanks.
> This covers:
> a. c
On Thu, 2009-04-02 at 04:38 +0800, Alex Deucher wrote:
> On 4/1/09, Eric Anholt wrote:
> > On Mon, 2009-03-23 at 11:30 +0800, yakui_zhao wrote:
> > > Subject: [DRM/I915]: Sync the default modes for LVDS output device
> > > From: Zhao Yakui
> > >
> &
This covers:
a. create the scaling mode property and attach it to LVDS
b. add the support of panel fitting property for LVDS
c. update the display mode according to the panel fitting mode
v2: the drm_calloc/drm_free is replaced by kzalloc/kfree based
on Eric's suggesti
On Sat, 2009-03-21 at 03:59 +0800, Eric Anholt wrote:
> On Fri, 2009-03-20 at 14:13 +0800, yakui_zhao wrote:
> > Subject: [DRM/I915]: Sync the default modes for LVDS output device
> > From: Zhao Yakui
> >
> > Sync the default modes for the LVDS output device
>
Subject: [DRM/I915]: Sync the default modes for LVDS output device
From: Zhao Yakui
Sync the default modes for the LVDS output device
This covers:
Add the default modes for the LVDS output device.
The bit of edid->feature.msc indicates whether the display device is not
continous-frequ
Subject: [DRM/I915]: Sync the mode validation for INTERLACE/DBLSCAN
From: Zhao Yakui
Sync the mode validation for INTERLACE/DBLSCAN
This covers:
Check whether the INTERLACE/DBLSCAN is supported by output device. If
not, the mode containing the flag of INTERLACE/DBLSCAN will be mark
Subject: DRM/I915: Sync the panel fitting property with 2D driver
From: Zhao Yakui
Sync the panel fitting property with 2D driver
This covers:
a. create the scaling mode property and attach it to LVDS
b. add the support of panel fitting property for LVDS
c. update the dis
Subject: [DRM/I915]: Sync the mode validation for INTERLACE/DBLSCAN
From: Zhao Yakui
Sync the mode validation for INTERLACE/DBLSCAN
This covers:
Check whether the INTERLACE/DBLSCAN is supported by output device. If
not, the mode containing the flag of INTERLACE/DBLSCAN will be mark
Subject: DRM/I915: Sync the panel fitting property with 2D driver
From: Zhao Yakui
Sync the panel fitting property with 2D driver
This covers:
a. create the scaling mode property and attach it to LVDS
b. add the support of panel fitting property for LVDS
c. update the dis
Hi
the following is the patch set for KMS about LVDS.
patch 01: Sync the mode validation for INTERLACE/DBLSCAN
Check whether the INTERLACE/DBLSCAN is supported by the output
device. If
it is unsupported, the mode containing the flag of INTERLACE/DBLSCAN will be
marked as
i
Subject: [DRM/I915]: Sync the mode validation for INTERLACE/DBLSCAN
From: Zhao Yakui
Sync the mode validation for INTERLACE/DBLSCAN
This covers:
Check whether the INTERLACE/DBLSCAN is supported by output device. If
not, the mode containing the flag of INTERLACE/DBLSCAN will be mark
Subject: [DRM/I915]: Sync the default modes for LVDS output device
From: Zhao Yakui
Sync the default modes for the LVDS output device
This covers:
Add the default modes for the LVDS output device.
The bit of edid->feature.msc indicates whether the display device is not
continous-f
Hi
the following is the patch set for KMS about LVDS.
patch 01: Sync the mode validation for INTERLACE/DBLSCAN
Check whether the INTERLACE/DBLSCAN is supported by the output
device. If
it is unsupported, the mode containing the flag of INTERLACE/DBLSCAN will be
marked as
i
The following is the updated patch.
This covers:
Add the load-detection for CRT detect
And when it fails in DDC CRT detection, the load-detection will be
used.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_crt.c | 140
++-
1 file chan
On Tue, 2009-03-03 at 18:25 +0800, Steven J Newbury wrote:
> On Tue, 2009-03-03 at 17:48 +0800, yakui_zhao wrote:
> > Hi
> > the following is the patch set for KMS about CRT/LVDS. I have tested
> > them on the
> > T61 box.
> > patch 01: add the CRT save/re
Subject: Patch DRM/i915: Add the crt save/restore function for VT switch
From: Zhao Yakui
Add the crt save/restore function for VT switch
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_crt.c | 22 ++
1 file changed, 22 insertions(+)
Index: linux-2.6/drivers/gp
Subject: Patch DRM/I915: Sync crt hotplug detection with intel video driver
From: Zhao Yakui
Synchronize the function of crt hotplug detection with intel driver
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/i915_reg.h | 16 +
drivers/gpu/drm/i915/intel_crt.c | 47
Subject: Patch DRM/I915: Sync mode_valid/mode_set with intel video driver
From: Zhao Yakui
Synchronize the function of mode_valid/mode_set with intel video driver
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_crt.c | 20
1 file changed, 16 insertions(+), 4 del
Subject: Patch DRM/I915: Add the load-detection for crt detect
From: Zhao Yakui
Add the load-detection for crt detect
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/intel_crt.c | 136 ++-
1 file changed, 133 insertions(+), 3 deletions(-)
Index: li
Subject: Patch DRM/I915: Sync the LVDS save/restore function with intel driver
From: Zhao Yakui
Sync the LVDS save/restore functin with intel driver. At the same time
the possible_crtcs/clones for LVDS is added explicitly.
Signed-off-by: Zhao Yakui
---
drivers/gpu/drm/i915/i915_reg.h |
Hi
the following is the patch set for KMS about CRT/LVDS. I have tested them
on the
T61 box.
patch 01: add the CRT save/restore for VT switch
patch 02: Sync crt mode_valid/mode_set with intel driver
patch 03: sync CRT hotplug detection with intel driver
patch 04: add the load-d
93 matches
Mail list logo
