On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote:
> Allwinner A64's DE2 needs to claim a section of SRAM (SRAM C) to work.
>
> Add support for it.
>
> Signed-off-by: Icenowy Zheng
> ---
> drivers/clk/sunxi-ng/ccu-sun8i-de2.c | 32
> 1 file changed, 24 inserti
(Adding dri-devel back, and trying to respond to some comments from
the different forks)
James Jones wrote:
> Your worst case analysis above isn't far off from our HW, give or take
> some bits and axes here and there. We've started an internal discussion
> about how to lay out all the bits we ne
On Thu, 2017-12-21 at 12:04 +0200, Dmitry Rozhkov wrote:
> printk format strings accepting a single subsequent argument
> are shorter thus easier to read.
>
> Instead of having format strings accepting 3 different arguments
> pointing to first 3 bytes of the same buffer rewrite the format
> string
On 26/12/2017 at 11:16:34 -0600, Rob Herring wrote:
> On Fri, Dec 22, 2017 at 4:56 AM, Alexandre Belloni
> wrote:
> > + Philippe
> >
> > On 22/12/2017 at 11:43:33 +0100, Andreas Färber wrote:
> >> >> I'll change it for v3 of this patch however it will end up like this:
> >> >> //SPDX-License...
>
On 12/28/2017 07:18 PM, Dave Airlie wrote:
> Hi Linus,
>
> Just dequeuing some fixes, I'm on holidays next week again, but I
> think things should be fine.
>
> Dave.
Hi,
It would be good to get this documentation build error patch
merged into 4.15. Daniel Vetter says that he merged (applied) i
On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote:
> The H3/H5 SoCs have a HDMI output and a TV Composite output.
>
> Add simplefb nodes for these outputs.
>
> Signed-off-by: Icenowy Zheng
> ---
> arch/arm/boot/dts/sunxi-h3-h5.dtsi | 29 +
> 1 file changed, 29 inse
On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote:
> This patchset adds support for the SimpleFB on Allwinner SoCs with
> "Display Engine 2.0".
>
> PATCH 1 to PATCH 3 are DE2 CCU fixes for H3/H5 SoCs.
>
> PATCH 4 adds the pipeline strings for DE2 SimpleFB.
>
> PATCH 5 to 7 adds necessary device
On Thu, 28 Dec 2017, Randy Dunlap wrote:
> It would be good to get this documentation build error patch
> merged into 4.15. Daniel Vetter says that he merged (applied) it.
>
> [PATCH] documentation/gpu/i915: fix docs build error after file rename
> https://marc.info/?l=linux-kernel&m=1512344194
From: Yue Hin Lau
Signed-off-by: Yue Hin Lau
Reviewed-by: Eric Bernstein
Acked-by: Harry Wentland
Signed-off-by: Alex Deucher
[dr...@endlessm.com: backport to 4.15]
Signed-off-by: Daniel Drake
---
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_dpp.h | 2 +-
drivers/gpu/drm/amd/display/
On 26 December 2017 at 19:19, Matt Roper wrote:
> On Wed, Dec 20, 2017 at 10:59:57AM +0100, Daniel Vetter wrote:
>> On Tue, Dec 19, 2017 at 03:27:31PM -0800, Dongwon Kim wrote:
>> > I forgot to include this brief information about this patch series.
>> >
>> > This patch series contains the impleme
https://bugs.freedesktop.org/show_bug.cgi?id=104412
Bug ID: 104412
Summary: RX 460 HDMI 4k 60fps not working, DisplayPort is.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #1 from S.H. ---
Created attachment 136446
--> https://bugs.freedesktop.org/attachment.cgi?id=136446&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #2 from S.H. ---
Added drm parts of dmesg and Xorg.0.log file.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesk
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #3 from S.H. ---
Sorry, pressed the send button too early.
For anyone willing to help, here's my system:
- kernel-4.15-rc5
- xf86-video-amdgpu-1.4.0
- xorg-server-1.19.6
- Sapphire RX 460
- iiyama G-Master GB2888UHSU
If you need a
We were calling enable_irq on bind, where it was already enabled previously
by the IRQ helper. Additionally, dev->irq is not set correctly until after
postinstall and so was always zero here, triggering a warning in 4.15.
Fix both by moving the enable to the power management resume path, where we
k
https://bugs.freedesktop.org/show_bug.cgi?id=97909
Thomas Rohloff changed:
What|Removed |Added
CC||v10la...@myway.de
--- Comment #9 from T
On Tue, 19 Dec 2017, Daniel Vetter wrote:
> On Wed, Dec 13, 2017 at 08:47:42PM +0100, Max Staudt wrote:
>> Dear fbdev and fbcon developers,
>>
>> Thank you very much for your input for the first patch series.
>>
>> I've included your feedback into this second roll, and kindly ask for
>> your opi
On Monday, November 13, 2017 11:27:19 AM Johan Hovold wrote:
> Fix child-node lookup during probe, which ended up searching the whole
> device tree depth-first starting at the parent rather than just matching
> on its children.
>
> To make things worse, the parent display node was also prematurely
On Thursday, November 23, 2017 10:55:53 AM Colin King wrote:
> From: Colin Ian King
>
> The assignment of height to itself is redundant and can be removed.
> Detected with Coccinelle.
>
> Signed-off-by: Colin Ian King
Patch queued for 4.16, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
S
On Friday, November 24, 2017 08:30:04 PM SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 24 Nov 2017 20:22:10 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus El
On Friday, November 24, 2017 08:53:02 PM SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 24 Nov 2017 20:42:08 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus El
On Friday, November 24, 2017 09:48:14 PM SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 24 Nov 2017 21:45:54 +0100
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (4):
> Delete an error message for a failed memory alloca
On Friday, November 24, 2017 10:30:34 PM Rolf Eike Beer wrote:
> Markus Elfring wrote:
> > From: Markus Elfring
> > Date: Fri, 24 Nov 2017 22:22:06 +0100
> >
> > Omit an extra message for a memory allocation failure in this function.
> >
> > This issue was detected by using the Coccinelle softwa
>> Delete an error message for a failed memory allocation in two functions
>
> This patch removes the information about the device for which the allocation
> fails.
* Do you find a Linux allocation failure report insufficient in this use case?
* Are you looking for any more clarification?
>
On Saturday, November 25, 2017 05:04:02 PM SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 25 Nov 2017 16:56:46 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Delete an error message for a failed memory alloca
>> Delete an error message for a failed memory allocation
>
> This patch removes the information about the device for which the allocation
> fails.
How do you think about to take another look if a Linux allocation failure report
could be sufficient in this use case?
>> Improve a size deter
On Saturday, November 25, 2017 09:42:57 PM SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 25 Nov 2017 21:38:42 +0100
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (5):
> Delete an error message for a failed memory allo
>> Delete an error message for a failed memory allocation in two functions
>
> This patch removes the information about the device for which the allocation
> fails.
Should a Linux allocation failure report be sufficient here?
>> Less checks in ufx_usb_probe() after error detection
>
> Thi
https://bugs.freedesktop.org/show_bug.cgi?id=104143
Gert Wollny changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Mon, 27 Nov 2017, Mike Keehan wrote:
> I am getting a General Protection Fault on 4.15-rc1, and the X11 screen
> locks up.
Catching up with some old mails... Is this still an issue? Please file a
bug at [1].
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #4 from dwagner ---
You might experience the same issue as I did, read
https://bugs.freedesktop.org/show_bug.cgi?id=102820 for details.
The bottom line of which is: Unless you revert commit
ebbf7337e2daacacef3e01114e6be68a2a4f11b4 t
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #5 from dwagner ---
(My above referenced commit ID was valid for an older version of the
amd-staging-drm-next git branch - to find the same commit in the kernel git
branch you use, search for "drm/amd/display: Block 6Ghz timing if SB
https://bugzilla.kernel.org/show_bug.cgi?id=198221
Pierre Moreau (pierre.mor...@free.fr) changed:
What|Removed |Added
CC||pierre.mor...@free
https://bugzilla.kernel.org/show_bug.cgi?id=198221
--- Comment #5 from Petr Vandrovec (p...@vandrovec.name) ---
Yes, it fixes the crash. I am not sure what impact have holding lock for longer
time, but I didn't notice anything bad.
--
You are receiving this mail because:
You are watching the ass
Ping
On 2017-07-22 — 13:54, Pierre Moreau wrote:
> Reviewed-by: Pierre Moreau
>
> On 2017-06-21 — 15:19, Hans de Goede wrote:
> > Hi,
> >
> > On 26-05-17 09:35, Hans De Goede wrote:
> > > The local #define of ACPI_VIDEO_NOTIFY_PROBE was only added temporarily
> > > to avoid a dependency between
Ping: this can still be an issue today as kstrtol() & co haven’t changed their
possible return value since the patch was written.
On 2017-07-22 — 14:13, Pierre Moreau wrote:
> Reviewed-by: Pierre Moreau
>
> On 2017-07-17 — 11:17, Dan Carpenter wrote:
> > kstrtol() and friends can return -EINVAL
Right now it is not possible to return a value larger than LONG_MAX on 32
bit systems. You can pass a rate of ULONG_MAX but can't return anything
past LONG_MAX due to the fact both the rounded_rate and negative error
codes are represented in the return value of round_rate().
Most implementations e
37 matches
Mail list logo
