From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Linux kernel version of armv6l and armv7l stay at v5.5
Date: Wed, 14 Apr 2021 14:16:48 +0200 [thread overview]
Message-ID: <20210414121648.nLbZdlZslHjKu6JfQtYx6y1eUo7rEbYNjawnjI7sbVY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30205@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/30205#issuecomment-819472718
Comment:
There isn't, no. `armv6l` maybe shows its age in a lot of places, but it's also a valuable target due to the RPi Zero. `armv7l` is still sufficiently modern and people may need 32-bit on aarch64 devices that support it.
The issue with `armv*` kernels is that very few platforms actually work with the generic kernel, so it isn't of much value to provide one, even. If you're interested in using those platforms with Void and they work with a modern generic kernel, you can probably base the config off of `linux5.4` (which has `arm-dotconfig`) and we'll merge it in and keep it up to date with kernel updates; but I'm not going to add this support to `linux5.11` myself, my rpi uses `rpi-kernel` just fine.
All that said, it should be perfectly possible to install `linux5.4` directly and use that, though it is admittedly more fiddly than just using the `linux` package directly.
next prev parent reply other threads:[~2021-04-14 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 11:45 [ISSUE] " ruantu
2021-04-13 18:43 ` ericonr
2021-04-14 1:57 ` ruantu
2021-04-14 12:16 ` ericonr [this message]
2021-04-16 6:32 ` ruantu
2021-04-16 6:43 ` ericonr
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=20210414121648.nLbZdlZslHjKu6JfQtYx6y1eUo7rEbYNjawnjI7sbVY@z \
--to=ericonr@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).