This will otherwise cause a lockdep splat if reservations were a real lock
type, so warn when nouveau forgets to unpin a buffer, and fix up the ones I've
hit.
Signed-off-by: Maarten Lankhorst
---
diff --git a/drivers/gpu/drm/nouveau/nouveau_abi16.c
b/drivers/gpu/drm/nouveau/nouveau_abi16.c
inde
Hi Eunchul,
IMHO, each function for source and destination has quite similar routine
and it seems that there are some redundant code. I'm not sure these
duplicated code can be removed with mergeing similar part.
Some comments are below.
On 2012? 10? 29? 22:10, Eunchul Kim wrote:
> FIMC is stand
Dear Seung-Woo Kim
Thank's for your comment. and you gave the first comment. :)
I also considered about mergeing set_fmt, set_fmt_order.
but If we merge this function, we need to seperate all "switch case"
routine.
so, complexity has increased after mergeing.
and I designed this set_fmt functio
Hi Linus,
I let this go a few days longer than I normally do since you looked to be
having lots of fun with various underwater things, so this is an all over
set of fixes, nothing really stands out, nearly all of them fix a
regression in one driver or another, or some sort of oops.
its vmware
Hi Laurent,
On Wed, Nov 21, 2012 at 11:02:44PM +0100, Laurent Pinchart wrote:
> Hi Steffen,
>
> > +
> > + htotal = vm->hactive + vm->hfront_porch + vm->hback_porch +
> > +vm->hsync_len;
> > + vtotal = vm->vactive + vm->vfront_porch + vm->vback_porch +
> > +vm->vsync_le
The 'pages' structure in the exynos gem buffer has been
removed. So we get the fix.smem_start from the first sgl
of the scatter gather table.
Signed-off-by: Prathyush K
---
drivers/gpu/drm/exynos/exynos_drm_fbdev.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drive
On 2012? 11? 21? 20:36, Rahul Sharma wrote:
> Hi Seung Woo,
>
> Thanks for your inputs. Please find my response below.
>
> On Wed, Nov 21, 2012 at 2:12 PM, ??? wrote:
>> Hi Rahul,
>>
>> Control part seems good, and my comment is below.
>>
>> On 2012? 11? 10? 01:21, Rahul Sharma wrote:
>>> This p
ode1, struct drm_display_mode
> *mode2)
> +bool drm_mode_equal(const struct drm_display_mode *mode1,
> + const struct drm_display_mode *mode2)
I think this change warrants a separate commit.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/3ea9637c/attachment-0001.pgp>
uld just as well convert all of them.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/d3ab1164/attachment.pgp>
the drm docbook, that would
> be rather awesome ;-)
I suck at documentation =), but I'll see what I can do.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/cd88111f/attachment.pgp>
Right, I missed.
Thanks,
Inki Dae
> -Original Message-
> From: Prathyush K [mailto:prathyush.k at samsung.com]
> Sent: Thursday, November 22, 2012 3:49 PM
> To: dri-devel at lists.freedesktop.org
> Cc: inki.dae at samsung.com
> Subject: [PATCH] drm/exynos: use sgt instead of pages for fra
2012/11/22 Thierry Reding :
> On Wed, Nov 21, 2012 at 05:08:12PM +0100, Daniel Vetter wrote:
>> On Wed, Nov 21, 2012 at 4:47 PM, Thierry Reding
>> wrote:
>> > Oh great, so I copied that table for nothing. Thanks for Cc'ing, I can
>> > reuse that in the HDMI infoframe series.
>>
>> Wrt the infofram
for
some hardware, but should be enough according to the specification.
Having more data in the AVI infoframe shouldn't hurt, though.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/d3ffed20/attachment.pgp>
On 21 November 2012 20:42, Sachin Kamat wrote:
> Hi Dave,
>
> Please ignore this patch.
>
>
Please ignore this mail. Sorry for the noise.
--
With warm regards,
Sachin
Hi Inki,
On 19 November 2012 15:32, Sachin Kamat wrote:
> On 19 November 2012 15:30, Inki Dae wrote:
>>
>>
>>> -Original Message-
>>> From: Sachin Kamat [mailto:sachin.kamat at linaro.org]
>>> Sent: Monday, November 19, 2012 6:56 PM
>>> To: Inki Dae
>>> Cc: dri-devel at lists.freedesktop
> -Original Message-
> From: Sachin Kamat [mailto:sachin.kamat at linaro.org]
> Sent: Thursday, November 22, 2012 3:13 PM
> To: Inki Dae
> Cc: dri-devel at lists.freedesktop.org; jy0922.shim at samsung.com;
> patches at linaro.org
> Subject: Re: [PATCH 1/1] drm/exynos: Fix potential NULL
> -Original Message-
> From: Sachin Kamat [mailto:sachin.kamat at linaro.org]
> Sent: Thursday, November 22, 2012 5:19 PM
> To: Inki Dae
> Cc: dri-devel at lists.freedesktop.org; jy0922.shim at samsung.com;
> patches at linaro.org
> Subject: Re: [PATCH 1/1] drm/exynos: Fix potential NULL
https://bugzilla.kernel.org/show_bug.cgi?id=43751
--- Comment #4 from wmotti at gmail.com 2012-11-22 08:34:19 ---
Same problem here with 3.6.6 kernel
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watchi
Hi Sascha,
On Thursday 22 November 2012 07:20:00 Sascha Hauer wrote:
> On Wed, Nov 21, 2012 at 11:02:44PM +0100, Laurent Pinchart wrote:
> > Hi Steffen,
> >
> > > +
> > > + htotal = vm->hactive + vm->hfront_porch + vm->hback_porch +
> > > + vm->hsync_len;
> > > + vtotal = vm->vactive + v
Those tend to be totally not interesting for end-users, and for
debugging we tend to dump the entire noise anyway by enabling all
debug messages.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=57388
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_edid.c |2 +-
1 file changed, 1
On Thu, Nov 22, 2012 at 09:50:10AM +0100, Laurent Pinchart wrote:
> Hi Sascha,
>
> On Thursday 22 November 2012 07:20:00 Sascha Hauer wrote:
> > On Wed, Nov 21, 2012 at 11:02:44PM +0100, Laurent Pinchart wrote:
> > > Hi Steffen,
> > >
> > > > +
> > > > + htotal = vm->hactive + vm->hfront_po
On Thursday 22 November 2012 09:53:42 Sascha Hauer wrote:
> On Thu, Nov 22, 2012 at 09:50:10AM +0100, Laurent Pinchart wrote:
> > On Thursday 22 November 2012 07:20:00 Sascha Hauer wrote:
> > > On Wed, Nov 21, 2012 at 11:02:44PM +0100, Laurent Pinchart wrote:
> > > > Hi Steffen,
> > > >
> > > > >
Hi!
On Wed, Nov 21, 2012 at 09:03:38AM -0600, Rob Herring wrote:
> On 11/21/2012 05:52 AM, Thierry Reding wrote:
> > On Wed, Nov 21, 2012 at 12:48:43PM +0100, Steffen Trumtrar wrote:
> >> Hi!
> >>
> >> On Wed, Nov 21, 2012 at 10:12:43AM +, Manjunathappa, Prakash wrote:
> >>> Hi Steffen,
> >>>
The patches have been reordered and the changes suggested by
Takashi Iwai have been worked in.
Egbert Eich (18):
1. Make error handling of EDID extension blocks a bit more fault
tolorant:
* Don't fail when EDID extension blocks cannot be read or memory
cannot be allocated.
* Don't r
When we fail to allocate space for EDID extensions we should just
warn, fix up the EDID block count and return the base block instead
of failing.
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/drm_edid.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/d
There are displays which announce EDID extension blocks in the
Extension Flag of the EDID base block although they are not EDDC
capable (ie. take a segment address at I2C slave address 0x30).
We test this by looking for an EDID header which is only possible
in the base block.
If the segment address
EEDID v1.3 mandates map blogs if more than one EDID extension block
is used while in v1.4 they are optional.
If the extension count has been changed (because some extension
blocks were not readable) those map blocks need fixing.
In case of v1.4 or higher we simply eliminate all map blogs as
this is
EDID extension blogs are only expected for EDIDs version 1.3 or higher.
If an EDID with a lower version is found fix the block count in the
extension flags and return the base block.
This should help to avoid issues with older displays with broken
DDC implementations.
Signed-off-by: Egbert Eich
-
valid_extensions (the number of EDID extensions found to be valid)
can never be > block[EDID_EXTENSION_FLAG_OFFSET].
There is no point of reallocating the block in this case: the
extra blocks at the end of the EDID structure will not hurt,
also the implementation of krealloc() will just return the
Consolidate the null_edid_counter and the bad_edid_counter
into EDID error state flags which for the last EDID read
are accessible from user.
Errors are looged it the same error has not been present
in the previous read of the EDID. This will reset the
EDID error status for example when the monitor
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/mgag200/mgag200_mode.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/mgag200/mgag200_mode.c
b/drivers/gpu/drm/mgag200/mgag200_mode.c
index d3d99a2..f89a0c1 100644
--- a/drivers/gpu/drm/mgag200/mgag200_mode.
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/gma500/cdv_intel_dp.c|1 +
drivers/gpu/drm/gma500/oaktrail_lvds.c |1 +
drivers/gpu/drm/gma500/psb_intel_modes.c |1 +
3 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/gma500/cdv_intel_dp.c
b/drivers/g
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/ast/ast_mode.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c
index 7fc9f72..c27aa8d 100644
--- a/drivers/gpu/drm/ast/ast_mode.c
+++ b/drivers/gpu/drm/ast/ast_m
EDIDs are an integral concept of connectors, connectors are a concept
of drm core also drm_edid.o is already part of this drm core.
Overridden, 'firmware-supplied' EDIDs should be treated exactly the
same as device supplied ones.
Therefore move drm_edid_load from the helper level to the drm core.
v2: Use offsetof().
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/drm_edid.c | 16 +---
1 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 049fa52..9e64069 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drive
According the the VESA specs there can be up to 254 EEDID extension blocks.
Since we may read the EDID (including extensions) in 10 second intervals to
probe for display hotplugging (at least in cases where no hardware hotplug
detection exists) and I2C transfer is rather slow we may end up consumin
So far it was only possible to load an EDID for a single connector (unless
no connector was specified at all in which case the same EDID file was used
for all).
This patch extends the EDID loader so that EDID files can be specified for
more than one connector. A semicolon is used to separate the di
Signed-off-by: Egbert Eich
---
include/drm/drm_crtc.h |8
include/drm/drm_edid.h |9 +
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
index d402b3b..7eed9bd 100644
--- a/include/drm/drm_crtc.h
+++ b/include/d
This patch is a bit cosmetic as the variable size will truncate
the start address anyway but for readability it should be made
explicite that the lowest bit in the EDID block number determines
the I2C start address.
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/drm_edid.c |2 +-
1 files cha
Firmware supplied EDIDs where fed in in
drm_helper_probe_single_connector_modes()
in place of calling the driver supplied get_modes() function.
This has two problems:
1. Drivers don't call drm_get_edid() only from within get_modes().
2. The get_modes() replacement in drm_load_edid_firmware() provi
If I2C readout fails for an extension block but we have read a
valid base block, don't fail completely but at least return the
base block.
v2: Make goto target names more telling.
Signed-off-by: Egbert Eich
---
drivers/gpu/drm/drm_edid.c |7 +--
1 files changed, 5 insertions(+), 2 delet
in drm_edid.c there's now code to fix extension blockmaps if the number
of extensions has changed. This code also rearranges the EDID blocks.
Replace the exisiting EDID rearrange code with a call to this code.
v2: Make adjustments required by patch reordering, add missing memcpy().
Signed-off-by:
On Thu, Nov 22, 2012 at 2:50 PM, Linus Torvalds
wrote:
> On Wed, Nov 21, 2012 at 6:34 PM, Dave Airlie wrote:
>>
>> its vmware/nouveua/radeon/intel/ttm scattered.
>
> Hmm. That's not what I see. I just see nouveau and soem PCI ID addition.
>
>> 21 files changed, 108 insertions(+), 31 deletions(-)
On Thu, Nov 22, 2012 at 05:22:55AM -0500, Egbert Eich wrote:
> There are displays which announce EDID extension blocks in the
> Extension Flag of the EDID base block although they are not EDDC
> capable (ie. take a segment address at I2C slave address 0x30).
> We test this by looking for an EDID he
On Thu, Nov 22, 2012 at 10:07:07AM +0100, Laurent Pinchart wrote:
> On Thursday 22 November 2012 09:53:42 Sascha Hauer wrote:
> > On Thu, Nov 22, 2012 at 09:50:10AM +0100, Laurent Pinchart wrote:
> > > On Thursday 22 November 2012 07:20:00 Sascha Hauer wrote:
> > > > On Wed, Nov 21, 2012 at 11:02:4
Ville Syrj?l? writes:
> On Thu, Nov 22, 2012 at 05:22:55AM -0500, Egbert Eich wrote:
> > There are displays which announce EDID extension blocks in the
> > Extension Flag of the EDID base block although they are not EDDC
> > capable (ie. take a segment address at I2C slave address 0x30).
> > W
On Thu, Nov 22, 2012 at 01:07:28PM +0100, Egbert Eich wrote:
> Ville Syrj?l? writes:
> > On Thu, Nov 22, 2012 at 05:22:55AM -0500, Egbert Eich wrote:
> > > There are displays which announce EDID extension blocks in the
> > > Extension Flag of the EDID base block although they are not EDDC
> > >
On Thu, Nov 22, 2012 at 12:18 PM, Henrik Rydberg wrote:
>> My apologies for the long delay in answering, I've somehow mixed up
>> different bugreports and thought I've sent you a patch to test
>> already. Anyway, please test
>>
>> https://patchwork.kernel.org/patch/1728111/
>
> Tested-by: Henr
Ville Syrj?l? writes:
>
> Me neither. I just figured it might reduce the chance of false
> positives. But if you say that can't happen, I'll take your word
> for it.
>
> > Regarding memcmp() you are definitely right, I will change the code.
> >
> > >
> > > Also the comment is somehow
On Thu, Nov 22, 2012 at 12:06 PM, ??? wrote:
> On 2012? 11? 21? 20:36, Rahul Sharma wrote:
>> Hi Seung Woo,
>>
>> Thanks for your inputs. Please find my response below.
>>
>> On Wed, Nov 21, 2012 at 2:12 PM, ??? wrote:
>>> Hi Rahul,
>>>
>>> Control part seems good, and my comment is below.
>>>
>>
Just add the definition according the kernel's copy of drm.h
Signed-off-by: Imre Deak
---
include/drm/drm.h |1 +
1 file changed, 1 insertion(+)
diff --git a/include/drm/drm.h b/include/drm/drm.h
index a847689..d14b973 100644
--- a/include/drm/drm.h
+++ b/include/drm/drm.h
@@ -779,6 +779,7
On Thu, Nov 22, 2012 at 05:23:03AM -0500, Egbert Eich wrote:
> According the the VESA specs there can be up to 254 EEDID extension blocks.
> Since we may read the EDID (including extensions) in 10 second intervals to
> probe for display hotplugging (at least in cases where no hardware hotplug
> det
Ville Syrj?l? writes:
> On Thu, Nov 22, 2012 at 05:23:03AM -0500, Egbert Eich wrote:
> >
> > - /* if there's no extensions, we're done */
> > + /* if there are no extensions, we're done - don't bother caching */
> >if (block[EDID_EXTENSION_FLAG_OFFSET] == 0)
> >return bloc
https://bugzilla.kernel.org/show_bug.cgi?id=50881
Alan changed:
What|Removed |Added
CC||alan at lxorguk.ukuu.org.uk
Component|Vi
There are displays which announce EDID extension blocks in the
Extension Flag of the EDID base block although they are not EDDC
capable (ie. take a segment address at I2C slave address 0x30).
We test this by looking for an EDID header which is only possible
in the base block.
If the segment address
According the the VESA specs there can be up to 254 EEDID extension blocks.
Since we may read the EDID (including extensions) in 10 second intervals to
probe for display hotplugging (at least in cases where no hardware hotplug
detection exists) and I2C transfer is rather slow we may end up consumin
Consolidate the null_edid_counter and the bad_edid_counter
into EDID error state flags which for the last EDID read
are accessible from user.
Errors are looged it the same error has not been present
in the previous read of the EDID. This will reset the
EDID error status for example when the monitor
Op 21-11-12 14:27, Thomas Hellstrom schreef:
> On 11/21/2012 02:12 PM, Maarten Lankhorst wrote:
>> Op 21-11-12 13:42, Thomas Hellstrom schreef:
>>> On 11/21/2012 12:38 PM, Maarten Lankhorst wrote:
Hey,
Op 20-11-12 16:08, Thomas Hellstrom schreef:
> On 11/20/2012 02:13 PM, Maarten
Add conversion from videomode to drm_display_mode
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
---
drivers/gpu/drm/drm_modes.c | 37
The struct display_timing is specific to the via subsystem. The naming leads to
collisions with the new struct display_timing, that is supposed to be a shared
struct between different subsystems.
To clean this up, prepend the existing struct with the subsystem it is specific
to.
Signed-off-by: Ste
Add helper to get fb_videomode from devicetree.
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
---
drivers/video/fbmon.c | 42
Add display_timing structure and the according helper functions. This allows
the description of a display via its supported timing parameters.
Also, add helper functions to convert from display timings to a generic
videomode
structure.
The struct display_timing specifies all needed parameters to
Hi!
Changes since v12:
- rename struct display_timing to via_display_timing in via subsystem
- fix refreshrate calculation
- fix "const struct *" warnings
(reported by: "Manjunathappa, Prakash" )
- some CodingStyle fixes
- rewrite parts of co
Add helper to get drm_display_mode from devicetree.
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
---
drivers/gpu/drm/drm_modes.c | 34 ++
Add a function to convert from the generic videomode to a fb_videomode.
Signed-off-by: Steffen Trumtrar
Reviewed-by: Thierry Reding
Acked-by: Thierry Reding
Tested-by: Thierry Reding
Tested-by: Philipp Zabel
Reviewed-by: Laurent Pinchart
Acked-by: Laurent Pinchart
Signed-off-by: Steffen Tru
This adds support for reading display timings from DT into a struct
display_timings. The of_display_timing implementation supports multiple
subnodes. All children are read into an array, that can be queried.
If no native mode is specified, the first subnode will be used.
For cases, where the grap
On Thu, Nov 22, 2012 at 09:44:42AM -0500, Egbert Eich wrote:
> Consolidate the null_edid_counter and the bad_edid_counter
> into EDID error state flags which for the last EDID read
> are accessible from user.
> Errors are looged it the same error has not been present
> in the previous read of the E
Hi Steffen,
On Thursday 22 November 2012 17:00:13 Steffen Trumtrar wrote:
> Add helper to get fb_videomode from devicetree.
>
> Signed-off-by: Steffen Trumtrar
> Reviewed-by: Thierry Reding
> Acked-by: Thierry Reding
> Tested-by: Thierry Reding
> Tested-by: Philipp Zabel
> Reviewed-by: Laure
Hi Daniel,
> >> My apologies for the long delay in answering, I've somehow mixed up
> >> different bugreports and thought I've sent you a patch to test
> >> already. Anyway, please test
> >>
> >> https://patchwork.kernel.org/patch/1728111/
> >
> > Tested-by: Henrik Rydberg
>
> Can you please
Hi Steffen,
On Thursday 22 November 2012 17:00:12 Steffen Trumtrar wrote:
> Add a function to convert from the generic videomode to a fb_videomode.
>
> Signed-off-by: Steffen Trumtrar
> Reviewed-by: Thierry Reding
> Acked-by: Thierry Reding
> Tested-by: Thierry Reding
> Tested-by: Philipp Zab
Ville Syrj?l? writes:
> >
> > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> > index dd0df60..aa9b34d 100644
> > --- a/drivers/gpu/drm/drm_edid.c
> > +++ b/drivers/gpu/drm/drm_edid.c
> > @@ -157,6 +157,17 @@ int drm_edid_header_is_valid(const u8 *raw_edid)
> > }
>
On Thu, Nov 22, 2012 at 07:28:44PM +0100, Egbert Eich wrote:
> Ville Syrj?l? writes:
> > >
> > > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> > > index dd0df60..aa9b34d 100644
> > > --- a/drivers/gpu/drm/drm_edid.c
> > > +++ b/drivers/gpu/drm/drm_edid.c
> > > @@ -15
Consolidate the null_edid_counter and the bad_edid_counter
into EDID error state flags which for the last EDID read
are accessible from user.
Errors are looged it the same error has not been present
in the previous read of the EDID. This will reset the
EDID error status for example when the monitor
ierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/d76da079/attachment.pgp>
v2: Adjusted to apply cleanly.
Signed-off-by: Egbert Eich
---
include/drm/drm_crtc.h |8
include/drm/drm_edid.h |9 +
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
index 7a3ccbf..7eed9bd 100644
--- a/includ
Instead of using the stride derived from the display mode, use the pitch
associated with the currently active framebuffer. This fixes a bug where
the LCD display content would be skewed when enabling HDMI with a video
mode different from that of the LCD.
Signed-off-by: Thierry Reding
---
drivers
est it twice with libgl 8.0.4 and 9.0.1.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/9b615afd/attachment.html>
ompiled.
Could the bug be in there? I guess not.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121122/5793c36e/attachment.html>
Ville Syrj?l? writes:
> On Thu, Nov 22, 2012 at 07:28:44PM +0100, Egbert Eich wrote:
> >
> > Something similar should be done for drm_edid_is_valid() - even if the
> > driver doesn't bother (for instance because this function is only called
> > once when the device structures are initialized
On Thu, Nov 22, 2012 at 7:23 PM, Henrik Rydberg wrote:
>> >> My apologies for the long delay in answering, I've somehow mixed up
>> >> different bugreports and thought I've sent you a patch to test
>> >> already. Anyway, please test
>> >>
>> >> https://patchwork.kernel.org/patch/1728111/
>> >
>> >
On 11/22/2012 04:51 PM, Maarten Lankhorst wrote:
> Op 21-11-12 14:27, Thomas Hellstrom schreef:
>> On 11/21/2012 02:12 PM, Maarten Lankhorst wrote:
>>> Op 21-11-12 13:42, Thomas Hellstrom schreef:
On 11/21/2012 12:38 PM, Maarten Lankhorst wrote:
> Hey,
>
> Op 20-11-12 16:08, Thomas
> Yeah, the utter lack of a vbt fits very nicely, thanks for checking,
> I've merged the patch into drm-intel-fixes and will forward it for
> inclusion into 3.7 rsn.
Great, thanks. One thing about that patch: if we would ever encounter
a non-zero edp.bpp < 3, display_bpc would not be clamped. I su
Consolidate the null_edid_counter and the bad_edid_counter
into EDID error state flags which for the last EDID read
are accessible from user.
Errors are looged it the same error has not been present
in the previous read of the EDID. This will reset the
EDID error status for example when the monitor
On Thu, Nov 22, 2012 at 10:35:22PM +0100, Krzysztof Mazur wrote:
> On Thu, Nov 22, 2012 at 09:17:54PM +0100, Daniel Vetter wrote:
> > Hi,
> >
> >
> > Since a dpms ioctl call tends to follow a modeset, this likely only
> > results in that dpms call enabling the hw again. Can you please add
> > drm
https://bugzilla.kernel.org/show_bug.cgi?id=49121
--- Comment #3 from Joseph D. Wagner 2012-11-22
21:43:33 ---
Issue appears to be resolved in 3.6.6-1.fc17.x86_64 (gcc version 4.7.2 20120921
(Red Hat 4.7.2-2) (GCC) ).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=ema
From: Laurent Pinchart
Hi everybody,
Here's the second RFC of what was previously known as the Generic Panel
Framework.
I won't repeat all the background information from the first version here, you
can read it at http://lwn.net/Articles/512363/.
Many developers showed interest in the first RF
From: Laurent Pinchart
Signed-off-by: Laurent Pinchart
---
drivers/video/Kconfig|1 +
drivers/video/Makefile |1 +
drivers/video/display/Kconfig|4 +
drivers/video/display/Makefile |1 +
drivers/video/display/display-core.c | 362
From: Laurent Pinchart
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig | 13 +++
drivers/video/display/Makefile|1 +
drivers/video/display/panel-dpi.c | 147 +
include/video/panel-dpi.h | 24 ++
4 files changed,
From: Laurent Pinchart
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig|4 +
drivers/video/display/Makefile |1 +
drivers/video/display/mipi-dbi-bus.c | 228 ++
include/video/display.h |5 +
include/video/m
From: Laurent Pinchart
The R61505 is a SYS-80 bus panel controller from Renesas.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig|9 +
drivers/video/display/Makefile |1 +
drivers/video/display/panel-r61505.c | 554 ++
inc
From: Laurent Pinchart
The R61517 is a MIPI DBI panel controller from Renesas.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig|9 +
drivers/video/display/Makefile |1 +
drivers/video/display/panel-r61517.c | 447 ++
inclu
[snip]
>> >> And NULL pointer checking was already done above like below,
>> >> if (overlay_ops && overlay_ops->disable)
>> >> overlay_ops->disable(manager->dev, zpos);
>> > Correct. But that check is applicable only for that one statement
>> > (overlay_ops->disable(manager-
Hi Daniel,
> My apologies for the long delay in answering, I've somehow mixed up
> different bugreports and thought I've sent you a patch to test
> already. Anyway, please test
>
> https://patchwork.kernel.org/patch/1728111/
Tested-by: Henrik Rydberg
Thanks,
Henrik
This patch adds code for composing AVI and AUI info frames
and send them every VSYNC.
This patch is important for hdmi certification.
Based on exynos-drm-fixes branch of
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
Signed-off-by: Rahul Sharma
Signed-off-by: Fahad Kunnath
Hi,
since Linux 3.1 I'm having some problems with i915 driver on HP nc6120
with 915GM chipset. The display goes black after the kernel tries to
blank screen while LID is closed (see steps to reproduce to more detailed
description).
Currently I'm using Linux 3.7-rc6 with KMS enabled and disabled A
On Thu, Nov 22, 2012 at 09:17:54PM +0100, Daniel Vetter wrote:
> Hi,
>
> Thanks for the report. Now this smells like something which could take
> a bit longer to track down, so can you please file this on
> bugs.freedesktop.org against DRM -> DRI/Intel to ensure that we dont'
> loose track of it?
On Thu, Nov 22, 2012 at 09:17:54PM +0100, Daniel Vetter wrote:
> Hi,
>
>
> Since a dpms ioctl call tends to follow a modeset, this likely only
> results in that dpms call enabling the hw again. Can you please add
> drm.debug=0xe to your kernel cmdline and boot into a 3.6 with this
> hack applied,
2012/11/22 Thierry Reding :
> On Wed, Nov 21, 2012 at 05:08:12PM +0100, Daniel Vetter wrote:
>> On Wed, Nov 21, 2012 at 4:47 PM, Thierry Reding
>> wrote:
>> > Oh great, so I copied that table for nothing. Thanks for Cc'ing, I can
>> > reuse that in the HDMI infoframe series.
>>
>> Wrt the infofram
On Thu, Nov 22, 2012 at 09:00:24AM +0100, Rafał Miłecki wrote:
> 2012/11/22 Thierry Reding :
> > On Wed, Nov 21, 2012 at 05:08:12PM +0100, Daniel Vetter wrote:
> >> On Wed, Nov 21, 2012 at 4:47 PM, Thierry Reding
> >> wrote:
> >> > Oh great, so I copied that table for nothing. Thanks for Cc'ing, I
> > [ 245.003823] handlers:
> > [ 245.003838] [] azx_interrupt [snd_hda_intel]
> > [ 245.003841] Disabling IRQ #16
>
> Does /proc/interrupts show IRQ 16 being shared between snd_hda_intel
> and radeon? If not, this looks like a snd_hda_intel (or another driver
> sharing the IRQ) issue.
/proc/in
1 - 100 of 202 matches
Mail list logo
