On Mon, Dec 9, 2019 at 3:31 AM Gerd Hoffmann wrote:
>
> > > > 1) Driver sends RESOURCE_CREATE_2D shared request
> > > > 2) Driver sends ATTACH_BACKING request
> > > > 3) Device creates a shared resource
> > > > 4) Driver sends SET_SCANOUT request
> > > > 5) Device sends shared resource to display
+Changyeon Jo for his awareness
Thanks,
- Enrico
On Mon, Dec 9, 2019 at 6:20 AM Dmitry Sepp
wrote:
> Hello,
>
> I'd like to invite everyone to share ideas regarding required encoder
> features
> in this separate sub-tree.
>
> In general, encoder devices are more complex compared to decoders.
Hello,
I'd like to invite everyone to share ideas regarding required encoder features
in this separate sub-tree.
In general, encoder devices are more complex compared to decoders. So the
question I'd like to rise is in what way we define the minimal subset of
features to be implemented by the
On Sat, Dec 7, 2019 at 12:50 AM Enrico Granata wrote:
>
> On Fri, Dec 6, 2019 at 4:30 AM Keiichi Watanabe wrote:
> >
> > Hi,
> >
> > On Fri, Dec 6, 2019 at 4:32 PM Gerd Hoffmann wrote:
> > >
> > > Hi,
> > >
> > > > > > > > +\subsection{Device ID}\label{sec:Device Types / Video Device /
> > >
Hi,
On Mon, Dec 9, 2019 at 8:38 PM Dmitry Sepp wrote:
>
> Hi,
>
> On Montag, 9. Dezember 2019 11:46:15 CET Gerd Hoffmann wrote:
> > Hi,
> >
> > > > For (1) you'll simply do a QUEUE_BUFFER. The command carries references
> > > > to the buffer pages. No resource management needed.
> > > >
> >
Hi,
On Montag, 9. Dezember 2019 11:46:15 CET Gerd Hoffmann wrote:
> Hi,
>
> > > For (1) you'll simply do a QUEUE_BUFFER. The command carries references
> > > to the buffer pages. No resource management needed.
> > >
> > > For (2) you'll have RESOURCE_CREATE + RESOURCE_DESTROY +
> > > 1) Driver sends RESOURCE_CREATE_2D shared request
> > > 2) Driver sends ATTACH_BACKING request
> > > 3) Device creates a shared resource
> > > 4) Driver sends SET_SCANOUT request
> > > 5) Device sends shared resource to display
> > > 6) Driver sends DETACH_BACKING request
> >
> > Hmm, I
Hi,
> > For (1) you'll simply do a QUEUE_BUFFER. The command carries references
> > to the buffer pages. No resource management needed.
> >
> > For (2) you'll have RESOURCE_CREATE + RESOURCE_DESTROY + QUEUE_RESOURCE,
> > where RESOURCE_CREATE passes the scatter list of buffer pages to the
> >
