search

jefflunt / glint-box

(retired) This was fun - but seriously, try Lakka instead (http://www.lakka.tv/)
MIT License
21 stars 5 forks source link

Should we overclock by default? #38

Open jefflunt opened 11 years ago

jefflunt commented 11 years ago

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware do not void warranties, but I don't know if there is a risk that overclocked Pis will have shorter shelf lives as a result of the extra heat.

brandtdaniels commented 11 years ago

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

jefflunt commented 11 years ago

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels notifications@github.comwrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203.

brandtdaniels commented 11 years ago

It means it won't over clock unless it needs to

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:36 AM, Jeff Lunt notifications@github.com wrote:

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels notifications@github.comwrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203.

— Reply to this email directly or view it on GitHub.

jefflunt commented 11 years ago

Hm, very cool.

So basically we can overclock to 900MHz out of the box without a problem? So long as I'm setting overclocking through the raspi-config then I don't need to worry about damaging the Pi?

Does it sound like I have that correct?

On Mon, Jan 7, 2013 at 3:03 PM, Brandt Daniels notifications@github.comwrote:

It means it won't over clock unless it needs to

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:36 AM, Jeff Lunt notifications@github.com wrote:

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels notifications@github.comwrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub< https://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11971546.

brandtdaniels commented 11 years ago

Raspi-config only writes to /boot/config.txt with recommended setting. If you write to the text file manually the options are endless.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 1:28 PM, Jeff Lunt notifications@github.com wrote:

Hm, very cool.

So basically we can overclock to 900MHz out of the box without a problem? So long as I'm setting overclocking through the raspi-config then I don't need to worry about damaging the Pi?

Does it sound like I have that correct?

On Mon, Jan 7, 2013 at 3:03 PM, Brandt Daniels notifications@github.comwrote:

It means it won't over clock unless it needs to

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:36 AM, Jeff Lunt notifications@github.com wrote:

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels notifications@github.comwrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub< https://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11971546.

— Reply to this email directly or view it on GitHub.

jefflunt commented 11 years ago

Right, I understand that part. I guess what I'm getting at is, is it safe? It used to be that overclocking past a certain point was considered unstable and potentially dangerous to the Pi. What I'm asking is, where is the "unsafe" line at this point (or isn't there one anymore)?

-Jeff

On Mon, Jan 7, 2013 at 5:19 PM, Brandt Daniels notifications@github.comwrote:

Raspi-config only writes to /boot/config.txt with recommended setting. If you write to the text file manually the options are endless.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 1:28 PM, Jeff Lunt notifications@github.com wrote:

Hm, very cool.

So basically we can overclock to 900MHz out of the box without a problem? So long as I'm setting overclocking through the raspi-config then I don't need to worry about damaging the Pi?

Does it sound like I have that correct?

On Mon, Jan 7, 2013 at 3:03 PM, Brandt Daniels notifications@github.comwrote:

It means it won't over clock unless it needs to

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:36 AM, Jeff Lunt notifications@github.com wrote:

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels < notifications@github.com>wrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub<

https://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub< https://github.com/normalocity/glint-nes/issues/38#issuecomment-11971546>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11977138.

brandtdaniels commented 11 years ago

Preselected values below 1000mhz that raspi-config uses would be safe

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 3:32 PM, Jeff Lunt notifications@github.com wrote:

Right, I understand that part. I guess what I'm getting at is, is it safe? It used to be that overclocking past a certain point was considered unstable and potentially dangerous to the Pi. What I'm asking is, where is the "unsafe" line at this point (or isn't there one anymore)?

-Jeff

On Mon, Jan 7, 2013 at 5:19 PM, Brandt Daniels notifications@github.comwrote:

Raspi-config only writes to /boot/config.txt with recommended setting. If you write to the text file manually the options are endless.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 1:28 PM, Jeff Lunt notifications@github.com wrote:

Hm, very cool.

So basically we can overclock to 900MHz out of the box without a problem? So long as I'm setting overclocking through the raspi-config then I don't need to worry about damaging the Pi?

Does it sound like I have that correct?

On Mon, Jan 7, 2013 at 3:03 PM, Brandt Daniels notifications@github.comwrote:

It means it won't over clock unless it needs to

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:36 AM, Jeff Lunt notifications@github.com wrote:

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels < notifications@github.com>wrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt notifications@github.com wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub<

https://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub< https://github.com/normalocity/glint-nes/issues/38#issuecomment-11971546>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11977138.

— Reply to this email directly or view it on GitHub.

jefflunt commented 11 years ago

Great, thanks.

On Mon, Jan 7, 2013 at 6:57 PM, Brandt Daniels notifications@github.comwrote:

Preselected values below 1000mhz that raspi-config uses would be safe

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 3:32 PM, Jeff Lunt notifications@github.com wrote:

Right, I understand that part. I guess what I'm getting at is, is it safe? It used to be that overclocking past a certain point was considered unstable and potentially dangerous to the Pi. What I'm asking is, where is the "unsafe" line at this point (or isn't there one anymore)?

-Jeff

On Mon, Jan 7, 2013 at 5:19 PM, Brandt Daniels notifications@github.comwrote:

Raspi-config only writes to /boot/config.txt with recommended setting. If you write to the text file manually the options are endless.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 1:28 PM, Jeff Lunt notifications@github.com wrote:

Hm, very cool.

So basically we can overclock to 900MHz out of the box without a problem? So long as I'm setting overclocking through the raspi-config then I don't need to worry about damaging the Pi?

Does it sound like I have that correct?

On Mon, Jan 7, 2013 at 3:03 PM, Brandt Daniels < notifications@github.com>wrote:

It means it won't over clock unless it needs to

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:36 AM, Jeff Lunt notifications@github.com wrote:

Which means that it will drop down to lower performance if the heat gets too high?

On Mon, Jan 7, 2013 at 1:36 PM, Brandt Daniels < notifications@github.com>wrote:

It uses a governor by default unless you specify not to use it.

-Brandt

Sent from my iPhone

On Jan 7, 2013, at 11:33 AM, Jeff Lunt < notifications@github.com> wrote:

The default setting for glint-nes is 800MHz.

The latest firmware includes the option to overclock up to 1GHz, though there is reportedly a risk of SD card corruption.

There is, apparently, no such warning for going to 900MHz, and overclocking it to this point does seem to resolve the minor glitch issues in most games by giving the Pi just a little extra head room.

As far as I know the built-in overclock settings that come with the latest firmware does not void warranties, but I don't know if there is a risk that overclocked Pis will shorten their shelf life.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub<

https://github.com/normalocity/glint-nes/issues/38#issuecomment-11967203>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub<

https://github.com/normalocity/glint-nes/issues/38#issuecomment-11971546>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub< https://github.com/normalocity/glint-nes/issues/38#issuecomment-11977138>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/normalocity/glint-nes/issues/38#issuecomment-11979805.

jefflunt commented 11 years ago

Adrian mentioned that speed issues are largely caused by sound driver issues, and that the new binaries he's building may also resolve the issue.

brandtdaniels commented 11 years ago

http://elinux.org/RPiconfig#Tested_values