2017년 02월 03일 15:38에 Inki Dae 이(가) 쓴 글:
>
>
> 2017년 02월 01일 17:29에 Andrzej Hajda 이(가) 쓴 글:
>> On TM2/TM2e platforms HDMI output is connected to MHL bridge
>> SiI8620. To allow configure UltraHD modes on the bridge
>> and to eliminate unsupported modes this bridge should be
>> attached to
2017년 02월 01일 17:29에 Andrzej Hajda 이(가) 쓴 글:
> On TM2/TM2e platforms HDMI output is connected to MHL bridge
> SiI8620. To allow configure UltraHD modes on the bridge
> and to eliminate unsupported modes this bridge should be
> attached to drm_encoder implemented in exynos_hdmi.
>
>
2017년 02월 02일 04:03에 Sean Paul 이(가) 쓴 글:
> On Wed, Feb 01, 2017 at 03:29:40PM +, Emil Velikov wrote:
>> On 1 February 2017 at 14:52, Thierry Reding wrote:
>>> On Tue, Jan 31, 2017 at 02:54:53PM -0800, Eric Anholt wrote:
Thierry Reding
2017년 02월 02일 00:29에 Emil Velikov 이(가) 쓴 글:
> On 1 February 2017 at 14:52, Thierry Reding wrote:
>> On Tue, Jan 31, 2017 at 02:54:53PM -0800, Eric Anholt wrote:
>>> Thierry Reding writes:
>>>
[ Unknown signature status ]
On Tue, Jan
Regards
Shashank
On 2/2/2017 11:43 PM, Thierry Reding wrote:
On Thu, Feb 02, 2017 at 11:08:22AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 2/1/2017 10:02 PM, Thierry Reding wrote:
On Wed, Feb 01, 2017 at 06:14:39PM +0530, Shashank Sharma wrote:
HDMI 2.0 spec mandates scrambling
https://bugs.freedesktop.org/show_bug.cgi?id=99488
--- Comment #3 from Jan Vesely ---
(In reply to nixscripter from comment #1)
> I'm still trying some versions in order to help you guys pin this down (it's
> not always easy to tell what reinstall is having what
https://bugs.freedesktop.org/show_bug.cgi?id=99488
nixscrip...@gmail.com changed:
What|Removed |Added
Summary|[r600g]OpenCL driver causes |[r600g]OpenCL driver causes
https://bugs.freedesktop.org/show_bug.cgi?id=99488
--- Comment #2 from nixscrip...@gmail.com ---
Correction on the steps to reproduce:
1. Get the current tree of ImageMagick from GitHub:
https://github.com/ImageMagick/ImageMagick
2. Compile it with OpenCL and HDRI support (--enable-opencl
https://bugs.freedesktop.org/show_bug.cgi?id=99488
--- Comment #1 from nixscrip...@gmail.com ---
I'm still trying some versions in order to help you guys pin this down (it's
not always easy to tell what reinstall is having what effect, since Arch Linux
has three packages involved). In the mean
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-4.9
head: 99eb22d3eab149aa18e770da839165e07467db25
commit: 7adb2bbcdf7259533c5afc95c4a788b59bb59306 [5/14] drm/amd/display: DMCU
Compile and Load
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3)
https://bugs.freedesktop.org/show_bug.cgi?id=93341
Michel Dänzer changed:
What|Removed |Added
Attachment #129306|text/x-log |text/plain
https://bugzilla.kernel.org/show_bug.cgi?id=192271
Richard Herbert changed:
What|Removed |Added
CC|
On Fri, Feb 03, 2017 at 01:30:14AM +0200, Martin Peres wrote:
> On 01/02/17 22:05, Manasi Navare wrote:
> >On Wed, Feb 01, 2017 at 11:58:16AM -0800, Eric Anholt wrote:
> >>Jani Nikula writes:
> >>
> >>>On Tue, 31 Jan 2017, Eric Anholt wrote:
>
2017-02-02 19:26 GMT-02:00 Fabio Estevam :
>
> From: Fabio Estevam
>
> Currently the framebuffer content is displayed with incorrect offsets
> in both the vertical and horizontal directions.
>
> The fbdev version of the driver does not show this problem.
On 02/01/2017 05:51 PM, Peter Senna Tschudin wrote:
On 01 February, 2017 12:35 CET, Daniel Vetter wrote:
On Wed, Feb 01, 2017 at 10:58:43AM +, Peter Senna Tschudin wrote:
Hi Archit,
On 01 February, 2017 10:44 CET, Archit Taneja wrote:
On
Add support for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480)
TFT with Touch-Panel, which can be supported by the simple panel driver.
Data-sheet available at:
http://www.glyn.de/data/glyn/media/doc/43wvf1g-0.pdf
Signed-off-by: Breno Lima
---
On 02/02/2017 01:32 AM, Jani Nikula wrote:
> On Thu, 02 Feb 2017, Shuah Khan wrote:
>> Change drm_helper_probe_single_connector_modes() to print an error to
>> report connector disconnected status instead of a debug message.
>>
>> When this condition occurs, application
On 02 February, 2017 02:46 CET, Emil Velikov wrote:
> On 1 February 2017 at 11:35, Daniel Vetter wrote:
> > On Wed, Feb 01, 2017 at 10:58:43AM +, Peter Senna Tschudin wrote:
> >> Hi Archit,
> >>
> >> On 01 February, 2017 10:44 CET, Archit
On 1 February 2017 at 11:35, Daniel Vetter wrote:
> On Wed, Feb 01, 2017 at 10:58:43AM +, Peter Senna Tschudin wrote:
>> Hi Archit,
>>
>> On 01 February, 2017 10:44 CET, Archit Taneja wrote:
>>
>> >
>> >
>> > On 01/30/2017 10:35 PM, Jani Nikula wrote:
Change drm_helper_probe_single_connector_modes() to print an error to
report connector disconnected status instead of a debug message.
When this condition occurs, application doesn't know the real error and
reports it as driver lacking support for mode setting. Change it to an
error to make it
On 2 February 2017 at 11:53, Peter Senna Tschudin
wrote:
>
> On 02 February, 2017 02:46 CET, Emil Velikov wrote:
>
>> On 1 February 2017 at 11:35, Daniel Vetter wrote:
>> > On Wed, Feb 01, 2017 at 10:58:43AM +, Peter
Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for
disposable private objects") introduced a regression for the kernel
running as Xen dom0: when switching to graphics mode a GPU HANG
occurred.
Reason seems to be a missing adaption similar to that done in
commit 7453c549f5f648
The Sharp lq123p1jx31 has a requirement that the VDD is on for at
least 300 ms before being turned off. At the moment nothing anywhere
in the kernel is ensuring this.
The simplest way to ensure this is to add a "disable" timing of 150
ms. With this the we know that there will be at least 300 ms
On 01/02/17 22:05, Manasi Navare wrote:
On Wed, Feb 01, 2017 at 11:58:16AM -0800, Eric Anholt wrote:
Jani Nikula writes:
On Tue, 31 Jan 2017, Eric Anholt wrote:
Martin Peres writes:
Despite all the careful
Hi Linus,
Another fixes pull for v4.10, it's a bit big due to the backport of the
VMA fixes for i915 that should fix the oops on shutdown problems that you've
worked around.
There are also two drm core connector registration fixes, a bunch of nouveau
regression fixes and two AMD fixes.
Dave.
Introduced in 028715ee
Move the dereference after the null check.
---
intel/intel_decode.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/intel/intel_decode.c b/intel/intel_decode.c
index 803d202..2721ffd 100644
--- a/intel/intel_decode.c
+++ b/intel/intel_decode.c
@@
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #13 from Steven A. Falco ---
I successfully built a custom kernel. It appears to be working well. Thanks
for the help!
I included a new dmesg.log file because I still see messages like:
[9.719278]
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #14 from Steven A. Falco ---
One other error message I just noticed:
[5.538117] amdgpu: [powerplay] Can't find requested voltage id in
vdd_dep_on_sclk table!
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #12 from Steven A. Falco ---
Created attachment 253891
--> https://bugzilla.kernel.org/attachment.cgi?id=253891=edit
New dmesg file
--
You are receiving this mail because:
You are watching the assignee of
v2:
Modify for movig pflip flags to crtc_state
v4:
Fix identation.
v5:
Rename field to pageflip_flags.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h | 1 -
.../drm/amd/display/amdgpu_dm/amdgpu_dm_types.c| 113
This series is a folow-up on
https://patchwork.kernel.org/patch/9501787/
The first patch makes changes to atomic helpers to allow for drives with ASYNC
flip support to use them.
Patch 2 is to use this in AMDGPU/DC.
Patch 3 is possible cleanup in nouveau/kms who seems to have to duplicate the
v2:
Update code after flip_flags moved from plane_state
to crtc_state
v5:
Rename to pageflip_flags.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/nouveau/nv50_display.c | 84 --
1 file changed, 10 insertions(+), 74 deletions(-)
Allows using atomic flip helpers for drivers
using ASYNC flip.
Remove ASYNC_FLIP restriction in helpers and
caches the page flip flags in drm_crtc_state
to be used in the low level drivers.
v2:
Resending the patch since the original was broken.
v3:
Save flag in crtc_state instead of plane_state
From: Fabio Estevam
Currently the framebuffer content is displayed with incorrect offsets
in both the vertical and horizontal directions.
The fbdev version of the driver does not show this problem. Breno Lima
dumped the eLCDIF controller registers on both the drm and
Hi Thierry,
On Thu, Feb 2, 2017 at 6:18 PM, Thierry Reding wrote:
> Shawn, Fabio, anyone want to give this a Tested-by? I take it that this,
> in combination with Fabio's patch to fix the displacement would make the
> SabreSD display work properly?
Yes, that is
The drm_mm range manager claimed to support top-down insertion, but it
was neither searching for the top-most hole that could fit the
allocation request nor fitting the request to the hole correctly.
In order to search the range efficiently, we create a secondary index
for the holes using either
On Thu, Jan 26, 2017 at 05:03:54PM -0500, Rob Clark wrote:
> On Thu, Jan 26, 2017 at 4:09 PM, Rob Herring wrote:
> > On Thu, Jan 26, 2017 at 1:51 PM, Rob Clark wrote:
> >> On Thu, Jan 26, 2017 at 2:11 PM, Rob Herring wrote:
> >>> On Tue,
On Thu, Feb 2, 2017 at 8:46 PM, Volker Vogelhuber
wrote:
> On Thu, Feb 02, 2017 at 05:19:58PM +0100, Volker Vogelhuber wrote:
>>> I'm currently trying to mmap the memory of an OpenGL texture I've created by
>>> doing the following:
>>>
>>> std::vector
tree: git://anongit.freedesktop.org/drm-intel drm-intel-nightly
head: 0f01216949002d20b9dc6d300c82df5ffa59e9a7
commit: e4563f6ba71792c77aeccb2092cc23149b44e642 [1076/1086] drm: Rely on
mode_config data for fb_helper initialization
config: i386-randconfig-x0-02030244 (attached as .config)
On Thu, Feb 02, 2017 at 06:04:00PM -0200, Breno Lima wrote:
> Add support for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480)
> TFT with Touch-Panel, which can be supported by the simple panel driver.
>
> Data-sheet available at:
> http://www.glyn.de/data/glyn/media/doc/43wvf1g-0.pdf
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #23 from Jean-François Fortin Tam ---
Created attachment 129306
--> https://bugs.freedesktop.org/attachment.cgi?id=129306=edit
Xorg log
Xorg.0.log file found in ~/.local/share/xorg as "Xorg.0.log.old"
As you
https://bugs.freedesktop.org/show_bug.cgi?id=93341
Jean-François Fortin Tam changed:
What|Removed |Added
Attachment #128278|0 |1
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #21 from Jean-François Fortin Tam ---
Created attachment 129304
--> https://bugs.freedesktop.org/attachment.cgi?id=129304=edit
journalctl output at the time of a deadlock on F25 - X GDM session output only
Hi
I'm going to need to cool down for a bit. Let's resume this on Monday,
maybe we can get back to being constructive after the weekend.
Thierry
signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
On Thu, Feb 02, 2017 at 05:19:58PM +0100, Volker Vogelhuber wrote:
>> I'm currently trying to mmap the memory of an OpenGL texture I've created by
>> doing the following:
>>
>> std::vector image_attribs = {
>> EGL_WIDTH, static_cast(m_texWidth & 0x7FFF),
>>
On Thu, Feb 02, 2017 at 05:39:00PM -0200, Gabriel Krisman Bertazi wrote:
> Commit be7f735cd5ea ("drm: Rely on mode_config data for fb_helper
> initialization") broke the build when CONFIG_DRM_FBDEV_EMULATION is
> disabled because it didn't update the prototype for drm_fb_helper_init
> in that
Commit be7f735cd5ea ("drm: Rely on mode_config data for fb_helper
initialization") broke the build when CONFIG_DRM_FBDEV_EMULATION is
disabled because it didn't update the prototype for drm_fb_helper_init
in that case.
Fixes: be7f735cd5ea ("drm: Rely on mode_config data for fb_helper
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: 36aab92fa2091dd54ea983752aa40e427e83d113
commit: e4563f6ba71792c77aeccb2092cc23149b44e642 [1066/1073] drm: Rely on
mode_config data for fb_helper initialization
config: i386-randconfig-x007-201705 (attached as .config)
compiler:
vmwgfx part: Reviewed-by: Sinclair Yeh
On Thu, Feb 02, 2017 at 11:44:33AM +, Chris Wilson wrote:
> The drm_mm range manager claimed to support top-down insertion, but it
> was neither searching for the top-most hole that could fit the
> allocation request nor fitting the
On Thu, Feb 02, 2017 at 11:08:22AM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 2/1/2017 10:02 PM, Thierry Reding wrote:
> > On Wed, Feb 01, 2017 at 06:14:39PM +0530, Shashank Sharma wrote:
> > > HDMI 2.0 spec mandates scrambling for modes with pixel clock higher
> > > than
On Wed, Feb 1, 2017 at 2:04 PM, Breno Matheus Lima
wrote:
> - The image is displaced even when using the same timing values in
> the datasheet.
Managed to fix this framebuffer displacement problem. Will submit a patch soon.
___
On Thu, Feb 02, 2017 at 02:26:40PM -0200, Gabriel Krisman Bertazi wrote:
> Instead of receiving the num_crts as a parameter, we can read it
> directly from the mode_config structure. I audited the drivers that
> invoke this helper and I believe all of them initialize the mode_config
> struct
On Thu, Feb 02, 2017 at 10:58:43AM +0530, Sharma, Shashank wrote:
> Thanks for the review Thierry. My comments inline.
>
> Regards
> Shashank
> On 2/1/2017 9:40 PM, Thierry Reding wrote:
> > On Wed, Feb 01, 2017 at 06:14:38PM +0530, Shashank Sharma wrote:
> > > This patch does following:
> > > -
On Tue, Jan 31, 2017 at 01:05:20PM +0100, Andrzej Hajda wrote:
> On 31.01.2017 09:54, Thierry Reding wrote:
> > On Tue, Jan 31, 2017 at 09:01:07AM +0900, Inki Dae wrote:
> >>
> >> 2017년 01월 24일 10:50에 Hoegeun Kwon 이(가) 쓴 글:
> >>> Dear Thierry,
> >>>
> >>> Could you please review this patch?
> >>
Daniel Vetter writes:
> On Wed, Feb 01, 2017 at 11:58:16AM -0800, Eric Anholt wrote:
>> Jani Nikula writes:
>>
>> > On Tue, 31 Jan 2017, Eric Anholt wrote:
>> >> Martin Peres writes:
>> >>
>> >>>
Hi Dave,
Just a couple of small fixes for 4.10
The following changes since commit 52b679f60e2a68af88411f12318675a2424a0e14:
Merge tag 'drm-misc-fixes-2017-01-31' of
git://anongit.freedesktop.org/git/drm-misc into drm-fixes (2017-02-01 08:45:27
+1000)
are available in the git repository at:
On Wed, Feb 1, 2017 at 12:03 PM, Andrey Grodzovsky
wrote:
> This series is a folow-up on
> https://patchwork.kernel.org/patch/9501787/
>
> The first patch makes changes to atomic helpers to allow for drives with
> ASYNC flip support to use them.
> Patch 2 is to use
On Wed, Feb 1, 2017 at 12:03 PM, Andrey Grodzovsky
wrote:
> Allows using atomic flip helpers for drivers
> using ASYNC flip.
> Remove ASYNC_FLIP restriction in helpers and
> caches the page flip flags in drm_crtc_state
> to be used in the low level drivers.
>
> v2:
>
On Thu, Feb 02, 2017 at 05:30:34PM +0200, Jani Nikula wrote:
> On Tue, 31 Jan 2017, Thierry Reding wrote:
> > On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
> >> I would love for drm-panel to be moved under -misc.
> >
> > Like that's going to magically
On Thu, Feb 02, 2017 at 05:19:58PM +0100, Volker Vogelhuber wrote:
> Hi,
>
> I'm currently trying to mmap the memory of an OpenGL texture I've created by
> doing the following:
>
> std::vector image_attribs = {
> EGL_WIDTH, static_cast(m_texWidth & 0x7FFF),
>
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #20 from Alex Deucher ---
(In reply to Jean-François Fortin Tam from comment #19)
> What would be the equivalent in the systemd/journalctl world? Apparently
> Fedora 25 doesn't generate Xorg.log files anymore,
Hi,
I'm currently trying to mmap the memory of an OpenGL texture I've
created by
doing the following:
std::vector image_attribs = {
EGL_WIDTH, static_cast(m_texWidth & 0x7FFF),
EGL_HEIGHT, static_cast(m_texHeight & 0x7FFF),
Instead of receiving the num_crts as a parameter, we can read it
directly from the mode_config structure. I audited the drivers that
invoke this helper and I believe all of them initialize the mode_config
struct accordingly, prior to calling the fb_helper.
I used the following coccinelle hack to
On Wed, Jan 04, 2017 at 08:42:30PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> DRM_UT_CORE generates way too much noise usually, so having the
> framebuffer init failures use DRM_UT_CORE is a pain when trying to
> find out the reason why
On Wed, Jan 04, 2017 at 08:42:29PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> intel_fill_fb_info() should pass the correct plane index to
> _intel_compute_tile_offset() once we start to care about the AUX
> surface.
>
> Signed-off-by:
https://bugs.freedesktop.org/show_bug.cgi?id=99549
--- Comment #3 from Marek Olšák ---
That's up to you. I'm not so into fixing the postprocessing, because the
options shouldn't be put into drirc, because the filters change what the OpenGL
spec specifies.
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #11 from Alex Deucher ---
(In reply to fin4478 from comment #8)
> Alex, thanks for the new firmware. Still Bios recognition errors at boot,
> but otherwise ok.
>
> [3.461112] [drm] BIOS signature incorrect
Gabriel Krisman Bertazi writes:
> Scheduling the output_poll_work before calling bind_all to create the
> crtcs can race the fbdev initialization with the components
> initialization (i.e. crtc initialization). One side effect is that we
> may call drm_fbdev_cma_init
Hi Dave, here's Maarten's backport of the vma fixes for v4.10.
BR,
Jani.
The following changes since commit 566cf877a1fcb6d6dc0126b076aad062054c2637:
Linux 4.10-rc6 (2017-01-29 14:25:17 -0800)
are available in the git repository at:
git://anongit.freedesktop.org/git/drm-intel
On Tue, 31 Jan 2017, Thierry Reding wrote:
> On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
>> I would love for drm-panel to be moved under -misc.
>
> Like that's going to magically motivate people to spend their time
> reviewing other patches. The only
https://bugs.freedesktop.org/show_bug.cgi?id=99549
--- Comment #2 from LoneVVolf ---
After seeing marek reply I experimented a bit with PP_DEBUG and post processing
filters.
Half of the error messages comes from pp_jimenezmlaa filter , the other half
from pp_jimenezmlaa_color
On Thu, Feb 02, 2017 at 02:33:54PM +0100, Lucas Stach wrote:
> Am Donnerstag, den 02.02.2017, 11:44 + schrieb Chris Wilson:
> > @@ -192,6 +188,8 @@ static int etnaviv_iommu_find_iova(struct etnaviv_iommu
> > *mmu,
> > list_del_init(>scan_node);
> > }
> >
> >
On Wed, Jan 04, 2017 at 08:42:28PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> Based on empirical evidence the display engine (at least) always
> treats Yf tiles as 128Bx32. Currently we're assuming the tile dimensions
> change based on
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #10 from Steven A. Falco ---
Thanks for the information on building a new kernel. I'll give that a try.
I'm running Fedora 25, but I think I can follow your Debian instructions.
--
You are receiving this
On Thu, Feb 2, 2017 at 6:44 AM, Chris Wilson wrote:
> The drm_mm range manager claimed to support top-down insertion, but it
> was neither searching for the top-most hole that could fit the
> allocation request nor fitting the request to the hole correctly.
>
> In order
On Tue, Jan 31, 2017 at 10:51:06PM +0100, Thierry Reding wrote:
> On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
> [...]
> > As is, I'm stuck out here with my panel driver I submitted on December
> > 14th completely ignored, and no other developer will look at it because
> > their
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #19 from Jean-François Fortin Tam ---
What would be the equivalent in the systemd/journalctl world? Apparently Fedora
25 doesn't generate Xorg.log files anymore, the last modification timestamp on
that one file is
On Wed, Jan 04, 2017 at 08:42:27PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> To make life easier let's allow skl_plane_stride() to be called for the
> AUX surface even when there is no AUX surface. Avoids special cases in
> the callers.
On Wed, Jan 04, 2017 at 08:42:26PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> Let's try to keep the alignment requirements in one place, and so
> towards that end let's move the AUX_DIST alignment handling into
> intel_surf_alignment()
Am Donnerstag, den 02.02.2017, 11:44 + schrieb Chris Wilson:
> The drm_mm range manager claimed to support top-down insertion, but it
> was neither searching for the top-most hole that could fit the
> allocation request nor fitting the request to the hole correctly.
>
> In order to search the
On Wed, Jan 04, 2017 at 08:42:25PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> Now that framebuffers can be used even before calling
> drm_framebuffer_init() we can start to plumb them into more places,
> instead of passing individual
https://bugs.freedesktop.org/show_bug.cgi?id=97861
--- Comment #4 from Elia Argentieri ---
Same problem on R7 370 except that my monitor shows a black screen and reports
"frequency not supported".
--
You are receiving this mail because:
You are the assignee for
Dear Thierry,
2017년 02월 01일 23:44에 Thierry Reding 이(가) 쓴 글:
> On Wed, Feb 01, 2017 at 08:48:30AM +0900, Inki Dae wrote:
>>
>>
>> 2017년 02월 01일 06:31에 Thierry Reding 이(가) 쓴 글:
>>> On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
Thierry Reding writes:
On Thu, Feb 02, 2017 at 04:15:21PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 2/2/2017 3:32 PM, Ville Syrjälä wrote:
> > On Thu, Feb 02, 2017 at 11:23:19AM +0530, Sharma, Shashank wrote:
> >> Regards
> >>
> >> Shashank
> >>
> >>
> >> On 2/1/2017 10:06 PM, Ville Syrjälä
On Thu, Feb 02, 2017 at 12:11:29PM +, Tvrtko Ursulin wrote:
>
> On 02/02/2017 09:47, Juergen Gross wrote:
> >Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for
> >disposable private objects") introduced a regression for the kernel
> >running as Xen dom0: when switching to
On 02/02/2017 09:47, Juergen Gross wrote:
Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for
disposable private objects") introduced a regression for the kernel
running as Xen dom0: when switching to graphics mode a GPU HANG
occurred.
Reason seems to be a missing adaption
On Thu, Feb 02, 2017 at 11:50:59AM +0100, Neil Armstrong wrote:
> On 02/02/2017 11:45 AM, Daniel Vetter wrote:
> > On Thu, Feb 02, 2017 at 10:47:44AM +0100, Neil Armstrong wrote:
> >> The platform driver name is currently "meson" which can lead to some
> >> confusion, this patch renames it to
Sure, Thanks for the information, will add that in V2.
Regards
Shashank
-Original Message-
From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
Sent: Thursday, February 2, 2017 4:55 PM
To: Sharma, Shashank ;
dri-devel@lists.freedesktop.org;
Check that if we request bottom-up allocation from drm_mm_insert_node()
we receive the next available hole from the bottom.
Signed-off-by: Chris Wilson
Reviewed-by: Joonas Lahtinen
---
drivers/gpu/drm/selftests/drm_mm_selftests.h | 1
The drm_mm range manager claimed to support top-down insertion, but it
was neither searching for the top-most hole that could fit the
allocation request nor fitting the request to the hole correctly.
In order to search the range efficiently, we create a secondary index
for the holes using either
On Wed, 01 Feb 2017, Shashank Sharma wrote:
> From: Thierry Reding
>
> SCDC is a mechanism defined in the HDMI 2.0 specification that allows
> the source and sink devices to communicate.
>
> This commit introduces helpers to access the SCDC and
On Thu, Feb 02, 2017 at 11:48:21AM +0100, Daniel Vetter wrote:
> On Thu, Feb 02, 2017 at 10:47:11AM +0100, Juergen Gross wrote:
> > Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for
> > disposable private objects") introduced a regression for the kernel
> > running as Xen dom0:
On 02/02/2017 11:45 AM, Daniel Vetter wrote:
> On Thu, Feb 02, 2017 at 10:47:44AM +0100, Neil Armstrong wrote:
>> The platform driver name is currently "meson" which can lead to some
>> confusion, this patch renames it to "meson-drm" and removes the owner
>> attribute.
>>
>> Signed-off-by: Neil
On Thu, Feb 02, 2017 at 10:47:11AM +0100, Juergen Gross wrote:
> Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for
> disposable private objects") introduced a regression for the kernel
> running as Xen dom0: when switching to graphics mode a GPU HANG
> occurred.
>
> Reason
Regards
Shashank
On 2/2/2017 3:32 PM, Ville Syrjälä wrote:
On Thu, Feb 02, 2017 at 11:23:19AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 2/1/2017 10:06 PM, Ville Syrjälä wrote:
On Wed, Feb 01, 2017 at 06:14:40PM +0530, Shashank Sharma wrote:
Geminilake platform has a native HDMI
On Thu, Feb 02, 2017 at 10:47:44AM +0100, Neil Armstrong wrote:
> The platform driver name is currently "meson" which can lead to some
> confusion, this patch renames it to "meson-drm" and removes the owner
> attribute.
>
> Signed-off-by: Neil Armstrong
> ---
>
Regards
Shashank
On 2/2/2017 3:58 PM, Ville Syrjälä wrote:
On Thu, Feb 02, 2017 at 03:46:55PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 2/2/2017 3:21 PM, Ville Syrjälä wrote:
On Thu, Feb 02, 2017 at 11:18:51AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 2/1/2017 10:02
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #9 from fin4...@hotmail.com ---
After updating the firmware I still have powerplay erros:
[3.574222] amdgpu: [powerplay] [AVFS] Something is broken. See log!
[3.577052] amdgpu: [powerplay] Can't find requested voltage id in
Hi,
This is a respin of the previous serie called "Support fast framebuffer
panning for i.MX6" made by Stefan 6 monthes ago. The imx6 bits have been
removed, and the comments that were made at that time fixed (hopefully).
Let me know what you think,
Maxime
Changes from v1:
- Added
From: Xinliang Liu
This patch add a config to support to create multi buffer for cma fbdev.
Such as double buffer and triple buffer.
Cma fbdev is convient to add a legency fbdev. And still many Android
devices use fbdev now and at least double buffer is needed for these
1 - 100 of 123 matches
Mail list logo