On 03/15/2012 07:50 PM, Dave Airlie wrote:
G2D is a 2D graphic accelerator that supports Bit Block Transfer. This
G2D driver is exynos drm specific and supports only exynos4x12 series.
user application fills command set in cmdlist and once dma start request
these cmdlists are parsed and performed
drm_fb_helper_modinit() calls find_module() which only
needs rcu_read_lock_sched().
The rest seems still have to hold module_mutex to prevent
module insertion/deletion. Instead of exporting module_mutex
for them, export two functions lock_modules()/unlock_modules()
and hide module_mutex.
Cc: Eric
Hi Ben,
I'm sorry for the very very late reply. Please do not jump to the
conclusion that I do not care - I do! Just I am very busy, just as you.
On Wednesday 11 January 2012 01:40:58 pm Ben Skeggs wrote:
> On Wed, 2012-01-11 at 11:17 +0100, Jean Delvare wrote:
> > In the commit message, you com
Hi Dave.
2012년 3월 15일 오후 8:21, Inki Dae 님의 말:
>> -Original Message-
>> From: Dave Airlie [mailto:airl...@gmail.com]
>> Sent: Thursday, March 15, 2012 7:40 PM
>> To: Inki Dae
>> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
>> kyungmin.p...@samsung.com; sw0312@samsung.com
>> Su
> -Original Message-
> From: David Airlie [mailto:airlied at redhat.com]
> Sent: Thursday, March 15, 2012 8:44 PM
> To: Inki Dae
> Cc: kyungmin park; sw0312 kim; dri-devel at lists.freedesktop.org; Dave
> Airlie
> Subject: Re: [PATCH 10/10] drm/exynos: added virtual display driver.
>
>
> -Original Message-
> From: Dave Airlie [mailto:airlied at gmail.com]
> Sent: Thursday, March 15, 2012 7:44 PM
> To: Inki Dae
> Cc: dri-devel at lists.freedesktop.org; kyungmin.park at samsung.com;
> sw0312.kim at samsung.com
> Subject: Re: [PATCH 10/10] drm/exynos: added virtual display
> -Original Message-
> From: Dave Airlie [mailto:airlied at gmail.com]
> Sent: Thursday, March 15, 2012 7:40 PM
> To: Inki Dae
> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
> kyungmin.park at samsung.com; sw0312.kim at samsung.com
> Subject: Re: [PATCH 02/10] drm/exynos: ad
On 03/15/2012 07:50 PM, Dave Airlie wrote:
>> G2D is a 2D graphic accelerator that supports Bit Block Transfer. This
>> G2D driver is exynos drm specific and supports only exynos4x12 series.
>> user application fills command set in cmdlist and once dma start request
>> these cmdlists are parsed and
On 03/15/2012 07:52 PM, Dave Airlie wrote:
>> index 1ed3aae..aff2313 100644
>> --- a/include/drm/exynos_drm.h
>> +++ b/include/drm/exynos_drm.h
>> @@ -147,11 +147,13 @@ struct exynos_drm_common_hdmi_pd {
>> * @timing: default video mode for initializing
>> * @default_win: default window layer n
From: Ville Syrj?l?
The error handling code w.r.t. idr usage looks inconsistent.
In the case of drm_mode_object_get() and drm_ctxbitmap_next() the error
handling is also incomplete.
Unify the code to follow the same pattern always.
Signed-off-by: Ville Syrj?l?
---
drivers/gpu/drm/drm_context
On 03/15/2012 05:19 PM, Joonyoung Shim wrote:
> The contents of exynos_mixer.h are used only in exynos_mixer.c, so
> separated header is unnecessary.
>
> Signed-off-by: Joonyoung Shim
> Signed-off-by: Kyungmin Park
> ---
> drivers/gpu/drm/exynos/exynos_mixer.c | 49 +-
> driver
On Thu, Mar 15, 2012 at 09:57:53AM +, Dave Airlie wrote:
> > Use a do {} while() loop instead of a goto in drm_mode_object_get().
>
> I don't like this one just because it diverges our idr usage from the
> canonical idr usage at
>
> http://lwn.net/Articles/103209/
>
> So unless there is a go
On Thu, Mar 15, 2012 at 03:32:40PM +0100, Jean Delvare wrote:
> Hi Ville,
>
> On Wed, 14 Mar 2012 10:32:52 +0200, Ville Syrj?l? wrote:
> > When the system is under heavy load, there can be a significant delay
> > between the getscl() and time_after() calls inside sclhi(). That delay
> > may cause
This patch adds hdmi audio feature for exynos drm.
With this patch, i2s channel feeds audio data in hdmi when hdmi is connected.
This patch is for drm-next branch and the base of this patch is patch set from
Joonyoung Shim, "[PATCH 2/2] drm/exynos: cleanup exynos_hdmi.h".
link:
http://www.
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #32 from Alex Deucher 2012-03-15 10:41:15 PDT
---
(In reply to comment #31)
> It is a single DVI-I physically.
>
> But even identifying it would not change anything with regards to polling
> induced rendering stalls, right?
>
Wel
https://bugs.freedesktop.org/show_bug.cgi?id=42611
--- Comment #8 from Cesare Leonardi 2012-03-15 17:40:15
PDT ---
With the latest Firefox from Debian (Iceweasel 10.0.3esr-1), the problem looks
resolved: no more crashes for me. The fix is documented here:
https://bugzilla.mozilla.org/show_bug.cg
The some contents of the exynos_hdmi.h are used only in exynos_hdmi.c,
so move them to exynos_hdmi.c.
Signed-off-by: Joonyoung Shim
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 36
drivers/gpu/drm/exynos/exynos_hdmi.h | 42 --
The contents of exynos_mixer.h are used only in exynos_mixer.c, so
separated header is unnecessary.
Signed-off-by: Joonyoung Shim
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_mixer.c | 49 +-
drivers/gpu/drm/exynos/exynos_mixer.h | 92 --
On 02/28/2012 07:04 PM, Jesse Barnes wrote:
> On Tue, 28 Feb 2012 10:21:44 +0100
> Lars-Peter Clausen wrote:
>
>> The code should obviously check the EDID feature field for EDID feature flags
>> and not the color_formats field of the drm_display_info struct. Also update
>> the
>> color_formats f
put() */
>void (*release)(struct dma_buf *);
>
> + int (*mmap)(struct dma_buf *, struct file *, struct vm_area_struct
> *);
> + int (*prepare_access)(struct dma_buf *);
> + int (*finish_access)(struct dma_buf *);
> +
> };
>
> /**
> --
> 1.7.5.4
>
>
> ___
> Linaro-mm-sig mailing list
> Linaro-mm-sig at lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-mm-sig
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/757718f7/attachment.htm>
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #31 from Tvrtko Ursulin 2012-03-15
09:13:58 PDT ---
(In reply to comment #30)
> > Hm, shared_ddc is also set with single physical DVI-I connector, at least on
> > this motherboard.
>
> According to your vbios tables there are actua
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-i915-panel-invert-brightness-acer-aspire-5734z.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/8b8362ea/attachment.txt>
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-i915-panel-invert-brightness-via-quirk.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/505c68e6/attachment.asc>
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-i915-panel-invert-brightness-via-parameter.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/666f6657/attachment.txt>
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/2bfa4ed6/attachment.asc>
Changes from V4 to V5:
1. Split the previous patch 2/2 into three patches to separately i) add the
module parameter, ii) add the quirk infrastructure, and iii) actually quirk
the related machine.
2. Rename the module parameter variable to i915_panel_invert_brightness.
3. Make the module paramete
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #30 from Alex Deucher 2012-03-15 08:45:10 PDT
---
(In reply to comment #29)
t sure what the right answer is.
>
> Is it possible to have DVI-D + VGA breakout cable from a single DVI-I which
> would give two independent simultaneous o
https://bugs.freedesktop.org/show_bug.cgi?id=47363
Alex Deucher changed:
What|Removed |Added
Attachment #58516|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #29 from Tvrtko Ursulin 2012-03-15
08:34:48 PDT ---
(In reply to comment #28)
> (In reply to comment #26)
> > >
> > > I'm not sure we necessarily want to do that. Even though they may have a
> > > shared ddc line, it would be nice
https://bugs.freedesktop.org/show_bug.cgi?id=47363
Alex Deucher changed:
What|Removed |Added
AssignedTo|xorg-driver-ati at lists.x.org |dri-devel at
lists.freedesktop
Hi Ville,
On Wed, 14 Mar 2012 10:32:52 +0200, Ville Syrj?l? wrote:
> When the system is under heavy load, there can be a significant delay
> between the getscl() and time_after() calls inside sclhi(). That delay
> may cause the time_after() check to trigger after SCL has gone high,
> causing sclhi
> as a headsup, if you are basing a tree on mine, please use
> drm-core-next not drm-next itself as a basis for your tree.
>
> At the moment they've diverged as I've put the UDL kms driver into
> drm-next but not drm-core-next as it needs an external fbdev patch to
> work.
Is this temporary?
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #28 from Alex Deucher 2012-03-15 08:16:33 PDT
---
(In reply to comment #26)
> >
> > I'm not sure we necessarily want to do that. Even though they may have a
> > shared ddc line, it would be nice to report the proper connected statu
On Thu, 15 Mar 2012 15:56:27 +0100, Carsten Emde wrote:
> Mark the Acer Aspire 5734Z that this machines requires the module to
> invert the panel backlight brightness value after reading from and prior
> to writing to the PCI configuration space.
>
> Signed-off-by: Carsten Emde
Acked-by: Chris W
On Thu, 15 Mar 2012 15:56:26 +0100, Carsten Emde wrote:
> A machine may need to invert the panel backlight brightness value. This
> patch adds the infrastructure for a quirk to do so.
>
> Signed-off-by: Carsten Emde
Reviewed-by: Chris Wilson
-Chris
--
Chris Wilson, Intel Open Source Technolog
On Thu, 15 Mar 2012 15:56:25 +0100, Carsten Emde wrote:
> Following the documentation of the Legacy Backlight Brightness (LBB)
> Register in the configuration space of some Intel PCI graphics adapters,
> setting the LBB register with the value 0x0 causes the backlight to be
> turned off, and 0xFF
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #26 from Tvrtko Ursulin 2012-03-15
08:03:32 PDT ---
(In reply to comment #22)
> (In reply to comment #20)
> > Right, thanks for your comments. In this case how about this approach:
> >
> > 1. Where there is shared DDC, one end being
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #25 from Alex Deucher 2012-03-15 08:02:57 PDT
---
(In reply to comment #23)
> > What system is this? Most new boards don't have shared ddc setups.
>
> FUJITSU D3003-S2
>
> > Does DDC
> > work on both the VGA and DVI ports?
>
> Ye
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #24 from Tvrtko Ursulin 2012-03-15
07:57:11 PDT ---
Created attachment 58515
--> https://bugs.freedesktop.org/attachment.cgi?id=58515
Video BIOS from the board with DP + DVI-I (shared DDC setup)
--
Configure bugmail: https://bugs
From: Yoichi Yuasa
It cannot map correctly if page fault begins from a intermediate address.
[The driver prefaults the mapping, so we need to work from the correct
base address not the faulting address otherwise the map appears offset by
the fault offset]
Signed-off-by: Yoichi Yuasa
Signed-o
From: Rob Clark
Minor cleanup.. use drm_core_check_feature() consistently in core.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_fops.c |6 +++---
drivers/gpu/drm/drm_gem.c |6 +++---
drivers/gpu/drm/drm_stub.c |4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
diff --g
https://bugzilla.kernel.org/show_bug.cgi?id=42920
--- Comment #7 from j.fikar at gmail.com 2012-03-15 14:26:25 ---
ok, so vramlimit works, but doesn't solve my problem.
I have tried 128MB UMA with vramlimit=64 and then 256MB UMA with vramlimit=64.
The memory gets smaller, but is wrongly loca
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #22 from Alex Deucher 2012-03-15 07:08:45 PDT
---
(In reply to comment #20)
> Right, thanks for your comments. In this case how about this approach:
>
> 1. Where there is shared DDC, one end being connected will imply the other is
>
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #21 from Alex Deucher 2012-03-15 06:59:49 PDT
---
(In reply to comment #15)
> Bad news from a different motherboard. This one has DVI-D and DP connectors.
> With a DVI monitor connected stalls are still there due to the shared_ddc
>
Hi Linus,
two minor updates from Jesse for Intel SNB fixes, and a few fixes from
Samsung for exynos. The pull req has Alan's commit in it since Intel based
their tree on my tree at that time, but it all seems fine wrt merging.
Dave.
The following changes since commit 762ad8a5330325b789cfb6dc8
ent;
> >> * @unmap_dma_buf: decreases usecount of buffer, might deallocate
> scatter
> >> *pages.
> >> * @release: release this buffer; to be called after the last
> dma_buf_put.
> >> + * @mmap: [optional, allowed to fail] operation called if userspace
> calls
> >> + * mmap() on the dmabuf fd. Note that userspace should
> use
> >> the
> >> + * DMA_BUF_PREPARE_ACCESS / DMA_BUF_FINISH_ACCESS ioctls
> >> before/after
> >> + * sw access to the buffer, to give the exporter an
> >> opportunity to
> >> + * deal with cache maintenance.
> >> + * @prepare_access: [optional] handler for PREPARE_ACCESS ioctl.
> >> + * @finish_access: [optional] handler for FINISH_ACCESS ioctl.
> >> */
> >> struct dma_buf_ops {
> >>int (*attach)(struct dma_buf *, struct device *,
> >> @@ -72,6 +90,10 @@ struct dma_buf_ops {
> >>/* after final dma_buf_put() */
> >>void (*release)(struct dma_buf *);
> >>
> >> + int (*mmap)(struct dma_buf *, struct file *, struct
> vm_area_struct
> >> *);
> >> + int (*prepare_access)(struct dma_buf *);
> >> + int (*finish_access)(struct dma_buf *);
> >> +
> >> };
> >>
> >> /**
> >> --
> >> 1.7.5.4
> >>
> >>
> >> ___
> >> Linaro-mm-sig mailing list
> >> Linaro-mm-sig at lists.linaro.org
> >> http://lists.linaro.org/mailman/listinfo/linaro-mm-sig
> >
> >
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/68fb87e9/attachment-0001.htm>
Hi
as a headsup, if you are basing a tree on mine, please use
drm-core-next not drm-next itself as a basis for your tree.
At the moment they've diverged as I've put the UDL kms driver into
drm-next but not drm-core-next as it needs an external fbdev patch to
work.
Dave.
ent;
> >> * @unmap_dma_buf: decreases usecount of buffer, might deallocate
> scatter
> >> *pages.
> >> * @release: release this buffer; to be called after the last
> dma_buf_put.
> >> + * @mmap: [optional, allowed to fail] operation called if userspace
> calls
> >> + * mmap() on the dmabuf fd. Note that userspace should
> use
> >> the
> >> + * DMA_BUF_PREPARE_ACCESS / DMA_BUF_FINISH_ACCESS ioctls
> >> before/after
> >> + * sw access to the buffer, to give the exporter an
> >> opportunity to
> >> + * deal with cache maintenance.
> >> + * @prepare_access: [optional] handler for PREPARE_ACCESS ioctl.
> >> + * @finish_access: [optional] handler for FINISH_ACCESS ioctl.
> >> */
> >> struct dma_buf_ops {
> >>int (*attach)(struct dma_buf *, struct device *,
> >> @@ -72,6 +90,10 @@ struct dma_buf_ops {
> >>/* after final dma_buf_put() */
> >>void (*release)(struct dma_buf *);
> >>
> >> + int (*mmap)(struct dma_buf *, struct file *, struct
> vm_area_struct
> >> *);
> >> + int (*prepare_access)(struct dma_buf *);
> >> + int (*finish_access)(struct dma_buf *);
> >> +
> >> };
> >>
> >> /**
> >> --
> >> 1.7.5.4
> >>
> >>
> >> ___
> >> Linaro-mm-sig mailing list
> >> Linaro-mm-sig at lists.linaro.org
> >> http://lists.linaro.org/mailman/listinfo/linaro-mm-sig
> >
> >
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/1abe7e3b/attachment.htm>
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #20 from Tvrtko Ursulin 2012-03-15
06:29:20 PDT ---
Right, thanks for your comments. In this case how about this approach:
1. Where there is shared DDC, one end being connected will imply the other is
disconnected.
This will ensure
Hi Dave.
Please pull from
git://git.infradead.org/users/kmpark/linux-samsung exynos-drm-fixes
this patch set is just miner fixes and had already been posted last week for
review
and another one included in this patch set also already been posted by Sascha
Hauer
last month. for this you
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #19 from Alex Deucher 2012-03-15 06:10:34 PDT
---
Only digital connectors (HDMI, DVI (digital portion only), DP) have HDP pins.
There is no hotplug spec for analog connectors. They almost always have to be
polled if you want connec
From: Rob Clark
Minor cleanup.. use drm_core_check_feature() consistently in core.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_fops.c |6 +++---
drivers/gpu/drm/drm_gem.c |6 +++---
drivers/gpu/drm/drm_stub.c |4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
diff --g
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-i915-backlight-brightness-inverted.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/3c97303f/attachment.asc>
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/64b381ac/attachment.txt>
Changes from V3 to V4:
Reverted the removal of the "brightness_inverted" parameter of the i915
module as suggested by Chris. Inversion of the sense of the brightness
variable is now enabled, if either the quirked notebook is encountered
or the "brightness_inverted" module parameter switch is set.
On Thu, 15 Mar 2012 12:19:49 +0100, Carsten Emde wrote:
> Following the documentation of the Legacy Backlight Brightness (LBB)
> Register in the configuration space of some Intel PCI graphics adapters,
> setting the LBB register with the value 0x0 causes the backlight to be
> turned off, and 0xFF
Bastien,
>> Broken monitors and/or broken graphic boards may send erroneous or no
>> EDID data. This also applies to broken KVM devices that are unable to
>> correctly forward the EDID data of the connected monitor but invent
>> their own fantasy data.
>>
>> This patch allows to specify an EDID da
On Thu, Mar 15, 2012 at 10:52 AM, Carsten Emde wrote:
> Broken monitors and/or broken graphic boards may send erroneous or no
> EDID data. This also applies to broken KVM devices that are unable to
> correctly forward the EDID data of the connected monitor but invent
> their own fantasy data.
>
>
- Original Message -
> From: "James Simmons"
> To: "Dave Airlie"
> Cc: "dri-devel"
> Sent: Thursday, 15 March, 2012 3:18:14 PM
> Subject: Re: drm-core-next vs drm-next
>
>
> > as a headsup, if you are basing a tree on mine, please use
> > drm-core-next not drm-next itself as a basis
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #18 from Simon Farnsworth
2012-03-15 04:20:56 PDT ---
I've spoken with Tvrtko - we think the patch is not quite right.
Specifically, it assumes that we will get appropriate HPD sense when a VGA
monitor is connected, but we've come u
On Thu, 15 Mar 2012, Paul Menzel wrote:
> Dear Carsten,
>
>
> Am Donnerstag, den 15.03.2012, 00:35 +0100 schrieb Carsten Emde:
> > Einfaches Textdokument-Anlage
> > (drivers-gpu-drm-allow-to-load-edid-firmware.patch)
>
> somehow your message was send as an attachment. Could you configure your
>
https://bugs.freedesktop.org/show_bug.cgi?id=32422
--- Comment #17 from Da Fox 2012-03-15 04:02:49
PDT ---
asasassadadasdasdasdasdasdadasdad
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for
> index 1ed3aae..aff2313 100644
> --- a/include/drm/exynos_drm.h
> +++ b/include/drm/exynos_drm.h
> @@ -147,11 +147,13 @@ struct exynos_drm_common_hdmi_pd {
> ?* @timing: default video mode for initializing
> ?* @default_win: default window layer number to be used for UI.
> ?* @bpp: default bit per
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #17 from Tvrtko Ursulin 2012-03-15
03:52:33 PDT ---
(In reply to comment #16)
> Furthermore, I've left in the bit which trusts HPD sense on R600+ ASICs,
> meaning as long as HPD sense remained unchanged, connector detect functions
>
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-i915-quirk-backlight-inverted.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/62716955/attachment.asc>
An embedded and charset-unspecified text was scrubbed...
Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/2921a7a1/attachment.txt>
Changes from V2 to V3:
1. The help text of the DRM_LOAD_EDID_FIRMWARE Kconfig item and the
related explanation in Documentation/kernel-parameters.txt now contain
a pointer to the documentation as suggested by Paul.
2. Removed the "brightness_inverted" parameter of the i915 module and
replaced it b
From: Ville Syrjälä
The error handling code w.r.t. idr usage looks inconsistent.
In the case of drm_mode_object_get() and drm_ctxbitmap_next() the error
handling is also incomplete.
Unify the code to follow the same pattern always.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/drm_context
>
> G2D is a 2D graphic accelerator that supports Bit Block Transfer. This
> G2D driver is exynos drm specific and supports only exynos4x12 series.
> user application fills command set in cmdlist and once dma start request
> these cmdlists are parsed and performed by dma.
Where is this block docum
ecially if there's room for improvement.
Tomi
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20120315/9aa3fa92/attachment.pgp>
> diff --git a/include/drm/exynos_drm.h b/include/drm/exynos_drm.h
> index 907daaf..1123342 100644
> --- a/include/drm/exynos_drm.h
> +++ b/include/drm/exynos_drm.h
> @@ -76,6 +76,22 @@ struct drm_exynos_gem_mmap {
> ? ? ? ?uint64_t mapped;
> ?};
>
> +/**
> + * A structure for user connection reque
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #32 from Alex Deucher 2012-03-15 10:41:15 PDT ---
(In reply to comment #31)
> It is a single DVI-I physically.
>
> But even identifying it would not change anything with regards to polling
> induced rendering stalls, right?
>
Well
> ?};
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> b/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> index de81883..2d9a0e6 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_crtc.c
> @@ -249,7 +249,11 @@ exynos_drm_crtc_mode_set(struct drm_cr
On Thu, Mar 15, 2012 at 09:57:53AM +, Dave Airlie wrote:
> > Use a do {} while() loop instead of a goto in drm_mode_object_get().
>
> I don't like this one just because it diverges our idr usage from the
> canonical idr usage at
>
> http://lwn.net/Articles/103209/
>
> So unless there is a go
On Thu, 15 Mar 2012 10:52:21 +0100, Carsten Emde wrote:
> Following the documentation of the Legacy Backlight Brightness (LBB)
> Register in the configuration space of some Intel PCI graphics adapters,
> setting the LBB register with the value 0x0 causes the backlight to be
> turned off, and 0xFF
> Use a do {} while() loop instead of a goto in drm_mode_object_get().
I don't like this one just because it diverges our idr usage from the
canonical idr usage at
http://lwn.net/Articles/103209/
So unless there is a good reason for the change I'd rather not apply it.
I've applied the other pat
https://bugs.freedesktop.org/show_bug.cgi?id=47007
Tvrtko Ursulin changed:
What|Removed |Added
Attachment #58360|0 |1
is obsolete|
Following the documentation of the Legacy Backlight Brightness (LBB)
Register in the configuration space of some Intel PCI graphics adapters,
setting the LBB register with the value 0x0 causes the backlight to be
turned off, and 0xFF causes the backlight to be set to 100% intensity
(http://download
A machine may need to invert the panel backlight brightness value. This
patch adds the infrastructure for a quirk to do so.
Signed-off-by: Carsten Emde
---
Documentation/kernel-parameters.txt | 17 +++--
drivers/gpu/drm/i915/i915_drv.h |1 +
drivers/gpu/drm/i915/intel_di
Mark the Acer Aspire 5734Z that this machines requires the module to
invert the panel backlight brightness value after reading from and prior
to writing to the PCI configuration space.
Signed-off-by: Carsten Emde
---
drivers/gpu/drm/i915/intel_display.c |6 +-
1 file changed, 5 insertio
Broken monitors and/or broken graphic boards may send erroneous or no
EDID data. This also applies to broken KVM devices that are unable to
correctly forward the EDID data of the connected monitor but invent
their own fantasy data.
This patch allows to specify an EDID data set to be used instead o
Changes from V4 to V5:
1. Split the previous patch 2/2 into three patches to separately i) add the
module parameter, ii) add the quirk infrastructure, and iii) actually quirk
the related machine.
2. Rename the module parameter variable to i915_panel_invert_brightness.
3. Make the module paramete
drm_fb_helper_modinit() calls find_module() which only
needs rcu_read_lock_sched().
The rest seems still have to hold module_mutex to prevent
module insertion/deletion. Instead of exporting module_mutex
for them, export two functions lock_modules()/unlock_modules()
and hide module_mutex.
Cc: Eric
On Thu, Mar 15, 2012 at 2:16 AM, Abhinav Kochhar
wrote:
> do we need to pass the dmabuf object to dmabuf->ops->mmap(dmabuf, file,
> vma)?
>
> as file->private_data can retrieve the dmabuf object.
>
> "dmabuf = file->private_data"
>
> removing dmabuf from the function arguments will keep it consist
Broken monitors and/or broken graphic boards may send erroneous or no
EDID data. This also applies to broken KVM devices that are unable to
correctly forward the EDID data of the connected monitor but invent
their own fantasy data.
This patch allows to specify an EDID data set to be used instead o
On Mit, 2012-03-14 at 15:13 -0400, Alex Deucher wrote:
> 2012/3/14 Michel D?nzer :
> > From: Michel D?nzer
> >
> > The hardware only takes 27 bits for the offset, so larger offsets are
> > truncated, and the display shows random bits other than the intended ones.
> >
> > Signed-off-by: Michel D?n
Following the documentation of the Legacy Backlight Brightness (LBB)
Register in the configuration space of some Intel PCI graphics adapters,
setting the LBB register with the value 0x0 causes the backlight to be
turned off, and 0xFF causes the backlight to be set to 100% intensity
(http://download
Changes from V3 to V4:
Reverted the removal of the "brightness_inverted" parameter of the i915
module as suggested by Chris. Inversion of the sense of the brightness
variable is now enabled, if either the quirked notebook is encountered
or the "brightness_inverted" module parameter switch is set.
Changes from V2 to V3:
1. The help text of the DRM_LOAD_EDID_FIRMWARE Kconfig item and the
related explanation in Documentation/kernel-parameters.txt now contain
a pointer to the documentation as suggested by Paul.
2. Removed the "brightness_inverted" parameter of the i915 module and
replaced it b
Bastien,
Broken monitors and/or broken graphic boards may send erroneous or no
EDID data. This also applies to broken KVM devices that are unable to
correctly forward the EDID data of the connected monitor but invent
their own fantasy data.
This patch allows to specify an EDID data set to be us
On Thu, 15 Mar 2012, Paul Menzel wrote:
> Dear Carsten,
>
>
> Am Donnerstag, den 15.03.2012, 00:35 +0100 schrieb Carsten Emde:
> > Einfaches Textdokument-Anlage
> > (drivers-gpu-drm-allow-to-load-edid-firmware.patch)
>
> somehow your message was send as an attachment. Could you configure your
>
On Thu, Mar 15, 2012 at 10:52 AM, Carsten Emde wrote:
> Broken monitors and/or broken graphic boards may send erroneous or no
> EDID data. This also applies to broken KVM devices that are unable to
> correctly forward the EDID data of the connected monitor but invent
> their own fantasy data.
>
>
Broken monitors and/or broken graphic boards may send erroneous or no
EDID data. This also applies to broken KVM devices that are unable to
correctly forward the EDID data of the connected monitor but invent
their own fantasy data.
This patch allows to specify an EDID data set to be used instead o
Following the documentation of the Legacy Backlight Brightness (LBB)
Register in the configuration space of some Intel PCI graphics adapters,
setting the LBB register with the value 0x0 causes the backlight to be
turned off, and 0xFF causes the backlight to be set to 100% intensity
(http://download
On Thu, Mar 15, 2012 at 03:32:40PM +0100, Jean Delvare wrote:
> Hi Ville,
>
> On Wed, 14 Mar 2012 10:32:52 +0200, Ville Syrjälä wrote:
> > When the system is under heavy load, there can be a significant delay
> > between the getscl() and time_after() calls inside sclhi(). That delay
> > may cause
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #31 from Tvrtko Ursulin 2012-03-15
09:13:58 PDT ---
(In reply to comment #30)
> > Hm, shared_ddc is also set with single physical DVI-I connector, at least on
> > this motherboard.
>
> According to your vbios tables there are actua
https://bugzilla.kernel.org/show_bug.cgi?id=42876
--- Comment #3 from legia 2012-03-15 09:11:59 ---
(In reply to comment #2)
> I have the same problem. No boot with 3.2.x kernel(Debian, Fedora).
>
> C2D
> Asus P5Q-E
> GeForce 550 Ti
No problem with parameter acpi=off noapic
--
Configure
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #30 from Alex Deucher 2012-03-15 08:45:10 PDT ---
(In reply to comment #29)
t sure what the right answer is.
>
> Is it possible to have DVI-D + VGA breakout cable from a single DVI-I which
> would give two independent simultaneous ou
https://bugs.freedesktop.org/show_bug.cgi?id=47363
Alex Deucher changed:
What|Removed |Added
Attachment #58516|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #29 from Tvrtko Ursulin 2012-03-15
08:34:48 PDT ---
(In reply to comment #28)
> (In reply to comment #26)
> > >
> > > I'm not sure we necessarily want to do that. Even though they may have a
> > > shared ddc line, it would be nice
1 - 100 of 164 matches
Mail list logo
