Good Morning Everyone,
In the sig-docs [1] repository we have a CI job that runs daily and builds, runs
and checks a number of images [2].
When those builds/runs/checks fail there is usually a good reason that we should
go and check.
Currently I believe I'm the only one being notified about those failure.
As part of https://gitlab.com/CentOS/automotive/sig-docs/-/merge_requests/441
I'd like this list to be notified, but I don't want to do this without asking
before.
So what do you all think? Is anyone against this?
If not, then I'll go ahead with the change and if it starts to be too
annoying/noisy we can always revisit later :)
Looking forward for your feedback :)
Pierre
Dear list,
Hopefully I'm subscribed now and the email is not lost. I'd like to make a
request for a `k3-upstream-boot` repository at `
https://gitlab.com/CentOS/automotive/rpms/`
<https://gitlab.com/CentOS/automotive/rpms/>. This repository will host the
RPM package for firmware needed to boot TI k3 platforms like the J784S4 EVM
and AM69-SK boards.
While here, I'd like to take the opportunity to ask you to create another
repository, 's32g-vendor-boot'. Similar to the other, this repository will
host the RPM package for firmware needed to boot S32G platforms using the
public vendor components/repositories
Your help is appreciated.
Best regards,
Enric
> On Thu, Jul 31, 2025 at 4:13 PM Enric Balletbo i Serra <
> eballetb(a)redhat.com> wrote:
>
>> Dear list,
>>
>> Could you please create a `k3-upstream-boot` repository in our GitLab
>> instance under https://gitlab.com/CentOS/automotive/rpms/?
>>
>> The purpose of this repository is to track the rpm package that
>> contains the firmware required to boot different TI k3 platforms like
>> J784S4 EVM and AM69-SK boards.
>>
>> Best regards,
>> Enric
>>
>
On Wed, Aug 27, 2025 at 01:35:26PM +0200, Enric Balletbo i Serra via automotive-sig wrote:
> Dear list,
> Hopefully I'm subscribed now and the email is not lost. I'd like to make a
> request for a `k3-upstream-boot` repository at
> `[1]https://gitlab.com/CentOS/automotive/rpms/`. This repository will host
> the RPM package for firmware needed to boot TI k3 platforms like the
> J784S4 EVM and AM69-SK boards.
> While here, I'd like to take the opportunity to ask you to create another
> repository, 's32g-vendor-boot'. Similar to the other, this repository will
> host the RPM package for firmware needed to boot S32G platforms using the
> public vendor components/repositories
Both projects have been created:
https://gitlab.com/CentOS/automotive/rpms/k3-upstream-boothttps://gitlab.com/CentOS/automotive/rpms/s32g-vendor-boot
Happy packing!
Pierre
PS: now sent from the right email
Hello,
I would like to request a new demo repository in
https://gitlab.com/CentOS/automotive/demos, named
"soafee-virtual-platform-blueprint".
This repository will host demo files to run our SOAFEE virtual platform
blueprint (AutoSD Frankenbuild for now).
Regards,
--
Leonardo Rossetti
Principal Software Engineer,
Red Hat <https://www.redhat.com>
lrossett(a)redhat.com
<https://www.redhat.com>
Hello,
I would like to request a new demo repository: "autoware" here:
https://gitlab.com/CentOS/automotive/demos.
The repository would host Autoware (Open Ad-Kit for now) quadlet manifest
files and aib files to deploy/run their ADAS software in an AutoSD image.
Regards,
--
Leonardo Rossetti
Principal Software Engineer,
Red Hat <https://www.redhat.com>
lrossett(a)redhat.com
<https://www.redhat.com>
I would like to request a new repository to transfer https://gitlab.com/ernunes/acrn-hypervisor-spec to the automotive-sig.
It is a .spec file repository for the ACRN hypervisor which can be used with AutoSD.
Please note that the package cannot be built as-is, due to how that project works it requires a platform-specific configuration to be added by the user before building the actual RPMs.
So I think the appropriate path for now would be src/acrn-hypervisor.
This will be referenced in the automotive-sig docs as a followup.