https://bugs.freedesktop.org/show_bug.cgi?id=91319
ree...@gmail.com changed:
What|Removed |Added
CC||ree...@gmail.com
--- Comment #16 from
From: Ville Syrjälä
This series first unifies all users of drm_atomic_helper_check_plane_state()
to populate the clip rectangle with drm_mode_get_hv_timing(), and once
everything is unified the clip rectangle handling is sucked into
pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
where a PCI device is present. This restricts the device drivers to be
reused for other domain numbers.
Use pci_get_domain_bus_and_slot() with a domain number of 0 where we can't
extract the domain number. Other places, use
On Thu, Nov 23, 2017 at 09:04:47PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> This series first unifies all users of drm_atomic_helper_check_plane_state()
> to populate the clip rectangle with drm_mode_get_hv_timing(), and once
> everything is unified
pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
where a PCI device is present. This restricts the device drivers to be
reused for other domain numbers.
Getting ready to remove pci_get_bus_and_slot() function in favor of
pci_get_domain_bus_and_slot().
Replace
Tried the given patch on top of next-20171121. HDMI monitor is
connected, but I don't see any output. Here's a portion of my Xorg.log
(I installed xf86-video-nouveau-git):
[ 1046.301] (II) NOUVEAU driver Date: Tue Jun 13 09:23:42 2017 -0400
[ 1046.301] (II) NOUVEAU driver for NVIDIA chipset
pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
where a PCI device is present. This restricts the device drivers to be
reused for other domain numbers.
Getting ready to remove pci_get_bus_and_slot() function in favor of
pci_get_domain_bus_and_slot().
Replace
https://bugs.freedesktop.org/show_bug.cgi?id=100567
--- Comment #11 from 988a...@mail.ru ---
Same problem on Linux Neon 4.10.0-40-generic
xserver-xorg-video-nouveau-hwe-16.04 - 1:1.0.14-0ubuntu1~16.04.1
--
You are receiving this mail because:
You are the assignee for the
The kbuild test bot complained about a new coccinelle warning nearby,
which sparked a discussion about the assignment to 'memory' inside of
the conditional expression. See Link below for the original post.
Fix the assignment to silence the coccinelle warning and also make the
code look a little
On Thu, Nov 30, 2017 at 01:35:58PM +0100, Karol Herbst wrote:
> Well, you are most likely using the CPU for decoding here. Currently
> nobody is working on that, because this is quite a big and challenging
> project. We have an open project idea regarding this for EVoC and GSoC
> though:
>
Well, you are most likely using the CPU for decoding here. Currently
nobody is working on that, because this is quite a big and challenging
project. We have an open project idea regarding this for EVoC and GSoC
though:
"Maxwell Accelerated Video Decoding" https://www.x.org/wiki/SummerOfCodeIdeas/
Hi Everyone,
I have a Maxwell Card (GTX 970/NV 110) and would very much like to use
nouveau to drive it. The problem is that the performance -- especially
when decoding high-resolution video -- seems to be relatively poor
compared to the proprietary Nvidia driver. I'm interested in Kernel
12 matches
Mail list logo