From: Depau <Depau@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: overclock patch
Date: Mon, 18 Jan 2021 13:16:49 +0100 [thread overview]
Message-ID: <20210118121649.EYL9vsfb2grm3yrlcee-l-06UFtJdPLYu9X4a3gQ7JI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28007@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
New comment by Depau on void-packages repository
https://github.com/void-linux/void-packages/pull/28007#issuecomment-762213677
Comment:
Overclocking related issues are super hard to isolate and bisect, especially on a machine that already has other issues.
Why merge this into the main kernel package when you can simply ship an overlay and instruct users on how to apply it and stress-test their own silicon? It's literally 1 line in the u-boot boot script.
Silicon lottery applies to RK3399 too. If Google has their SoCs tested to be able to reach higher clock speeds, good for them. Does Pine64 have them tested for higher clocks? I don't think so.
next prev parent reply other threads:[~2021-01-18 12:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 11:55 [PR PATCH] " thypon
2021-01-18 11:57 ` [PR PATCH] [Updated] " thypon
2021-01-18 12:16 ` Depau [this message]
2021-01-18 12:38 ` Johnnynator
2021-01-18 13:06 ` thypon
2021-01-18 17:40 ` thypon
2021-01-18 17:41 ` thypon
2021-01-18 18:02 ` CameronNemo
2021-01-18 18:10 ` thypon
2021-01-18 18:10 ` thypon
2021-01-18 18:11 ` thypon
2021-01-18 18:12 ` thypon
2021-01-18 18:20 ` CameronNemo
2021-01-18 18:45 ` Depau
2021-01-18 19:39 ` thypon
2021-01-18 19:41 ` thypon
2021-01-18 19:44 ` thypon
2021-01-18 22:12 ` thypon
2021-01-19 23:07 ` thypon
2021-01-21 14:34 ` thypon
2021-01-21 14:35 ` thypon
2021-01-21 14:37 ` thypon
2021-01-21 14:38 ` thypon
2021-01-21 14:39 ` thypon
2021-01-21 14:39 ` thypon
2021-01-21 14:40 ` thypon
2021-01-21 14:41 ` thypon
2021-01-21 14:42 ` thypon
2021-01-21 14:46 ` thypon
2021-01-21 14:46 ` thypon
2021-01-21 14:50 ` thypon
2021-01-21 14:51 ` thypon
2021-01-21 14:52 ` thypon
2021-01-21 14:53 ` thypon
2021-01-21 14:56 ` thypon
2022-05-02 2:16 ` github-actions
2022-05-17 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20210118121649.EYL9vsfb2grm3yrlcee-l-06UFtJdPLYu9X4a3gQ7JI@z \
--to=depau@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).