Hi Jyri,
Thank you for the patch.
On Monday 10 Apr 2017 14:16:54 Jyri Sarha wrote:
> If the LCDC is already enabled (e.g. by the bootloader) at the
> initialization phase, disable it before returning from the probe.
>
> Signed-off-by: Jyri Sarha
> Reported-by: Emiliano Ingrassia
> ---
> This p
Hi,
On 11 April 2017 at 07:48, Daniel Vetter wrote:
> Note: As Daniel Stone mentioned in the announcement fd.o admins
> started chatting with the communities their hosting, which includs the
> X.org foundation board, to figure out how to fan out enforcement and
> allow projects to run things on t
https://bugzilla.kernel.org/show_bug.cgi?id=195321
Bug ID: 195321
Summary: nouveau?/DRI3?: dual monitors unusable without running
compton --paint-on-overlay
Product: Drivers
Version: 2.5
Kernel Version: 4.10.8
Hardware:
Hi Nikhil,
On Tue, Apr 11, 2017 at 09:44:35AM +0530, Nikhil Mahale wrote:
> There is not interest in relaxing the export of refcount_inc, and
> changing the license of nvidia-drm.ko isn't viable right now.
Why not dual-license as MIT+GPL?
> * Make these static inline DRM functions EXPORT_SYMBO
On Mon, 10 Apr 2017 12:10:14 -0400
Ilia Mirkin wrote:
> On Mon, Apr 10, 2017 at 11:09 AM, Pekka Paalanen wrote:
> > I also wonder if a real BE machine could have different results than
> > the virtual machine.
>
> I have a PPC G5 with an AGP GeForce FX 5200 that I can test things on,
> if ne
On 11 April 2017 at 12:38, Daniel Stone wrote:
> Hi,
>
> On 11 April 2017 at 07:48, Daniel Vetter wrote:
>> Note: As Daniel Stone mentioned in the announcement fd.o admins
>> started chatting with the communities their hosting, which includs the
>> X.org foundation board, to figure out how to fan
On 04/11/17 10:01, Laurent Pinchart wrote:
> Hi Jyri,
>
> Thank you for the patch.
>
> On Monday 10 Apr 2017 14:16:54 Jyri Sarha wrote:
>> If the LCDC is already enabled (e.g. by the bootloader) at the
>> initialization phase, disable it before returning from the probe.
>>
>> Signed-off-by: Jyri
Inki Dae wrote:
>
>
> 2017년 04월 10일 19:29에 Tobias Jakobi 이(가) 쓴 글:
>> Inki Dae wrote:
>>> 2017-04-07 20:40 GMT+09:00 Tobias Jakobi :
Hello Inki,
Inki Dae wrote:
> Hello Tobias,
>
>
> 2017년 04월 07일 02:10에 Tobias Jakobi 이(가) 쓴 글:
>> Hello Inki,
>>
>>
On Tue, Apr 11, 2017 at 01:22:17PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> This object can be used to implement the Vulkan semaphores.
>
> The object behaviour differs from fence, in that you can
> replace the underlying fence, and you cannot merge semaphores.
>
> Signed-off-by: Dave
On 04/11/2017 01:03 PM, Sumit Semwal wrote:
On 11 April 2017 at 12:38, Daniel Stone wrote:
Hi,
On 11 April 2017 at 07:48, Daniel Vetter wrote:
Note: As Daniel Stone mentioned in the announcement fd.o admins
started chatting with the communities their hosting, which includs the
X.org founda
Inki Dae wrote:
>
>
> 2017년 04월 10일 19:27에 Tobias Jakobi 이(가) 쓴 글:
>> Inki Dae wrote:
>>> 2017-03-29 20:56 GMT+09:00 Tobias Jakobi :
Hello Daniel,
same question here. Patch doesn't introduce any functional changes (just
adds code documentation), so can you merge it through drm
https://bugzilla.kernel.org/show_bug.cgi?id=195321
--- Comment #1 from Jimi (jimijames.b...@gmail.com) ---
OK, this is getting really weird. Despite working over quite a few monitor
disconnections for the past few hours, the --paint-on-overlay option is
suddenly no longer fixing it. I *have* to tu
https://bugzilla.kernel.org/show_bug.cgi?id=195321
--- Comment #2 from Jimi (jimijames.b...@gmail.com) ---
I've just confirmed that switching to DRI2 doesn't fix it, either.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Another thing that I noticed. Why wasn't the v2 that ended up in your
git ever submitted to the mailing list? Because it should have, in
particular to spot these obvious errors.
- Tobias
Tobias Jakobi wrote:
> Inki Dae wrote:
>>
>>
>> 2017년 04월 10일 19:29에 Tobias Jakobi 이(가) 쓴 글:
>>> Inki Dae wro
On 11/04/17 10:51, Archit Taneja wrote:
On 04/11/2017 01:03 PM, Sumit Semwal wrote:
On 11 April 2017 at 12:38, Daniel Stone wrote:
Hi,
On 11 April 2017 at 07:48, Daniel Vetter wrote:
Note: As Daniel Stone mentioned in the announcement fd.o admins
started chatting with the communities thei
https://bugs.freedesktop.org/show_bug.cgi?id=100591
Michel Dänzer changed:
What|Removed |Added
Attachment #130710|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=100591
Michel Dänzer changed:
What|Removed |Added
Attachment #130711|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=100591
--- Comment #5 from Michel Dänzer ---
Did this not happen with an older version of the kernel or other software
components?
--
You are receiving this mail because:
You are the assignee for the bug.__
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think th
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think th
On Tue, Apr 11, 2017 at 3:18 AM, Eric Anholt wrote:
> From: Tom Cooksey
Well that can be debated at this point. I think it should have
your Author: tag and just Tom in the Signed-off-by, then mention
the history in the commit message.
> This is a modesetting driver for the pl111 CLCD display c
Sorry for the delayed response, have been busy with other stuff recently.
Am 13.03.2017 um 17:43 schrieb Andy Shevchenko:
v2: rebase on changes in rbar support
This kind of comments usually goes after --- delimiter below.
That would remove it from the commit message which I don't want.
+
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think th
Am 13.03.2017 um 17:49 schrieb Andy Shevchenko:
On Mon, Mar 13, 2017 at 2:41 PM, Christian König
wrote:
Most BIOS don't enable this because of compatibility reasons.
Manually enable a 64bit BAR of 64GB size so that we have
enough room for PCI devices.
+static void pci_amd_enable_64bit_bar(str
On Tue, 11 Apr 2017, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anything
On Tue, Apr 11, 2017 at 11:17 AM, Linus Walleij
wrote:
>> +++ b/drivers/gpu/drm/pl111/Kconfig
>> @@ -0,0 +1,12 @@
>> +config DRM_PL111
>> + tristate "DRM Support for PL111 CLCD Controller"
>> + depends on DRM
>> + depends on ARM || ARM64 || COMPILE_TEST
>> + select DRM_KMS_
On Mon, Apr 10, 2017 at 06:44:14PM -0700, Eric Anholt wrote:
> This is needed for proper synchronization with display on another DRM
> device (pl111 or tinydrm) with buffers produced by vc4 V3D. Fixes the
> new igt vc4_dmabuf_poll testcase, and rendering of one of the glmark2
> desktop tests on pl
On 04/11/2017 08:48 AM, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anyth
On 04/11/2017 11:03 AM, Daniel Vetter wrote:
> On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
>> freedesktop.org has adopted a formal&enforced code of conduct:
>>
>> https://www.fooishbar.org/blog/fdo-contributor-covenant/
>> https://www.freedesktop.org/wiki/CodeOfConduct/
>>
>> Bes
Op 11-04-17 om 08:48 schreef Daniel Vetter:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anything
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
freedesktop.org has adopted a formal&enforced code of conduct:
https://www.fooishbar.org/blog/fdo-contributor-covenant/
https://www.freedesktop.org/wiki/CodeOfConduct/
Besides formalizing things a bit more I don't think this changes
On Tue, Apr 11, 2017 at 08:00:11AM +0300, Laurent Pinchart wrote:
[...]
> The point I don't agree with is that timings have to be specified in C code.
> As pointed in in a comment to
> https://sietch-tagr.blogspot.fi/2016/04/display-panels-are-not-special.html,
> there's a huge number of display p
Hello Inki,
please don't forget to review this series.
Also some pointers concerning the video plane flickering and the
interlacing issue would be very welcome.
Looking at the current register defines for MXR_INT_EN suggests that
there are at least three more type of interrupt available. Any cha
On Fri, Apr 07, 2017 at 10:43:02AM -0400, Sean Paul wrote:
> On Fri, Apr 07, 2017 at 11:02:33AM +0800, Shawn Guo wrote:
> > When you suggested to have a lock for DETECT_SEL register access, I
> > thought we are accessing it in a read-modify-write way and thus agreed
> > to add a lock. However, I j
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1875-ga2de738b139a)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1875-ga2de738b139a/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1875-ga2de738b139a
Git Commit: a2d
Hi,
> > Just let know what you need tested, I should be able to turn it around
> > within a couple of days.
>
> That's part of my problem. I don't really know what should be tested.
> What do people do with their BE machines that we should avoid breaking?
For the virtual machine use case the b
From: Shawn Guo
It adds VGA driver support, which needs to configure corresponding VOU
interface in RGB_888 format, and thus the following changes are needed
on zx_vou.
- Rename the CSC block of Graphic Layer a bit to make it more specific,
and add CSC of Channel to support RGB output.
- By
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #25 from Jean-François Fortin Tam ---
Hi Julien, unfortunately with that benchmark I was not able to reproduce it so
far (I've had it running for about 9 hours). This might be just "luck" though,
as I've sometimes had the issue refuse
https://bugs.freedesktop.org/show_bug.cgi?id=92432
yann changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Y
On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
On Tue, Apr 11, 2017 at 01:22:20PM +1000, Dave Airlie wrote:
> +static int amdgpu_sem_lookup_and_sync(struct amdgpu_cs_parser *p,
> + uint32_t handle)
> +{
> + int r;
> + struct dma_fence *old_fence;
> +
> + r = drm_syncobj_swap_fences(p->filp, handle,
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1880-g52e53d64fa4a)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1880-g52e53d64fa4a/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1880-g52e53d64fa4a
Git Commit: 52e
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think th
On Tue, Apr 11, 2017 at 3:12 PM, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
>> freedesktop.org has adopted a formal&enforced code of conduct:
>>
>> https://www.fooishbar.org/blog/fdo-contributor-covenant/
>> https://www.freedesktop.org/wiki/CodeOfConduct/
drm-tip/drm-tip build: 207 builds: 0 failed, 207 passed, 45 warnings
(v4.11-rc6-1886-g20c20ad1f78a)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1886-g20c20ad1f78a/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1886-g20c20ad1f78a
Git Commit: 20c
On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wrote:
> On Tue, Apr 11, 2017 at 3:12 PM, Luc Verhaegen wrote:
> > On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> >> freedesktop.org has adopted a formal&enforced code of conduct:
> >>
> >> https://www.fooishbar.org/blog/fdo
On Fri, Apr 07, 2017 at 10:02:29PM +0200, Jonathan Neuschäfer wrote:
> On SPARC, the udl driver filled my kernel log with these messages:
>
> [186668.910612] Kernel unaligned access at TPC[76609c]
> udl_render_hline+0x13c/0x3a0
>
> Use put_unaligned_be16 to avoid them. On x86 this results in the
Hey
On Tue, Apr 11, 2017 at 8:48 AM, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this ch
On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wrote:
>> On Tue, Apr 11, 2017 at 3:12 PM, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
>> >> freedesktop.org has adopted a formal&enforced c
From: Colin Ian King
The current message contains a spelling mistake and is not easily
parsable. Re-phrase it to be more understandable.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/medi
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think th
On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
> > On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wrote:
> >> On Tue, Apr 11, 2017 at 3:12 PM, Luc Verhaegen wrote:
> >> > On Tue, Apr 11, 2017 at 08:48:15AM +0200, Dan
On Tue, 11 Apr 2017, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
>> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wrote:
>> >> On Tue, Apr 11, 2017 at 3:12 PM, Luc Verhaegen wrote:
>> >
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1889-g328f79e8c2dc)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1889-g328f79e8c2dc/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1889-g328f79e8c2dc
Git Commit: 328
On Tue, Apr 11, 2017 at 3:31 AM, Pekka Paalanen wrote:
> On Mon, 10 Apr 2017 12:10:14 -0400
> Ilia Mirkin wrote:
>
>> On Mon, Apr 10, 2017 at 11:09 AM, Pekka Paalanen wrote:
>
>> > I also wonder if a real BE machine could have different results than
>> > the virtual machine.
>>
>> I have a PPC G
drm-tip/drm-tip boot: 129 boots: 4 failed, 125 passed
(v4.11-rc6-1875-ga2de738b139a)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1875-ga2de738b139a/
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1875-ga2de
On 04/10/2017 12:32 PM, Jason Ekstrand wrote:
On April 10, 2017 12:29:12 PM Chad Versace
wrote:
On Tue 04 Apr 2017, Keith Packard wrote:
Jason Ekstrand writes:
> Interesting question. To my knowledge, no one has actually
implemented the
> Vulkan WSI direct-to-display extensions. (I tried
On Tue, Apr 11, 2017 at 04:58:51PM +0300, Jani Nikula wrote:
> On Tue, 11 Apr 2017, Luc Verhaegen wrote:
> > On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
> >> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
> >> > On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wro
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale wrote:
My name is Nikhil Mahale, and I work at NVIDIA in the Linux drivers
team.
I have been working on adding DRM KMS support to our driver. The
On Tue, Apr 11, 2017 at 5:14 PM, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 04:58:51PM +0300, Jani Nikula wrote:
>> On Tue, 11 Apr 2017, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
>> >> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
>> >>
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #8 from at...@t-online.de ---
I have no idea how to start the game in valgrind because I have to start the
game through steam. For gdb I used the --pid option to take over the process of
the game after starting it through steam but th
Hi Bjorn,
first of all sorry for the delay, had been busy with other stuff in the
last few weeks.
Am 24.03.2017 um 22:34 schrieb Bjorn Helgaas:
+ release_child_resources(res);
Doesn't this recursively release *all* child resources? There could
be BARs from several devi
On 2017-04-11 02:48 AM, Daniel Vetter wrote:
freedesktop.org has adopted a formal&enforced code of conduct:
https://www.fooishbar.org/blog/fdo-contributor-covenant/
https://www.freedesktop.org/wiki/CodeOfConduct/
Besides formalizing things a bit more I don't think this changes
anything for us
Am 24.03.2017 um 16:47 schrieb Bjorn Helgaas:
On Mon, Mar 13, 2017 at 01:41:35PM +0100, Christian König wrote:
From: Christian König
Most BIOS don't enable this because of compatibility reasons.
Can you give any more details here? Without more hints, it's hard to
know whether any of the comp
On Tue, Apr 11, 2017 at 11:14 AM, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 04:58:51PM +0300, Jani Nikula wrote:
>> On Tue, 11 Apr 2017, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
>> >> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
>> >>
On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1898-g1a8653e657e1)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1898-g1a8653e657e1/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1898-g1a8653e657e1
Git Commit: 1a8
Russell King - ARM Linux writes:
> On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
>> v5: Move register definitions inside the driver directory, fix build
>> in COMPILE_TEST and !AMBA mode.
>
> Why is it necessary to move the register definitions there, when
> they're already ava
On 2017-04-11 11:15 AM, James Jones wrote:
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale
wrote:
My name is Nikhil Mahale, and I work at NVIDIA in the Linux drivers
team.
I have been working o
On Tue, Apr 11, 2017 at 5:50 PM, Alex Deucher wrote:
> On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter wrote:
>> freedesktop.org has adopted a formal&enforced code of conduct:
>>
>> https://www.fooishbar.org/blog/fdo-contributor-covenant/
>> https://www.freedesktop.org/wiki/CodeOfConduct/
>>
>> Be
Linus Walleij writes:
> On Tue, Apr 11, 2017 at 3:18 AM, Eric Anholt wrote:
>
>> From: Tom Cooksey
>
> Well that can be debated at this point. I think it should have
> your Author: tag and just Tom in the Signed-off-by, then mention
> the history in the commit message.
I'm happy giving credit
Daniel Vetter writes:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anything for us, we've alrea
drm-tip/drm-tip boot: 135 boots: 5 failed, 129 passed with 1 offline
(v4.11-rc6-1880-g52e53d64fa4a)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1880-g52e53d64fa4a/
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11
GPU cores with the DYNAMIC_FREQUENCY_SCALING feature bit set expect the
platform to provide the clock scaling and ignore any requests to use the
internal FSCALE divider. Writes to this register still work, but don't
have any effect on the GPU clock frequency.
Save the initial core and shader clock
On Sat, Apr 8, 2017 at 3:45 PM, Fabio Estevam wrote:
> Thierry/Rob,
>
> On Tue, Feb 7, 2017 at 10:48 PM, Fabio Estevam wrote:
>> On Tue, Feb 7, 2017 at 9:36 PM, Rob Herring wrote:
>>
>>> Except I have no way of knowing whether: a) you omitted a supply
>>> because you don't (yet) care, b) the pan
On 04/11/2017 09:09 AM, Harry Wentland wrote:
On 2017-04-11 11:15 AM, James Jones wrote:
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale
wrote:
My name is Nikhil Mahale, and I work at NVIDIA in
The HDMI driver is currently enabling all clks and probe time and keep
the power-domain connected to the HDMI encoder enabled.
Move all activation code to vc4_hdmi_encoder_enable() and make sure
the clks and power domain are released when the HDMI encoder is not used
by adding deactivation steps i
On 04/10/2017 11:47 PM, Laurent Pinchart wrote:
> Hi Laura,
>
> Thank you for the patch.
>
> On Monday 03 Apr 2017 11:57:55 Laura Abbott wrote:
>> When CMA was first introduced, its primary use was for DMA allocation
>> and the only way to get CMA memory was to call dma_alloc_coherent. This
>> pu
drm-tip/drm-tip boot: 128 boots: 5 failed, 121 passed with 2 offline
(v4.11-rc6-1886-g20c20ad1f78a)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1886-g20c20ad1f78a/
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11
On Fri, Apr 7, 2017 at 12:33 PM, Thierry Reding wrote:
> On Fri, Apr 07, 2017 at 05:44:15AM +1000, Dave Airlie wrote:
>> On 5 April 2017 at 16:51, Laurent Pinchart
>> wrote:
>> > As the DRM LVDS panel driver uses a different approach to DT bindings
>> > compared to what Thierry Reding advocates,
On Tue, Apr 11, 2017 at 12:09 PM, Daniel Vetter wrote:
> On Tue, Apr 11, 2017 at 5:50 PM, Alex Deucher wrote:
>> On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter
>> wrote:
>>> freedesktop.org has adopted a formal&enforced code of conduct:
>>>
>>> https://www.fooishbar.org/blog/fdo-contributor-cov
2017-04-11 Daniel Vetter :
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anything for us, we've
On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater
wrote:
> Enable stereoscopic output for HDMI and DisplayPort connectors on
> NV50+ (G80+) hardware. We do not enable stereoscopy on older
> hardware in case there is some older board that still has HDMI
> output but for which we have no logic
Chris Wilson writes:
> On Mon, Apr 10, 2017 at 06:44:14PM -0700, Eric Anholt wrote:
>> This is needed for proper synchronization with display on another DRM
>> device (pl111 or tinydrm) with buffers produced by vc4 V3D. Fixes the
>> new igt vc4_dmabuf_poll testcase, and rendering of one of the g
drm-tip/drm-tip boot: 120 boots: 3 failed, 117 passed
(v4.11-rc6-1889-g328f79e8c2dc)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1889-g328f79e8c2dc/
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1889-g328f
On 2017-04-11 12:37 PM, James Jones wrote:
On 04/11/2017 09:09 AM, Harry Wentland wrote:
On 2017-04-11 11:15 AM, James Jones wrote:
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale
wrote:
My na
https://bugs.freedesktop.org/show_bug.cgi?id=98996
--- Comment #2 from Christoph Haag ---
Created attachment 130804
--> https://bugs.freedesktop.org/attachment.cgi?id=130804&action=edit
performance with amd-staging-4.9 and mesa git
Screenshot with out of the box performance on latest amd-stagi
On Mon, Apr 10, 2017 at 2:27 PM, Dave Airlie wrote:
> On 10 April 2017 at 19:03, Laurent Pinchart
> wrote:
>> Hi Thierry,
>>
>> On Monday 10 Apr 2017 09:17:59 Thierry Reding wrote:
>>> On Sun, Apr 09, 2017 at 01:31:40PM +0100, Emil Velikov wrote:
>>> > Hi Thierry,
>>> >
>>> > I don't mean to stir
drm-tip/drm-tip boot: 122 boots: 4 failed, 117 passed with 1 offline
(v4.11-rc6-1898-g1a8653e657e1)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1898-g1a8653e657e1/
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11
Hi Dave,
I have a lonely pull request for you. Just the patch you asked me to pick up
this morning.
drm-misc-fixes-2017-04-11:
Core changes:
- None
Driver changes
- udl: Fix unaligned memory access on SPARC (Jonathan)
Cheers, Sean
The following changes since commit a71c9a1c779f2499fb2afc0
On Mon, Apr 10, 2017 at 12:55:33PM -0700, Eric Anholt wrote:
> Gustavo Padovan writes:
>
> > From: Gustavo Padovan
> >
> > In some cases, like cursor updates, it is interesting to update the
> > plane in an asynchronous fashion to avoid big delays.
> >
> > The current queued update could be stil
On Mon, Apr 10, 2017 at 01:06:46PM -0700, Eric Anholt wrote:
> Gustavo Padovan writes:
>
> > From: Gustavo Padovan
> >
> > Add support to async updates of cursors by using the new atomic
> > interface for that. Basically what this commit does is do what
> > vc4_update_plane() did but through ato
Yannick Fertre writes:
> This controller provides output signals to interface directly a variety
> of LCD and TFT panels. These output signals are: RGB signals
> (up to 24bpp), vertical & horizontal synchronisations, data enable and
> the pixel clock.
>
> Signed-off-by: Yannick Fertre
> ---
> d
On Tue, Apr 11, 2017 at 01:45:01PM -0700, Eric Anholt wrote:
> Yannick Fertre writes:
> > +static void ltdc_crtc_disable(struct drm_crtc *crtc)
> > +{
> > + struct ltdc_device *ldev = crtc_to_ltdc(crtc);
> > + struct drm_pending_vblank_event *event = crtc->state->event;
> > +
> > + DRM_DEBUG
Russell King - ARM Linux writes:
> On Tue, Apr 11, 2017 at 09:06:31AM -0700, Eric Anholt wrote:
>> Russell King - ARM Linux writes:
>>
>> > On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
>> >> v5: Move register definitions inside the driver directory, fix build
>> >> in COMPIL
https://bugzilla.kernel.org/show_bug.cgi?id=195295
--- Comment #3 from Eugene Shalygin (eugene.shaly...@gmail.com) ---
Tried 4.10.6, which was free of this bug at the time I used it, but now it show
the same behaviour. Here is a part from dmesg:
[ 21.074717] usb 3-1: new high-speed USB device n
On Wed, Apr 12, 2017 at 04:57:54AM +0800, Jeffy Chen wrote:
> My previous patch (c5d8fac2bf drm: Unplug drm device when unregistering
> it) calls drm_unplug_dev when unregistering drm dev. But if open_count
> is 0, the unplug will try to unregister the drm dev again and cause
> deadlock.
>
> Fix
Linus Walleij writes:
> On Tue, Apr 11, 2017 at 3:18 AM, Eric Anholt wrote:
>
>> From: Tom Cooksey
>
> Well that can be debated at this point. I think it should have
> your Author: tag and just Tom in the Signed-off-by, then mention
> the history in the commit message.
>
>> This is a modesettin
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #26 from Jean-François Fortin Tam ---
OK, I've got good news... Julien, thanks to the crazy furry donut "torture
test" you suggested, I was able to finally pinpoint the real trigger for this
bug.
My understanding is that on Radeons (
Hi Lucas,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on next-20170411]
[cannot apply to v4.11-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Lucas-Stach/drm-etnaviv
1 - 100 of 166 matches
Mail list logo
