public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Up for grabs: Raspberry Pi stack
Date: Sat, 20 Apr 2024 10:03:37 +0100	[thread overview]
Message-ID: <3a629438a94b83538922fa67cab0a07a11cf5bb8.camel@gentoo.org> (raw)
In-Reply-To: <87mspo67iy.fsf@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

On Sat, 2024-04-20 at 04:24 +0100, Sam James wrote:
> I don't have the hardware set up at the moment (and haven't for a while)
> to test this properly.
> 
> The following packages are up for grabs:
> * media-libs/raspberrypi-userland-bin
> * sys-kernel/raspberrypi-image
> 
> I dropped myself as a co-maintainer on the following:
> * sys-firmware/raspberrypi-wifi-ucode
> * media-libs/raspberrypi-userland-bin
> * sys-boot/raspberrypi-firmware
> * sys-kernel/raspberrypi-sources
> * sys-kernel/raspberrypi-image
> 
> I think anyone interested in these packages should probably consider
> joining the lot.
> 
> There's a few outstanding bugs, notably https://bugs.gentoo.org/930269
> for Raspberry Pi 5 support, but a bunch of others including bumps being
> due.

I've been working in this area because of my PiStorm efforts, but it's been
hard to find the time lately. I can at least say that I was on the way to last
riting media-libs/raspberrypi-userland(-bin). Ideally, we need libcamera
first, otherwise users of things like media-video/motion will be impacted. I
don't know whether we have any such users though. As for hardware, I only have
a Pi 4b and have no need for a Pi 5.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

      reply	other threads:[~2024-04-20  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20  3:24 [gentoo-dev] Up for grabs: Raspberry Pi stack Sam James
2024-04-20  9:03 ` James Le Cuirot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3a629438a94b83538922fa67cab0a07a11cf5bb8.camel@gentoo.org \
    --to=chewi@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox