Hello Jan, >Michael already expressed to me a while ago that he cannot work on it >very often. Problem for me is that I do not have a target for this layer >anymore, plus there is no testing setup for accepting PRs without own, >then likely manual testing effort.
Thanks for your open answer, and I must say that I suspected this scenario. >Who is using this layer? Who would be able to help out, with providing >updates from time to time and with making them better testable (some >pipeline that builds and runs a qemu image at least)? I am seriously considering using this layer for a few products we have which are x86-based and built with Yocto. I would be happy to provide patches to bring it up to date as of now. If we do adopt efibootguard for our products, I would also be happy to provide ongoing patches and developing a pipeline to build and run a qemu image would not be out of the question, but it is early days yet. I have made a lot of progress with efibootguard in our Yocto environment over the last few days and I have a good feeling about it and the principles involved. We have diverse embedded environments, comprising 2 ARM-based platforms, for which we use Yocto and swupdate, but not sure about efibootguard, however, we have 3 deeply embedded x86 platforms for which we use Yocto and swupdate, and it is for these I am currently most interested in as the existing platform is not completely current and I would like to use efibootguard for this. In addition we have a few requirements where the CIP would be very attractive and we are seriously considering adopting CIP for these - but this requires further discussion. Hamish -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to efibootguard-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/efibootguard-dev/AS1P190MB1776E9FA9D05FE5125313A6683A72%40AS1P190MB1776.EURP190.PROD.OUTLOOK.COM.
