From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeffrey Baker <jwbaker@acm.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: centrino
Date: 03 May 2003 16:21:58 +0100 [thread overview]
Message-ID: <1051975317.24563.12.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030502183222.GA30189@heat>
> Power management didn't work at all because ACPI is a sick
> joke. In 2.4 ACPI does nothing, and in 2.5.68 it can put
> the machine to sleep, but not wake it up. APM could almost
> wake the system from sleep, but then it crashed immediately.
> ACPI incorrectly reports the state of the system fans, the
> battery, the battery charger, and the temperature sensor.
> In other words, no part of it functions correctly . This is
> either a problem with Centrino chipset in general or Acer
> BIOS programming in particular.
For some people centrino seems to work a little better so it may
be BIOS bugs too. The usual "buy something 6 months old" rule applies
to BIOS code as well as anything else
> CPU frequency scaling didn't work in either kernel but there
> seem to be rumbles of reverse engineering going on with
> that.
Intel are still being a pain about this. Quite why they think its
a secret is beyond me. Fortunately every other CPU vendor is being a
lot more positive.
> The wireless doesn't work in any kernel, and Intel have
> stated specifically on their web site that they have no
> plans for any future Linux driver for that device.
There are awkward issues there certainly.
> The Centrino package is altogether hostile to Linux.
Time may change that. The ATI/ALi chipset AMD laptops like the Compaq
z9xx were really Linux hostile. Now with the right stuff in place and
some things fixed (some working around their bugs, some fixing ours)
they work really well.
Centrino ultimately is a help - the laptop chipset space is
consolidating and there are less and less variations appearing. That
helps us because there is less to support. Its the same as with X and
IDE and other things nowdays - we get a lot less deeply weird hardware
to fight.
next prev parent reply other threads:[~2003-05-03 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 18:32 centrino Jeffrey Baker
2003-05-03 15:21 ` Alan Cox [this message]
2003-05-03 20:29 ` centrino Anders Karlsson
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 20:05 centrino Grover, Andrew
2003-05-02 4:53 Centrino Anders Karlsson
2003-05-02 7:30 ` Centrino Martin List-Petersen
2003-05-02 8:53 ` Centrino Anders Karlsson
[not found] ` <20030502085720.GA629@localhost.localdomain>
2003-05-02 15:31 ` Centrino Anders Karlsson
2003-05-02 15:46 ` Centrino Balram Adlakha
2003-05-02 16:03 ` Centrino Anders Karlsson
2003-05-02 22:09 ` Centrino dean gaudet
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=1051975317.24563.12.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jwbaker@acm.org \
--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
all inboxes | Powered by JetHome®