From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rpi*-kernel: update to 5.10.92.
Date: Sat, 22 Jan 2022 20:51:58 +0100 [thread overview]
Message-ID: <20220122195158.O149IfkRaGe9vbnCk93jRVDFtF9LJ828I8qFjunfVXI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34962@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/34962#issuecomment-1019347452
Comment:
Tested with:
- rpi 1 B+
- rpi zero
- rpi 2 B
- rpi 3 B
- rpi zero 2 W
on glibc and musl. all boot but did not do extensive testing. Unfortunately I do not have any rpi 4s so I can't test that one.
on the zero 2 W, there was a message that popped up in dmesg during boot, but it did not seem to cause any issues:
```
[7.024198] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
```
next prev parent reply other threads:[~2022-01-22 19:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 10:45 [PR PATCH] rpi*-kernel: update to 5.10.90 JamiKettunen
2022-01-09 13:15 ` JamiKettunen
2022-01-09 13:16 ` JamiKettunen
2022-01-09 13:25 ` ahesford
2022-01-09 13:29 ` JamiKettunen
2022-01-09 13:29 ` Duncaen
2022-01-09 13:30 ` JamiKettunen
2022-01-09 13:31 ` Duncaen
2022-01-09 13:37 ` [PR PATCH] [Updated] " JamiKettunen
2022-01-09 19:40 ` JamiKettunen
2022-01-09 19:41 ` JamiKettunen
2022-01-09 19:42 ` JamiKettunen
2022-01-10 16:57 ` marmeladema
2022-01-21 21:18 ` [PR PATCH] [Updated] " JamiKettunen
2022-01-21 21:21 ` JamiKettunen
2022-01-22 19:51 ` classabbyamp [this message]
2022-01-22 19:56 ` rpi*-kernel: update to 5.10.92 classabbyamp
2022-01-27 18:21 ` karlgrose
2022-01-27 18:22 ` karlgrose
2022-01-27 18:23 ` karlgrose
2022-01-27 18:24 ` karlgrose
2022-02-01 21:14 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220122195158.O149IfkRaGe9vbnCk93jRVDFtF9LJ828I8qFjunfVXI@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).