From: Brandon Stewart <rbrandonstewart@yahoo.com>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Jan Rychter <jan@rychter.com>, linux-kernel@vger.kernel.org
Subject: Re: Centrino support
Date: Fri, 15 Aug 2003 16:46:19 -0400 [thread overview]
Message-ID: <3F3D469B.2020507@yahoo.com> (raw)
In-Reply-To: <1060972810.29086.8.camel@serpentine.internal.keyresearch.com>
I thought that this line of argument was due to FCC regulations. That
is, software settings would allow the hardware to violate frequency or
strength-of-signal limitations set by government regulations. This is
only from memory, so feel free to correct.
-Brandon
Bryan O'Sullivan wrote:
>On Fri, 2003-08-15 at 11:13, Jan Rychter wrote:
>
>
>>Well, that was almost 5 months ago. So I figured I'd ask if there's any
>>progress -- so far the built-in wireless in my notebook still doesn't
>>work with Linux and the machine is monstrously power-hungry because
>>Linux doesn't scale the CPU frequency.
>>
>>
>
>Intel shows no inclination to release Centrino wireless drivers for
>Linux. There have been vague insinuations that this is due to excessive
>software controllability, but no public explanations have been given,
>beyond "we're not doing it at this moment".
>
>If you want built-in wireless in the nearish term, you'll have to get a
>supported MiniPCI card and replace your Centrino card.
>
>As far as CPU is concerned, if you're using recent 2.5 or 2.6 kernels,
>there's Pentium M support in cpufreq. Jeremy Fitzhardinge has written a
>userspace daemon that varies the Pentium M CPU frequency in response to
>load.
>
next prev parent reply other threads:[~2003-08-15 20:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 18:13 Centrino support Jan Rychter
2003-08-15 18:29 ` Dave Jones
2003-08-15 18:33 ` Martin List-Petersen
2003-08-15 18:40 ` Bryan O'Sullivan
2003-08-15 20:24 ` Christian Axelsson
2003-08-15 20:35 ` Randy.Dunlap
2003-08-15 20:55 ` Bryan O'Sullivan
2003-08-15 21:22 ` Martin List-Petersen
2003-08-16 22:32 ` insecure
2003-08-17 4:16 ` Jamie Lokier
2003-08-15 20:35 ` Jan Rychter
2003-08-15 20:53 ` Bryan O'Sullivan
2003-08-16 19:58 ` Jan Rychter
2003-08-16 14:23 ` Dave Jones
2003-08-16 15:12 ` Alan Cox
2003-08-18 23:52 ` Rob Landley
2003-08-15 20:46 ` Brandon Stewart [this message]
2003-08-16 10:34 ` Stephan von Krawczynski
2003-08-16 19:58 ` Jan Rychter
2003-08-17 19:17 ` Jamie Lokier
2003-08-17 19:24 ` Alan Cox
2003-08-16 11:27 ` Tomas Szepe
2003-08-18 8:31 ` Helge Hafting
2003-08-19 21:15 ` James H. Cloos Jr.
2003-08-19 23:55 ` Jamie Lokier
2003-08-21 19:33 ` Micha Feigin
2003-08-17 20:07 ` Jussi Laako
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 20:32 Jean Tourrilhes
2003-08-15 22:36 Ricardo Galli
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=3F3D469B.2020507@yahoo.com \
--to=rbrandonstewart@yahoo.com \
--cc=bos@serpentine.com \
--cc=jan@rychter.com \
--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