Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: pinephone-kernel: update to 5.10.12.
Date: Tue, 02 Feb 2021 20:16:12 +0100	[thread overview]
Message-ID: <20210202191612.X276igyngMzvpBVQ2g53qIjjWxc72Xg5JUqfraTN2IQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28399@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

pinephone-kernel: update to 5.10.12.
https://github.com/void-linux/void-packages/pull/28399

Description:
<!-- Mark items with [x] where applicable -->

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64
  - [x] aarch64-musl
-->

New version of megi's pinephone kernel. In addition to regular kernel updates, this brings new improvements:

- Display refresh is now at 60hz from ~45hz
- Improved wifi power management
- Modem driver has added support for new Quectel modem features
- Audio codec drivers work better with the hardware, higher sample rates in phone calls. This also unblocks #25084 

So far I've tested a pretty barebones userspace on top of this, sway window manager, firefox, mpv music/video playback, wifi/bluetooth, and typec docking are all still working.

I also cleaned the template up a bit, to better match the mainline kernel. Of course it's not exactly 1:1, but I believe the style is close enough.

Also, for the maintainers: I admit I've been pretty lazy about documentation. I'd like to get some docs going for mklive and sxmo on the device, so we at least have a MVP userspace people can try out (or try and help some other enthusiastic people do this). Of course, this PR will make it easier to get there :-)

      parent reply	other threads:[~2021-02-02 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  1:19 [PR PATCH] " jjsullivan5196
2021-02-02  1:46 ` [PR REVIEW] " ericonr
2021-02-02  1:47 ` ericonr
2021-02-02  5:44 ` [PR PATCH] [Updated] " jjsullivan5196
2021-02-02  5:45 ` [PR REVIEW] " jjsullivan5196
2021-02-02  5:46 ` jjsullivan5196
2021-02-02 19:02 ` [PR REVIEW] " ericonr
2021-02-02 19:11 ` jjsullivan5196
2021-02-02 19:16 ` ericonr [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=20210202191612.X276igyngMzvpBVQ2g53qIjjWxc72Xg5JUqfraTN2IQ@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).