https://bugzilla.kernel.org/show_bug.cgi?id=199917
--- Comment #1 from Nicholas Johnson (nicholas.john...@outlook.com.au) ---
On the first stack dump, it says not tainted, and then on the following ones,
it says tainted. Can having a stack dump taint the kernel? Either way, I had
not modified the
On 6/3/18 5:00 PM, Noralf Trønnes wrote:
Den 25.05.2018 21.36, skrev David Lechner:
This series adds a new tinydrm driver for the Ilitek ILI9341
controller and
a 2.4" display panel that uses this controller.
David, do you have commit rights now?
No. Opened a bug a while back to request
https://bugzilla.kernel.org/show_bug.cgi?id=199917
Bug ID: 199917
Summary: Stack dump with amdgpu.dc=1 the instant FreeSync is
enabled in the connected display.
Product: Drivers
Version: 2.5
Kernel Version: 4.17.0-041700-generic
The use of load and unload hooks is deprecated. DRM drivers should
use drm_dev_alloc|drm_dev_init and drm_dev_register for initialization
and publishing.
Signed-off-by: Fabio Rafael da Rosa
Reviewed-by: Nicholas Mc Guire
---
Changes in v2:
- Replace drm_dev_unref (also depretated) by
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
between commit:
a9e8d27574f2 ("drm/amd/display: Make atomic-check validate underscan changes")
from Linus' tree and commit:
dm_update_crtcs_state ("drm/amd/display:
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #16 from ejr.ph...@gmail.com ---
I have this issue too, disabling page flipping fixes it for me on my vega10. It
started with 4.16rc1 IIRC
--
You are receiving this mail because:
You are the assignee for the
On 4 June 2018 at 00:40, Mikulas Patocka wrote:
> Hi
>
> Here I'm sending bug fixes and performance improvements for the USB
> DisplayLink framebuffer and modesetting drivers for this merge window.
>
Hi,
You probably want to split these up into separate series for the kms and fbdev
drivers.
Den 25.05.2018 21.36, skrev David Lechner:
This series adds a new tinydrm driver for the Ilitek ILI9341 controller and
a 2.4" display panel that uses this controller.
David, do you have commit rights now?
Noralf.
A few things to note here:
* The datasheet for this display[1] doesn't have a
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #4 from dwagner ---
I was asked in
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1027705-amdgpu-on-linux-4-18-to-offer-greater-vega-power-savings-displayport-1-4-fixes?p=1027933#post1027933
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #3 from dwagner ---
Just for the record, others have reported similar symptoms - here is a recent
example: https://bugs.freedesktop.org/show_bug.cgi?id=10
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=10
--- Comment #11 from dwagner ---
The symptoms you describe sound very much the same as the ones I experience - I
reported them in https://bugs.freedesktop.org/show_bug.cgi?id=102322
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106533
michael.panzl...@fau.de changed:
What|Removed |Added
CC||michael.panzl...@fau.de
---
/linux/commits/Mikulas-Patocka/USB-DisplayLink-patches/20180603-233013
base: git://people.freedesktop.org/~airlied/linux.git drm-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed
Am 01.06.2018 um 21:56 schrieb Andrey Grodzovsky:
On 06/01/2018 01:22 PM, Christian König wrote:
Am 01.06.2018 um 19:11 schrieb Andrey Grodzovsky:
Dying process might be blocked from receiving any more signals
so avoid using it.
Also retire enity->fini_status and just check the SW queue,
if
https://bugs.freedesktop.org/show_bug.cgi?id=100616
Arham Amouei changed:
What|Removed |Added
Priority|medium |high
--- Comment #2 from Arham Amouei
On 29.05.2018 10:17, Ville Syrjälä wrote:
> On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote:
>> Color keying is the action of replacing pixels matching a given color
>> (or range of colors) with transparent pixels in an overlay when
>> performing blitting. Depending on the hardware
On Fri, Jun 1, 2018 at 5:18 PM, Christian König
wrote:
> Am 31.05.2018 um 07:07 schrieb Souptick Joarder:
>>
>> On Thu, May 24, 2018 at 12:25 AM, Souptick Joarder
>> wrote:
>>>
>>> Use new return type vm_fault_t for fault handler. For
>>> now, this is just documenting that the function returns
On Sat, Jun 02, 2018 at 08:41:44AM -0300, Fabio Rafael da Rosa wrote:
> The use of load and unload hooks is deprecated. DRM drivers should
> use drm_dev_alloc|drm_dev_init and drm_dev_register for initialization
> and publishing.
>
> Signed-off-by: Fabio Rafael da Rosa
Reviewed-by: Nicholas Mc
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
I have a USB display adapter using the udlfb driver and I use it on an ARM
board that doesn't have any graphics card. When I plug the adapter in, the
console is properly displayed, however when I unplug and re-plug the
adapter, the console is not displayed and I can't access it until I reboot
the
https://bugs.freedesktop.org/show_bug.cgi?id=106795
Bug ID: 106795
Summary: Laptop with Intel+Nvidia hybrid graphics won't suspend
after hibernation
Product: DRI
Version: unspecified
Hardware: Other
OS: All
The udl kms driver writes messages to the syslog whenever some application
opens or closes /dev/fb0 and whenever the user switches between the
Xserver and the console.
This patch changes the priority of these messages to debug.
Signed-off-by: Mikulas Patocka
---
drivers/gpu/drm/udl/udl_fb.c
The displaylink hardware has such a peculiarity that it doesn't render a
command until next command is received. This produces occasional
corruption, such as when setting 22x11 font on the console, only the first
line of the cursor will be blinking if the cursor is located at some
specific
Currently, the udlfb driver only tests for identical bytes at the
beginning or at the end of a page and renders anything between the first
and last mismatching pixel. But pages are not the same as lines, so this
is quite suboptimal - if there is something modified at the beginning of a
page and at
The udlfb driver reprograms the hardware everytime the user switches the
console, that makes quite unusable when working on the console.
This patch makes the driver remember the videomode we are in and avoid
reprogramming the hardware if we switch to the same videomode.
We mask the "activate"
spin_lock_irqsave and spin_unlock_irqrestore is inteded to be called from
a context where it is unknown if interrupts are enabled or disabled (such
as interrupt handlers). From a process context, we should call
spin_lock_irq and spin_unlock_irq, that avoids the costly pushf and popf
instructions.
The defio subsystem overwrites the method fb_osp->mmap. That method is
stored in module's static data - and that means that if we have multiple
diplaylink adapters, they will over write each other's method.
In order to avoid interference between multiple adapters, we copy the
fb_ops structure to
The udl driver crashes when fbdefio is used. The crash can be reproduced
with this sequence:
1. echo 1 >/sys/module/udl/parameters/fb_defio
2. run some program that maps the framebuffer, such as 'links -g' or 'fbi'
3. allocate memory to the point where the machine starts swapping
The reason for
Allocations larger than PAGE_ALLOC_COSTLY_ORDER are unreliable and they
may fail anytime. This patch fixes the udlfb driver so that when a large
alloactions fails, it tries to do multiple smaller allocations.
Signed-off-by: Mikulas Patocka
Cc: sta...@vger.kernel.org
---
The default delay 5 jiffies is too much when the kernel is compiled with
HZ=100 - it results in jumpy cursor in Xwindow.
In order to find out the optimal delay, I benchmarked the driver on
1280x720x30fps video. I found out that with HZ=1000, 10ms is acceptable,
but with HZ=250 or HZ=300, we need
Hi
Here I'm sending bug fixes and performance improvements for the USB
DisplayLink framebuffer and modesetting drivers for this merge window.
Mikulas
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
If we leave urbs around, it causes not only leak, but also memory
corruption. This patch fixes the function udl_free_urb_list, so that it
always waits for all urbs that are in progress.
Signed-off-by: Mikulas Patocka
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/udl/udl_main.c |7 +--
Division is slow, so it shouldn't be done by the pixel generating code.
The driver supports only 2 or 4 bytes per pixel, so we can replace
division with a shift.
Signed-off-by: Mikulas Patocka
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/udl/udl_drv.h |2 -
Allocations larger than PAGE_ALLOC_COSTLY_ORDER are unreliable and they
may fail anytime. This patch fixes the udl kms driver so that when a large
alloactions fails, it tries to do multiple smaller allocations.
Signed-off-by: Mikulas Patocka
Cc: sta...@vger.kernel.org
---
Set the variable "line_length" in the function dlfb_ops_set_par. Without
this, we get garbage if we select different videomode with fbset.
Signed-off-by: Mikulas Patocka
Cc: sta...@vger.kernel.org
---
drivers/video/fbdev/udlfb.c |1 +
1 file changed, 1 insertion(+)
Index:
Modern processors can detect linear memory accesses and prefetch data
automatically, so there's no need to use prefetch.
Signed-off-by: Mikulas Patocka
---
drivers/gpu/drm/udl/udl_transfer.c |7 ---
1 file changed, 7 deletions(-)
Index: linux-4.16.12/drivers/gpu/drm/udl/udl_transfer.c
The defio subsystem overwrites the method fb_osp->mmap. That method is
stored in module's static data - and that means that if we have multiple
diplaylink adapters, they will over write each other's method.
In order to avoid interference between multiple adapters, we copy the
fb_ops structure to
Modern processors can detect linear memory accesses and prefetch data
automatically, so there's no need to use prefetch.
Signed-off-by: Mikulas Patocka
---
drivers/video/fbdev/udlfb.c |8
1 file changed, 8 deletions(-)
Index: linux-4.17-rc7/drivers/video/fbdev/udlfb.c
spin_lock_irqsave and spin_unlock_irqrestore is inteded to be called from
a context where it is unknown if interrupts are enabled or disabled (such
as interrupt handlers). From a process context, we should call
spin_lock_irq and spin_unlock_irq, that avoids the costly pushf and popf
instructions.
This patch changes udlfb so that it may reallocate the framebuffer when
setting higher-resolution mode. If we boot the system without monitor
attached, udlfb creates a framebuffer with the size 800x600. This patch
makes it possible to select higher videomode with the fbset command when
a monitor
We must use kzalloc when allocating the fb_deferred_io structure.
Otherwise, the field first_io is undefined and it causes a crash.
Signed-off-by: Mikulas Patocka
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/udl/udl_fb.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
The displaylink hardware has such a peculiarity that it doesn't render a
command until next command is received. This produces occasional
corruption, such as when setting 22x11 font on the console, only the first
line of the cursor will be blinking if the cursor is located at some
specific
I observed that the performance of the udl fb driver degrades over time.
On a freshly booted machine, it takes 6 seconds to do "ls -la /usr/bin";
after some time of use, the same operation takes 14 seconds.
The reason is that the value of "limit_sem" decays over time.
The udl driver uses a
https://bugs.freedesktop.org/show_bug.cgi?id=106471
--- Comment #4 from mirh ---
Phoronix also reported 4870 not to work on 4.17.
Could you try some previous kernel version?
--
You are receiving this mail because:
You are the assignee for the
On Sun 2018-06-03 10:27:02, Daniel Stone wrote:
> Hi Pavel,
>
> On 2 June 2018 at 18:55, Pavel Machek wrote:
> >> On 30 May 2018 at 12:17, Pavel Machek wrote:
> >> > Any chance to still get in this one?
> >> >
> >> >
Hi Pavel,
On 2 June 2018 at 18:55, Pavel Machek wrote:
>> On 30 May 2018 at 12:17, Pavel Machek wrote:
>> > Any chance to still get in this one?
>> >
>> > https://github.com/freedesktop/drm-misc/commit/2bc5ff0bdc00d81d719dad74589317a260d583ed
>> >
>> > ...it fixes display on Nokia N900, and
This is a note to let you know that I've just added the patch titled
drm/psr: Fix missed entry in PSR setup time table.
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/psr: Fix missed entry in PSR setup time table.
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/psr: Fix missed entry in PSR setup time table.
to the 4.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
49 matches
Mail list logo
