On Thu, Jan 24, 2019 at 07:55:51AM +1300, Kees Cook wrote:
> On Thu, Jan 24, 2019 at 4:44 AM Jani Nikula
> wrote:
> >
> > On Wed, 23 Jan 2019, Edwin Zimmerman wrote:
> > > On Wed, 23 Jan 2019, Jani Nikula wrote:
> > >> On Wed, 23 Jan 2019, Greg KH wrote:
> > >> > On Wed, Jan 23, 2019 at 03:03:
Hi Dave/Daniel,
Just a small fix for sun4i in drm-misc-fixes. :)
drm-misc-fixes-2019-01-24:
drm-misc-fixes for v5.0-rc4:
- Small refcounting fix to sun4i's HDMI support.
The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:
Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)
are
On Tue, Jan 22, 2019 at 03:25:47PM +, Biju Das wrote:
> The LVDS encoders on RZ/G1N SoC is similar to RZ/G1M. Add support for
> RZ/G1N (R8A7744) SoC to the LVDS encoder driver.
>
> Signed-off-by: Biju Das
Reviewed-by: Simon Horman
> ---
> drivers/gpu/drm/rcar-du/rcar_lvds.c | 1 +
> 1 fil
23.01.2019 12:39, Thierry Reding пишет:
> From: Thierry Reding
>
> Loading the firmware requires an allocation of IOVA space to make sure
> that the VIC's Falcon microcontroller can read the firmware if address
> translation via the SMMU is enabled.
>
> However, the allocation currently happens
This attempts to duplicate the proposed gcc option -finit-local-vars[1]
in an effort to implement the "always initialize local variables" kernel
development goal[2].
Enabling CONFIG_GCC_PLUGIN_STACKINIT should stop all "uninitialized
stack variable" flaws as long as they don't depend on being zero
On Wed, 23 Jan 2019 at 13:09, Jann Horn wrote:
>
> On Wed, Jan 23, 2019 at 1:04 PM Greg KH wrote:
> > On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote:
> > > Variables declared in a switch statement before any case statements
> > > cannot be initialized, so move all instances out of the
On Wed, 23 Jan 2019, Jani Nikula wrote:
> On Wed, 23 Jan 2019, Greg KH wrote:
> > On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote:
> >> Variables declared in a switch statement before any case statements
> >> cannot be initialized, so move all instances out of the switches.
> >> After t
On Wed, Jan 23, 2019 at 1:04 PM Greg KH wrote:
> On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote:
> > Variables declared in a switch statement before any case statements
> > cannot be initialized, so move all instances out of the switches.
> > After this, future always-initialized stack
This adds a new plugin "stackinit" that attempts to perform unconditional
initialization of all stack variables[1]. It has wider effects than
GCC_PLUGIN_STRUCTLEAK_BYREF_ALL=y since BYREF_ALL does not consider
non-structures. A notable weakness is that padding bytes in many cases
remain uninitializ
On Wed, Jan 23, 2019 at 05:23:15PM -0500, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> When range of virtual address is updated read only and corresponding
> user ptr object are already read only it is pointless to do anything.
> Optimize this case out.
>
> Signed-off-by: Jérôme Glisse
>
On Wed, 23 Jan 2019 at 08:15, Christoph Hellwig wrote:
>
> On Tue, Jan 22, 2019 at 10:07:07PM +0100, Ard Biesheuvel wrote:
> > Yes, so much was clear. And the reason this breaks on some arm64
> > systems is because
> > a) non-snooped PCIe TLP attributes may be ignored, and
> > b) non-x86 CPUs do n
On Thu, Jan 24, 2019 at 12:22:00AM +0200, Laurent Pinchart wrote:
>
> On Wed, Jan 23, 2019 at 02:21:05PM -0800, Dmitry Torokhov wrote:
> > On Thu, Jan 24, 2019 at 12:17:35AM +0200, Laurent Pinchart wrote:
> > > On Wed, Jan 23, 2019 at 02:03:42PM -0800, Dmitry Torokhov wrote:
> > >> On Wed, Jan 23
On Wed, Jan 23, 2019 at 04:17:30PM +0200, Jani Nikula wrote:
> Can't have:
>
> switch (i) {
> int j;
> case 0:
> /* ... */
> }
>
> because it can't be turned into:
>
> switch (i) {
> int j = 0; /* not valid C */
> case 0:
>
On Wed, Jan 23, 2019 at 12:54:05AM +0200, Laurent Pinchart wrote:
> The LVDS1 encoder must supply a pixel clock to the DU for the DPAD
> output when the LVDS0 encoder is used. Enable it despite its output not
> being connected.
>
> Signed-off-by: Laurent Pinchart
> ---
> Changes since v1:
>
> -
On Tue, Jan 22, 2019 at 7:43 PM Jayant Shekhar wrote:
>
> The interconnect framework is designed to provide a
> standard kernel interface to control the settings of
> the interconnects on a SoC.
>
> The interconnect API uses a consumer/provider-based model,
> where the providers are the interconne
On Thu, Jan 24, 2019 at 4:44 AM Jani Nikula wrote:
>
> On Wed, 23 Jan 2019, Edwin Zimmerman wrote:
> > On Wed, 23 Jan 2019, Jani Nikula wrote:
> >> On Wed, 23 Jan 2019, Greg KH wrote:
> >> > On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote:
> >> >> Variables declared in a switch statem
23.01.2019 12:39, Thierry Reding пишет:
> From: Thierry Reding
>
> On Tegra186 and later, the ARM SMMU provides an input address space that
> is 48 bits wide. However, memory clients can only address up to 40 bits.
> If the geometry is used as-is, allocations of IOVA space can end up in a
> regio
Replace memset(vaddr_out + src_offset + 24, 0, 8) with
memset(vaddr_out + src_offset + 3, 0, 1) because memset fills
memory in bytes and not in bits.
Signed-off-by: Mamta Shukla
---
drivers/gpu/drm/vkms/vkms_crc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/d
23.01.2019 16:42, Thierry Reding пишет:
> From: Thierry Reding
>
> Upon driver failure, the driver core will take care of clearing the
> driver data, so there's no need to do so explicitly in the driver.
>
> Signed-off-by: Thierry Reding
> ---
> drivers/gpu/drm/tegra/vic.c | 1 -
> 1 file chan
Use the alpha value to blend vaddr_src with vaddr_dst instead
of overwriting it in blend().
Signed-off-by: Mamta Shukla
---
drivers/gpu/drm/vkms/vkms_crc.c | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/vkms/vkms_crc.c b/drivers/gpu/dr
On Wed, Jan 23, 2019 at 12:54:04AM +0200, Laurent Pinchart wrote:
> The LVDS1 encoder must supply a pixel clock to the DU for the DPAD
> output when the LVDS0 encoder is used. Enable it despite its output not
> being connected.
>
> Signed-off-by: Laurent Pinchart
> ---
> Changes since v1:
>
> -
23.01.2019 12:39, Thierry Reding пишет:
> From: Thierry Reding
>
> Loading the firmware requires an allocation of IOVA space to make sure
> that the VIC's Falcon microcontroller can read the firmware if address
> translation via the SMMU is enabled.
>
> However, the allocation currently happens
Adds test for stack initialization coverage. We have several build options
that control the level of stack variable initialization. This test lets us
visualize which options cover which cases, and provide tests for options
that are currently not available (padding initialization).
All options pass
23.01.2019 12:39, Thierry Reding пишет:
> From: Thierry Reding
>
> Tegra DRM clients need access to their parent, so store a pointer to it
> upon registration.
>
> Signed-off-by: Thierry Reding
> ---
> drivers/gpu/drm/tegra/drm.c | 2 ++
> drivers/gpu/drm/tegra/drm.h | 1 +
> 2 files changed,
23.01.2019 12:39, Thierry Reding пишет:
> From: Thierry Reding
>
> Move initialization of the shared IOMMU domain after the host1x device
> has been initialized. At this point all the Tegra DRM clients have been
> attached to the shared IOMMU domain.
>
> This is important because Tegra186 and la
On Mon, Jan 21, 2019 at 1:36 AM Jani Nikula wrote:
>
> On Fri, 18 Jan 2019, "Kristian H. Kristensen" wrote:
> > Otherwise we get hard to track down "Purging: 123123 bytes" messages in
> > the log.
> >
> > Signed-off-by: Kristian H. Kristensen
> > ---
> > drivers/gpu/drm/msm/msm_gem_shrinker.c |
23.01.2019 18:55, Dmitry Osipenko пишет:
> 23.01.2019 17:04, Thierry Reding пишет:
>> On Wed, Jan 23, 2019 at 04:41:44PM +0300, Dmitry Osipenko wrote:
>>> 23.01.2019 12:39, Thierry Reding пишет:
From: Thierry Reding
On Tegra186 and later, the ARM SMMU provides an input address space
On Tue, Jan 22, 2019 at 05:44:28PM +0200, Laurent Pinchart wrote:
> Hi Biju,
>
> Thank you for the patch.
>
> On Tue, Jan 22, 2019 at 03:25:46PM +, Biju Das wrote:
> > Document the RZ/G1N (R8A7744) LVDS bindings.
> >
> > Signed-off-by: Biju Das
>
> Reviewed-by: Laurent Pinchart
>
> and t
Variables declared in a switch statement before any case statements
cannot be initialized, so move all instances out of the switches.
After this, future always-initialized stack variables will work
and not throw warnings like this:
fs/fcntl.c: In function ‘send_sigio_to_task’:
fs/fcntl.c:738:13: w
On Thu, Dec 20, 2018 at 10:29 PM Jayant Shekhar wrote:
>
> Add interconnect properties such as the source and the destination
> ports for MDSS on SDM845.
>
> Signed-off-by: Jayant Shekhar
Reviewed-by: Evan Green
___
dri-devel mailing list
dri-devel@li
Hi Laurent,
On Thu, Jan 24, 2019 at 12:17:35AM +0200, Laurent Pinchart wrote:
> Hello Dmity,
>
> On Wed, Jan 23, 2019 at 02:03:42PM -0800, Dmitry Torokhov wrote:
> > On Wed, Jan 23, 2019 at 09:45:56AM +0100, Lukas Wunner wrote:
> > > On Tue, Jan 22, 2019 at 06:13:11AM -0800, Ronald Tschalär wrote
On Tue, Jan 22, 2019 at 07:07:51PM +0200, Laurent Pinchart wrote:
> Hi Biju,
>
> Thank you for the patch.
>
> On Tue, Jan 22, 2019 at 03:25:48PM +, Biju Das wrote:
> > Add du node to r8a7744 SoC DT. Boards that want to enable the DU
> > need to specify the output topology.
> >
> > Signed-off
Hi Laurent,
On Tue, Jan 22, 2019 at 11:10:28PM +0200, Laurent Pinchart wrote:
>
> Thank you for the patch.
>
> On Tue, Jan 22, 2019 at 06:13:11AM -0800, Ronald Tschalär wrote:
> > commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge:
>
> Commits are usually quoted using the short 12 d
On Thu, Jan 24, 2019 at 8:18 AM Matthew Wilcox wrote:
>
> On Wed, Jan 23, 2019 at 04:17:30PM +0200, Jani Nikula wrote:
> > Can't have:
> >
> > switch (i) {
> > int j;
> > case 0:
> > /* ... */
> > }
> >
> > because it can't be turned into:
> >
> >
23.01.2019 17:04, Thierry Reding пишет:
> On Wed, Jan 23, 2019 at 04:41:44PM +0300, Dmitry Osipenko wrote:
>> 23.01.2019 12:39, Thierry Reding пишет:
>>> From: Thierry Reding
>>>
>>> On Tegra186 and later, the ARM SMMU provides an input address space that
>>> is 48 bits wide. However, memory clien
Hi Laurent,
On Wed, Jan 23, 2019 at 11:55:52AM +0200, Laurent Pinchart wrote:
> Hi Simon,
>
> On Wed, Jan 23, 2019 at 09:56:57AM +0100, Simon Horman wrote:
> > On Wed, Jan 23, 2019 at 12:54:04AM +0200, Laurent Pinchart wrote:
> > > The LVDS1 encoder must supply a pixel clock to the DU for the DPA
On Wed, Jan 23, 2019 at 09:45:56AM +0100, Lukas Wunner wrote:
> On Tue, Jan 22, 2019 at 06:13:11AM -0800, Ronald Tschalär wrote:
> > commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge:
> > sil_sii8620: do not have a dependency of RC_CORE) added a dependency on
> > INPUT. However, this caus
23.01.2019 12:39, Thierry Reding пишет:
> From: Thierry Reding
>
> Move initialization of the shared IOMMU domain after the host1x device
> has been initialized. At this point all the Tegra DRM clients have been
> attached to the shared IOMMU domain.
>
> This is important because Tegra186 and la
23.01.2019 17:04, Thierry Reding пишет:
> On Wed, Jan 23, 2019 at 04:41:44PM +0300, Dmitry Osipenko wrote:
>> 23.01.2019 12:39, Thierry Reding пишет:
>>> From: Thierry Reding
>>>
>>> On Tegra186 and later, the ARM SMMU provides an input address space that
>>> is 48 bits wide. However, memory clien
On Wed, 23 Jan 2019 at 17:44, Christoph Hellwig wrote:
>
> I think we just want a driver-local check for those combinations
> where we know this hack actually works, which really just seems
> to be x86-64 with PAT. Something like the patch below, but maybe with
> even more strong warnings to not d
> On Jan 23, 2019, at 5:09 AM, Jann Horn wrote:
>
> AFAICS this only applies to switch statements (because they jump to a
> case and don't execute stuff at the start of the block), not blocks
> after if/while/... .
It bothers me that we are going out of our way to deprecate valid C constructs
https://bugs.freedesktop.org/show_bug.cgi?id=109444
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109445
--- Comment #3 from Michel Dänzer ---
*** Bug 109444 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing lis
On Wed, Jan 23, 2019 at 11:21:25PM -0800, Life is hard, and then you die wrote:
> Since the two changes (the change here + the new driver) seem to be
> best submitted through different trees, I'm trying to figure out how
> best to handle this. I suppose I could temporarily change the driver
> Kconf
Am 24.01.19 um 10:13 schrieb Christoph Hellwig:
> On Wed, Jan 23, 2019 at 05:52:50PM +0100, Ard Biesheuvel wrote:
>> But my concern is that it seems likely that non-cache coherent
>> implementations are relying on this hack as well. There must be a
>> reason that this hack is only disabled for Powe
On 2019-01-23 5:52 p.m., Ard Biesheuvel wrote:
> On Wed, 23 Jan 2019 at 17:44, Christoph Hellwig wrote:
>>
>> I think we just want a driver-local check for those combinations
>> where we know this hack actually works, which really just seems
>> to be x86-64 with PAT. Something like the patch below
On Thu, Jan 24, 2019 at 09:56:51AM +1300, Christopher James Halse Rogers wrote:
> On 24 January 2019 6:18:32 am NZDT, Emil Velikov
> wrote:
> >On Wed, 23 Jan 2019 at 04:39, Christopher James Halse Rogers
> > wrote:
> >>
> >> We can't use drmSetMaster to query whether or not a drm fd is master
> >
Am 24.01.19 um 10:28 schrieb Ard Biesheuvel:
> On Thu, 24 Jan 2019 at 10:25, Koenig, Christian
> wrote:
>> Am 24.01.19 um 10:13 schrieb Christoph Hellwig:
>>> On Wed, Jan 23, 2019 at 05:52:50PM +0100, Ard Biesheuvel wrote:
But my concern is that it seems likely that non-cache coherent
im
On Wed, Jan 23, 2019 at 06:00:15PM +0100, Sam Ravnborg wrote:
> Hi Daniel.
>
> On Thu, Jan 17, 2019 at 10:03:34PM +0100, Daniel Vetter wrote:
> > Having the probe helper stuff (which pretty much everyone needs) in
> > the drm_crtc_helper.h file (which atomic drivers should never need) is
> > confu
On Thu, Jan 24, 2019 at 07:11:53AM +, Zhang, Tina wrote:
>
>
> > -Original Message-
> > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel
> > Vetter
> > Sent: Wednesday, January 23, 2019 6:56 PM
> > To: Zhang, Tina
> > Cc: intel-...@lists.freedesktop.org; dri-d
On Wed, Jan 23, 2019 at 06:38:17PM +0200, Ville Syrjälä wrote:
> On Wed, Jan 23, 2019 at 03:49:02PM +0200, Imre Deak wrote:
> > On Mon, Nov 12, 2018 at 06:59:59PM +0200, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > On gen3 we must disable the TV encoder vertical filter for >1024
> >
On 23.1.2019 21.42, Dmitry Osipenko wrote:
23.01.2019 18:55, Dmitry Osipenko пишет:
23.01.2019 17:04, Thierry Reding пишет:
On Wed, Jan 23, 2019 at 04:41:44PM +0300, Dmitry Osipenko wrote:
23.01.2019 12:39, Thierry Reding пишет:
From: Thierry Reding
On Tegra186 and later, the ARM SMMU provi
On Wed, Jan 23, 2019 at 11:54:07AM +0100, Noralf Trønnes wrote:
>
>
> Den 22.01.2019 20.30, skrev Daniel Vetter:
> > On Tue, Jan 22, 2019 at 8:07 PM Noralf Trønnes wrote:
> >>
> >>
> >>
> >> Den 22.01.2019 10.32, skrev Daniel Vetter:
> >>> On Mon, Jan 21, 2019 at 01:21:46PM +0100, Noralf Trønnes
On Friday, January 18, 2019 1:57:47 PM CET Daniel Vetter wrote:
> On Fri, Jan 18, 2019 at 12:38 PM Rafael J. Wysocki wrote:
> >
> > On Fri, Jan 18, 2019 at 12:17 PM Rafael J. Wysocki
> > wrote:
> > >
> > > On Fri, Jan 18, 2019 at 12:06 PM Daniel Vetter wrote:
> > > >
> > > > On Fri, Jan 18, 201
Hi all,
In commit
0f7555121609 ("drm/i915/gvt: release shadow batch buffer and wa_ctx before
destroy one workload")
Fixes tag
Fixes: 0cce2823ed37 ("drm/i915/gvt/kvmgt:Refine error handling for
prepare_execlist_workload")
has these problem(s):
- Subject does not match target commit sub
Am 24.01.19 um 10:59 schrieb Ard Biesheuvel:
> [SNIP]
> This is *exactly* my point the whole time.
>
> The current code has
>
> static inline bool drm_arch_can_wc_memory(void)
> {
> #if defined(CONFIG_PPC) && !defined(CONFIG_NOT_COHERENT_CACHE)
> return false;
>
> which means the optimization i
I see a few cleanups on Patch #3 which actually belong in patch #1:
> +void drm_sched_stop(struct drm_gpu_scheduler *sched, struct
> drm_sched_job *bad)
The "bad" job parameter actually isn't used any more, isn't it?
> +retry_wait:
Not used any more.
But apart from that at least patch #1 and #2
On Thu, 24 Jan 2019, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 0f7555121609 ("drm/i915/gvt: release shadow batch buffer and wa_ctx before
> destroy one workload")
>
> Fixes tag
>
> Fixes: 0cce2823ed37 ("drm/i915/gvt/kvmgt:Refine error handling for
> prepare_execlist_workload")
>
>
Am 24.01.19 um 12:26 schrieb Ard Biesheuvel:
> On Thu, 24 Jan 2019 at 12:23, Koenig, Christian
> wrote:
>> Am 24.01.19 um 10:59 schrieb Ard Biesheuvel:
>>> [SNIP]
>>> This is *exactly* my point the whole time.
>>>
>>> The current code has
>>>
>>> static inline bool drm_arch_can_wc_memory(void)
>>>
Hi heiko and thomas,
the SPDX license identifier is updated by the following patch, please
help to review, thanks.
https://patchwork.kernel.org/patch/10776935/
在 2019/1/18 下午8:34, Heiko Stuebner 写道:
Hi Thomas,
Am Freitag, 18. Januar 2019, 01:40:03 CET schrieb Thomas Gleixner:
On Thu, 30 Au
Hi Jerome,
This patch seems to have plenty of Cc:s, but none of the right ones :)
For further iterations, I guess you could use git option --cc to make
sure everyone gets the whole series, and still keep the Cc:s in the
patches themselves relevant to subsystems.
This doesn't seem to be on top of
Am 24.01.19 um 13:06 schrieb Ard Biesheuvel:
> The DRM driver stack is designed to work with cache coherent devices
> only, but permits an optimization to be enabled in some cases, where
> for some buffers, both the CPU and the GPU use uncached mappings,
> removing the need for DMA snooping and all
https://bugs.freedesktop.org/show_bug.cgi?id=108916
--- Comment #2 from smoki ---
I can't reproduce this on CIK (Kabini) using provided trace.
So, this sounds like hardware specific bug somewhere, probably llvm.
--
You are receiving this mail because:
You are the assignee for the bug.__
On Thu, Jan 24, 2019 at 10:46:47AM +0100, Daniel Vetter wrote:
> On Wed, Jan 23, 2019 at 06:00:15PM +0100, Sam Ravnborg wrote:
> > Hi Daniel.
> >
> > On Thu, Jan 17, 2019 at 10:03:34PM +0100, Daniel Vetter wrote:
> > > Having the probe helper stuff (which pretty much everyone needs) in
> > > the d
Allow to compile-test imx-drm on other platforms.
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/imx/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/imx/Kconfig b/drivers/gpu/drm/imx/Kconfig
index c55428490e56..c3c84a09e628 100644
--- a/drivers/gpu/d
Since the TVE provides a clock to the DI, the driver can only be
compiled if the common clock framework is enabled. With the COMMON_CLK
dependency in place, it will be possible to allow building the other
parts of imx-drm under COMPILE_TEST on architectures that do not select
the common clock frame
https://bugzilla.kernel.org/show_bug.cgi?id=201727
Michal Herko (misko.he...@gmail.com) changed:
What|Removed |Added
Status|REOPENED|RESOLVED
R
From: Lucas Stach
Currently there is a small race window where we could manage to arm the
vblank event from atomic flush, but programming the hardware was too close
to the frame end, so the hardware will only apply the current state on the
next vblank. In this case we will send out the commit don
Hi Dave & Daniel -
Just a couple of fixes. Late again this week, sorry, but nothing that
can't wait until next rc either.
BR,
Jani.
The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:
Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)
are available in the Git repository at:
On 24.1.2019 15.15, Dmitry Osipenko wrote:
24.01.2019 13:24, Mikko Perttunen пишет:
On 23.1.2019 21.42, Dmitry Osipenko wrote:
23.01.2019 18:55, Dmitry Osipenko пишет:
23.01.2019 17:04, Thierry Reding пишет:
On Wed, Jan 23, 2019 at 04:41:44PM +0300, Dmitry Osipenko wrote:
23.01.2019 12:39, T
The 2019 X.Org Foundation elections are rapidly approaching. We will be
forwarding the nominating process to the membership shortly. Please find the
election schedule below.
Please note that only current members can vote in the upcoming election, and
that the deadline for new memberships or ren
On Thu, Jan 24, 2019 at 6:45 AM Ard Biesheuvel
wrote:
>
> On Thu, 24 Jan 2019 at 12:37, Koenig, Christian
> wrote:
> >
> > Am 24.01.19 um 12:26 schrieb Ard Biesheuvel:
> > > On Thu, 24 Jan 2019 at 12:23, Koenig, Christian
> > > wrote:
> > >> Am 24.01.19 um 10:59 schrieb Ard Biesheuvel:
> > >>> [
On Thu, Jan 24, 2019 at 8:57 AM Ard Biesheuvel
wrote:
>
> On Thu, 24 Jan 2019 at 14:54, Alex Deucher wrote:
> >
> > On Thu, Jan 24, 2019 at 6:45 AM Ard Biesheuvel
> > wrote:
> > >
> > > On Thu, 24 Jan 2019 at 12:37, Koenig, Christian
> > > wrote:
> > > >
> > > > Am 24.01.19 um 12:26 schrieb Ard
On Thu, Jan 24, 2019 at 9:00 AM Ard Biesheuvel
wrote:
>
> On Thu, 24 Jan 2019 at 13:31, Koenig, Christian
> wrote:
> >
> > Am 24.01.19 um 13:06 schrieb Ard Biesheuvel:
> > > The DRM driver stack is designed to work with cache coherent devices
> > > only, but permits an optimization to be enabled
On Sat, Jan 19, 2019 at 09:40:14AM +0100, Sam Ravnborg wrote:
> With the removal of drmP.h from drm_modeset_helper.h
> the drmP.h are no longer included by any include files
> in include/drm.
> The drmP.h file is thus only included explicit
> either in .c files or in local .h files.
> This makes th
https://bugs.freedesktop.org/show_bug.cgi?id=108260
--- Comment #12 from Alex Deucher ---
(In reply to Martin Jørgensen from comment #11)
> Running on debian buster with 4.19 kernel I get the same warning, but only
> this warning. No errors regarding the GPU.
>
> Will there be a patch for 4.19,
[cc:Hans]
Den 21.01.2019 10.22, skrev Daniel Vetter:
> On Sun, Jan 20, 2019 at 12:43:10PM +0100, Noralf Trønnes wrote:
>> This adds a function that creates a simple connector that has only one
>> static mode. Additionally add a helper to set &drm_mode_config width
>> and height from the static mod
Note that you will have to re-register in the new system. Your previous
credentials won't work.
Harry
On 2019-01-24 8:42 a.m., Wentland, Harry wrote:
> The 2019 X.Org Foundation elections are rapidly approaching. We will be
> forwarding the nominating process to the membership shortly. Please f
On Thu, Jan 24, 2019 at 03:03:20PM +0100, Daniel Vetter wrote:
> On Sat, Jan 19, 2019 at 09:40:14AM +0100, Sam Ravnborg wrote:
> > With the removal of drmP.h from drm_modeset_helper.h
> > the drmP.h are no longer included by any include files
> > in include/drm.
> > The drmP.h file is thus only inc
On Wed, 23 Jan 2019 at 11:26, Emil Velikov wrote:
>
> On Wed, 23 Jan 2019 at 11:04, Eric Engestrom wrote:
> >
> > On Wednesday, 2019-01-23 10:45:17 +, Emil Velikov wrote:
> > > From: Emil Velikov
> > >
> > > Some devices can lack OF data or it may not be available in the uevent
> > > file. F
Hi,
On 24-01-19 15:38, Noralf Trønnes wrote:
[cc:Hans]
Den 21.01.2019 10.22, skrev Daniel Vetter:
On Sun, Jan 20, 2019 at 12:43:10PM +0100, Noralf Trønnes wrote:
This adds a function that creates a simple connector that has only one
static mode. Additionally add a helper to set &drm_mode_conf
On Tue, 2018-10-30 at 10:15 +0100, Heiko Stuebner wrote:
> From: Nickey Yang
>
> Support Kingdisplay kd097d04 9.7" 1536x2048 TFT LCD panel,
> it is a MIPI dual-DSI panel.
>
> v4-resend:
> - Thierry noted missing dt-bindings for v4 but forgot that he
> already had applied them one kernel releas
Hi Andrew,
On Wed, Jan 23, 2019 at 01:28:35PM -0600, Andrew F. Davis wrote:
> Previously the heap to allocate from was selected by a mask of allowed
> heap types. This may have been done as a primitive form of constraint
> solving, the first heap type that matched any set bit of the heap mask
> wa
OK, I will update patches 1 and 2 and given your RBs push them since
they fix some races. I will then update and test patch 3 on some basic
scenarios and will send it for separate review where I might put a TODO
comment in code with my objections regarding long jobs form our
discussion so you c
On Thu, Jan 24, 2019 at 02:09:12PM +0200, Joonas Lahtinen wrote:
> Hi Jerome,
>
> This patch seems to have plenty of Cc:s, but none of the right ones :)
So sorry, i am bad with git commands.
> For further iterations, I guess you could use git option --cc to make
> sure everyone gets the whole se
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #43 from Jerry Zuo ---
We observed MST cannot light up in every reboot since 4.20, and we've already
got the reboot/poweroff sequence fixed. The fix will show up soon ...
--
You are receiving this mail because:
You are the assignee
On 1/23/19 11:11 AM, Brian Starkey wrote:
> Hi Andrew,
>
> On Wed, Jan 23, 2019 at 10:51:24AM -0600, Andrew F. Davis wrote:
>> On 1/22/19 11:33 AM, Sumit Semwal wrote:
>>> Hello everyone,
>>>
>>> Sincere apologies for chiming in a bit late here, but was off due to
>>> some health issues.
>>>
>>
>>
On 2019-01-24 12:45 p.m., Ard Biesheuvel wrote:
> On Thu, 24 Jan 2019 at 12:37, Koenig, Christian
> wrote:
>> Am 24.01.19 um 12:26 schrieb Ard Biesheuvel:
>>> On Thu, 24 Jan 2019 at 12:23, Koenig, Christian
>>> wrote:
Am 24.01.19 um 10:59 schrieb Ard Biesheuvel:
> [SNIP]
> This is *e
On 1/24/19 9:24 AM, Brian Starkey wrote:
> Hi Andrew,
>
> On Wed, Jan 23, 2019 at 01:28:35PM -0600, Andrew F. Davis wrote:
>> Previously the heap to allocate from was selected by a mask of allowed
>> heap types. This may have been done as a primitive form of constraint
>> solving, the first heap t
Ping
On Sun, Dec 16, 2018 at 10:39 PM Fabio Estevam wrote:
>
> Hi Thierry,
>
> On Tue, Dec 4, 2018 at 2:57 PM Fabio Estevam wrote:
> >
> > Add support for the VXT VL050-8048NT-C01 800x480 panel to the
> > panel-simple driver.
> >
> > This panel is used on some boards manufactured by TechNexion,
On Thu, Jan 24, 2019 at 12:01:55PM -0300, Ezequiel Garcia wrote:
> On Tue, 2018-10-30 at 10:15 +0100, Heiko Stuebner wrote:
> > From: Nickey Yang
> >
> > Support Kingdisplay kd097d04 9.7" 1536x2048 TFT LCD panel,
> > it is a MIPI dual-DSI panel.
> >
> > v4-resend:
> > - Thierry noted missing dt-
On Thu, Jan 24, 2019 at 10:04:46AM -0600, Andrew F. Davis wrote:
> On 1/23/19 11:11 AM, Brian Starkey wrote:
[snip]
>
> I'm very new to all this, so any pointers to history in this area are
> appreciated.
>
[snip]
>
> > In case you didn't come across it already, the effort which seems to
> >
There have been a bunch of sign-ups without names which makes for a confusing
list on https://members.x.org/members
If you get chance please update your name and affiliation in your profile
(username > Your Profile).
Harry
On 2019-01-24 9:42 a.m., Wentland, Harry wrote:
> Note that you will ha
On Thu, Jan 24, 2019 at 10:12:10AM -0600, Andrew F. Davis wrote:
> On 1/24/19 9:24 AM, Brian Starkey wrote:
[snip]
> >
> > What do you think about renaming ion_allocation_data.unused to heap_id
> > and adding a flag instead? It's adding cruft to a staging API, but it
> > might soften the transit
The fbdev split between fix and var information is kinda
pointless for drm drivers since everything is fixed: The fbdev
emulation doesn't support changing modes at all.
Create a new simplified helper and use it in the generic fbdev
helper code. Follow-up patches will beef it up more and roll
it ou
This is only used by drm_irq_install(), which is an optional helper.
And the right choice is to set it for all pci devices, and not for
everything else.
Any driver with special needs should just use request_irq() directly,
and there's plenty of drivers doing that already.
Signed-off-by: Daniel Ve
If a non-legacy driver calls these it's valid to assume there is
interrupt support. The flag is really only needed for legacy drivers.
Also remove all the flag usage from non-legacy drivers.
Signed-off-by: Daniel Vetter
Cc: linux-arm-ker...@lists.infradead.org
Cc: intel-...@lists.freedesktop.org
The fbdev emulation helpers pretty much assume that this is set.
Let's do it for everyone.
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_fb_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
index
Only changes the name of the fb from "armada-drmfb" to armadafb.
Signed-off-by: Daniel Vetter
Cc: Russell King
---
drivers/gpu/drm/armada/armada_fbdev.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/armada/armada_fbdev.c
b/drivers/gpu/drm/armada/armad
Should not result in any changes.
Signed-off-by: Daniel Vetter
Cc: Alex Deucher
Cc: Junwei Zhang
Cc: Xinliang Liu
Cc: "Christian König"
Cc: Ajit Negi
Cc: Souptick Joarder
Cc: Daniel Vetter
Cc: John Garry
---
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 2 +-
drivers/gpu/drm/hisili
1 - 100 of 212 matches
Mail list logo
