Re: AGL Feature Planning for 2023

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello all,

I'd like to provide a short follow-up on this matter, as at this point I
have some more information and a clearer path in mind how to achieve
some of the things I've alluded initially with respect to using PipeWire
as a replacement for Waltham.  

While PipeWire is similar to the remoting plug-in, such that in combination 
with a helper client can stream out data buffers over some kind of a network, 
piggyback on it to deliver input events from one side to another isn't 
really feasible to do. There are far better solutions and these are either 
RDP or VNC. It remains to be seen which of these are more suitable here -
it depends on the encoding/decoding technologies they actually use.

So, with that in mind I've renamed SPEC-4689 and updated it with some of
the things I need to piece together to get this working. The support for
achieving this is WIP in upstream, at this moment, libweston supporting
both RDP and VNC but not in this particular use-case (combination) that
we have here: streaming data buffers on a remote site but also display
something natively/locally.

Further more, a Wayland native client using  freerdp2 or anyvnc would
needs to be on the remote site to display the incoming data buffers,
process inputs and send them back. While there are such clients I don't
know at this moment how much of these we can use or re-use.

PipeWire is still the technology to use in screen sharing the entire
output or just a window app, just not as a replacement for the use-case
we have/had with Waltham. We would still like to advance our PipeWire
usage in AGL so I've created SPEC-4711 for just sharing/screen sharing
functionality using PipeWire.

Additionally, I'd like to point another useful feature which was brought
in by Scott Murray, and I think it would be good to have on the feature
planning list alongside with the Waltham replacement task and PipeWire.

It's about the compositor being capable of using a *.d directory, 
drop-in configuration files, similar to systemd or apache conf.d files. 
I've further added some examples in the associated Jira task 
SPEC-4710.

Thanks!

On Thu, Jan 26, 2023 at 10:24:44AM +0200, Marius Vlad via lists.automotivelinux.org wrote:
> Hi,
> 
> We identified PipeWire as the common denominator technology in some of
> the key tasks added in that spreadsheet, related this time not to audio,
> but rather to video and graphics. Camera functionality, but also as a
> replacement for Waltham, are among a few items worth mentioning.
> Screen-sharing is also used in Wayland compositors so that's also
> something to think about.
> 
> With PipeWire gaining quite a bit of traction, focusing on it seems like the
> natural thing to do. libweston support for PipeWire is a bit inefficient
> at this stage, but with a bit of work we could replace our GSt pipeline 
> with PipeWire entirely for the video streaming part, while the remaining 
> bit would be to figure out how to relay input data back over some kind 
> of a side-channel, as to achieve parity to what we had over with Waltham.
> 
> Obviously at this point it is a bit too soon to assume that's
> achievable but we can look into other technologies, and
> see if we can come up with something similar in terms of functionality.
> 
> Anyway, with that in mind I created a Jira ticket [1] for this.
> 
> [1] https://jira.automotivelinux.org/browse/SPEC-4689
> 
> On Thu, Jan 19, 2023 at 08:40:05AM -0500, Walt Miner wrote:
> > Happy New Year everyone!   We had a very successful booth at CES earlier
> > this month and I was very happy to see a lot of familiar faces.  A number
> > of us in the AGL community plan to attend FOSDEM[1] in Brussels in a few
> > weeks. If you are there make sure to stop by the AGL Stand on Sunday to say
> > hello, grab a sticker or two, and see the latest AGL demos.
> > 
> > We have also kicked off our annual feature planning and roadmap
> > exercise[2]. Instructions and deadlines are in the README worksheet[2]. We
> > need each of the expert groups to review and update their feature lists
> > that were updated last year in the next two weeks. Once that is complete
> > the SAT will review the complete list and send it to the Steering Committee
> > for review and voting on the roadmap items that will be funded for this
> > year.
> > 
> > Regards,
> > Walt
> > 
> > 
> > [1] https://fosdem.org/2023
> > [2]
> > https://docs.google.com/spreadsheets/d/1BcjFnnOPlsc_zsF0djfEhTh5jG07OOqBU9y2IIJVVKo/edit?usp=sharing
> > Walt Miner
> > AGL Community Manager
> > The Linux Foundation
> > 
> > Visit us at:
> > www.automotivegradelinux.org
> > lists.automotivelinux.org
> > www.linuxfoundation.org
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
> 
> 




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10419): https://lists.automotivelinux.org/g/agl-dev-community/message/10419
Mute This Topic: https://lists.automotivelinux.org/mt/96376982/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/2167316/883735764/xyzzy [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-


Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux