All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: hawkboard at 456 Mhz?
Date: Sun, 21 Mar 2010 15:42:19 +0100	[thread overview]
Message-ID: <ho5b8b$oao$1@dough.gmane.org> (raw)
In-Reply-To: <ac9c93b11003210557u1fcbcc21jb0dafb9fa16ccc96@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21-03-10 13:57, Frans Meulenbroeks wrote:
> Hi,
> 
> In the openembedded repository I saw the following patch:
> http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-davinci/da850_omapl138_opp456mhz.patch
> This seems to suggest that it is possible to run the hawkboard at 456
> Mhz (and yeah: I know it is out of spec and out of warranty, but for
> an experiment it would be quite helpful for me).
> I've build the kernel with openembedded, the patch is applied,
> CONF_CPU_FREQ is defined, but the control hook in /sys is not there.
> I've also tried tweaking the file with the settings (ds850.c) but to no avail.
> 
> Anyone a suggestion on how to get this done?

You need a newer kernel that doesn't rely on the TPS part for cpufreq
(hawkboard lacks a PMIC, the evm uses the TPS). You can build from the
ti/staging[1] branch to get such a kernel.

Or wait a week for that branch to get merge, internal testing is finally
wrapping up.

[1] http://gitorious.org/angstrom/openembedded/commits/ti/staging
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLpjBLMkyGM64RGpERAs/NAJ9OK1jN2jxYYj12gWKu2vxCrNsCMACfelgj
+b0keOpVlJBB+WYeL4fJlyg=
=5LGb
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-03-21 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 12:57 hawkboard at 456 Mhz? Frans Meulenbroeks
2010-03-21 14:42 ` Koen Kooi [this message]
2010-03-21 19:38   ` Frans Meulenbroeks
2010-03-22  8:35     ` Koen Kooi
2010-03-22  9:29       ` Frans Meulenbroeks
2010-03-22  9:32         ` Frans Meulenbroeks

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='ho5b8b$oao$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.