From: Adam Belay <abelay@novell.com>
To: felix-linuxkernel@fefe.de
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, cpufreq@ZenII.linux.org.uk
Subject: Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10
Date: Mon, 21 Mar 2005 20:20:55 -0500 [thread overview]
Message-ID: <1111454454.6633.5.camel@linux.site> (raw)
In-Reply-To: <20050321163225.4af1c169.akpm@osdl.org>
On Mon, 2005-03-21 at 19:32, Andrew Morton wrote:
> Adam Belay <abelay@novell.com> wrote:
> >
> > On Fri, 2005-03-11 at 17:35 -0800, Andrew Morton wrote:
> > > Felix von Leitner <felix-linuxkernel@fefe.de> wrote:
> > > >
> > > > Finally Centrino SpeedStep.
> > > > I have a "Intel(R) Pentium(R) M processor 1.80GHz" in my notebook.
> > > > Linux does not support it. This architecture has been out there for
> > > > months now, and there even was a patch to support it posted here a in
> > > > October last year or so. Linux still does not include it. Until
> > > > 2.6.11-rc4-bk8 or so, the old patched file from back then still worked.
> > > > Now it doesn't. Because some interface changed. Now what? Using a
> > > > Centrino notebook without CPU throttling is completely out of the
> > > > question. Linux might as well not boot on it at all.
> > >
> > > Could you please dig out the old patch, send it?
> >
> > Why not use ACPI for CPU scaling?
> >
>
> Felix, did you try this?
>
ACPI is the preferred (and only standardized) method of controlling cpu
throttling on x86 systems.
Also, as I said earlier, I wanted to see an lspci for the usb issues.
Thanks,
Adam
next prev parent reply other threads:[~2005-03-22 1:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 20:21 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Felix von Leitner
2005-03-12 1:32 ` Andrew Morton
2005-03-13 21:30 ` Felix von Leitner
2005-03-12 1:33 ` Andrew Morton
2005-03-22 0:33 ` Andrew Morton
2005-03-22 2:18 ` Johannes Stezenbach
2005-03-22 16:22 ` Johannes Stezenbach
2005-03-24 11:59 ` [PATCH] [IPV6] Fix address/interface handling according to the scoping architecture (is Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10) YOSHIFUJI Hideaki / 吉藤英明
2005-04-25 19:57 ` IPv6 has trouble assigning an interface Felix von Leitner
2005-04-25 21:00 ` Pekka Savola
2005-04-26 6:10 ` Felix von Leitner
2005-04-27 22:57 ` Kyle Moffett
2005-04-27 23:31 ` David Stevens
2005-03-12 1:35 ` 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Andrew Morton
2005-03-12 3:54 ` Adam Belay
2005-03-22 0:32 ` Andrew Morton
2005-03-22 1:20 ` Adam Belay [this message]
2005-03-22 22:29 ` Felix von Leitner
2005-03-24 23:33 ` Jeremy Fitzhardinge
2005-03-25 0:17 ` Felix von Leitner
2005-03-25 13:37 ` Bruno Ducrot
2005-03-13 21:31 ` Felix von Leitner
2005-03-12 3:51 ` Adam Belay
[not found] <3GZyA-16B-17@gated-at.bofh.it>
2005-03-12 5:06 ` Robert Hancock
2005-03-12 5:19 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 10:24 Stefan Rompf
2005-03-12 20:34 ` Greg KH
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=1111454454.6633.5.camel@linux.site \
--to=abelay@novell.com \
--cc=akpm@osdl.org \
--cc=cpufreq@ZenII.linux.org.uk \
--cc=felix-linuxkernel@fefe.de \
--cc=linux-kernel@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