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.
On Tue, May 27, 2025 at 11:28 AM Pierre-Yves Chibon <pingou(a)redhat.com>
wrote:
> On Tue, May 27, 2025 at 10:29:39AM +0200, Martin Perina via automotive-sig
> wrote:
> > On Mon, May 26, 2025 at 3:08 PM Mark Kemel via automotive-sig
> > <[1]automotive-sig(a)lists.centos.org> wrote:
> >
> > Hello all,
> > Currently we have two packages, for which we have dedicated COPR
> repos
> > for release versions:
> > [2]
> https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/automotive-…
> > and
> > [3]
> https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/osbuild-aut…
> .
> > These are automatically built with Packit, triggered by GitLab
> releases,
> > allowing users to run a-i-b on Fedora.
> > Following the Slack discussion on auto-boot-check COPR builds, I
> want to
> > address this here. For packages like auto-boot-check, which are
> built
> > solely for the AutoSD/Automotive SIG and not intended for Fedora
> release
> > but should be installable from COPR, we need to decide on the
> repository
> > structure. Should we create a separate COPR repo for each package
> under
> > the '@centos-automotive-sig' project, similar to a-i-b and
> osbuild-auto,
> > or should we group these packages into repos by usage? For instance,
> > should auto-boot-check release builds be done within the
> > automotive-image-builder repo?
>
> I'd think it depends how tied together the packages are and if they are
> released
> together or at different rhythms.
> I can see pros and cons to both approaches
>
> > I think it would be beneficial to have an official repository for
> Fedora,
> > which will contain releases of the same packages as we have in AutoSD.
>
> So you're thinking 1 COPR repo for fedora builds of all the AutoSD
> packages?
>
Yeah, that seems to me much easier than having a separate copr repo per
package
>
> Pierre
>
>
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.