Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rpi-*: update and support rpi5
Date: Sat, 23 Dec 2023 19:13:03 +0100	[thread overview]
Message-ID: <20231223181303.U1dXInAEJsbZ07YCOOOJbE4MbLa1nhNfHKwe_V_QMZ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47288@inbox.vuxu.org>

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

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/47288#issuecomment-1868344109

Comment:
updated things because this has sat for a bit

new versions should be available at https://files.placeviolette.net/rpi5 for testing

TODOs left:
- [ ] give everything a quick test
- [ ] deconflict `linux-firmware-broadcom` and `rpi-firmware` (probably simple)
- [ ] figure out #47290
- [ ] rpi5-kernel pagesize gives issues with jemalloc

  parent reply	other threads:[~2023-12-23 18:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18  4:01 [PR PATCH] " classabbyamp
2023-11-18  4:02 ` [PR PATCH] [Updated] " classabbyamp
2023-11-18 19:54 ` classabbyamp
2023-11-19 19:19 ` classabbyamp
2023-11-20  3:17 ` classabbyamp
2023-11-21 11:57 ` 0x5c
2023-11-22 22:39 ` moabeat-berlin
2023-12-23 18:09 ` [PR PATCH] [Updated] " classabbyamp
2023-12-23 18:10 ` classabbyamp
2023-12-23 18:13 ` classabbyamp [this message]
2023-12-23 22:24 ` [PR PATCH] [Updated] " classabbyamp
2023-12-23 22:26 ` classabbyamp
2024-01-05 19:46 ` [PR PATCH] [Updated] " classabbyamp
2024-01-05 21:26 ` classabbyamp
2024-01-05 21:28 ` classabbyamp
2024-01-05 21:28 ` classabbyamp
2024-01-17 19:23 ` [PR PATCH] [Merged]: " classabbyamp

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=20231223181303.U1dXInAEJsbZ07YCOOOJbE4MbLa1nhNfHKwe_V_QMZ4@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).