linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Centrino support
Date: Sat, 16 Aug 2003 12:58:42 -0700	[thread overview]
Message-ID: <m2d6f5gyrx.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: 1060980793.29086.21.camel@serpentine.internal.keyresearch.com

[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]

>>>>> "Bryan" == Bryan O'Sullivan <bos@serpentine.com>:
 Bryan> On Fri, 2003-08-15 at 13:35, Jan Rychter wrote:
 >> I keep dreaming about the day when I'll be able to have a modern
 >> laptop with a stable Linux kernel. As for now, it has taken me (on
 >> one of my laptops) about 1.5 years to get to a point where 2.4
 >> works, most of my hardware works, and software suspend (pretty much
 >> a requirement for laptops) works. I'm not about to give that up
 >> easily, so I'm not that eager to jump to 2.5/2.6.

 Bryan> Can't say that's been my experience.  I bought a new Thinkpad
 Bryan> X31 the other day, and it's already running 2.6.0-test3.
 Bryan> Suspend works, all's happy.

Lucky you! That's because almost two years (or so) of heavy work by many
people went into this. Also, you're probably lucky with your Thinkpad.

When I bought this laptop (a Sharp Mebius PC-MT1-H5) back in Sept 2001,
there weren't many machines on the market that had only ACPI (and no
APM). And Linux ACPI wasn't in a very sane state back then, not to
mention swsusp. It took almost two years for the software to mature, and
only recently did I get a stable machine that I can work on for a month
without rebooting (suspending/resuming several times a day).

I've just gotten a Centrino-based Toshiba Dynabook SS S7/290LNKW, and
the story continues -- I've already hit at least two ACPI bugs, while
swsusp problems seem to have been ironed out thanks to hard work by
Nigel Cunningham. And of course, the built-in wireless card does not
work. My guess is another 6 months (if not more) until Linux works on
it.

--J.

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-08-17 19:09 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 [this message]
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
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
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=m2d6f5gyrx.fsf@tnuctip.rychter.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).