public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM realy sucks on 2.6.x
Date: Tue, 8 Jun 2004 11:17:09 +0200	[thread overview]
Message-ID: <20040608091709.GC2569@elf.ucw.cz> (raw)
In-Reply-To: <40C580BE.1030802@tequila.co.jp>

Hi!

> |>| PCMCIA... well, that's another obsolete technology. Too bad.
> |>
> |>PCMCIA is obsolete? Did I miss something, or was this a joke?
> |
> |
> | Obsoleted by cardbus, I believe. (cardbus cards look like PCMCIA
> | cards, but electrical protocol is different) Plus, as someone else
> | noted, stuff moves into mainboard. USB also replacs part of what
> | PCMCIA was for.
> 
> hmm, I didn't know that there is a change from PCMCIA to cardbus.
> Thought still there are lot of pcmcia stuff around. wlan cards, eg my
> dial up card (CF card into a PCMCIA adapter). Well I wouldn't abandon
> PCMCIA so fast. At least the linux kernel is know for beeing able to use
> very old hardware in a very good way ...

Yes, pcmcia still survives in form of compactflash, mostly used by
low-powered handhelds etc. That's where ISA survives too.

I agree that supporting PCMCIA is usefull, and that linux should run
on old hardware; but you can see that PCMCIA and APM is in "old
hardware" category, along with ISA, Pentium I CPUs and serial ports.

Linux still tries to support 386 cpus, and its right. However its not
same level of support as modern hardware.
								Pavel 
-- 
934a471f20d6580d5aad759bf0d97ddc

  reply	other threads:[~2004-06-08  9:34 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
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 [this message]
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=20040608091709.GC2569@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=cs@tequila.co.jp \
    --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