public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Sebastian Kloska <kloska@scienion.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM realy sucks on 2.6.x
Date: Mon, 7 Jun 2004 16:48:41 +0200	[thread overview]
Message-ID: <20040607144841.GD1467@elf.ucw.cz> (raw)
In-Reply-To: <40C47B94.6040408@scienion.de>

Hi!

> >Yes, that's pretty much what I meant. ACPI has ~5 people actively
> >working on it, some of them probably full-time. That's a lot of
> >manpower, compared to APM.
> 
> 
>   This becomes a little bit scary. Someone else on this list already
>  mentioned that there is a strong movement towards everything which
>  is at least a desktop/server machine. And on the other hand there are
>  these embedded systems which seem to be attractive for linux to.
> 
>  ACPI seems to be nifty for such things like hardware monitoring and
>  stuff. That makes it interesting for servers etc...
> 
>  Everything in the middle (aka laptops) seems to slowly drop out of the
>  loop. PCMCIA seems to be another ugly example. Anyway ...  I'm not 
>  frightened

HP sells compaq nx5000 notebooks with Linux preloaded. Unfortunately
suspend-to-RAM is not there (IIRC). That's because suspend-to-RAM is
hard to do with ACPI.

PCMCIA... well, that's another obsolete technology. Too bad. 

They are people who care about notebooks, there's just no one that
cares about *old* notebooks any more.
								Pavel
-- 
934a471f20d6580d5aad759bf0d97ddc

  reply	other threads:[~2004-06-07 14:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 21:26 APM realy sucks on 2.6.x Sebastian Kloska
2004-06-04 23:14 ` Keith Duthie
2004-06-05  8:03   ` Sebastian Kloska
2004-06-04 23:54 ` Hugh Dickins
2004-06-05 17:18   ` Sebastian Kloska
2004-06-06  3:29     ` Michael Clark
2004-06-06  4:25       ` Andrew Morton
2004-06-06 13:56         ` Sebastian Kloska
2004-06-07 12:38 ` Pavel Machek
2004-06-07 13:37   ` Sebastian Kloska
2004-06-07 14:05     ` Pavel Machek
2004-06-07 14:28       ` Sebastian Kloska
2004-06-07 14:48         ` Pavel Machek [this message]
2004-06-07 19:53           ` Felipe Alfaro Solana
2004-06-07 21:13             ` Sebastian Kloska
2004-06-08  4:16           ` Clemens Schwaighofer
2004-06-08  7:12             ` Sebastian Kloska
2004-06-08  8:58             ` Pavel Machek
2004-06-08  9:02               ` Clemens Schwaighofer
2004-06-08  9:17                 ` Pavel Machek
2004-06-08  9:50                   ` Clemens Schwaighofer
2004-06-08  9:55                     ` Pavel Machek
2004-06-08 23:59                       ` Clemens Schwaighofer
2004-06-08 17:48               ` Bill Davidsen
2004-06-08 18:59                 ` Daniel Gryniewicz
2004-06-08 20:18                 ` Ian Stirling
2004-06-07 14:42     ` Keith Duthie
2004-06-07 14:44       ` Pavel Machek
2004-06-07 14:47       ` Sebastian Kloska
2004-06-07 14:51         ` Pavel Machek
2004-06-07 15:09           ` Sebastian Kloska
2004-06-07 16:26             ` Pavel Machek
2004-06-07 15:19         ` Keith Duthie
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  8:11 Sebastian Kloska
2004-06-08  9:49 Sau Dan Lee

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=20040607144841.GD1467@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=kloska@scienion.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