From: Kevin Hilman <khilman@deeprootsystems.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: "linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: PM branch and cpufreq
Date: Mon, 12 Jan 2009 20:33:57 -0800 [thread overview]
Message-ID: <878wpfn7t6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <D1986163-A086-4798-A1D7-0A5E93984C21@student.utwente.nl> (Koen Kooi's message of "Mon\, 12 Jan 2009 08\:16\:10 +0100")
Koen Kooi <k.kooi@student.utwente.nl> writes:
> Op 11 jan 2009, om 19:53 heeft Koen Kooi het volgende geschreven:
>
>> Hi,
>>
>> I was trying to get cpufreq going on beagleboard
>> (http://cgit.openembedded.net/cgit.cgi?url=openembedded/blob/&id=f56b27781d810dcca0a9946cfd2524c36b7a49c0&path=packages/linux/linux-omap-pm/beagle-cpufreq.diff
>> ) and I ran into a few issues;
>>
>> * pm-prev branch: SD card doesn't initialize, and my rootfs is in SD
>
> SD *does* initialize, but 'rootwait' doesn't work, booting from a
> ubifs volume in nand works and udev automounts my SD card. Cpufreq
> isn't working, so I still need advice on that :)
pm-next isn't supposed to work. ;) It is work in progress. Once it's
ready it will become 'pm'.
Re: SD/MMC problem I see the same problem in linux-omap HEAD where
rootwait doesn't seem to work, so at least the 'rootwait' problem
think is not PM branch related.
Re: CPUfreq on Beagle. I haven't done any testing of CPUfreq on
beagle. AFAICT, the OPP definitions are not being defined for Beagle.
That would explain no availabe operating points.
These are board specific settings. You could start by looking at the
*_rate_table definitions in board-3430sdp.c.
Kevin
next prev parent reply other threads:[~2009-01-13 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 18:53 PM branch and cpufreq Koen Kooi
2009-01-11 18:58 ` Koen Kooi
2009-01-12 7:16 ` Koen Kooi
2009-01-13 4:33 ` Kevin Hilman [this message]
2009-01-13 7:58 ` Koen Kooi
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=878wpfn7t6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.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