Am 08.06.2018 um 08:02 schrieb Christoph Hellwig:
On Thu, Jun 07, 2018 at 02:32:46PM +0200, Gabriel C wrote:
Ok done.. bisect points to:
What is the failure mode you are seeing? Can't find anything in the
mail unfortunately.
As far as I analyzed it we now get an -ENOMEM from dma_alloc_attrs(
Hi Christoph,
Am 08.06.2018 um 08:01 schrieb Christoph Hellwig:
On Thu, Jun 07, 2018 at 07:20:37PM +0200, Christian König wrote:
Hi Christopher,
I don't see a Christopher on the Cc list..
Sorry, auto-uncorrection. I indeed meant you :)
Christian.
Am 08.06.2018 um 06:36 schrieb Souptick Joarder:
On Sat, Jun 2, 2018 at 12:57 AM, Souptick Joarder wrote:
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_fau
Call the devfreq_remove_device() API to remove the GPU devfreq instance
during GPU driver cleanup.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/msm_gpu.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/msm/msm_gpu.c b/drivers/gpu/drm/msm/msm_gpu.c
index ffa5b77..c9
This series re-factors the devfreq code a bit in preparation for the upcoming
A6x related devfreq changes. The code applies cleanly on 4.17 and has been
verified on DB820C.
V2: Addressed code review comments from Jordan Crouse.
V3: Added a new patch for devfreq cleanup.
V4: removed "drm/msm: move
Devfreq turns on and starts recommending power level as soon as it is
initialized. The GPU is still not powered on by the time the devfreq
init happens and this leads to problems on GPU's where register access
is needed to get/set power levels. So we start suspended and only restart
devfreq when GP
devfreq framework requires the drivers to provide busy time estimations.
The GPU driver relies on the hardware performance counters for the busy time
estimations, but different hardware revisions have counters which can be
sourced from different clocks. So the busy time estimation will be target
de
Hi,
On 22/05/18 21:13, Souptick Joarder wrote:
> 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 1c
https://bugzilla.kernel.org/show_bug.cgi?id=199979
Bug ID: 199979
Summary: amdgpu: changing pwm1_enable from 1 to 2 does not
resume automatic fan control
Product: Drivers
Version: 2.5
Kernel Version: 4.17.0
Hardware: Al
There is no need to flip reset pin twice. Also delays can be changed to
values present in vendor's code.
Signed-off-by: Andrzej Hajda
---
Hi,
This is v2 of forgotten patch, awaiting reviewers, any volunteers.
Also "drm/bridge/sii8620: fix loops in EDID fetch logic" waits for reviewers.
In this
On Thu, Jun 07, 2018 at 02:32:46PM +0200, Gabriel C wrote:
> Ok done.. bisect points to:
What is the failure mode you are seeing? Can't find anything in the
mail unfortunately.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.fre
On Thu, Jun 07, 2018 at 07:20:37PM +0200, Christian König wrote:
> Hi Christopher,
I don't see a Christopher on the Cc list..
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
This patch adds a simple helper function to help write 64 bit payloads
to the ringbuffer.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 12
drivers/gpu/drm/msm/adreno/a5xx_power.c | 3 +--
drivers/gpu/drm/msm/msm_ringbuffer.h| 6 ++
3 files ch
https://bugzilla.kernel.org/show_bug.cgi?id=199959
--- Comment #4 from Alexander Mezin (mezin.alexan...@gmail.com) ---
Commit d6895ad39f3b396be199f5b6fdfb8cde4be7bbf7 seems to be the cause. Resume
works on 4.16 if I revert that single commit (tested on 4.16.0, 4.16.13, with
both amdgpu.dc=0 and am
https://bugs.freedesktop.org/show_bug.cgi?id=106430
--- Comment #8 from mikhail.v.gavri...@gmail.com ---
Created attachment 140078
--> https://bugs.freedesktop.org/attachment.cgi?id=140078&action=edit
fresh dmesg from kernel 4.18.0-0.rc0.git2.1
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=106289
--- Comment #4 from Dave Coffin ---
Thanks, Roland's patch fixed the mupen64plus crash but not the mplayer crash,
which happens in libvdpau_r300.so.1 I don't know where the source code for
that file is; it's not in mesa-18.0.5 or in libvdpau-1.
On Thu, Jun 07, 2018 at 10:26:39AM +0100, Liviu Dudau wrote:
On Fri, May 25, 2018 at 04:32:38PM +0100, Brian Starkey wrote:
On Thu, May 24, 2018 at 05:41:01PM +0100, Liviu Dudau wrote:
> From: Brian Starkey
>
> Writeback connectors represent writeback engines which can write the
> CRTC output t
Am Donnerstag, 7. Juni 2018, 23:10:20 CEST schrieb Brian Norris:
> Hi,
>
> I only have a little bit to add, but Heiko did solicit my opinion.
yep ... and I realized that I am/was way to attached to my (working)
endpoint-based thingy to really appreciate the other arguments ;-)
And your DSI-relat
Hi,
I only have a little bit to add, but Heiko did solicit my opinion.
On Thu, Jun 07, 2018 at 03:25:18PM +0200, Heiko Stuebner wrote:
> Am Donnerstag, 7. Juni 2018, 12:39:03 CEST schrieb Andrzej Hajda:
> > On 07.06.2018 01:08, Heiko Stuebner wrote:
> > > Am Mittwoch, 6. Juni 2018, 18:07:46 CEST
Hi Jani
thanks for pointing it out.
I have fixed it and uploaded v4.
Abhinav
On 2018-06-07 05:19, Jani Nikula wrote:
On Fri, 01 Jun 2018, Abhinav Kumar wrote:
Make the pclk_rate u64 to accommodate higher pixel clock
rates.
Changes in v3:
- Rebased on top of https://patchwork.kernel.org/pat
Make the pclk_rate u64 to accommodate higher pixel clock
rates.
Changes in v4:
- fixed commit message
Signed-off-by: Abhinav Kumar
---
drivers/gpu/drm/msm/dsi/dsi_host.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c
b/drivers/g
On Tue, Jun 05, 2018 at 08:45:33PM -0700, Jeykumar Sankaran wrote:
> This change removes all the dpu plane custom properties
> and its handlers.
>
> changs in v2:
> - remove stale code in blend config(Sean Paul)
> - Makefile changes to remove warning flags(Sean Paul)
>
> Signed-off-by
Make the pclk_rate u64 to accommodate higher pixel clock
rates.
Changes in v4:
- fixed commit message
Signed-off-by: Abhinav Kumar
---
drivers/gpu/drm/msm/dsi/dsi_host.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c
b/drivers/g
On Tue, Jun 05, 2018 at 08:45:31PM -0700, Jeykumar Sankaran wrote:
> Submitting a series of patches to further clean up DPU driver by stripping
> down a list of custom properties supporting proprietary features. It
> removes the property installers/handlers and cleans up relevant files of
> of som
From: Jérôme Glisse
This ghost file have been haunting us.
Signed-off-by: Jérôme Glisse
---
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/gp10b. | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 drivers/gpu/drm/nouveau/nvkm/subdev/mmu/gp10b.
diff --git a/drivers/gpu/drm/nouve
Hi,
When we talk about control bus enable and video transfer enable for DSI, there
is a mode in which control commands can be sent, interleaved with the video.
This is often done at the end-of-frame and/or end of line. I've seen this
handled in some other DSI device drivers. In these cases,
Hi Christopher,
Am 07.06.2018 um 18:24 schrieb Gabriel C:
[SNIP]
Ok done.. bisect points to:
b468620f2a1dfdcfddfd6fa54367b8bcc1b51248 is the first bad commit
commit b468620f2a1dfdcfddfd6fa54367b8bcc1b51248
Author: Christoph Hellwig
Date: Mon Mar 19 11:38:19 2018 +0100
iommu/amd_iommu: U
Use recently introduced common helpers to unify GEM handling code.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_fb.c | 10 --
drivers/gpu/drm/exynos/exynos_drm_ipp.c | 10 +-
2 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm
drm_gem_object_unreference() function is just a compatibility alias for
drm_gem_object_put() and should not be used by the new code, so convert
all users of compatibility functions to use the new API.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_gem.c | 4 ++--
1 file ch
Replace all calls to exynos_drm_gem_get_{dma_addr,size}, by a simpler
function exynos_drm_gem_get(). This lets the caller to get access to
exynos_drm_gem object and extract any information about GEM object
without searching object tree for getting each parameter.
Signed-off-by: Marek Szyprowski
-
Exynos G2D driver is the last client of the custom Exynos 'sub-driver'
framework. In the current state it doesn't really resolve any of the
issues it has been designed for, as Exynos DRM is already built only
as a single kernel module. Remove the custom 'sub-driver' framework and
simply use generic
Dear all,
This patchset performs a significant cleanup of Exynos DRM code. This
includes the following 2 big items:
- the custom 'sub-driver' framework has been finally replaced by generic
device component code;
- access to exynos GEM object has been simplified and unified.
Best regards
Marek S
Hi Andrzej,
Am Donnerstag, 7. Juni 2018, 12:39:03 CEST schrieb Andrzej Hajda:
> On 07.06.2018 01:08, Heiko Stuebner wrote:
> > Am Mittwoch, 6. Juni 2018, 18:07:46 CEST schrieb Archit Taneja:
> >> On Wednesday 06 June 2018 04:16 PM, Heiko Stübner wrote:
> >>> Hi Archit,
> >>>
> >>> Am Mittwoch, 6.
On Fri, 01 Jun 2018, Abhinav Kumar wrote:
> Make the pclk_rate u64 to accommodate higher pixel clock
> rates.
>
> Changes in v3:
> - Rebased on top of https://patchwork.kernel.org/patch/10348865/
>
> Signed-off-by: Abhinav Kumar
Please have a look at the output of
$ git log --pretty=%s -- driv
Hi Ville,
On Thursday, 7 June 2018 15:03:12 EEST Ville Syrjälä wrote:
> On Wed, Jun 06, 2018 at 12:08:12PM +0300, Laurent Pinchart wrote:
> > The drm_connector_helper_funcs .mode_valid() operation should not modify
> > the mode it receives in any way. To make this explicit, constify the
> > mode p
On 07/06/18 15:03, Ville Syrjälä wrote:
> On Wed, Jun 06, 2018 at 12:08:12PM +0300, Laurent Pinchart wrote:
>> The drm_connector_helper_funcs .mode_valid() operation should not modify
>> the mode it receives in any way. To make this explicit, constify the
>> mode pointer as done for all other .mode
On Wed, Jun 06, 2018 at 12:08:12PM +0300, Laurent Pinchart wrote:
> The drm_connector_helper_funcs .mode_valid() operation should not modify
> the mode it receives in any way. To make this explicit, constify the
> mode pointer as done for all other .mode_valid() operations, and update
> all drivers
The only bits that should be preserved in decon_win_set_fmt() is
WINCONx_ENWIN_F. All other bits depends on the selected pixel formats and
are set by the mentioned function.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 2 +-
1 file changed, 1 insertion(+),
Investigation revealed that GScaler hardware requires the real buffer width
(pitch) to be aligned to 16 pixels.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_gsc.c
Set per-plane global alpha to maximum value to get proper blending of
XRGB and ARGB planes. This fixes the strange order of overlapping planes.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Prepare a common function for size and scale checks and call it for
source and destination buffers. Then also move there the state-less checks
from exynos_drm_ipp_task_setup_buffer, so the format information is already
available in limits processing. Finally perform the IPP_LIMIT_BUFFER check
on th
DMA hardware should respect buffer pitch, so use the width calculated from
the buffer pitch instead of the virtual one.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/
Dear all,
This patchset is a result of running various tests of Exynos DRM IPP
modules. It turned out that some drivers incorrectly interpreted
real buffer width (calculated from buffer pitch), had swapped horizontal
and vertial flips or used incorrect variant of the YUV modes. This
patchset fixes
Horizontal (DRM_MODE_REFLECT_Y) and vertical (DMR_MODE_REFLECT_Y) flip
were swapped in GScaler driver. Fix this by swapping code for interpreting
them.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 16
1 file changed, 8 insertions(+), 8 deletions(
Horizontal (DRM_MODE_REFLECT_Y) and vertical (DMR_MODE_REFLECT_Y) flip
were swapped in Rotator driver. Fix this by swapping code for interpreting
them.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_rotator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Fix Cb/CR components order in two-planar YUV420, YUV422 and YUV444 modes.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_scaler.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_scaler.c
b/drivers/gpu/drm/
Fix following issues related to planar YUV pixel format configuration:
- NV16/61 modes were incorrectly programmed as NV12/21,
- YVU420 was programmed as YUV420 on source,
- YVU420 and YUV422 were programmed as YUV420 on output.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_d
DMA hardware should respect buffer pitch, so use the width calculated from
the buffer pitch instead of the virtual one.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exyno
From: Andrzej Pietrasiewicz
Ensure that Scaler hardware is properly reset and interrupts are cleared
before processing next image.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_scaler.c | 32 --
1 file changed, 2
On 07.06.2018 01:08, Heiko Stuebner wrote:
> Am Mittwoch, 6. Juni 2018, 18:07:46 CEST schrieb Archit Taneja:
>> On Wednesday 06 June 2018 04:16 PM, Heiko Stübner wrote:
>>> Hi Archit,
>>>
>>> Am Mittwoch, 6. Juni 2018, 12:21:16 CEST schrieb Archit Taneja:
On Wednesday 06 June 2018 02:00 PM, He
On Wed, Jun 06, 2018 at 01:18:31PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The current use of result is or'ing in values and checking for
> a non-zero result, however, result is not initialized to zero
> so it potentially contains garbage to start with. Fix this by
> initializing it t
On 06.06.2018 21:04, Eric Anholt wrote:
> For DSI, we want to pre_enable once the DSI link is up but before
> video packets are being sent, and similarly we want to be able to
> post_disable while the link is still up but after video has stopped.
>
> Given that with drm_panels we've had issues with
On Fri, May 25, 2018 at 04:32:38PM +0100, Brian Starkey wrote:
> On Thu, May 24, 2018 at 05:41:01PM +0100, Liviu Dudau wrote:
> > From: Brian Starkey
> >
> > Writeback connectors represent writeback engines which can write the
> > CRTC output to a memory framebuffer. Add a writeback connector typ
https://bugs.freedesktop.org/show_bug.cgi?id=106846
--- Comment #4 from Tim Carr ---
Created attachment 140064
--> https://bugs.freedesktop.org/attachment.cgi?id=140064&action=edit
dmesg with amdgpu.dc=0
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106846
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com
--- Comment #3 f
On 06/07/2018 12:48 AM, Boris Ostrovsky wrote:
On 06/06/2018 08:10 AM, Oleksandr Andrushchenko wrote:
On 06/05/2018 01:07 AM, Boris Ostrovsky wrote:
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
+
+static struct sg_table *
+dmabuf_exp_ops_map_dma_buf(struct dma_buf_attachment *attac
Am Mittwoch, den 06.06.2018, 10:48 -0700 schrieb Eric Anholt:
> Between creation and queueing of a job, you need to prevent any other
> job from being created and queued. Otherwise the scheduler's fences
> may be signaled out of seqno order.
>
> v2: move mutex unlock to the error label.
>
> > Si
https://bugs.freedesktop.org/show_bug.cgi?id=106846
--- Comment #2 from Tim Carr ---
Created attachment 140062
--> https://bugs.freedesktop.org/attachment.cgi?id=140062&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=106846
--- Comment #1 from Tim Carr ---
Created attachment 140061
--> https://bugs.freedesktop.org/attachment.cgi?id=140061&action=edit
Xorg.log
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=106846
Bug ID: 106846
Summary: RX480 with multiple HDMI ports shows monitor connected
to unused port when using amdgpu.dc=1
Product: DRI
Version: unspecified
Hardware: x86-64 (AM
https://bugzilla.kernel.org/show_bug.cgi?id=199959
Christian König (christian.koe...@amd.com) changed:
What|Removed |Added
CC||christian.koe
On 06/07/2018 01:05 AM, Dongwon Kim wrote:
On Wed, Jun 06, 2018 at 05:51:38PM -0400, Boris Ostrovsky wrote:
On 06/06/2018 08:46 AM, Oleksandr Andrushchenko wrote:
On 06/05/2018 01:36 AM, Boris Ostrovsky wrote:
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenk
On 06/07/2018 12:32 AM, Boris Ostrovsky wrote:
On 06/06/2018 05:06 AM, Oleksandr Andrushchenko wrote:
On 06/04/2018 11:49 PM, Boris Ostrovsky wrote:
On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
+struct gntdev_dmabuf_export_args {
+ int dummy;
+};
Please define the full structure (
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #27 from Christian König ---
(In reply to Ben Crocker from comment #26)
> foxbat, thanks for posting this!
>
> > [ 175.501965] [drm] size=167768376 > sa_manager->size=1048576
>
> Well, isn't THAT interesting!
> Requested size is A
Am 06.06.2018 um 17:44 schrieb Gabriel C:
2018-06-06 17:03 GMT+02:00 Michel Dänzer :
On 2018-06-06 04:44 PM, Christian König wrote:
Am 06.06.2018 um 16:12 schrieb Michel Dänzer:
[SNIP]
At least in theory it should work when we use the coherent DMA allocator.
When that really worked before, so
Dne ponedeljek, 04. junij 2018 ob 18:23:57 CEST je Maxime Ripard napisal(a):
> On Mon, Jun 04, 2018 at 05:09:56PM +0200, Jernej Škrabec wrote:
> > Dne ponedeljek, 04. junij 2018 ob 13:50:34 CEST je Maxime Ripard
napisal(a):
> > > On Fri, Jun 01, 2018 at 09:19:43AM -0700, Chen-Yu Tsai wrote:
> > >
On 06/06/2018 03:24 AM, Oleksandr Andrushchenko wrote:
> On 06/04/2018 07:37 PM, Boris Ostrovsky wrote:
>> On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
>>> diff --git a/include/xen/mem-reservation.h
>>> b/include/xen/mem-reservation.h
>>> new file mode 100644
>>> index ..a727d
Trivial fix to spelling mistake in tilcdc.txt devicetree documentation.
Signed-off-by: Enric Balletbo i Serra
---
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/tilcdc/tilc
On 06/06/2018 05:06 AM, Oleksandr Andrushchenko wrote:
> On 06/04/2018 11:49 PM, Boris Ostrovsky wrote:
>> On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
>> +struct gntdev_dmabuf_export_args {
>> + int dummy;
>> +};
>>
>> Please define the full structure (at least what you have in the n
On 06/06/2018 08:10 AM, Oleksandr Andrushchenko wrote:
> On 06/05/2018 01:07 AM, Boris Ostrovsky wrote:
>> On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
>> +
>> +static struct sg_table *
>> +dmabuf_exp_ops_map_dma_buf(struct dma_buf_attachment *attach,
>> + enum dma_data_di
On 06/06/2018 08:46 AM, Oleksandr Andrushchenko wrote:
> On 06/05/2018 01:36 AM, Boris Ostrovsky wrote:
>> On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
>>> From: Oleksandr Andrushchenko
>>>
>>> Allow creating grant device context for use by kernel modules which
>>> require functionality,
2018-04-11 7:02 GMT+02:00 Gabriel C :
>>2018-04-11 6:00 GMT+02:00 Gabriel C :
>> 2018-04-09 11:42 GMT+02:00 Christian König
>> :
>>> Am 07.04.2018 um 00:00 schrieb Jean-Marc Valin:
> ...
>> I can help testing code for 4.17/++ if you wish but that is *different*
>> storry.
>>
>
> Quick tested an 4
2018-06-06 17:03 GMT+02:00 Michel Dänzer :
> On 2018-06-06 04:44 PM, Christian König wrote:
>> Am 06.06.2018 um 16:12 schrieb Michel Dänzer:
>>> On 2018-06-06 03:33 PM, Gabriel C wrote:
2018-06-06 14:19 GMT+02:00 Christian König :
> Am 06.06.2018 um 14:08 schrieb Gabriel C:
>> 2018-06-
2018-06-06 14:19 GMT+02:00 Christian König :
> Am 06.06.2018 um 14:08 schrieb Gabriel C:
>>
>> 2018-06-06 13:33 GMT+02:00 Christian König :
>>>
>>> Am 06.06.2018 um 13:28 schrieb Gabriel C:
2018-04-11 7:02 GMT+02:00 Gabriel C :
>>
>> 2018-04-11 6:00 GMT+02:00 Gabriel C :
>> 20
2018-06-06 16:44 GMT+02:00 Christian König :
> Am 06.06.2018 um 16:12 schrieb Michel Dänzer:
>>
>> On 2018-06-06 03:33 PM, Gabriel C wrote:
>>>
>>> 2018-06-06 14:19 GMT+02:00 Christian König :
Am 06.06.2018 um 14:08 schrieb Gabriel C:
>
> 2018-06-06 13:33 GMT+02:00 Christian König
Hi Mikulas,
On Tue, 2018-06-05 at 11:30 -0400, Mikulas Patocka wrote:
>
> On Tue, 5 Jun 2018, Alexey Brodkin wrote:
>
> > Hi Mikulas,
> >
> > On Sun, 2018-06-03 at 16:41 +0200, Mikulas Patocka wrote:
> > > Modern processors can detect linear memory accesses and prefetch data
> > > automatically
On 06/06/2018 04:14 AM, Oleksandr Andrushchenko wrote:
> On 06/04/2018 11:12 PM, Boris Ostrovsky wrote:
>> On 06/01/2018 07:41 AM, Oleksandr Andrushchenko wrote:
>> @@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)
>> if (map == NULL)
>> return;
>> +#ifdef C
Title: Untitled document
Hello,
How are you?
We are the professional manufacture the SDI products for many years,
Our main produces is as below:
SDI Fiber Video converter
ASI fiber video converter
SDI Extender
SDI to HDMI Converter
…..
1CH 3G SDI/ASI fiber video converter, transmit 1ch 3G
2018-06-06 13:33 GMT+02:00 Christian König :
> Am 06.06.2018 um 13:28 schrieb Gabriel C:
>>
>> 2018-04-11 7:02 GMT+02:00 Gabriel C :
2018-04-11 6:00 GMT+02:00 Gabriel C :
2018-04-09 11:42 GMT+02:00 Christian König
:
>
> Am 07.04.2018 um 00:00 schrieb Jean-Marc Valin:
>>>
79 matches
Mail list logo
