Tomorrow (Wednesday) at 12:00 UTC I will be holding an experimental
Spectrum community call. The idea here is that it gives all
participants in the Spectrum community (interested users, developers,
etc.) the chance to meet and talk about upcoming development work.
So if you would like to hear or ask questions about where Spectrum is
going, or if you're working on Spectrum (or would like to be!) and want
to share what you're doing, please join us tomorrow at the following URL:
Since somebody has asked already: I don't plan on recording this call.
If it goes well and we make this a regular thing, we can discuss at that
point whether calls should be recorded.
In the spectrum OS, as far as I know, all appvms will connect to outside through netvm.
And each appvm has different subnet.
However, sometimes, a app should be able to access the host network by bridging.
For example, an P2P app needs to send and receive multicast or broadcast to find other peers.
I wonder if it(bridging to host network) is possible in spectrum OS model, and if possible,
I want to know how to do it.
And if there is no such feature, I want to know the plan or opinion to support such app in spectrum OS.
We've built the wayland demo branch on aarch64 port and added some other
apps on it to showcase embedded virtualization with Spectrum OS.
The build configuration for the reference device is documented  with
the out-of-tree build configuration as agreed in our earlier
discussion. There's also some additional accompanied documentation on
binary cache we have used with aarch64 and could be of general use. I'd
like to see that documentation upstreamed as much as possible.
Would it make sense to link this work from Spectrum documentation? To
indicate work in progress aarch64 support with known issues on a ref.
device and avoid forking this documentation?
The practical benefit is that anyone interested in building Spectrum OS
for an aarch64 device using vendor BSP would have some reference linked
from Spectrum OS documentation - e.g. an initial porting guide as even
the x86_64 does not yet use the build configuration. Additionally, I
don't want to fragment Spectrum OS ports and their documentation further