From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>
Subject: Re: 2.6.21: longhaul freq-scaling broken
Date: Tue, 01 May 2007 17:53:50 +0200 [thread overview]
Message-ID: <4637628E.2010106@interia.pl> (raw)
In-Reply-To: <6bffcb0e0705010805i62c987ecj4dde5e8365a95d16@mail.gmail.com>
>> > Hi,
>> Hi
>> > the new longhaul driver of 2.6.21 is broken on my Via Eden board.
>> > Frequencies can no longer be switched by whatever governor.
>> > [...]
>> >
>> > I ported the longhaul driver from 2.6.20.7 to 2.6.21, it works fine.
>> Yes. My fault. Bug is known, but it was to late to include patch
>> fixing it in 2.6.21
>> > Yeah, I know there are only a few patches between both, but I would
>> like
>> > to reduce the test cycles to a minimum. Any suggestion where to look
>> > first is welcome therefore, ready-to-apply patches even more...
>> Longhaul ver. 2 support is the reason. First machine that was reported
>> not working is exactly like Your's: Samuel 2 600MHz. Patch reverting
>> changes is queued in cpufreq git. You can find it at
>> http://git.kernel.org/?p=linux/kernel/git/davej/cpufreq.git;a=commitdiff_plain;h=07844252ffd81ec192a62014bada1016c9703765
>>
>
> Should it go to -stable?
If I understood Dave Jones correcly it is work in progress.
> I have this on the list of known regressions already.
Can You send me more details?
> Regards,
> Michal
Regards
Rafał
----------------------------------------------------------------------- Linda jako gospodyni domowa - zobacz!!!
>>> http://link.interia.pl/f1a79
prev parent reply other threads:[~2007-05-01 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 14:16 2.6.21: longhaul freq-scaling broken Jan Kiszka
2007-05-01 14:48 ` Rafał Bilski
[not found] ` <6bffcb0e0705010805i62c987ecj4dde5e8365a95d16@mail.gmail.com>
2007-05-01 15:53 ` Rafał Bilski [this message]
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=4637628E.2010106@interia.pl \
--to=rafalbilski@interia.pl \
--cc=davej@redhat.com \
--cc=jan.kiszka@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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.