> Hmm, the cross-device buffer sharing framework I have in mind would
> basically be a buffer registry. virtio-gpu would create buffers as
> usual, create a identifier somehow (details to be hashed out), attach
> the identifier to the dma-buf so it can be used as outlined above.
Using physical ad
Hi,
> That said, Chrome OS would use a similar model, except that we don't
> use ION. We would likely use minigbm backed by virtio-gpu to allocate
> appropriate secure buffers for us and then import them to the V4L2
> driver.
What exactly is a "secure buffer"? I guess a gem object where read
a
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59516/
Build log: https://builder.linuxtv.org/job/patchwork/20785/
Build time: 00:21:46
Link:
https://lore.kernel.org/linux-media/1074d944-de6e-7483-3337-ca9acd1b1...@xs4all.nl
gpg: Signature made Thu 17 Oct 2019 06:51:0
Hi,
> > Also note that the guest manages the address space, so the host can't
> > simply allocate guest page addresses.
>
> Is this really true? I'm not an expert in this area, but on a bare
> metal system it's the hardware or firmware that sets up the various
> physical address allocations on
On Tue, Oct 15, 2019 at 11:06 PM Dmitry Morozov
wrote:
>
> Hello Gerd,
>
> On Dienstag, 15. Oktober 2019 09:54:22 CEST Gerd Hoffmann wrote:
> > On Mon, Oct 14, 2019 at 03:05:03PM +0200, Dmitry Morozov wrote:
> > > On Montag, 14. Oktober 2019 14:34:43 CEST Gerd Hoffmann wrote:
> > > > Hi,
> > > >
On Thu, Oct 17, 2019 at 4:19 PM Gerd Hoffmann wrote:
>
> Hi,
>
> > That said, Chrome OS would use a similar model, except that we don't
> > use ION. We would likely use minigbm backed by virtio-gpu to allocate
> > appropriate secure buffers for us and then import them to the V4L2
> > driver.
>
>
On Thu, Oct 17, 2019 at 4:44 PM Gerd Hoffmann wrote:
>
> Hi,
>
> > > Also note that the guest manages the address space, so the host can't
> > > simply allocate guest page addresses.
> >
> > Is this really true? I'm not an expert in this area, but on a bare
> > metal system it's the hardware or
Hi Niklas, Laurent,
On Tue, Oct 15, 2019 at 01:11:07AM +0300, Laurent Pinchart wrote:
> Hi Niklas,
>
> Thank you for the patch.
>
> On Mon, Oct 14, 2019 at 02:16:15AM +0200, Niklas Söderlund wrote:
> > Most Gen3 boards can output frames in NV12 format, add support for this
> > with a runtime check
Hi Antti,
I have a Logilink VG0022A device which is an af9035.c type device (with
ITE 9xxx frontned). The probe of the si2146 tuner fails and returns 0xffs.
Now I would like to work on fixing this. Mauro suggested the firmware might
be incorrect. Any tips on extracting the firmware? I can try and
Hi,
> That could be still a guest physical address. Like on a bare metal
> system with TrustZone, there could be physical memory that is not
> accessible to the CPU.
Hmm. Yes, maybe. We could use the dma address of the (first page of
the) guest buffer. In case of a secure buffer the guest ha
> > I doubt you can handle pci memory bars like regular ram when it comes to
> > dma and iommu support. There is a reason we have p2pdma in the first
> > place ...
>
> The thing is that such bars would be actually backed by regular host
> RAM. Do we really need the complexity of real PCI bar hand
Hi all,
Since we have three separate half-day sessions for different topics I decided
to split the announcement for this in three emails as well, so these things
can be discussed in separate threads.
All sessions are in room Terreaux VIP Lounge - Level 0.
There is a maximum of 15 people.
The fir
(Updated Maxime's email address in v3)
Hi all,
Since we have three separate half-day sessions for different topics I decided
to split the announcement for this in three emails as well, so these things
can be discussed in separate threads.
All sessions are in room Terreaux VIP Lounge - Level 0.
T
(Just updated the attendee list for this meeting, no other changes)
Hi all,
Since we have three separate half-day sessions for different topics I decided
to split the announcement for this in three emails as well, so these things
can be discussed in separate threads.
All sessions are in room Ter
Hi all,
Since we have three separate half-day sessions for different topics I decided
to split the announcement for this in three emails as well, so these things
can be discussed in separate threads.
All sessions are in room Terreaux VIP Lounge - Level 0.
There is a maximum of 15 people.
The thi
The driver implementation assumed the binning limits could change
dynamically based on the binning configuration. This is not actually the
case; these limits are static and suitable to be used with all binning
configurations but possibly not optimal limit for many of those
configurations.
Signed-o
Use non-binned limits when binning is disabled and binned when they're
enabled.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 27 +++---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers
Hi folks,
This set cleans up binning limit handling and fixes runtime PM use by
enabling runtime PM *before* any functionality requiring runtime PM may be
used.
Also a small omap3isp fix is included.
Sakari Ailus (7):
smiapp: Don't get binning limits dynamically
smiapp: Move binning configur
Rename the confusingly named smiapp_update_mode() function as
smiapp_pll_blanking_update(). The function is used to calculate new PLL
and blanking configuration after binning or scaling configuration has been
changed.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 6 +++
The sensor configuration since it was previously powered off was not
changed, so no need to update the PLL configuration etc. What is necessary
though is to re-apply the configuration to the sensor's registers.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 4
1 fi
Only write the binning configuration at stream start. It has no effect
otherwise.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 43 +-
1 file changed, 22 insertions(+), 21 deletions(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/driv
The isp was marked to have failed to stop if stopping streaming on an
external subdev failed. The return value from the external subdev should
be ignored instead as it is not part of the ISP and thus the ISP does not
need to be reset for that reason.
Signed-off-by: Sakari Ailus
---
drivers/media
Earlier it was possible that the parts of the driver that assumed runtime
PM was enabled were being called before runtime PM was enabled in the
driver's probe function. So enable runtime PM before registering the
sub-device.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c
Hello,
On 10/17/19 12:08 PM, Sean Young wrote:
Hi Antti,
I have a Logilink VG0022A device which is an af9035.c type device (with
ITE 9xxx frontned). The probe of the si2146 tuner fails and returns 0xffs.
Now I would like to work on fixing this. Mauro suggested the firmware might
be incorrect.
Hi there,
On 10/17/19 2:15 PM, Antti Palosaari wrote:
Hello,
On 10/17/19 12:08 PM, Sean Young wrote:
Hi Antti,
I have a Logilink VG0022A device which is an af9035.c type device (with
ITE 9xxx frontned). The probe of the si2146 tuner fails and returns
0xffs.
Now I would like to work on fixi
On 10/17/19 4:46 PM, JP wrote:
Hi there,
On 10/17/19 2:15 PM, Antti Palosaari wrote:
Hello,
On 10/17/19 12:08 PM, Sean Young wrote:
Hi Antti,
I have a Logilink VG0022A device which is an af9035.c type device (with
ITE 9xxx frontned). The probe of the si2146 tuner fails and returns
0xffs.
Hi Stanimir,
On Thu, 3 Oct 2019 at 12:15, Stanimir Varbanov
wrote:
>
> I have tested this on db410c with following gst pipeline:
>
> gst-launch-1.0 -v videotestsrc !
> video/x-raw,format=NV12,width=1280,height=960,framerate=24/1 !
> v4l2h264enc
> extra-controls="controls,h264_profile=4,h264_level
Hi Loic,
On 10/17/19 6:08 PM, Loic Poulain wrote:
> Hi Stanimir,
>
> On Thu, 3 Oct 2019 at 12:15, Stanimir Varbanov
> wrote:
>>
>> I have tested this on db410c with following gst pipeline:
>>
>> gst-launch-1.0 -v videotestsrc !
>> video/x-raw,format=NV12,width=1280,height=960,framerate=24/1 !
>>
Hi Stanimir,
On Thu, 17 Oct 2019 at 17:47, Stanimir Varbanov
wrote:
>
> Hi Loic,
>
> On 10/17/19 6:08 PM, Loic Poulain wrote:
> > Hi Stanimir,
> >
> > On Thu, 3 Oct 2019 at 12:15, Stanimir Varbanov
> > wrote:
> >>
> >> I have tested this on db410c with following gst pipeline:
> >>
> >> gst-launc
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Fri Oct 18 05:00:13 CEST 2019
media-tree git hash:4b1d7c2760d26363c497b959a81f8d055ba767c1
media_build gi
30 matches
Mail list logo
