Github messages for voidlinux
 help / color / mirror / Atom feed
From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rockpro64-uboot: update to 2025.01.
Date: Sun, 02 Feb 2025 14:08:04 +0100	[thread overview]
Message-ID: <20250202130804.4F7AA217F2@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53925@inbox.vuxu.org>

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

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/pull/53925#issuecomment-2611004270

Comment:
Hey, I am going to get back to this!

I have successfully moved all my services from my `RockPro64` NAS to my new `media center`. 

Currently updated my RockPro64 and also applied this PR, lets see how it goes ...

Edit: Okay, I finally am able to boot from USB 3.0, I think this can be merged (even though I am still having issues with my device, but that is not related to this PR).

Edit 2: Is it normaly that I cannot boot from the SD card itself when I flashed the SPI to it? It's not like I need it, but it would've been nice knowing it in advance because I currently cannot boot until I reinstalled Void on a ssd. :)

Edit3: I read somewhere else that this happens and since I am able to boot `Armbian` for `RockPro64` I think it's good enough to merge this. 

  parent reply	other threads:[~2025-02-02 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  1:57 [PR PATCH] " tsndqst
2025-01-11  2:04 ` tsndqst
2025-01-11  2:17 ` [PR PATCH] [Updated] " tsndqst
2025-01-11 11:52 ` Anachron
2025-01-11 13:29 ` tsndqst
2025-01-23 20:58 ` Anachron
2025-01-23 21:12 ` Anachron
2025-01-23 21:22 ` Anachron
2025-02-02 13:08 ` Anachron [this message]
2025-02-04  2:07 ` tsndqst
2025-02-23 15:56 ` [PR PATCH] [Updated] " tsndqst

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=20250202130804.4F7AA217F2@inbox.vuxu.org \
    --to=anachron@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).