From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi 2 Model B
Date: Sat, 7 Feb 2015 16:50:24 +0000 [thread overview]
Message-ID: <9dc091ed831c3704ab93c49f93f37cab@hamnavoe.com> (raw)
In-Reply-To: <eaba1591f62bc65645231d43fec58b47@hamnavoe.com>
I said:
> Disclaimer: if you put silly numbers in arm_freq, bad stuff
> might happen. Supposedly the firmware detects this and sets
> an irreversible bit somewhere that voids your warranty.
There are claims in the raspberry pi forums that the 'void
warranty' bit will be set if you configure force_turbo=1,
whatever the frequency. So if you care about this, you
may be stuck at 600Mhz unless someone cares enough to
reverse engineer the linux speed management code.
next prev parent reply other threads:[~2015-02-07 16:50 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 12:48 Shane Morris
2015-02-02 13:14 ` Richard Miller
2015-02-02 13:41 ` Sean Hinchee
2015-02-02 20:54 ` Skip Tavakkolian
2015-02-02 21:24 ` Bakul Shah
2015-02-02 21:37 ` Joe Bowers
2015-02-02 22:20 ` Sean Hinchee
2015-02-02 21:38 ` Steve Simon
2015-02-03 11:32 ` hiro
2015-02-03 11:40 ` Peter Hull
2015-02-03 11:46 ` hiro
2015-02-03 11:43 ` hiro
2015-02-03 12:37 ` Costin Chirvasuta
2015-02-03 14:23 ` hiro
2015-02-05 8:17 ` Dante
2015-02-05 10:09 ` Shane Morris
2015-02-05 10:19 ` David du Colombier
2015-02-05 14:41 ` cinap_lenrek
2015-02-05 14:46 ` Siarhei Zirukin
2015-02-05 15:40 ` Steven Stallion
2015-02-05 15:48 ` Kurt H Maier
2015-02-05 16:47 ` Dante
2015-02-05 17:34 ` Charles Forsyth
2015-02-05 15:38 ` Steve Simon
2015-02-05 16:07 ` David du Colombier
2015-02-05 17:32 ` cinap_lenrek
2015-02-05 19:15 ` erik quanstrom
2015-02-05 19:22 ` Shane Morris
2015-02-05 19:42 ` cinap_lenrek
2015-02-05 19:56 ` Shane Morris
2015-02-05 21:17 ` Quintile
2015-02-05 21:20 ` Shane Morris
2015-02-06 4:19 ` erik quanstrom
2015-02-06 4:34 ` lucio
2015-02-06 4:42 ` Kurt H Maier
2015-02-06 4:55 ` erik quanstrom
2015-02-06 5:12 ` Kurt H Maier
2015-02-06 5:35 ` erik quanstrom
2015-02-06 12:00 ` cinap_lenrek
2015-02-06 13:57 ` Richard Miller
2015-04-20 14:23 ` Kurt H Maier
2015-05-03 3:24 ` Lyndon Nerenberg
2015-02-06 14:05 ` erik quanstrom
2015-02-05 19:29 ` cinap_lenrek
2015-02-05 19:25 ` Richard Miller
2015-02-05 19:25 ` erik quanstrom
2015-02-06 11:55 ` Steve Simon
2015-02-06 14:18 ` erik quanstrom
2015-02-06 18:13 ` Richard Miller
2015-02-06 18:18 ` Joe Bowers
2015-02-07 9:38 ` Dante
2015-02-07 16:50 ` Richard Miller [this message]
2015-02-07 20:21 ` Bakul Shah
2015-02-08 1:10 ` hiro
2015-02-08 2:22 ` Bakul Shah
2015-02-08 2:48 ` erik quanstrom
2015-02-08 3:26 ` Bakul Shah
2015-02-08 2:36 ` Kurt H Maier
2015-02-08 3:18 ` Brian L. Stuart
2015-02-08 10:02 ` Richard Miller
2015-02-08 10:09 ` Richard Miller
2015-02-03 3:52 ` erik quanstrom
2015-02-03 4:41 ` Bakul Shah
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=9dc091ed831c3704ab93c49f93f37cab@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).